[
https://issues.apache.org/jira/browse/NIFI-9722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497403#comment-17497403
]
ASF subversion and git services commented on NIFI-9722:
-------------------------------------------------------
Commit 9237b4e923eeac6016d0ac605abf36c745ef0c63 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9237b4e ]
NIFI-9722: Do not throw an Exception from verifyCanUpdateProperties when
property descriptor & parameter descriptor's sensitivities don't match -
instead allow the set to happen and let processor become invalid. Also, allow
values such as abc#{param} for ghost processors.
Signed-off-by: Joe Gresock <[email protected]>
This closes #5795.
> Cannot create a "ghost" processor if it references non-sensitive parameters
> ---------------------------------------------------------------------------
>
> Key: NIFI-9722
> URL: https://issues.apache.org/jira/browse/NIFI-9722
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.16.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I attempted to import a user's flow into my NiFi instance. The flow
> referenced processors that are not part of the standard Apache NiFi build. I
> got an error indicating that the flow couldn't be imported because a property
> is non-sensitive but referenced a sensitive parameter.
> This is problematic because for a "ghost" processor, all properties are
> considered sensitive. We already have validation setup so that the component
> becomes invalid in such a case. We should avoid throwing an Exception in the
> {{verify}} method and instead just let the component be invalid.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
