[
https://issues.apache.org/jira/browse/NIFI-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-7106:
---------------------------------
Description:
In addition to the {{parentId}}, it would be useful to also have the
{{parentName}} (meaning the name of the parent process group containing the
component), as well as the {{parentPath}} (meaning the process groups path from
the root process group to the process group containing the component).
Since reporting tasks are defined at global level, it's up to the user
configuring the reporting task to evaluate if exposing the values is a risk or
not. If it is, using the record writer, it is possible to remove the
corresponding fields with the appropriate schema.
was:
In addition to the {{parentId}}, it would be useful to also have the
{{parentName}} (meaning the name of the parent process group containing the
component).
Since reporting tasks are defined at global level, it's up to the user
configuring the reporting task to evaluate if exposing this value is a risk or
not. If it is, using the record writer, it is possible to remove this field
with the appropriate schema.
> Add parent name and parent path in SiteToSiteStatusReportingTask
> ----------------------------------------------------------------
>
> Key: NIFI-7106
> URL: https://issues.apache.org/jira/browse/NIFI-7106
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In addition to the {{parentId}}, it would be useful to also have the
> {{parentName}} (meaning the name of the parent process group containing the
> component), as well as the {{parentPath}} (meaning the process groups path
> from the root process group to the process group containing the component).
> Since reporting tasks are defined at global level, it's up to the user
> configuring the reporting task to evaluate if exposing the values is a risk
> or not. If it is, using the record writer, it is possible to remove the
> corresponding fields with the appropriate schema.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
