nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Burgess (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (NIFI-4218) ElasticsearchHttp processors should support dynamic properties as query parameters
Date Wed, 02 Aug 2017 13:42:00 GMT

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

Matt Burgess reassigned NIFI-4218:
----------------------------------

    Assignee: Matt Burgess

> 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
>
> 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)

Mime
View raw message