[
https://issues.apache.org/jira/browse/SOLR-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688863#action_12688863
]
Hoss Man commented on SOLR-1086:
--------------------------------
we could add a lot new error checking for to deal with these case, but
personally i think we should make it possible to specify an Analyzer on *any*
fieldType. For every FieldType except TextField, the result would be the same
as if every token produced by the analyzer had been added as a multivalue. a
new "ConcatAllTokenFilter" could be added to make it easy for people concat all
tokens produced by a tokenizer and other tokenfilters back into a single string
if necessary.
> Need to rectify inconsistent behavior when people associate an analyzer with
> a non-TextField fieldType
> ------------------------------------------------------------------------------------------------------
>
> Key: SOLR-1086
> URL: https://issues.apache.org/jira/browse/SOLR-1086
> Project: Solr
> Issue Type: Bug
> Components: Analysis
> Affects Versions: 1.1.0, 1.2, 1.3, 1.4
> Reporter: Hoss Man
>
> Currently, specifying an <analyzer> is only supported when using the
> TextField class -- however:
> 1) no error is logged if an <analyzer> is declared for other field types
> 2) the analysis screen gives the mistaken impression that the analyzer is
> being used...
> http://www.nabble.com/Field-tokenizer-question-to22594575.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
