[
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-756:
------------------------------
Attachment: SolrPluginUtilsDisMax.patch
The patch file is only to be applied on SolrPluginUtils.java. The patch file
might need to be modified to remove the header that indicates the path to this
file which is unique to my development system.
Testing this would be a little tricky because this parser is only used by one
QParser and it prohibits doing the type of queries that would exercise these
changes. I have tests on my system but they involve other things that I have
not contributed (yet, any way).
> Make DisjunctionMaxQueryParser generally useful by supporting all query types.
> ------------------------------------------------------------------------------
>
> Key: SOLR-756
> URL: https://issues.apache.org/jira/browse/SOLR-756
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: David Smiley
> Attachments: SolrPluginUtilsDisMax.patch
>
>
> This is an enhancement to the DisjunctionMaxQueryParser to work on all the
> query variants such as wildcard, prefix, and fuzzy queries, and to support
> working in "AND" scenarios that are not processed by the min-should-match
> DisMax QParser. This was not in Solr already because DisMax was only used for
> a very limited syntax that didn't use those features. In my opinion, this
> makes a more suitable base parser for general use because unlike the
> Lucene/Solr parser, this one supports multiple default fields whereas other
> ones (say Yonik's {!prefix} one for example, can't do dismax). The notion of
> a single default field is antiquated and a technical under-the-hood detail of
> Lucene that I think Solr should shield the user from by on-the-fly using a
> DisMax when multiple fields are used.
> (patch to be attached soon)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
