[
https://issues.apache.org/jira/browse/SOLR-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578417#comment-13578417
]
Jan Høydahl commented on SOLR-4457:
-----------------------------------
Ok, crossing fingers for some code contribution here, else we'll go ahead and
implement something. I already have a patch for eDisMax which stupidly removes
trailing "?", and it works well. You can even disable it with the same trick of
adding a space and a . or + at the end to not trigger the removal. But it's
nothing fancy about detecting question words or such.
Perhaps a better solution is a generic query-preprocessor plugin, which hooks
in at the very top of parse(). The default implementation would be a class
doing the question mark stuff, but if anyone wants to plug their own
processing, they can write their own. This gets us back to supporting pluggable
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 defined
in solrconfig.xml and refered to by name we could use?
> 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øydahl
>
> 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 administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
