You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Koji Kawamura (JIRA)" <ji...@apache.org> on 2018/05/23 04:36:00 UTC

[jira] [Commented] (NIFI-4810) Improve Extensibility of WriteAheadProvenanceRepository

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

Koji Kawamura commented on NIFI-4810:
-------------------------------------

[~mmaioe] Instead of extending WriteAheadProvenanceRepository, provenance events can be analyzed by ReportingTasks. SiteToSiteProvenanceReportingTask or ReportLineageToAtlas can be references to do that.
SiteToSiteProvenanceReportingTask can expose provenance events as JSON objects so that a NiFi flow can receive it via Site-to-Site (Remote Input Port) to analyze those events. This page may be useful https://community.hortonworks.com/articles/72727/extracting-nifi-provenance-data-using-sitetositepr.html

I'd recommend implementing a custom ReportingTask instead of extending ProvenanceRepository.

> Improve Extensibility of WriteAheadProvenanceRepository
> -------------------------------------------------------
>
>                 Key: NIFI-4810
>                 URL: https://issues.apache.org/jira/browse/NIFI-4810
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Mao Ito
>            Priority: Minor
>
> If we want to create some new ProvenanceRepository extending WriteAheadProvenanceRepository, we have some issues.
> The scenarios is that the new ProvenanceRepsoitory just intercept event without losing the functionality of WriteAheadProvenanceRepository (i.e. allow writing message into the disk).
> In this scenario, 
> We can just override the method of "registerEvents".
> And, the issue is that we want to get "eventId" assigned by WriteAheadProvenanceRepository.
> However, there is no efficient and easy way to get these eventIds as far as I see.
> We have the below options to improve it:
> 1. change "private" to "protected" for fields of WriteAheadProvenanceRepository
> 2. return "StorageResult" for "registerEvents" method
> StorageResult includes "eventIds" assigned by WriteAheadProvenanceRepository
> If there is actually an easy way to do, give us some comments.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)