exceptionfactory opened a new pull request, #10209: URL: https://github.com/apache/nifi/pull/10209
# Summary [NIFI-14865](https://issues.apache.org/jira/browse/NIFI-14865) Corrects configuration verification for the `ListAzureBlobStorage_v12` and `ListAzureDataLakeStorage` Processors. Prior to this correction, attempting to verify the configuration resulted in a `NullPointerException` due to the required `clientFactory` instance not being initialized. With the parent abstract Processor implementing the verify method and passing the Listing Mode, the corrected approach creates a new instance of the required `clientFactory` when called with the Configuration Verification option. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `./mvnw clean install -P contrib-check` - [X] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
