feat(load): add bounded Arrow IPC ingestion path - #28145
Open
iamlinjunhong wants to merge 39 commits into
Open
Conversation
iamlinjunhong
requested review from
LeftHandCold,
XuPeng-SH,
aptend,
aunjgr and
fengttt
as code owners
September 4, 2026 08:09
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
iamlinjunhong
force-pushed
the
m-23684
branch
from
September 4, 2026 08:29
55b4b75 to
f6e0cb9
Compare
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
5 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 type of PR is this?
Which issue(s) this PR fixes:
Closes #23684
What this PR does / why we need it:
Adds a bounded Apache Arrow IPC File/Stream ingestion path to
LOAD DATA. The implementation is LOAD-only and preserves normal statement atomicity, schema validation, range identity checks, and cleanup/lease accounting.Rollout and compatibility
cn.frontend.arrow-load.enabled=true; S3/stage and distributed execution additionally require their explicit gates on every executing CN.force-materialize=trueis the immediate rollback/diagnostic path for borrowed backing.Design and readiness
The design artifact is an implementation proposal and records that independent approval remains pending; no unapproved Arrow surface is default-reachable. The readiness record also lists the still-required aggregate-admission, provider, mixed-version artifact, deployment, and owner evidence before broader rollout.
Validation
Focused configuration, planner, remote-protocol, external-reader/worker-gate, and real MySQL public-path gate tests pass locally using the repository CGo test wrapper. Required CI is running for the current head.