NIFI-14190 Add Max String Length to ValidationJson

[NimrodAvni]

Summary

NIFI-14190

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 the contribution @NimrodAvni! The overall approach looks good, I just noted two convention-related things, and otherwise this should be good.

[exceptionfactory]

The variable name should be lowercased to mapper since it is no longer static.

Suggested change

	private ObjectMapper MAPPER;
	private ObjectMapper mapper;

[dan-s1]

@exceptionfactory I was wondering whether this should be done in light of the changes you made in #9648. Do want ObjectMapper to be an instance variable in this processor?

[exceptionfactory]

Thanks @dan-s1. This does result in creating an instance of ObjectMapper per Processor instance, but since it is created in onScheduled it is the correct place for initialization.

[exceptionfactory]

Since this is a new property, the displayName is not needed.

Suggested change

.displayName("Max String Length")

[exceptionfactory]

Thanks for making the adjustments @NimrodAvni, the latest version looks good! +1 merging