[
https://issues.apache.org/jira/browse/LUCENE-8273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16455543#comment-16455543
]
Robert Muir commented on LUCENE-8273:
-------------------------------------
just imaging scenarios more, its probably useful if the thing can avoid
corrupting graphs. By that i mean: conceptually the user has to understand that
the filtering applies the condition based on the first token and that the
filter gets whatever it pulls (based on its wanted context), and those are
provided "graph-aligned" or something. I think its just inherent in what you
are trying to do and not specific to the implementation: it needs to have some
restrictions to avoid trouble? So maybe this filter should also consider
positionLength...
> 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
>
>
> 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]
