[
https://issues.apache.org/jira/browse/NIFI-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351834#comment-15351834
]
ASF GitHub Bot commented on NIFI-2068:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/576
Per an offline discussion with @JPercivall, Multi-Get and/or Search
capabilities are not really right for the FetchXYZ processor idiom. A better
solution may be a List/Search/Execute processor for Elasticsearch that works in
the same vein as the existing ListXYZ processors, to maintain the List->Fetch
pattern.
> 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)
