[ 
https://issues.apache.org/jira/browse/SOLR-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645566#action_12645566
 ] 

Otis Gospodnetic commented on SOLR-756:
---------------------------------------

My colleagues and I have recently hit a similar wall -- DisMax not allowing 
wildcards.
I think Hoss will be the loudest (not in a negative sense) here, so here are 
some specific questions:

# are we OK with adding wildcard (and other) support to "dismax"?
# if yes, which part of "dismax" should that be added to? (David described the 
2 meanings of "dismax")

I've hit this wall a couple of times that I think it's worth thinking about how 
to get support for non-plain-keywords-only queries somethere in the DisMax 
area.  Like David, I too want to make use of the other functionality that 
already exists there, such as bf, ps, etc.

Thanks.


> 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.

Reply via email to