We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Summary
Description for this feature.
Currently, we have OrNull aggregate function adaptor as follows:
An SQL with three aggregate functions.
[InnerState1 FLAG1] --- [InnerState2 FLAG2] --- [InnerState2 FLAG3]
we can optimize the FLAG state into one sate, like:
[InnerState1 ---- InnerState2 ---- InnerState2 FLAG]
It could save lots of allocations for high cardinality queries
The text was updated successfully, but these errors were encountered:
forsaken628
No branches or pull requests
Summary
Description for this feature.
Currently, we have OrNull aggregate function adaptor as follows:
An SQL with three aggregate functions.
we can optimize the FLAG state into one sate, like:
It could save lots of allocations for high cardinality queries
The text was updated successfully, but these errors were encountered: