[
https://issues.apache.org/jira/browse/SOLR-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937734#comment-14937734
]
Hoss Man commented on SOLR-8109:
--------------------------------
Isn't this situation already pretty sell resolved more robustly by
CloneFieldUpdateProcessorFactory + FirstFieldValueUpdateProcessorFactory
instead of using copyField?
Particularly because it can be configured on a per processor chain basis, so
you can pick "first" in some cases, or "max" in others (depending on
wh/what/where the docs are coming from)
https://lucene.apache.org/solr/5_3_0/solr-core/org/apache/solr/update/processor/FirstFieldValueUpdateProcessorFactory.html
https://lucene.apache.org/solr/5_3_0/solr-core/org/apache/solr/update/processor/CloneFieldUpdateProcessorFactory.html
In general i think update processors are a much better way to address problems
like this moving forward, rather then adding more features at the "schema"
level (like new copyField options) ... particularly when you consider how low
level copyField operations are, and how they (by definition) *must* happen
after both atomic update operations about any distributed processing for cloud
setups
> Option to Copy just the first value from a multivalued field
> ------------------------------------------------------------
>
> Key: SOLR-8109
> URL: https://issues.apache.org/jira/browse/SOLR-8109
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Affects Versions: 5.3
> Reporter: Gus Heck
> Attachments: SOLR-8109.patch
>
>
> Provide a firstValueOnly boolean option for copyField
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
