[
https://issues.apache.org/jira/browse/SOLR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-309:
--------------------------
Attachment: SOLR-309.patch
path that modifies FieldType.setAnalyzer to fail by default, so that only
TextField allows the specification of an analyzer.
this leaves the door open for other future FieldTypes to also allow analyzers,
but solve the problem of Solr silently allowing analyzers to be set on field
types that don't actually use them
(and since the bogus analyzer can no longer be set on other field types,
analysis.jsp won't use that bogus analyzer)
> A solr.StrField that has analyzers configured should emit warning to log
> ------------------------------------------------------------------------
>
> Key: SOLR-309
> URL: https://issues.apache.org/jira/browse/SOLR-309
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Thomas Peuss
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 3.1, 4.0
>
> Attachments: SOLR-309.patch
>
>
> A solr.StrField that has analyzers configured in schema.xml should emit a
> warning/error to the log. As I understand StrFields never get tokenized.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
