[
https://issues.apache.org/jira/browse/SOLR-4619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611964#comment-13611964
]
David Smiley commented on SOLR-4619:
------------------------------------
bq. 1. It could be based on the document itself (tricky, in the light of
multiple serialization formats).
I don't understand.
bq. 2. OR, we could extend SolrInputField (and the document serializations) to
support additional per-field flags to indicate this, but that would complicate
matters even more.
If it were generalized, i.e. per-field map of metadata, then I rather like it.
Though it'd take a fair amount of work I think to fully realize this (e.g.
update SolrJ & XML & JSON input formats), and it might also make URP's into
more of a full-fledged pipeline but I think such things are better done
external to Solr.
bq. 3. OR, if this decision is going to be based on schema we would have to
extend schema to pass additional flags to mark fields as preanalyzed - also
tricky.
I don't like this, as it ties the choice of pre-analysis to the schema which I
think is unnecessary coupling just as it is to the field type.
bq. 4. And finally, we could put the list of fields to always convert in the
init args of this UpdateRequestProcessor in solrconfig ... but that's a bit
ugly, mixing schema and solrconfig.
I don't see it as "mixing schema" unless you simply mean to say that fields are
referred to outside of the schema. But heck, that's inevitable as fields are
already referred to all over solrconfig.xml. It's unrealistic to expect the
names of fields in one's schema to not exist outside of schema.xml -- the app
needs to know too :-)
One option would be to pass in a pseudo field {{\_pre-analyzed\_}} (leading and
trailing underscore) with a list of field names that are pre-analyzed. The
sender of the data is certainly aware of which fields are pre-analyzed as it
had to pre-analyze them, so it can simply communicate that.
> 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]
