[
https://issues.apache.org/jira/browse/SOLR-2988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672492#comment-13672492
]
Erick Erickson commented on SOLR-2988:
--------------------------------------
As far as I know, just a lack of manpower. Which really translates as nobody
who really wants to dive into the code has had a compelling reason to fix it.
What often happens is people find a way to work around the issue and declare
victory.....
> edismax does not respect pf params using non-tokenized fields
> -------------------------------------------------------------
>
> Key: SOLR-2988
> URL: https://issues.apache.org/jira/browse/SOLR-2988
> Project: Solr
> Issue Type: Bug
> Components: query parsers
> Affects Versions: 3.5
> Reporter: Hoss Man
>
> for reasons i don't fully understand, edismax ignores fields in the pf param
> if those fields are non-tokenized.
> Consider this example *dismax* query in Solr 3.5...
> {noformat}
> http://localhost:8983/solr/select/?debugQuery=true&defType=dismax&qf=name^5+features^3&pf=features^2+cat^4&q=hard+drive
> <str name="parsedquery">
> +((DisjunctionMaxQuery((features:hard^3.0 | name:hard^5.0))
> DisjunctionMaxQuery((features:drive^3.0 | name:drive^5.0))
> )~2)
> DisjunctionMaxQuery((features:"hard drive"^2.0 | cat:hard drive^4.0))
> {noformat}
> ...compared to the equivalent *edismax* query...
> {noformat}
> http://localhost:8983/solr/select/?debugQuery=true&defType=edismax&qf=name^5+features^3&pf=features^2+cat^4&q=hard+drive
> <str name="parsedquery">
> +((DisjunctionMaxQuery((features:hard^3.0 | name:hard^5.0))
> DisjunctionMaxQuery((features:drive^3.0 | name:drive^5.0))
> )~2)
> DisjunctionMaxQuery((features:"hard drive"^2.0))
> {noformat}
--
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]
