feat: add strict mode to json reader #4421
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
blinkseb
force-pushed
the
feat-json-strict-mode
branch
2 times, most recently
from
a82774e to
d72a87d
Compare
When strict mode is enabled, the parser will return an error if it encounters a column not present in the schema
blinkseb
force-pushed
the
feat-json-strict-mode
branch
from
d72a87d to
16d5610
Compare
tustvold
approved these changes
Jun 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
Hello,
This PR adds a new strict mode for the json reader. If strict mode is enabled, the parser will return an error if it encounters a column not present in the schema. It's useful for example if you want to ensure that your schema match 100% the JSON file.
The strict mode is added as a new option of
ReaderBuilder.What changes are included in this PR?
Are there any user-facing changes?