[
https://issues.apache.org/jira/browse/LUCENE-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13842249#comment-13842249
]
Adrien Grand commented on LUCENE-4963:
--------------------------------------
The way to generate a query based on the token stream of the query string is
the responsibility of the query parser. For example, QueryParserBase has the
{{setEnablePositionIncrements}} method
http://lucene.apache.org/core/4_4_0/queryparser/org/apache/lucene/queryparser/classic/QueryParserBase.html#setEnablePositionIncrements(boolean)
which can be used to ignore holes in the token stream (which seems to be what
you are looking for).
> Deprecate broken TokenFilter constructors
> -----------------------------------------
>
> Key: LUCENE-4963
> URL: https://issues.apache.org/jira/browse/LUCENE-4963
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Fix For: 4.4
>
> Attachments: LUCENE-4963.patch
>
>
> We have some TokenFilters which are only broken with specific options. This
> includes:
> * TrimFilter when updateOffsets=true
> * StopFilter, JapanesePartOfSpeechStopFilter, KeepWordFilter, LengthFilter,
> TypeTokenFilter when enablePositionIncrements=false
> I think we should deprecate these behaviors in 4.4 and remove them in trunk.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
