[
https://issues.apache.org/jira/browse/LUCENE-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658546#comment-13658546
]
Adrien Grand commented on LUCENE-4981:
--------------------------------------
bq. Without PositionFilter, is there some way to achieve the same goal?
My understanding is that this use-case would like the query parser to interpret
phrase queries as sub-phrase queries. But instead of creating a specific query
parser in order to process phrase queries differently (by overriding
newFieldQuery for example), it tries to hack the token stream so that the
default query parser generates the expected query. So I don't really think this
is a use-case for PositionFilter?
> Deprecate PositionFilter
> ------------------------
>
> Key: LUCENE-4981
> URL: https://issues.apache.org/jira/browse/LUCENE-4981
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-4981.patch
>
>
> According to the documentation
> (http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.PositionFilterFactory),
> PositionFilter is mainly useful to make query parsers generate boolean
> queries instead of phrase queries although this problem can be solved at
> query parsing level instead of analysis level (eg. using
> QueryParser.setAutoGeneratePhraseQueries).
> So given that PositionFilter corrupts token graphs (see TestRandomChains), I
> propose to deprecate it.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
