[
https://issues.apache.org/jira/browse/NIFI-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540351#comment-16540351
]
ASF GitHub Bot commented on NIFI-5407:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2877
> It shouldn't be strictly coupled to the ES version, but they obviously
could introduce breaking changes, as they could for the existing ES processors.
AIUI the next major version should maintain the REST API, but certainly the
transport client is getting deprecated in the next major version and removed in
the subsequent and I've no idea what they'd do beyond that.
We have a new bundle in progress called nifi-elasticsearch-restapi that is
based on the high level rest client from Elastic. V5 i the only one officially
in, but I have a PR for adding V6 as well with a cloned copy of the controller
service.
If you want to discuss this issue in depth, we can take it to the mailing
list because my team has done a lot w/ NiFi and ELK.
> Add a MetricsReportingTask to send to ElasticSearch
> ---------------------------------------------------
>
> Key: NIFI-5407
> URL: https://issues.apache.org/jira/browse/NIFI-5407
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.7.0
> Reporter: rich
> Priority: Trivial
>
> As far as I can tell, there isn't a MetricsReportingTask which persists to
> Elastic.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
