[
https://issues.apache.org/jira/browse/LUCENE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742441#action_12742441
]
Yonik Seeley commented on LUCENE-1804:
--------------------------------------
OO design principal of not removing functionality - Tokenizer's superclass can
specify it's AttributeSource... why can't Tokenizer? We shouldn't disallow it
just because we can't immediately think of a use case.
bq. I am still not sure, why a simple TokenFilter does not serve the same
pupose you would like to have with Tokenizer here.
Simplest case: a Tokenizer that delegates to an existing Tokenizer or
TokenStream?
> Can't specify AttributeSource for Tokenizer
> -------------------------------------------
>
> Key: LUCENE-1804
> URL: https://issues.apache.org/jira/browse/LUCENE-1804
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Yonik Seeley
> Attachments: LUCENE-1804.patch
>
>
> One can't currently specify the attribute source for a Tokenizer like one can
> with any other TokenStream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
