You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Otis Gospodnetic (JIRA)" <ji...@apache.org> on 2010/01/15 19:26:54 UTC

[jira] Commented: (SOLR-758) Enhance DisMaxQParserPlugin to support full-Solr syntax and to support alternate escaping strategies.

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

Otis Gospodnetic commented on SOLR-758:
---------------------------------------

I this still needed with enhanced dismax now available?


> Enhance DisMaxQParserPlugin to support full-Solr syntax and to support alternate escaping strategies.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-758
>                 URL: https://issues.apache.org/jira/browse/SOLR-758
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 1.3
>            Reporter: David Smiley
>             Fix For: 1.5
>
>         Attachments: AdvancedQParserPlugin.java, AdvancedQParserPlugin.java, DisMaxQParserPlugin.java, DisMaxQParserPlugin.java, UserQParser.java, UserQParser.java, UserQParser.java-umlauts.patch
>
>
> The DisMaxQParserPlugin has a variety of nice features; chief among them is that is uses the DisjunctionMaxQueryParser.  However it imposes limitations on the syntax.  
> I've enhanced the DisMax QParser plugin to use a pluggable query string re-writer (via subclass extension) instead of hard-coding the logic currently embedded within it (i.e. the escape nearly everything logic). Additionally, I've made this QParser have a notion of a "simple" syntax (the default) or non-simple in which case some of the logic in this QParser doesn't occur because it's irrelevant (phrase boosting and min-should-max in particular). As part of my work I significantly moved the code around to make it clearer and more extensible.  I also chose to rename it to suggest it's role as a parser for user queries.
> Attachment to follow...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.