[
https://issues.apache.org/jira/browse/SOLR-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606943#comment-13606943
]
Hoss Man commented on SOLR-1086:
--------------------------------
this issue actually pre-dates a lot of newer functionality in solr -- in
particular UpdateProcessors.
I would suggest that while we should still add schema validation checking ot
error if someone tries to use an analyzer where it's no supported (if it hasn't
already been added?) for things like date format parsing or number format
parsing (where you want it to produce Date/Integer/Float/etc objects for
_storage_ not just for term indxing) those would make the most sense as
UpdateProcessors.
> 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: Schema and Analysis
> Affects Versions: 1.1.0, 1.2, 1.3, 1.4
> Reporter: Hoss Man
> Labels: newdev
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
