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.

Sign up for GitHub

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

Jump to bottom

[FEEDBACK] Core: approximate aggregations #96

Open
AlmogBaku opened this issue Jul 27, 2022 · 2 comments
Open

[FEEDBACK] Core: approximate aggregations #96

AlmogBaku opened this issue Jul 27, 2022 · 2 comments
Labels
component/historian Related to the Historian enhancement New feature or request provider/aws Related to the AWS provider provider/redis Related to the Redis provider provider/snowflake Related to the Snowflake provider roadmap This issue is part of the roadmap

Comments

@AlmogBaku
Copy link
Member

AlmogBaku commented Jul 27, 2022 •
edited
Loading

Background

Some aggregations require computing values against the raw data.
Since Raptor is designed as "production first", saving the raw data on the state then calculating is expensive and requires an intensive calculation.

That includes:

  1. Distinct count
  2. Percentile

What do you propose to do?

Distinct count

Implement HyperLogLog - redis already support this out of the box

Percentile

We can use uddsketch or t-digest
https://docs.timescale.com/timescaledb/latest/how-to-guides/hyperfunctions/percentile-approx/advanced-agg/#percentile-approximation-advanced-aggregation-methods
https://github.com/influxdata/tdigest

What have you already tried?

No response

What else should we know?

No response
@AlmogBaku AlmogBaku added the enhancement New feature or request label Jul 27, 2022
@AlmogBaku AlmogBaku changed the title [FEEDBACK] Core: approximate aggregations [FEEDBACK] Core: approximate aggregations Jul 27, 2022
@AlmogBaku AlmogBaku added provider/snowflake Related to the Snowflake provider provider/redis Related to the Redis provider component/historian Related to the Historian provider/aws Related to the AWS provider labels Jul 27, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the stale This issue is stale label Sep 26, 2022
@AlmogBaku AlmogBaku removed the stale This issue is stale label Sep 26, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the stale This issue is stale label Nov 26, 2022
@AlmogBaku AlmogBaku removed the stale This issue is stale label Nov 27, 2022
@AlmogBaku AlmogBaku added the roadmap This issue is part of the roadmap label Jan 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/historian Related to the Historian enhancement New feature or request provider/aws Related to the AWS provider provider/redis Related to the Redis provider provider/snowflake Related to the Snowflake provider roadmap This issue is part of the roadmap
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AlmogBaku