chore: bump substrait version to use substrait spec v0.75.0 #17866
+117
−123
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.
Which issue does this PR close?
What changes are included in this PR?
Bump the
substrait
version tov0.75.0
by bumpingsubstrait-rs
tov0.60.0
.Note that bumping
substrait-rs
resulted in a bump ofprost
andpbjson-types
. These needed to be specified specifically in thedatafusion-substrait
crate because the currently released version ofarrow-rs
depends on different versions ofprost
andpbjson-types
. Once the next version ofarrow-rs
is released and updated indatafusion
, the special handling can be removed. The special override of the versions of those packages is noted in a comment in theCargo.toml
file.Are these changes tested?
There are no tests here, but there is no change to any logic within datafusion. It is simply a bump in a dependency. Technically the public API does change, but as noted in the issue description, there is no change to internal logic because uri / urn from substrait plans are not used.
Are there any user-facing changes?
Yes. Previously substrait plans of spec version
v0.74.0
were accepted, and nowv0.75.0
is accepted. However, this is a backwards compatible change. The only difference is the inclusion of additional urn-based fields in substrait plans. In a later PR, the old uri-based fields will be dropped, which will be a breaking change.