[
https://issues.apache.org/jira/browse/LUCENE-8273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458507#comment-16458507
]
Robert Muir commented on LUCENE-8273:
-------------------------------------
I'm also curious about common use cases where the condition is just matching a
list of words, basically what the KeywordMarker factory provides today. Does
the user have access to stuff like resource loaders to read from files / is it
intuitive so they won't be reading the list of words in on every token or other
mistakes? If we can make this simple, I think we can deprecate KeywordMarker
and many other exception-list-type mechanisms hardcoded in all the filters,
which would be a really nice cleanup.
> Add a ConditionalTokenFilter
> ----------------------------
>
> Key: LUCENE-8273
> URL: https://issues.apache.org/jira/browse/LUCENE-8273
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Alan Woodward
> Priority: Major
> Attachments: LUCENE-8273.patch, LUCENE-8273.patch, LUCENE-8273.patch,
> LUCENE-8273.patch
>
>
> Spinoff of LUCENE-8265. It would be useful to be able to wrap a TokenFilter
> in such a way that it could optionally be bypassed based on the current state
> of the TokenStream. This could be used to, for example, only apply
> WordDelimiterFilter to terms that contain hyphens.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
