-
Notifications
You must be signed in to change notification settings - Fork 29.2k
[SPARK-57479][SQL] Read and infer XML schema from tar archives #56572
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
+384
−40
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
e57124f
[SPARK-57479][SQL] Read and infer XML schema from tar archives
akshatshenoi-db 0511f7c
[SPARK-57479][SQL] Address review: per-mode XML archive reads
akshatshenoi-db 1727cc6
[SPARK-57479][SQL] Address review: hoist XML archive inference to the…
akshatshenoi-db fc6c690
[SPARK-57479][SQL] Address review: per-mode XML archive inference
akshatshenoi-db 122213a
[SPARK-57479][SQL] Address review: document optimized multi-line arch…
akshatshenoi-db b446b37
[SPARK-57479][SQL] Address review: centralize archive readArchive ove…
akshatshenoi-db b9486a0
[SPARK-57479][SQL] Address review: test malformed records through arc…
akshatshenoi-db File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non-blocking: the JSON archive support you're porting keeps
readArchiveconcrete in the base — it calls an abstractreadStream(in, parser(), schema)that each mode overrides, so theArchiveReader.readEntrieswiring lives in one place. HerereadArchiveis left abstract and both modes (TextInputXmlDataSource:239,MultiLineXmlDataSource:332) re-implement theArchiveReader(file.toPath).readEntries(conf) { ... }wrapper, differing only in the per-entry body.Mirroring JSON — a concrete base
readArchiveover an abstractreadStream(single-linereadStream= lines +FailureSafeParser; multi-linereadStream= the legacy/optimized branch) — would centralize that wiring and match the peer. Behavior is identical either way, so this is purely a maintainability/consistency call.