[SPARK-58745][DOCS] Document missing JSON and XML data source options - #57971
Open
uros-b wants to merge 1 commit into
Open
[SPARK-58745][DOCS] Document missing JSON and XML data source options#57971uros-b wants to merge 1 commit into
uros-b wants to merge 1 commit into
Conversation
HyukjinKwon
approved these changes
Aug 12, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What changes were proposed in this pull request?
Adds table rows for options that are registered in the JSON and XML data sources but were missing from the option tables:
pretty,writeNonAsciiCharacterAsCodePointindent,multiLine,prefersDecimal,preferDateWhy are the changes needed?
Each is a real user-facing option registered via
newOption, so it passes option validation and can be set by any user, yet none appeared in the documented tables. The gap was found by diffing thenewOptionregistrations inJSONOptions/XmlOptionsagainst the<code>entries in each doc.Does this PR introduce any user-facing change?
No, other than newly documenting existing options.
How was this patch tested?
Documentation only. Every default and description is taken from source:
indentdefaults toXmlOptions.DEFAULT_INDENT(four spaces);multiLinedefaults totruefor XML;prefersDecimal/preferDateaffect schema inference andpreferDateis disabled whenspark.sql.legacy.timeParserPolicyisLEGACY;prettyandwriteNonAsciiCharacterAsCodePointare write-side and default tofalse.After this change the JSON table is complete. The XML table still omits
useLegacyXMLParser, a legacy parser-implementation switch, which is intentionally left undocumented.Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.8)