lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Lachinger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-758) Enhance DisMaxQParserPlugin to support full-Solr syntax and to support alternate escaping strategies.
Date Fri, 18 Sep 2009 11:07:16 GMT

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

Simon Lachinger commented on SOLR-758:
--------------------------------------

First of all thanks for providing wildcard matching for the dismax query handler, that is
exactly what I need. However, the WILDCARD_STRIP_CHARS regex in UserQParser.java does not
work with umlauts which makes the patch useless for languages like ie. German.

I will attach a diff file with the changes I have made to get it working with umlauts.

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