Derive AggregateUDFImpl
equality, hash from Eq
, Hash
traits
#17130
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.
Follows similar change for
WindowUDFImpl
, i.e. the 8494a39 commit.Previously, the
AggregateUDFImpl
trait containedequals
andhash_value
methods with contracts following theEq
andHash
traits. However, the existence of default implementations of these methods made it error-prone, with many functions (scalar, aggregate, window) missing to customize the equals even though they ought to. There is no fix to this that's not an API breaking change, so a breaking change is warranted.Removing the default implementations would be enough of a solution, but at the cost of a lot of boilerplate needed in implementations.
Instead, this removes the methods from the trait, and reuses
DynEq
,DynHash
traits used previously only for physical expressions. This allows for functions to provide their implementations using no more than#[derive(PartialEq, Eq, Hash)]
in a typical case.WindowUDFImpl
equality, hash fromEq
,Hash
traits #17081AggregateUDFImpl
) #16869AggregateUDFImpl::{equals,hash_value}
withUdfHash
,UdfEq
traits #16872