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.
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
Make state spillable in partitioned writer [databricks] #8667
Make state spillable in partitioned writer [databricks] #8667
Changes from 2 commits
13e3ab2
e349864
dce0f19
6eeb1a0
7fd33d6
e6a739b
f73790e
c056912
9825536
a921bfd
fbe0fb4
e5fe2e6
4922214
ab4633f
1420101
c989223
57bd89d
963a99a
9e3f5b3
f9cc9ec
bef9335
79ce06b
022e2d6
4fb645f
03d6105
1ade1f6
3c903d3
8c57ff2
22bafa4
8fe1d18
f556fbc
fd96e54
df425ce
f746816
3e0445b
87f22cc
54c83b3
a08e5a5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Not sure about this change. At this point we're actively trying to wield the batch, (we're in the middle of trying to write it), and thus it shouldn't be mandatory that it be spillable at this point, IMO. Also would like to keep the tracker API using pure Spark classes to mirror the columnar form of regular job/task stat trackers. If a particularly stat tracker does something complex that requires spill support (e.g.: Delta Lake stat gathering in their tracker), then that tracker can make the batch spillable when that makes sense.