You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/10/04 18:24:00 UTC
[jira] [Commented] (NIFI-9272) Validation can show component is
valid when required property depends on another and is unset
[ https://issues.apache.org/jira/browse/NIFI-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424093#comment-17424093 ]
ASF subversion and git services commented on NIFI-9272:
-------------------------------------------------------
Commit a675023b71fc8ffcb9bc2c73dd29abed7cd9f3c6 in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a675023 ]
NIFI-9272: When determining if Property dependency is satisfied, consider property default values also
Signed-off-by: Joe Gresock <jg...@gmail.com>
This closes #5432.
> Validation can show component is valid when required property depends on another and is unset
> ---------------------------------------------------------------------------------------------
>
> Key: NIFI-9272
> URL: https://issues.apache.org/jira/browse/NIFI-9272
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.15.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Consider a Processor that has two properties, Property A and Property B. Property A is required and defaults to a value of "foo". Property B is required but depends on Property A being set to "foo" (i.e., Property B is required iff Property A is set to the value "foo").
> When the Processor is created, Property A will have its default value, "foo". But Property B will be unset. The Processor is still considered valid, even though the required Property B is unset.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)