Skip to content

NIFI-12456 Enabled JsonTreeReader and JsonPathReader to parse JSON leniently.#11208

Open
dan-s1 wants to merge 1 commit intoapache:mainfrom
dan-s1:NIFI-12456
Open

NIFI-12456 Enabled JsonTreeReader and JsonPathReader to parse JSON leniently.#11208
dan-s1 wants to merge 1 commit intoapache:mainfrom
dan-s1:NIFI-12456

Conversation

@dan-s1
Copy link
Copy Markdown
Contributor

@dan-s1 dan-s1 commented May 5, 2026

Summary

NIFI-12456
The changes in this PR now allow for JsonTreeReader and JsonPathReader to parse incoming JSON leniently which includes allowing

  • Java comments (/**/ and //)
  • Yaml comments (start of line begins with #)
  • leading plus sign in numbers (e.g. +123)
  • leading zeros in numbers (e.g. 0001)
  • "missing" decimal numbers to end with a decimal point (e.g. 123.)
  • "missing value" in an array (i.e. sequence of two commas, without value in-between e.g. ["A",,"C"]),
  • trailing comma in an array or member in an object
  • use of single quotes for quoting strings (i.e. use of an apostrophe)
  • use of unquoted field names

Tracking

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

Issue Tracking

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 contains commits signed with a registered key indicating Verified status

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

@exceptionfactory exceptionfactory self-requested a review May 5, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant