[ 
https://issues.apache.org/jira/browse/NIFI-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540141#comment-16540141
 ] 

ASF GitHub Bot commented on NIFI-5407:
--------------------------------------

Github user richmidwinter commented on the issue:

    https://github.com/apache/nifi/pull/2877
  
    Thanks for taking a look.
    
    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.
    
    I can see pros and cons to both (for instance we've really suffered as the 
complexity of the flows grow, mostly with the overhead of developers 
understanding and working in parallel on them so we have a probably exceptional 
aversion to adding to them). This is just something that's worked for me - I'd 
understand if you guys choose not to take it.


> 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)

Reply via email to