[
https://issues.apache.org/jira/browse/NIFI-16324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-16324:
------------------------------
Description:
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.
was:
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
required property that should have its default.
This is the verify-path counterpart of NIFI-16242. Inheritance already
materializes required defaults into stored configuration. Verify should do the
same for applicable required defaults without overwriting explicit working or
request values. Optional defaults must not be inserted: inserting an optional
controlling default (for example {{SSL Mode=REQUIRED}}) can make dependent
required properties applicable and fail a configuration that should remain
valid.
Summary: Connector Verify Configuration does not include property
defaults (was: Connector Verify Configuration does not include required
property defaults)
> 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
>
> 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)
