[
https://issues.apache.org/jira/browse/NIFI-4218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16130970#comment-16130970
]
ASF subversion and git services commented on NIFI-4218:
-------------------------------------------------------
Commit 6b5015e39b4233cf230151fb45bebcb21df03730 in nifi's branch
refs/heads/master from [~mattyb149]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=6b5015e ]
NIFI-4218: Dynamic properties as query parameters in ESHttp processors
This closes #2049.
Signed-off-by: Bryan Bende <[email protected]>
> ElasticsearchHttp processors should support dynamic properties as query
> parameters
> ----------------------------------------------------------------------------------
>
> Key: NIFI-4218
> URL: https://issues.apache.org/jira/browse/NIFI-4218
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Minor
> Fix For: 1.4.0
>
>
> The Elasticsearch HTTP API has a number of fields that can be specified as
> query parameters in the URL, such as support for
> [pipelines|https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html].
> Rather than including all possibilities as processor properties, it might be
> more flexible to allow the user to specify dynamic properties on
> ElasticsearchHttp processors, and then use those to set query parameters on
> the API URL.
> Documentation should include a note that not all features are available to
> all versions of Elasticsearch, and thus the ES documentation should be
> consulted before adding dynamic properties. For example, pipelines were
> introduced in ES 5.x, so using pipeline parameters in an ElasticsearchHttp
> processor will not work if connecting to an ES 2.x cluster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
