[
https://issues.apache.org/jira/browse/NIFI-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509717#comment-16509717
]
ASF GitHub Bot commented on NIFI-5292:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2782
@markap14 Ok, that's fair. I think the general issue has to be addressed,
but the easy route is obviously blocked. So what I'm going to do to try to head
this is off is:
1. Rip out the changes to the 5x client and keep the 6x version.
2. Add some metadata to the 5x client service to help provide some visual
cues in the UI.
3. See if there is a way to get the protocol compatibility range from the
ES client API. I've seen debug info that suggests it looks for that and
enforces it, so I'm hoping there's a client API which will let us sniff that
and throw an error saying you need to change client services to keep w/ ES
protocol compatibility.
> Rename existing ElasticSearch client service impl to specify it is for 5.X
> --------------------------------------------------------------------------
>
> Key: NIFI-5292
> URL: https://issues.apache.org/jira/browse/NIFI-5292
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.7.0
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Priority: Major
> Labels: Migration
>
> The current version of the impl is 5.X, but has a generic name that will be
> confusing down the road.
> Add an ES 6.X client service as well.
>
> Migration note: Anyone using the existing client service component will have
> to create a new one that corresponds to the version of ElasticSearch they are
> using.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
