Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently, each ReportingTasks have to implement its own logic to consume NiFi Provenance events, including filtering by event type or component id, batch size and state management. Those implementation can be error-prone if it's done by each component (such as NIFI-4468).
It would be better if NiFi has a common utility class to consume Provenance events by different ReportingTasks.
Attachments
Issue Links
- is required by
-
NIFI-3709 Export NiFi flow dataset lineage to Apache Atlas
- Resolved
- links to