NIFI-8269 - Add support for schema inference in ForkRecord processor when extracting array records

[pvillard31]

Summary

NIFI-8269 - Add support for schema inference in ForkRecord processor when extracting array records

At the moment the ForkRecord processor will require the writer to be configured with a schema corresponding to what will be output. We could make things more clever to inherit the schema from the reader and change it based on the operation being performed.

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

[pvillard31]

Made a small change to make sure that we compute the schema of the writer out of the schema of the reader if, and only if, the writer is configured to inherit the schema from the reader. This is not a breaking change as using the reader's schema in extract mode is not a working option today.

[github-actions]

Automated review is marking this PR as stale due to lack of updates in the past four months. This PR will be closed in 15 days if the stale label is not removed. This stale label and automated closure does not indicate a judgement of the PR, just lack of reviewer bandwidth and helps us keep the PR queue more manageable. If you would like this PR re-opened you can do so and a committer can remove the stale label. Or you can open a new PR. Try to help review other PRs to increase PR review bandwidth which in turn helps yours.