[
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630217#action_12630217
]
David Smiley commented on SOLR-756:
-----------------------------------
The DisjunctionMaxQueryParser in Solr does more than limit the user's syntax.
It offers the DisjunctionMax capability which is unique to this query parser,
it has a boostingQuery, and a boostingFunctions capability too. Furthermore,
the DisjunctionMaxQueryParser prescribes a particular way of limiting the
user's syntax that I think applications should be able to specify if they so
choose.
Sure, I could "write my own query parser" but that's a pain... why should
everyone who wants the DisMax capability have to write their own just because
we don't want it to make assumptions about a limited syntax?
> 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.
