Hi Elasticsearch, still waiting to see if this is a known issue, possibly that's resolved in a future release, or if this is something I did? I'd appreciate knowing, at least, if anyone can help. Thanks much.
On Friday, March 14, 2014 5:29:10 PM UTC-4, Jon-Paul Lussier wrote: > > Hey Elasticsearch, hopefully someone can at least explain if this is > intentional and how it happens(I have had other fragment highlighting > issues not unlike this) > > The problem seems simple, I have a 64 character string that I generate 62 > tokens for. Whenever I search for the entire string, I end up getting the > highlight applied to the 50th fragment instead of the one that actually > most nearly matches my search query. > > Also confusing is if I try a very similar search, trying to use an exact > match on the SHA1 or MD5 attributes -- highlighting works like I'd expect > it to. > > > Please see the gist here: > https://gist.github.com/jonpaul/d4a9aa7f9c8741933cf5 > > > Currently I'm using 1.0.0-BETA2 so this *may* be a fixed bug, sorry if > that's the case, I couldn't find anything that matches my problem per se. > > Thanks very much in advance for help anyone can provide! > > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e2a9657d-e5df-4e0c-b1dc-78b13457827c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
