lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-8737) Managed synonym lists do not include the original term in the expand
Date Thu, 25 Feb 2016 14:00:20 GMT

    [ https://issues.apache.org/jira/browse/SOLR-8737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167217#comment-15167217
] 

Jan Høydahl commented on SOLR-8737:
-----------------------------------

Hints from mailing list that people have had issues with current behavior:
http://find.searchhub.org/document/bd969ff7efacf642
http://find.searchhub.org/document/8dfce8a277de0f2a

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message