Skip to content
New issue

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

Improve LongSumAggregation and DoubleSumAggregation serde #16624

Merged
merged 1 commit into from
Mar 19, 2023

Conversation

sopel39
Copy link
Member

@sopel39 sopel39 commented Mar 19, 2023

Previously row(bigint, boolean, bigint, boolean)] was used for long sum serde (and similar for doubles).

Now it's row(bigint, bigint)

The extra bigint (row count) is still only required for WINDOW function but this PR slighly improves serde.

We can remove extra booleans because Long and Decimal aggregations use row count to determine if null should be outputted.

RN

General
* Improve `sum` aggregtion query performance. ({issue})

Release notes

( ) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@sopel39 sopel39 requested a review from raunaqmorarka March 19, 2023 10:27
@cla-bot cla-bot bot added the cla-signed label Mar 19, 2023
Previously row(bigint, boolean, bigint, boolean)] was used
for long sum serde (and similar for doubles).

Now it's row(bigint, bigint)

The extra bigint (row count) is still only required for WINDOW function
but this PR slighly improves serde.

We can remove extra booleans because Long and Decimal aggregations
use row count to determine if null should be outputted.
@sopel39 sopel39 merged commit 3df4134 into trinodb:master Mar 19, 2023
@sopel39 sopel39 deleted the ks/improve_serde branch March 19, 2023 13:07
@sopel39 sopel39 mentioned this pull request Mar 19, 2023
@github-actions github-actions bot added this to the 411 milestone Mar 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants