Support native Delta OPTIMIZE writes on GPU for DBR 14.3 and 17.3 [databricks] - #15942
Open
nartal1 wants to merge 1 commit into
Open
Support native Delta OPTIMIZE writes on GPU for DBR 14.3 and 17.3 [databricks]#15942nartal1 wants to merge 1 commit into
nartal1 wants to merge 1 commit into
Conversation
Contributor
Greptile SummaryAdds GPU acceleration for the nested Delta write performed by native, non-clustered Databricks
Confidence Score: 5/5The PR appears safe to merge; no actionable regression remains in the changes since the previous review. The latest changes consolidate native OPTIMIZE plan validation into the shared helper without weakening the new test’s same-plan GPU requirements or changing existing callers, and the full PR retains explicit fallback guards for unsupported Delta writes. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart LR
A[Databricks OPTIMIZE command on CPU] --> B{Native non-clustered OPTIMIZE?}
B -->|No| C[Retain CPU write path]
B -->|Yes| D[GpuDataWritingCommandExec]
D --> E[GpuWriteFilesExec]
E --> F[GPU Parquet output]
F --> G[Delta transaction commit and statistics]
Reviews (2): Last reviewed commit: "Support native Delta OPTIMIZE writes on ..." | Re-trigger Greptile |
Signed-off-by: Niranjan Artal <nartal@nvidia.com>
nartal1
force-pushed
the
write_into_delta_command
branch
from
September 9, 2026 23:09
e384bb8 to
8ae72ac
Compare
Collaborator
Author
|
build |
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
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.
Fixes #11169.
Description
On DBR 14.3 and 17.3, native non-clustered Delta
OPTIMIZEusesWriteIntoDeltaCommandoutside the atomic write context. cudf-spark therefore rejected the command, causingDataWritingCommandExecandWriteFilesExectofall back to CPU.
This PR:
OPTIMIZEwrites on GPU when the input is aTahoeBatchFileIndexwith action typeOptimize.OPTIMIZEpath.GpuDataWritingCommandExecandGpuWriteFilesExec.The outer Databricks
OPTIMIZEcommand remains on CPU. This change accelerates its nested data writing plan.Testing
Added
test_delta_native_optimize_gpu_write, which isolates the native Databricks path and verifies:OPTIMIZEreduces the file count.Performance
Benchmark on DBR 17.3 with an NVIDIA T4 GPU:
OPTIMIZEstatement was timed.Checklists
Documentation
Testing
(Please provide the names of the existing tests in the PR description.)
Performance