lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Wolanin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-756) Make DisjunctionMaxQueryParser generally useful by supporting all query types.
Date Thu, 03 Sep 2009 14:14:57 GMT

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

Peter Wolanin commented on SOLR-756:
------------------------------------

We are regularly hitting this wall and users are very frustrated by not being able to use
wildcards becuase we wanted the other advantages of the dismax parser.

Any chance to get some of these changes in 1.4?

> 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
>             Fix For: 1.5
>
>         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.


Mime
View raw message