[
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630220#action_12630220
]
Mark Miller commented on SOLR-756:
----------------------------------
I am not suggesting that you maintain your own, but perhaps that a new
queryparser would be a better option. I am not positive in my answer, and am
only thinking out loud. I got the impression that dismax goes out of its way to
escape as much as it can to avoid parse errors and allow copy paste of text
type of uses. The functionality you mention appears all to be from components
below the dismax parser. In my mind, I like the idea of keeping dismax lean
and mean and starting something else to become a kitchen sink - Lucene's
queryparser became a bit of a kitchen sink and I think dismax looks to be coded
so as to avoid some of the problems that can emerge from that...
> 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.
