[
https://issues.apache.org/jira/browse/NIFI-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351695#comment-15351695
]
ASF GitHub Bot commented on NIFI-2068:
--------------------------------------
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/576
There have already been comments asking for a multi-get function for
ElasticSearch[1] could this be added to FetchElasticSearchHTTP now and be added
as a new feature to PutElasticSearch later (Create a Jira for it)?
[1]
https://community.hortonworks.com/questions/41951/how-to-get-all-values-with-expression-language-in.html
> Add Elasticsearch processors that use the REST API
> --------------------------------------------------
>
> Key: NIFI-2068
> URL: https://issues.apache.org/jira/browse/NIFI-2068
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Fix For: 1.0.0
>
>
> The current Elasticsearch processors use the Transport Client, and as a
> result there can be some compatibility issues between multiple versions of ES
> clusters. The REST API is much more standard between versions, so it would be
> nice to have ES processors that use the REST API, to enable things like
> migration from an Elasticsearch cluster with an older version to a cluster
> with a newer version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
