# \[BUG\] Re: Highlighting not working with synonym filter **URL:** \ **Category:** Elasticsearch\ **Created:** [October 24, 2013, 5:23pm UTC](https://discuss.elastic.co/t/bug-re-highlighting-not-working-with-synonym-filter/14094 "2013-10-24T17:23:54Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![vineeth\_mohan\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vineeth_mohan_2/32/747_2.png) [@vineeth\_mohan\_2](https://discuss.elastic.co/u/vineeth_mohan_2)\ **Post date:** [October 24, 2013, 5:23pm UTC](https://discuss.elastic.co/t/bug-re-highlighting-not-working-with-synonym-filter/14094/1 "2013-10-24T17:23:54Z")
Hi , I strongly feel this as a bug. Should i open a bug in the rep ? Thanks Vineeth On Wed, Oct 23, 2013 at 6:36 PM, vineeth mohan [vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com)wrote: > Steps to reproduce - > > Index creation script > > 1. Download [http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz](http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz) , > extract wn\_s.pl and place it in config directory. > 2. Create an index using this script - > [gist:7118283 · GitHub](https://gist.github.com/Vineeth-Mohan/7118283) > 3. ./AboveScript localhost > 4. Index a feed > curl -XPOST '[http://localhost:9200/events/news](http://localhost:9200/events/news)' -d ' { "Events" : { > "Event" : "large forest in large" } }' > 5. Execute this search - [gist:7118312 · GitHub](https://gist.github.com/Vineeth-Mohan/7118312) > 6. Output obtained - [gist:7118329 · GitHub](https://gist.github.com/Vineeth-Mohan/7118329) > > Observation - Received "large forest in > large" rather than "large forest in > large" for searching big ( big is present in the synonym > file) > > Thanks > Vineeth -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [October 25, 2013, 1:32pm UTC](https://discuss.elastic.co/t/bug-re-highlighting-not-working-with-synonym-filter/14094/2 "2013-10-25T13:32:43Z")
Just making sure I understand this: you are correctly seeing highlights of synonyms but incorrectly seeing highlights on the word after the synonym? You never searched the word "forest" but it is highlighted any way, correct? Before you file it I'd try searching for "forest" with an term filter on just that "large forest in large" document's id to see what it highlights. It ought to just highlight forest. If it doesn't then there is either a problem with the wordnet file or how it is parsed. Nik On Thu, Oct 24, 2013 at 1:23 PM, vineeth mohan [vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com)wrote: > Hi , I strongly feel this as a bug. > Should i open a bug in the rep ? > > Thanks > Vineeth > > On Wed, Oct 23, 2013 at 6:36 PM, vineeth mohan [vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com)wrote: > > > Steps to reproduce - > > > > Index creation script > > > > 1. Download [http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz](http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz) , > > extract wn\_s.pl and place it in config directory. > > 2. Create an index using this script - > > [gist:7118283 · GitHub](https://gist.github.com/Vineeth-Mohan/7118283) > > 3. ./AboveScript localhost > > 4. Index a feed > > curl -XPOST '[http://localhost:9200/events/news](http://localhost:9200/events/news)' -d ' { "Events" : { > > "Event" : "large forest in large" } }' > > 5. Execute this search - [gist:7118312 · GitHub](https://gist.github.com/Vineeth-Mohan/7118312) > > 6. Output obtained - [gist:7118329 · GitHub](https://gist.github.com/Vineeth-Mohan/7118329) > > > > Observation - Received "large forest in > > large" rather than "large forest in > > large" for searching big ( big is present in the synonym > > file) > > > > Thanks > > Vineeth > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![vineeth\_mohan\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vineeth_mohan_2/32/747_2.png) [@vineeth\_mohan\_2](https://discuss.elastic.co/u/vineeth_mohan_2)\ **Post date:** [October 26, 2013, 5:19am UTC](https://discuss.elastic.co/t/bug-re-highlighting-not-working-with-synonym-filter/14094/3 "2013-10-26T05:19:37Z")
Hello Nikolas , Searching forest , i am getting the below highlight - - large forest in large And for searching big or large - large forest in large - So conclusion is that on matching a term which don't have a synonym , things work fine But while doing it on a term with synonym , every indexed term is getting highlighting. Few more example - Text - the lake was frozen and high , all my team was at their best. Lets do the best then Search word - lake Result - the lake was frozen and high , all my team was at their best. Lets do the best then Search word - high Result - the lake was frozen and high , all my team was at their best. Lets do the best then Question - How did the term "all" , "my" and "best" got highlighted ? Conclusion - Seems every indexed term is not getting highlighted. But there is no pattern in which terms are highlighted. May be all terms having synonym in the text are highlighted !!! Search word - my Result - the lake was frozen and high , all my team was at their best. Lets do the best then Conclusion - Above conclusion is wrong. If all terms with synonyms were highlighted on any synonym match , it should have happened for my also. Also i don't find any issue with analyser or the wordnet. You can see the analyser output for the text "large forest" here - > As far as i can see , all the tokens are correctly identified and placed. I feel this is a bug with highlighter. Conclusion - I am not finding a pattern to this bug. Can i go ahead and file an issue ? Thanks Vineeth On Fri, Oct 25, 2013 at 7:02 PM, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > Just making sure I understand this: you are correctly seeing highlights of > synonyms but incorrectly seeing highlights on the word after the synonym? > You never searched the word "forest" but it is highlighted any way, correct? > > Before you file it I'd try searching for "forest" with an term filter on > just that "large forest in large" document's id to see what it highlights. > It ought to just highlight forest. If it doesn't then there is either a > problem with the wordnet file or how it is parsed. > > Nik > > On Thu, Oct 24, 2013 at 1:23 PM, vineeth mohan [vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com)wrote: > > > Hi , I strongly feel this as a bug. > > Should i open a bug in the rep ? > > > > Thanks > > Vineeth > > > > On Wed, Oct 23, 2013 at 6:36 PM, vineeth mohan \<[vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com) > > > > > wrote: > > > > > Steps to reproduce - > > > > > > Index creation script > > > > > > 1. Download [http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz](http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz) , > > > extract wn\_s.pl and place it in config directory. > > > 2. Create an index using this script - > > > [gist:7118283 · GitHub](https://gist.github.com/Vineeth-Mohan/7118283) > > > 3. ./AboveScript localhost > > > 4. Index a feed > > > curl -XPOST '[http://localhost:9200/events/news](http://localhost:9200/events/news)' -d ' { "Events" : { > > > "Event" : "large forest in large" } }' > > > 5. Execute this search - > > > [gist:7118312 · GitHub](https://gist.github.com/Vineeth-Mohan/7118312) > > > 6. Output obtained - [gist:7118329 · GitHub](https://gist.github.com/Vineeth-Mohan/7118329) > > > > > > Observation - Received "large forest in > > > large" rather than "large forest in > > > large" for searching big ( big is present in the synonym > > > file) > > > > > > Thanks > > > Vineeth > > > > -- > > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [October 26, 2013, 12:46pm UTC](https://discuss.elastic.co/t/bug-re-highlighting-not-working-with-synonym-filter/14094/4 "2013-10-26T12:46:37Z")
If file it with that much information, yes. Sent from my iPhone > On Oct 26, 2013, at 1:19 AM, vineeth mohan [vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com) wrote: > > Hello Nikolas , > > Searching forest , i am getting the below highlight - > large forest in large > > And for searching big or large > large forest in large > > So conclusion is that on matching a term which don't have a synonym , things work fine > But while doing it on a term with synonym , every indexed term is getting highlighting. > > Few more example - > Text - the lake was frozen and high , all my team was at their best. Lets do the best then > > Search word - lake > Result - the lake was frozen and high , all my team was at their best. Lets do the best then > > Search word - high > Result - the lake was frozen and high , all my team was at their best. Lets do the best then > Question - How did the term "all" , "my" and "best" got highlighted ? > Conclusion - Seems every indexed term is not getting highlighted. But there is no pattern in which terms are highlighted. May be all terms having synonym in the text are highlighted !!! > > Search word - my > Result - the lake was frozen and high , all my team was at their best. Lets do the best then > Conclusion - Above conclusion is wrong. If all terms with synonyms were highlighted on any synonym match , it should have happened for my also. > > Also i don't find any issue with analyser or the wordnet. You can see the analyser output for the text "large forest" here - [gist:7165559 · GitHub](https://gist.github.com/Vineeth-Mohan/7165559) > > As far as i can see , all the tokens are correctly identified and placed. I feel this is a bug with highlighter. > > Conclusion - I am not finding a pattern to this bug. Can i go ahead and file an issue ? > > Thanks > Vineeth > > > On Fri, Oct 25, 2013 at 7:02 PM, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > > Just making sure I understand this: you are correctly seeing highlights of synonyms but incorrectly seeing highlights on the word after the synonym? You never searched the word "forest" but it is highlighted any way, correct? > > > > Before you file it I'd try searching for "forest" with an term filter on just that "large forest in large" document's id to see what it highlights. It ought to just highlight forest. If it doesn't then there is either a problem with the wordnet file or how it is parsed. > > > > Nik > > > > > On Thu, Oct 24, 2013 at 1:23 PM, vineeth mohan [vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com) wrote: > > > Hi , I strongly feel this as a bug. > > > Should i open a bug in the rep ? > > > > > > Thanks > > > Vineeth > > > > > > > On Wed, Oct 23, 2013 at 6:36 PM, vineeth mohan [vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com) wrote: > > > > > > > > Steps to reproduce - > > > > > > > > Index creation script > > > > > > > > Download [http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz](http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz) , extract wn\_s.pl and place it in config directory. > > > > Create an index using this script - [gist:7118283 · GitHub](https://gist.github.com/Vineeth-Mohan/7118283) > > > > ./AboveScript localhost > > > > Index a feed > > > > curl -XPOST '[http://localhost:9200/events/news](http://localhost:9200/events/news)' -d ' { "Events" : { "Event" : "large forest in large" } }' > > > > Execute this search - [gist:7118312 · GitHub](https://gist.github.com/Vineeth-Mohan/7118312) > > > > Output obtained - [gist:7118329 · GitHub](https://gist.github.com/Vineeth-Mohan/7118329) > > > > Observation - Received "large forest in large" rather than "large forest in large" for searching big ( big is present in the synonym file) > > > > > > > > Thanks > > > > Vineeth > > > > > > -- > > > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![vineeth\_mohan\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vineeth_mohan_2/32/747_2.png) [@vineeth\_mohan\_2](https://discuss.elastic.co/u/vineeth_mohan_2)\ **Post date:** [October 26, 2013, 1:12pm UTC](https://discuss.elastic.co/t/bug-re-highlighting-not-working-with-synonym-filter/14094/5 "2013-10-26T13:12:56Z")
Filed a bug - [Highlighting working weirdly with synonym filter · Issue #3982 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/3982) On Sat, Oct 26, 2013 at 6:16 PM, Nik Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > If file it with that much information, yes. > > Sent from my iPhone > > On Oct 26, 2013, at 1:19 AM, vineeth mohan [vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com) > wrote: > > Hello Nikolas , > > Searching forest , i am getting the below highlight - > > - large forest in large > > And for searching big or large > > - large forest in large > - > > So conclusion is that on matching a term which don't have a synonym , > things work fine > But while doing it on a term with synonym , every indexed term is getting > highlighting. > > Few more example - > Text - the lake was frozen and high , all my team was at their best. Lets > do the best then > > Search word - lake > Result - the lake was frozen and high , all my team was at > their best. Lets do the best then > > Search word - high > Result - the lake was frozen and high , all > my team was at their best. Lets do the best then > Question - How did the term "all" , "my" and "best" got highlighted ? > Conclusion - Seems every indexed term is not getting highlighted. But > there is no pattern in which terms are highlighted. May be all terms having > synonym in the text are highlighted !!! > > Search word - my > Result - the lake was frozen and high , all my team was at > their best. Lets do the best then > Conclusion - Above conclusion is wrong. If all terms with synonyms were > highlighted on any synonym match , it should have happened for my also. > > Also i don't find any issue with analyser or the wordnet. You can see the > analyser output for the text "large forest" here - > [gist:7165559 · GitHub](https://gist.github.com/Vineeth-Mohan/7165559) > > As far as i can see , all the tokens are correctly identified and placed. > I feel this is a bug with highlighter. > > Conclusion - I am not finding a pattern to this bug. Can i go ahead and > file an issue ? > > Thanks > Vineeth > > On Fri, Oct 25, 2013 at 7:02 PM, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com)wrote: > > > Just making sure I understand this: you are correctly seeing highlights > > of synonyms but incorrectly seeing highlights on the word after the > > synonym? You never searched the word "forest" but it is highlighted any > > way, correct? > > > > Before you file it I'd try searching for "forest" with an term filter on > > just that "large forest in large" document's id to see what it highlights. > > It ought to just highlight forest. If it doesn't then there is either a > > problem with the wordnet file or how it is parsed. > > > > Nik > > > > On Thu, Oct 24, 2013 at 1:23 PM, vineeth mohan \<[vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com) > > > > > wrote: > > > > > Hi , I strongly feel this as a bug. > > > Should i open a bug in the rep ? > > > > > > Thanks > > > Vineeth > > > > > > On Wed, Oct 23, 2013 at 6:36 PM, vineeth mohan \< > > > [vm.vineethmohan@gmail.com](mailto:vm.vineethmohan@gmail.com)\> wrote: > > > > > > > Steps to reproduce - > > > > > > > > Index creation script > > > > > > > > 1. Download [http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz](http://wordnetcode.princeton.edu/3.0/WNprolog-3.0.tar.gz) > > > > , extract wn\_s.pl and place it in config directory. > > > > 2. Create an index using this script - > > > > [gist:7118283 · GitHub](https://gist.github.com/Vineeth-Mohan/7118283) > > > > 3. ./AboveScript localhost > > > > 4. Index a feed > > > > curl -XPOST '[http://localhost:9200/events/news](http://localhost:9200/events/news)' -d ' { "Events" : > > > > { "Event" : "large forest in large" } }' > > > > 5. Execute this search - > > > > [gist:7118312 · GitHub](https://gist.github.com/Vineeth-Mohan/7118312) > > > > 6. Output obtained - [gist:7118329 · GitHub](https://gist.github.com/Vineeth-Mohan/7118329) > > > > > > > > Observation - Received "large forest in > > > > large" rather than "large forest in > > > > large" for searching big ( big is present in the synonym > > > > file) > > > > > > > > Thanks > > > > Vineeth > > > > > > -- > > > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:10am UTC](https://discuss.elastic.co/t/bug-re-highlighting-not-working-with-synonym-filter/14094/6 "2017-07-06T02:10:29Z")