[NIFI-9272] Validation can show component is valid when required property depends on another and is unset

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.15.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 02/Oct/21 19:22
• Updated: 04/Oct/21 20:19
• Resolved: 04/Oct/21 20:19

Description

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.

Issue Links

• links to: GitHub Pull Request #5432