[
https://issues.apache.org/jira/browse/NIFI-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426120#comment-17426120
]
ASF subversion and git services commented on NIFI-8001:
-------------------------------------------------------
Commit f50c002692d18e6ab427c3664947e8163e7d54ca in nifi's branch
refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f50c002 ]
- NIFI-8001: Dynamic Properties as Request Parameters for Elasticsearch Client
Service processors
- NIFI-8003: UpdateByQueryElasticsearchProcessor
- Addressed various warnings and inefficiencies found in existing processor code
Signed-off-by: Joe Gresock <[email protected]>
This closes #4693.
> Elasticsearch REST processors should allow dynamic properties as query string
> parameters
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-8001
> URL: https://issues.apache.org/jira/browse/NIFI-8001
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.12.1
> Reporter: Chris Sampson
> Assignee: Chris Sampson
> Priority: Minor
> Attachments: NIFI-8001.xml, NiFi-8001.json
>
> Original Estimate: 2h
> Time Spent: 7h 40m
> Remaining Estimate: 0h
>
> The Elasticsearch REST processors (e.g. PutElasticsearchRecord) should allow
> query string parameters to be specified as dynamic properties on the
> processor (similar to the existing functionality on
> PutElasticsearchRecordHttp).
> This should be done for all processors in the
> nifi-elasticsearch-restapi-processors NAR.
> For example, adding a dynamic property with name=slices and value=auto would
> append {{?slices=auto}} to the {{_bulk}} operation URL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
