V0.51 exaforce rebase our changes#31
Merged
sundaresanr merged 1 commit intov0.51-exaforcefrom Apr 17, 2026
Merged
Conversation
sundaresanr
added a commit
that referenced
this pull request
Apr 17, 2026
Revert PR #31 (V0.51 exaforce rebase)
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
2 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.
Summary
v0.51-exaforce, bringing forward all changes that had accumulated onv0.45-exaforce.changescommit on top of upstreamv0.51.0.Parity with v0.45-exaforce
Verified (byte-identical):
lib/codecs/src/encoding/format/parquet.rs(parquet codec)src/sources/azure_blob/queue.rs(azure blob queue source)src/internal_events/azure_queue.rssrc/azure/mod.rsDifferences in
aws_s3/sink.rs,gcp.rs,codecs/encoding/config.rsare only upstream-v0.51 rustfmt/clippy modernization (inline format args,saturating_sub, etc.) — no exaforce behavior lost.Parquet crate present in
Cargo.lock.Notes
v0.51-exaforce).operationsrepogoservices/vector_exec_sources/Dockerfilecurrently pinsvector-base:v0.45-exaforce-cfe6effa. Once this PR merges andexaforce-publish.yamlruns onv0.51-exaforce, that pin can be bumped to the newv0.51-exaforce-<short-sha>tag.