[jira] [Resolved] (NIFI-16234) Create a Provenance Reporting Task using a Record Sink as the target

["Matt Burgess (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-16234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess resolved NIFI-16234.
---------------------------------
    Resolution: Won't Do

I realized we already have this functionality in QueryNiFiReportingTask. We can reopen if it is desired to have a reporting task that focuses on the Provenance repo (which would be more efficient) and doesn't require SQL knowledge.

> Create a Provenance Reporting Task using a Record Sink as the target
> --------------------------------------------------------------------
>
>                 Key: NIFI-16234
>                 URL: https://issues.apache.org/jira/browse/NIFI-16234
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Minor
>              Labels: provenance, reporting_task
>
> The current Provenance Reporting Task uses Site-to-Site to transmit the provenance events via S2S either back to the same NiFi cluster for processing, or a different S2S-compliant target. There are known limitations and perhaps undesirable consequences with using S2S, one being that the REST API must be used to get the peers which requires authorization, and another being that provenance events re-entered into the NiFi flow will create their own provenance events during processing.
> This Jira proposes to add a ProvenanceReportingTask that uses a RecordSinkService controller service, allowing the user to transmit provenance events to any target for which a RecordSink exists (Kafka, JDBC, Azure EventHub, etc.). This could lead to other RecordSink services being implemented that are more effective targets for provenance data, such as a graph database.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)