[jira] [Commented] (SOLR-8113) Accept replacement strings in CloneFieldUpdateProcessorFactory

["Gus Heck (JIRA)" <ji...@apache.org>]

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

Gus Heck commented on SOLR-8113:
--------------------------------

This was motivated by the response to SOLR-8109. This bridges the gap in the suggested alternate solution, but does look like it will likely be a lot less performant. I couldn't find a way to re-use the match done by the FieldNameSelector, so the regex matches have to execute twice. All attempts I made to do that resulted in major API changes.

This is however more flexible, will not interfere with atomic updates (as copyField apparently does) and Allows further movement away from the use of copyField.

My preference would be for both this and SOLR-8109 to become available since speed is one tradeoff, and atomic update support etc is another.

> Accept replacement strings in CloneFieldUpdateProcessorFactory
> --------------------------------------------------------------
>
>                 Key: SOLR-8113
>                 URL: https://issues.apache.org/jira/browse/SOLR-8113
>             Project: Solr
>          Issue Type: Improvement
>          Components: update
>    Affects Versions: 5.3
>            Reporter: Gus Heck
>         Attachments: SOLR-8113.patch
>
>
> Presently CloneFieldUpdateProcessorFactory accepts regular expressions to select source fields, which mirrors wildcards in the source for copyField in the schema. This patch adds a counterpart to copyField's wildcards in the dest attribute by interpreting the dest parameter as a regex replacement string.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org