See also SOLR-3390. Some cases have been addressed. Eg, if you match domain name system -> dns, then dns will have correct offsets spanning the full phrase "domain name system" in the input. (However: QueryParser won't work because a query for "domain name system" is pre-split on whitespace so the synonym never matches).
But for the reverse case, which I call "expanding" (ie, match dns -> domain name system), the results are not "correct" (or at least different from the previous SynFilter impl): the three tokens are overlapped onto subsequent tokens, resulting in highlighting the wrong tokens. However, QueryParser will work "correctly" for the query "domain name system"... But, I'd like to ask: why do apps want to "expand" (replace a match with more than one input token, ie the dns -> domain name system case)? Is it ONLY because of QueryParser's limitation (that it pre-splits on whitespace)? Or are there other realistic use cases? Mike McCandless http://blog.mikemccandless.com On Tue, Aug 14, 2012 at 11:53 AM, Marc Sturlese <marc.sturl...@gmail.com> wrote: > Has someone noticed this problem and solved it somehow? (without using > LUCENE_33 in the solrconfig.xml) > https://issues.apache.org/jira/browse/LUCENE-3668 > > Thanks in advance > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/offsets-issues-with-multiword-synonyms-since-LUCENE-33-tp4001195.html > Sent from the Solr - User mailing list archive at Nabble.com.
