[FLINK-39187][table] Add core built-in aggregate functions for BITMAP#27821
Open
dylanhz wants to merge 4 commits intoapache:masterfrom
Open
[FLINK-39187][table] Add core built-in aggregate functions for BITMAP#27821dylanhz wants to merge 4 commits intoapache:masterfrom
dylanhz wants to merge 4 commits intoapache:masterfrom
Conversation
Collaborator
…ve unused wrap method
…_OR_AGG, BITMAP_XOR_AGG
…nality return for bitmap aggregation
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
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 is the purpose of the change
This is the fifth PR for FLIP-556, following #27817.
This PR introduces built-in aggregate functions for the BITMAP type, including bitmap-returning aggregations and their cardinality-returning variants.
Brief change log
Verifying this change
This change added tests and can be verified as follows:
Does this pull request potentially affect one of the following parts:
@Public(Evolving): yesDocumentation