[
https://issues.apache.org/jira/browse/NIFI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240270#comment-17240270
]
Chris Sampson commented on NIFI-8003:
-------------------------------------
Suggest this is achieved by refactoring the bulk of the existing
{{DeleteByQueryElasticsearch}} processor into an abstract class, which can be
extended by a new {{UpdateByQueryElasticsearch}} processor too - the same for
the associated test class(es). A new {{updateByQuery}} method will be required
in the {{ElasticSearchClientService}}, but again that will be very similar to
the existing {{deleteByQuery}} method.
As I'm looking to implement NIFI-8001 already, it would probably make sense to
do this at the same time because it's relatively straight forward and would be
changing several of the same classes (and would therefore only cause merge
issues later).
> Create Elasticsearch update_by_query processor
> ----------------------------------------------
>
> Key: NIFI-8003
> URL: https://issues.apache.org/jira/browse/NIFI-8003
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.12.1
> Reporter: Chris Sampson
> Priority: Minor
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> An Elasticsearch processor allowing for _update_by_query operations should be
> created similar to the existing DeleteByQueryElasticsearch processor.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
