[
https://issues.apache.org/jira/browse/NIFI-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-11016:
-------------------------------
Fix Version/s: 2.0.0
1.24.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Consider providing a query-builder set of properties for the
> UpdateByQueryElasticsearch processor
> -------------------------------------------------------------------------------------------------
>
> Key: NIFI-11016
> URL: https://issues.apache.org/jira/browse/NIFI-11016
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Chris Sampson
> Assignee: Chris Sampson
> Priority: Minor
> Fix For: 2.0.0, 1.24.0
>
>
> While it is already possible to send a {{script}} field as part of the
> {{Query}} parameter in the {{UpdateByQueryElasticsearch}} processor, [there
> is question|https://github.com/apache/nifi/pull/6628#issuecomment-1308972782]
> about whether this is sufficiently clear to NiFi users or a "query builder"
> kind of experience would be preferred, e.g. if the {{query}} field were
> specified via one processor property and {{script}} via another
> One thing to be careful of with any changes is to retain the [current
> (default)
> behaviour|https://github.com/apache/nifi/pull/6628#issuecomment-1308978863]
> of the {{Query}} parameter of the processor so as to be backwards
> compatible/for anyone already specifying the whole Elasticsearch Update/Query
> DSL via the existing parameters
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
