[
https://issues.apache.org/jira/browse/NIFI-13724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende updated NIFI-13724:
-------------------------------
Fix Version/s: 2.0.0-M5
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Nifi Registry Events Include Additional Metadata
> ------------------------------------------------
>
> Key: NIFI-13724
> URL: https://issues.apache.org/jira/browse/NIFI-13724
> Project: Apache NiFi
> Issue Type: New Feature
> Components: NiFi Registry
> Reporter: Dye357
> Assignee: Dye357
> Priority: Minor
> Fix For: 2.0.0-M5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently the Nifi Registry EventFactory adds a few pieces of metadata to the
> EventType - when writing a custom extension for Nifi Registry a developer is
> limited in the amount of information they have about the event – this ticket
> would expand the scope of metadata included in each event to include the
> Name, Description and Timestamps.
> As a work-around we were using the nifi-registry-client to use the provided
> IDs to enrich our dataset however we've run into problems:
> 1. The nifi registry client is broken when running inside an Nifi Registry
> extension due to JavaX/Jakarta classpath issues. (Separate ticket)
> 2. This the most important of the two points – if we have a Bucket Deleted or
> Flow Deleted event only having the ID is useless because we can no longer
> query the API to get the name and description for the Entity in question
> which has led to some auditing/accountability concerns.
> I'm putting together a PR to include the additional specified metadata in the
> EventFactory. The PR should be merge-able on 1.x and 2.x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
