[
https://issues.apache.org/jira/browse/SOLR-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gus Heck updated SOLR-8113:
---------------------------
Attachment: SOLR-8113.patch
After chatting briefly with [~hossman] at Lucene/Solr Revolution it became
clear that the key point of his suggestion was the complete separation of the
selection phase and the replacement phase. The attached patch provides his
suggested configuration options. This does introduce the possibility that a
field could match the selector and not match the replacement pattern. I have
handled this case by ignoring such fields (as if they were not selected) and
logging a debug message. I also wound up creating my own entire unit test
before I found the existing tests in FieldMutatingProcessorFactoryTest. I have
moved the tests from there into my test class (CloneFieldUpdateFactoryTest) as
well so that they are easier to find. Both tests read the same config file.
> 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, 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: [email protected]
For additional commands, e-mail: [email protected]
