[
https://issues.apache.org/jira/browse/NIFI-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690965#comment-15690965
]
Randy Bovay commented on NIFI-3011:
-----------------------------------
There are 2 enhancements that would improve this processor.
1) We'd like to have expression language support for ElasticSearch Hosts, and
ClusterName field. This is good for developers, and allows us to vary our
targets per data center and environment. Otherwise we would have to deploy code
and then manually update it.
2) Also, the bulk transport clients should allow for configuring multiple hosts
in the elasticsearch hosts field. This allows us to have a Primary, and many
secondary lists of servers. So that if one goes offline, the processor will
connect to a backup to retrieve the routing table information.
This shows how to set multiple addresses.
https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/transport-client.html
> Support Elasticsearch 5.0 for Put/FetchElasticsearch processors
> ---------------------------------------------------------------
>
> Key: NIFI-3011
> URL: https://issues.apache.org/jira/browse/NIFI-3011
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Fix For: 1.1.0
>
>
> Now that Elastic has released a new major version (5.0) of Elasticsearch, the
> Put/FetchElasticsearch processors would need to be upgraded (or duplicated)
> as the major version of the transport client needs to match the major version
> of the Elasticsearch cluster.
> If upgrade is selected, then Put/FetchES will no longer work with
> Elasticsearch 2.x clusters, so in that case users would want to switch to the
> Http versions of those processors. However this might not be desirable (due
> to performance concerns with the HTTP API vs the transport API), so care must
> be taken when deciding whether to upgrade the existing processors or create
> new ones.
> Creating new versions of these processors (to use the 5.0 transport client)
> will also take some consideration, as it is unlikely the different versions
> can coexist in the same NAR due to classloading issues (multiple versions of
> JARs containing the same class names, e.g.). It may be necessary to create an
> "elasticsearch-5.0" version of the NAR, containing only the new versions of
> these processors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
