[
https://issues.apache.org/jira/browse/NIFI-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980883#comment-14980883
]
Matt Gilman commented on NIFI-986:
----------------------------------
-1
I don't believe the current patch would provide access to events when
clustered. Currently, actions are stored in the NCM and are bundled in the
response from the nodes. ClusteredEventAccess.getFlowChanges would need to be
implemented.
It makes sense to also store the actions locally on the nodes when clustered.
We should bundle the events to be stored at the NCM when the instance is a
connected node. However, we should always save the events in the local action
DB.
[~markap14] Is there a reason why we don't want to support Primary Node Only
scheduling strategy for reporting tasks? I think there may be a use case for it
here since the actions may be batched at the NCM. I see that previously I was
only adding support for Timer and CRON. I would add support conditionally based
on the Reporting Task Availability.
> Expose audit information on flow design changes to reporting tasks
> ------------------------------------------------------------------
>
> Key: NIFI-986
> URL: https://issues.apache.org/jira/browse/NIFI-986
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: 0.4.0
>
> Attachments: NIFI-986-2.patch, NIFI-986-3.patch, NIFI-986-4.patch,
> NIFI-986.patch
>
>
> It would be helpful for reporting tasks to have access to the audit
> information about flow design changes in order to report this information to
> external systems.
> The first use case for this would be reporting flow design changes to Atlas
> in order for Atlas to capture the flow design metadata.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
