[jira] [Updated] (NIFI-8001) Elasticsearch REST processors should allow dynamic properties as query string parameters

["Joe Gresock (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Gresock updated NIFI-8001:
------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> 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
>             Fix For: 1.15.0
>
>         Attachments: NIFI-8001.xml, NiFi-8001.json
>
>   Original Estimate: 2h
>          Time Spent: 7h 50m
>  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)