Steven Bedrick

Hello! I have just run into this exact problem, and before filing my own issue thought to check the existing ones. I see that the `utf` branch is pretty far...

Huh - on closer inspection, it looks like the [line in question](https://github.com/lhncbc/metamaplite/blob/8aae39319a4a4b40a013180bf6cde09b172c78a8/src/main/java/irutils/MappedMultiKeyIndex.java#L435) (which is 435, not 434, apologies) was actually added as part of commit da51d16e8a5a1869c3f021492719bcd149042b2e, which was about adding...

So irutils.MappedMultiKeyIndex does use the UTF-8 byte representation for the lookup key, which works for lookup keys that involve non-ASCII characters, **but** this leads to the binary search implementation breaking...

Here might be another piece of the puzzle - I'm revisiting the code that controls how the various postings/term dictionary/etc. files are generated, and if I am understanding things correctly,...

I ran into similar problems, and eventually traced it back to the same place that @pdyakov did... my _guess_ is that this test might be here to prevent an Advertiser...

That certainly does appear to be the explanation, thanks, @qiulang!

I would also vote for this; being able to run against a Bedrock back-end would be very helpful, even for a limited subset of models.

So I just ran into this issue and so spent a few minutes digging around in the code to figure out what was going on... another thought besides doing string-to-string...

I'm also seeing what I believe is the same behavior, on the same configuration (homebrew-installed, etc.).