[ 
https://issues.apache.org/jira/browse/SOLR-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14938196#comment-14938196
 ] 

Hoss Man commented on SOLR-8109:
--------------------------------

bq. Does FirstFieldValueUpdateProcessorFactory accept wildcards?

it does, but not in the way you are asking about - all 
FirstFieldValueUpdateProcessorFactory does is "prune" a list of values down to 
the first value for each the configured fields (which can be specified as a 
regex)

the "copy" part is handled by CloneFieldUpdateProcessorFactory, and in looking 
at it's docs again, i see there is still one disconnect between it's 
functionality and the older style copyField: wildcards in the dest.  we should 
definitely add equivalent functionality to cover that case.

bq. As for the weight of the code that "must happen after atomic update 
operations" ...

I didn't say anything about the "weight" of your code ... my point was that, by 
design, copyFields (and any new features we might add to copyFields) happen 
after the full processor chain  -- the user doesn't have any choice about it.  
I nparticularly this means any new features we might add to copyFields must 
also happen after atomic updates and distributed/cloud updates, which makes the 
utility of any new features we add to copyField extremely limited, since 
copyField already doesn't play nicely with those other features (see the blue 
note box on 
https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents, 
SOLR-3743, etc...).

ergo: i think it's a bad idea to keep trying to add features to copyField.  All 
the reasons mentioned above (and finer control over the _order_ that various 
features may be applied via the pipeline configuration) is the whole reason why 
CloneFieldUpdateProcessorFactory and the various 
FieldMutatingUpdateProcessorFactory were added in the first place.  I think 
it's important to move *away* from encouraging copyField usage, not towards it.

> 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

Reply via email to