nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Zhurakousky (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (NIFI-1021) Expose strategy to subscribe to provenance events
Date Mon, 12 Oct 2015 22:47:06 GMT

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

Oleg Zhurakousky edited comment on NIFI-1021 at 10/12/15 10:46 PM:
-------------------------------------------------------------------

A sample JAR which contains consumer writing events to standard out.
To test, simply drop it into the 'lib' directory of NiFi which is built with proposed changes,
start NiFi, create and start any flow and monitor the logs.

*Future Considerations:*
While current approach addresses the ability to wire-tap into the provenance event stream
with limited to no impact to NiFi health, it does require JAR file(s) on the classpath prior
to NiFi startup. In the future we may want to consider JMX or UI approach to register such
wire-taps on the fly. 



was (Author: ozhurakousky):
A sample JAR which contains consumer writing events to standard out.
To test, simply drop it into the 'lib' directory of NiFi which is built with proposed changes,
start NiFi, create and start any flow and monitor the logs.



> Expose strategy to subscribe to provenance events
> -------------------------------------------------
>
>                 Key: NIFI-1021
>                 URL: https://issues.apache.org/jira/browse/NIFI-1021
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework
>    Affects Versions: 0.3.0
>            Reporter: Oleg Zhurakousky
>            Assignee: Oleg Zhurakousky
>         Attachments: nifi-provenance-stream-1.0.0-SNAPSHOT.jar
>
>
> Currently access to the provenance events is exposed thru ReportingTask which is scheduled
and therefore provides a "near-real-time" access to provenance events.
> There are several valid use cases where such events may need to be streamed in "real-time"
for variety of real time analytics.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message