You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Oleg Zhurakousky (JIRA)" <ji...@apache.org> on 2015/10/04 21:13:26 UTC

[jira] [Commented] (NIFI-1021) Expose strategy to subscribe to provenance events

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

Oleg Zhurakousky commented on NIFI-1021:
----------------------------------------

One way of doing it would be a classic WireTap - http://www.enterpriseintegrationpatterns.com/patterns/messaging/WireTap.html on ProvenanceEventRepository#registerEvent(..) operation. Could be done via simple Proxy or by registering a standard service to be discovered with ServiceLoader (the technique already widely used across all of NiFi).

However, implementation must take into account the fact that the WireTap (by definition) must never break the system or affect its performance in any way.

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