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

ASF subversion and git services commented on NIFI-13724:
--------------------------------------------------------

Commit 27ad015bc558657ba876eb8395f484758064610d in nifi's branch 
refs/heads/support/nifi-1.x from Dye357
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=27ad015bc5 ]

NIFI-13724 Added additional Registry metadata to events for support branch 
(#9433)

Signed-off-by: David Handermann <[email protected]>

> Nifi Registry Events Include Additional Metadata
> ------------------------------------------------
>
>                 Key: NIFI-13724
>                 URL: https://issues.apache.org/jira/browse/NIFI-13724
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: NiFi Registry
>            Reporter: Dye357
>            Assignee: Dye357
>            Priority: Minor
>             Fix For: 2.0.0
>
>          Time Spent: 1h 40m
>  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)

Reply via email to