You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alexandre Rafalovitch (JIRA)" <ji...@apache.org> on 2016/10/02 01:20:20 UTC
[jira] [Closed] (SOLR-1086) Need to rectify inconsistent behavior
when people associate an analyzer with a non-TextField fieldType
[ https://issues.apache.org/jira/browse/SOLR-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexandre Rafalovitch closed SOLR-1086.
---------------------------------------
Resolution: Fixed
This validation has been long fixed. Quick test throws back an error:
{noformat}
StrField (ignored) does not support specifying an analyzer
{noformat}
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org