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

["Chris Sampson (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240271#comment-17240271 ] 

Chris Sampson commented on NIFI-8001:
-------------------------------------

Should be able to copy much of the existing {{Dynamic Property}} logic from processors such as {{PutElasticsearchHttp}}. Will require the {{ElasticSearchClientService}} to accept a collection of URL query string parameters as part of the various operation calls.

> 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
>            Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> 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)