NIFI-15180 Log initialization errors in ConsumeKinesis

[awelless]

Summary

NIFI-15180

So far the issues which failed Scheduler initialization are caused by misconfiguration and are not recoverable.
Like inability to access a Dynamodb/Kinesis endpoint due to invalid network rules, or an inability to act on a table/stream due to absent iam permissions.

If KCL scheduler fails to initialize, the processor's initialization fails as well.

The change was tested manually.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-15180
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-15180

Pull Request Formatting

• Pull Request based on current revision of the main branch
• 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

• Build completed using ./mvnw clean install -P contrib-check
  • JDK 21
  • JDK 25

Licensing

• New dependencies are compatible with the Apache License 2.0 according to the License Policy
• New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files

[awelless]

This branch is active only when a scheduler was shutdown, but no initialization error was provided. However, I didn't observe this behavior while testing.

[exceptionfactory]

If that is the case, it seems worth mentioning. Mentioning "check the application logs for more details" is not helpful because it already appears in the logs, so the message should be shortened.

[awelless]

The reason behind "check the application logs for more details" is that the error text is visible in a bulletin.
When an initialization error is present, it's logged and, therefore available in the bulletin too.

When error is not available for some reason, the bulletin will just mention that initialization failed. However, additional details may be present in application logs, which aren't available in NiFi canvas.

Is it expected for the NiFi users to inspect application logs as well? If so, then the "check the application logs for more details" part is not needed.

[exceptionfactory]

Bulletin messages are limited in nature, and often require checking logs as a general practice. More recent adjustments have introduced stack trace visibility for Bulletins, but checking the logs is almost always necessary, so including the statement in a message is redundant.

[exceptionfactory]

Thanks for adjusting the approach and implementing waiting on successful initialization @awelless. This looks like a good way forward in general. I recommended a few adjustments.

[exceptionfactory]

If that is the case, it seems worth mentioning. Mentioning "check the application logs for more details" is not helpful because it already appears in the logs, so the message should be shortened.

[exceptionfactory]

Thanks for the responses, this looks close to completion, I noted a few more minor recommendations.

[exceptionfactory]

Thanks for working through the feedback @awelless, the latest version looks good. +1 merging