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

Timothy Potter commented on SOLR-8737:
--------------------------------------

Thanks for fixing [~janhoy]. As a work-around until this is released, users can 
send in the mappings as a map, i.e.

{code}
curl -v -X PUT \
  -H 'Content-type:application/json' \
  --data-binary '{ "a": ["a","b","c"], "b": ["a","b","c"], "c":["a","b","c"]}' \
  'http://localhost:8983/solr/techproducts/schema/analysis/synonyms/english'
{code}

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

Reply via email to