[
https://issues.apache.org/jira/browse/NIFI-5561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597299#comment-16597299
]
ASF GitHub Bot commented on NIFI-5561:
--------------------------------------
Github user MikeThomsen commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2973#discussion_r213980541
--- Diff:
nifi-nar-bundles/nifi-site-to-site-reporting-bundle/nifi-site-to-site-reporting-task/src/main/java/org/apache/nifi/reporting/SiteToSiteProvenanceReportingTask.java
---
@@ -151,6 +151,25 @@
.addValidator(StandardValidators.NON_EMPTY_VALIDATOR)
.build();
+ static final PropertyDescriptor FILTER_COMPONENT_NAME = new
PropertyDescriptor.Builder()
+ .name("s2s-prov-task-name-filter")
+ .displayName("Component Name to Include")
+ .description("Regular expression to filter the provenance events
based on the component name. Only the events matching the regular "
+ + "expression will be sent. If no filter is set, all the
events are sent. If multiple filters are set, the filters are cumulative.")
+ .required(false)
+ .addValidator(StandardValidators.REGULAR_EXPRESSION_VALIDATOR)
--- End diff --
Our CM story is still really developing at this point, so I would say
whatever could be done to help facilitate making it easier for admins to
configure NiFi in a standardized way is going to make the a little happier even
if it's just "copy and paste this EL string."
> Add component name filtering to S2S Provenance Reporting Task
> -------------------------------------------------------------
>
> Key: NIFI-5561
> URL: https://issues.apache.org/jira/browse/NIFI-5561
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
>
> I'd like to add component name as a way to filter events sent by the
> SiteToSite Provenance Reporting task so that, for example, all events
> generated by components containing "Prov" in the name are picked.
> This will be much easier to manage rather than component IDs as the ID of a
> component could change when a workflow is promoted from one environment to
> another in a CI/CD pipeline.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)