[
https://issues.apache.org/jira/browse/NIFI-16324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18113592#comment-18113592
]
ASF subversion and git services commented on NIFI-16324:
--------------------------------------------------------
Commit c7fa678a12c0a9e5c5774bb2590c85bdc76162bc in nifi's branch
refs/heads/NIFI-16315 from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c7fa678a12c ]
NIFI-16324 Include property defaults during Connector Verify Configuration
(#11651)
> Connector Verify Configuration does not include property defaults
> -----------------------------------------------------------------
>
> Key: NIFI-16324
> URL: https://issues.apache.org/jira/browse/NIFI-16324
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When Verify Configuration is run for a Connector configuration step, the
> framework merges request overrides onto the working configuration. Properties
> the user never set, because they already have a default, are absent from both
> and therefore missing from the merged context.
> Framework validation still sees those defaults. Connector
> {{verifyConfigurationStep}} implementations typically re-merge with
> {{createWithOverrides}} and then read {{getProperty(stepName,
> propertyName)}}, which does not apply descriptor defaults. Verify can pass
> property validation and then fail or behave incorrectly because the Connector
> sees {{null}} for a property that should have its default.
> Verify should include applicable descriptor defaults for unset properties
> whose dependencies are satisfied, without overwriting explicit working or
> request values.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
