[
https://issues.apache.org/jira/browse/SOLR-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610058#comment-13610058
]
Andrzej Bialecki commented on SOLR-4619:
-----------------------------------------
David: hmm, I'm not sure about that ... this would complicate the processing of
all field types in order to support a use case that is very specific. If you
throw in the ability to support different serializations then the detection of
whether a field content is in a pre-analyzed format or not is not that simple
anymore. Do you have a use case in mind that would require switching on the fly
between the regular and pre-analyzed formats?
John: please test the patch that I attached. If this is what you had in mind
then I'd like to commit it soon, as it's a clear improvement over the current
functionality.
> 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, 5.0, 4.2.1
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Fix For: 5.0
>
> Attachments: 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 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: [email protected]
For additional commands, e-mail: [email protected]
