[
https://issues.apache.org/jira/browse/NIFI-14865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014569#comment-18014569
]
ASF subversion and git services commented on NIFI-14865:
--------------------------------------------------------
Commit bb27bebaffc01083b9ba7770595d2c92fd977e21 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=bb27bebaff ]
NIFI-14865 Fixed Config Verification for List Azure Processors
- Checked Listing Mode and created new Client Factory for configuration
verification
Signed-off-by: Pierre Villard <[email protected]>
This closes #10209.
> Configuration Verification Throws Exception in List Azure Processors
> --------------------------------------------------------------------
>
> Key: NIFI-14865
> URL: https://issues.apache.org/jira/browse/NIFI-14865
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{ListAzureDataLakeStorage}} and {{ListAzureBlobStorage_v12}} Processors
> extend from a class hierarchy that includes the {{AbstractListProcessor}},
> which supports configuration verification. The {{AbstractListProcessor}}
> implements the verify method and calls the {{performListing}} method with a
> Listing Mode, but the List Azure Processors do not check the Listing Mode
> when determining the Azure Client Factory that should be used. As a result,
> the Client Factory is null because the current implementations depend on this
> being initialized when the framework schedules the Processor. Checking the
> Listing Mode and optionally creating a Client Factory for the configuration
> verification should allow verification to work as expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
