Xuanwo opened a new pull request, #23832:
URL: https://github.com/apache/datafusion/pull/23832

   ## Which issue does this PR close?
   
   - Part of #318.
   - Umbrella PR: #23738.
   - Depends on #23829 (and transitively #23828).
   
   ## Rationale for this change
   
   This is the serialization layer of the ASOF JOIN stack. It gives logical and
   physical ASOF plans explicit protobuf representations without coupling wire
   format review to SQL or DataFrame APIs.
   
   GitHub shows the cumulative stack because fork branches cannot be selected as
   upstream PR bases. The isolated diff for this layer is:
   
https://github.com/Xuanwo/datafusion/compare/xuanwo/asof-logical...xuanwo/asof-proto
   
   ## What changes are included in this PR?
   
   - Add protobuf messages and enum values for logical and physical ASOF joins.
   - Encode and decode equality keys, ordered match expressions, match 
direction,
     join constraint, and right output indices.
   - Regenerate `prost` and `pbjson` sources with the repository generator.
   - Add logical round trips for all four match directions.
   - Add physical `AsOfJoinExec` round-trip coverage.
   
   ## Are these changes tested?
   
   Yes:
   
   - `./datafusion/proto-models/regen.sh`
   - `cargo fmt --all`
   - `cargo clippy --all-targets --all-features -- -D warnings`
   - `cargo test -p datafusion-proto roundtrip_asof_join --all-features`
   - Extended workspace tests from the contributor guide
   
   ## Are there any user-facing changes?
   
   Logical and physical ASOF join plans can be serialized through
   `datafusion-proto`. This extends the protobuf wire format with new message
   variants.
   
   This PR should be reviewed and merged after #23829. After its dependencies
   squash-merge, this branch will be refreshed from `main` without rewriting its
   published history.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to