lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-758) Enhance DisMaxQParserPlugin to support full-Solr syntax and to support alternate escaping strategies.
Date Fri, 05 Sep 2008 20:56:44 GMT

     [ https://issues.apache.org/jira/browse/SOLR-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Smiley updated SOLR-758:
------------------------------

    Attachment: AdvancedQParserPlugin.java
                DisMaxQParserPlugin.java
                UserQParser.java

I am contributing source files to this issue instead of patches because the code was significantly
reworked.
Note that this patch depends strongly on SOLR-756 and mildly on SOLR-757 which I've contributed
separately.  They need to be applied for this to compile.  Even if you don't get those patches,
you can read the source any way to see what it does.

> 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
>         Attachments: AdvancedQParserPlugin.java, DisMaxQParserPlugin.java, UserQParser.java
>
>
> 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.


Mime
View raw message