[
https://issues.apache.org/jira/browse/SOLR-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098237#comment-15098237
]
Steve Rowe commented on SOLR-4619:
----------------------------------
Massive change doesn't seem warranted.
{quote}
bq. But PreAnalyzedTokenizer doesn't have any attributes defined until the
input stream is consumed, in reset()
Right, thats a bug really.
{quote}
bq. fix this TokenStream to somehow provide attributes before reset()
Since the input reader must be consumed before the attributes can be provided,
the tokenizer must somehow have access to the input reader prior to reset().
The most likely place is setReader(), but Tokenizer.setReader() is final.
A new analyzer class employing PreAnalyzedTokenizer could override initReader()
or setReader(). I'll try with setReader(), since the docs for initReader() are
focused on reader conditioning via char filters.
> Improve PreAnalyzedField query analysis
> ---------------------------------------
>
> Key: SOLR-4619
> URL: https://issues.apache.org/jira/browse/SOLR-4619
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis
> Affects Versions: 4.0, 4.1, 4.2, 4.2.1, Trunk
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Fix For: Trunk
>
> Attachments: SOLR-4619.patch, SOLR-4619.patch
>
>
> PreAnalyzed field extends plain FieldType and mistakenly uses the
> DefaultAnalyzer as query analyzer, and doesn't allow for customization via
> <analyzer> schema elements.
> Instead it should extend TextField and support all query analysis supported
> by that type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
