Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 14 Feb 2013 15:00:23 +0000 (UTC)
From: =?utf-8?Q?Jan_H=C3=B8ydahl_=28JIRA=29?= <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12632354.1360840831887.289052.1360854023091@arcas>
In-Reply-To: <JIRA.12632354.1360840831887@arcas>
References: <JIRA.12632354.1360840831887@arcas>
Subject: [jira] [Commented] (SOLR-4457) Queries ending in question mark
 interpreted as wildcard
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/SOLR-4457?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13578=
417#comment-13578417 ]=20

Jan H=C3=B8ydahl commented on SOLR-4457:
-----------------------------------

Ok, crossing fingers for some code contribution here, else we'll go ahead a=
nd implement something. I already have a patch for eDisMax which stupidly r=
emoves trailing "?", and it works well. You can even disable it with the sa=
me trick of adding a space and a . or + at the end to not trigger the remov=
al. But it's nothing fancy about detecting question words or such.

Perhaps a better solution is a generic query-preprocessor plugin, which hoo=
ks in at the very top of parse(). The default implementation would be a cla=
ss doing the question mark stuff, but if anyone wants to plug their own pro=
cessing, they can write their own. This gets us back to supporting pluggabl=
e QP extensions... I implemented a simple plugin method for CurrencyField, =
the same could be used. Or is there some generic plugin type which can be d=
efined in solrconfig.xml and refered to by name we could use?
               =20
> Queries ending in question mark interpreted as wildcard
> -------------------------------------------------------
>
>                 Key: SOLR-4457
>                 URL: https://issues.apache.org/jira/browse/SOLR-4457
>             Project: Solr
>          Issue Type: Improvement
>          Components: query parsers
>            Reporter: Jan H=C3=B8ydahl
>
> For many search applications, queries ending in a question mark such as {=
{foo bar?}} would *not* mean a search for a four-letter word starting with =
{{bar}}. Neither will it mean a literal search for a question mark.
> The query parsers should have an option to discard trailing question mark=
 before passing to analysis.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org