[NIFI-3011] Support Elasticsearch 5.0 for Put/FetchElasticsearch processors

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Component/s: Extensions
• Assignee: Matt Burgess
• Reporter: Matt Burgess
• Created: 09/Nov/16 15:43
• Updated: 12/Feb/17 14:00
• Resolved: 21/Nov/16 21:15

Description

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.

Issue Links

• relates to: NIFI-3467 Add EL support to more fields
• links to: GitHub Pull Request #1233