NIFI-13542: Fix missing max string length parameter usage in multiple…

[mark-bathori]

… JSON Readers and Schema Access Strategy

Summary

NIFI-13542

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-00000
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

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 mvn clean install -P contrib-check
  • JDK 21

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

[exceptionfactory]

Thanks for addressing this issue @mark-bathori.

Most of the changes look straightforward, but I noted one question on the YAML Factory. In earlier versions of Jackson, the YAML implementation did not use or enforce the string length limitations, which is why the related properties were not exposed. Is that changed in more recent versions of Jackson?

[arpadboda]

Thanks for digging down in this topic and fixing these issues, LGTM!

[exceptionfactory]

Thanks for the reply @mark-bathori, and thanks for the review @arpadboda! +1 merging