uros-b opened a new pull request, #57971:
URL: https://github.com/apache/spark/pull/57971

   ### 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:
   
   - JSON: `pretty`, `writeNonAsciiCharacterAsCodePoint`
   - XML: `indent`, `multiLine`, `prefersDecimal`, `preferDate`
   
   ### Why 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 the `newOption` registrations 
in `JSONOptions`/`XmlOptions` against 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: 
`indent` defaults to `XmlOptions.DEFAULT_INDENT` (four spaces); `multiLine` 
defaults to `true` for XML; `prefersDecimal`/`preferDate` affect schema 
inference and `preferDate` is disabled when `spark.sql.legacy.timeParserPolicy` 
is `LEGACY`; `pretty` and `writeNonAsciiCharacterAsCodePoint` are write-side 
and default to `false`.
   
   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)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to