[
https://issues.apache.org/jira/browse/NIFI-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509631#comment-16509631
]
ASF GitHub Bot commented on NIFI-5292:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2782
Hey @MikeThomsen when we discussed the renaming on the mailing list, I was
under the impression that the Elasticsearch Client Service was new for 1.7.0.
But it appears that it already has been released in 1.6.0. We need to avoid
changing the names of components once they have been released because doing so
would break users' flows. I think we need to keep the name
nifi-elasticsearch-client-service and then we can use the name
nifi-elasticsearch-client-service-6, etc. for the new one. Then we'd just
document the old one to indicate that it was designed to work against
Elasticsearch 5.x. Sorry for the confusion! We do need to ensure that we keep
existing flows stable, though, and we only want to break a flow if there's no
feasible way around it.
> 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)
