[
https://issues.apache.org/jira/browse/SOLR-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612533#comment-13612533
]
Andrzej Bialecki commented on SOLR-4619:
-----------------------------------------
So it looks to me like the least controversial option is to put the list of
preanalyzed fields in solrconfig in the specification of the URP. The trick
with a "magic" field name sounds useful too - it would allow overriding the
list of fields on a per-document basis. This could be also achieved by passing
the list of fields via SolrParams - although it would affect all documents in a
given update request.
Anyway, I think these are good ideas worth trying. I'll start working on a
patch. Thanks for the comments!
> 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]
