[
https://issues.apache.org/jira/browse/SOLR-8737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169419#comment-15169419
]
ASF subversion and git services commented on SOLR-8737:
-------------------------------------------------------
Commit c7214a2ba5f96492e5c4cd6a558734217afe5089 in lucene-solr's branch
refs/heads/branch_5_5 from [~cpoerschke]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=c7214a2 ]
Merge 5.5.1 changes sections from SOLR-8737 and SOLR-8734 tickets.
> Managed synonym lists do not include the original term in the expand
> --------------------------------------------------------------------
>
> Key: SOLR-8737
> URL: https://issues.apache.org/jira/browse/SOLR-8737
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis
> Affects Versions: 5.5
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Fix For: 5.5.1
>
> Attachments: SOLR-8737.patch
>
>
> Spinoff from discussion in solr-user list
> http://find.searchhub.org/document/8dfce8a277de0f2a
> The managed synonyms filter does not behave the same way as the original
> synonym filter when a list is added. The original synonyms filter with
> default {{expand=true}} produces the following map when parsing a line:
> Input:
> {noformat}
> a, b, c
> {noformat}
> Becomes:
> {noformat}
> a => a, b, c
> b => a, b, c
> c => a, b, c
> {noformat}
> But the managed filter excludes the original term in the mapping, so an input
> {{\["a", "b", "c"\]}} becomes:
> {noformat}
> a => b, c
> b => a, c
> c => a, b
> {noformat}
> This can also be seen in {{TestManagedSynonymFilterFactory.java}} where it is
> tested explicitly, while the tests for the file based synonymfilter expect an
> all-way expand including the original term.
> This causes a query for "a" to *not* match documents with the term "a", but
> only those with term "b" or "c".
> The offending line in {{ManagedSynonymFilterFactory}} is this
> {code}
> 188: treeTerms.remove(origTerm);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
