nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <>
Subject [jira] [Commented] (NIFI-6566) Decouple status analytics model from connection status analytics objects
Date Tue, 27 Aug 2019 16:44:01 GMT


ASF subversion and git services commented on NIFI-6566:

Commit 8810f9c7b96a9bd3833eda703085e7938ff0a312 in nifi's branch refs/heads/analytics-framework
from Yolanda Davis
[;h=8810f9c ]

NIFI-6566 - Refactor to decouple model instance from status analytics object. Also allow configurable
model from

NIFI-6566 - changes to allow scoring configurations for model in

NIFI-6566 - added default implementation value to NiFiProperties

NIFI-6566 - correction to default variable name in NiFiProperties, removed unnecessary init
method from ConnectionStatusAnalytics

Signed-off-by: Matthew Burgess <>

This closes #3663

> Decouple status analytics model from connection status analytics objects 
> -------------------------------------------------------------------------
>                 Key: NIFI-6566
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Core Framework
>            Reporter: Yolanda M. Davis
>            Assignee: Yolanda M. Davis
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
> Currently the connection status analytics object is tightly coupled with the type of
model used for prediction. This should be refactored to allow flexibility for model selection.
Users should also be able to configure the model used via as described below:
> nifi.anlytics.connecttion.model.score.threshold=.90

This message was sent by Atlassian Jira

View raw message