[
https://issues.apache.org/jira/browse/SOLR-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-4153.
----------------------------
Resolution: Not A Problem
This is not a problem in edismax, this is an issue of how your field analysis
is configured.
Please look at the example schema.xml and note in particular the discussion of
autoGeneratePhraseQueries. (and it's usage in "text_en_splitting")
> eDismax: Misinterpretation of hyphens
> -------------------------------------
>
> Key: SOLR-4153
> URL: https://issues.apache.org/jira/browse/SOLR-4153
> Project: Solr
> Issue Type: Improvement
> Components: query parsers
> Affects Versions: 4.0
> Reporter: Leonhard Maylein
>
> The eDismax parser treats hyphens as OR operator:
> &q:
> british history 1815-1914
> &qf:
> ti sw
> Parsed as:
> (+((DisjunctionMaxQuery((sw:british | ti:british))
> DisjunctionMaxQuery((sw:history | ti:history)) DisjunctionMaxQuery(((sw:1815
> sw:1914) | (ti:1815 ti:1914))))~3))/no_coord
> What is the reason for this behavior? Wouldn't it be better
> to treat 'term1-term2' as a PhraseQuery "term1 term2" (as the
> WordDelimiterFilter does)?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
