[
https://issues.apache.org/jira/browse/SOLR-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098245#comment-15098245
]
Steve Rowe commented on SOLR-4619:
----------------------------------
bq. 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.
I was referring to TokenStreamComponents.setReader() here, which is called as
part of Analyzer.tokenStream(): A subclass created in the new analyzer's
overridden createComponents() could call a new method on PreAnalyzedTokenizer
to consume the input reader and in so doing provide the attributes.
> 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]
