-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add support for cumulative counts #813
Comments
There is a discussion on this here: https://groups.google.com/forum/#!msg/influxdb/qU-_hi-8FwI/xfbkx40oEGgJ |
I'm new to influxdb and a way to count the cumulative of values would be very useful. |
@rtuin continuous queries are partially documented here: http://influxdb.com/docs/v0.9/concepts/continuous_queries.html but the docs are already out of date (see #2267). Right now there are no cumulative counts built into the query engine. Continuous queries are a great use case for cumulative counts, but they are not a good way to create cumulative counts. |
ping @corylanou - is this one to remove |
Removing help wanted tag while query engine is going through refactoring. |
As mentioned in my post to the mailing list we are experimenting with simplifying our open GitHub Issues. This feature request has been rolled into an aggregate issue for all function requests, so that we can close this issue until we are ready to work on it. You may continue to make comments here. Closing the issue does not mean we are rejecting this idea. |
This may be fixed now via #7388 Something like |
We should have an aggregate function that will return cumulative counts. For example, say we're grouping by 5m. The first 5m has 2 points, the second 5m has 1, and the last 5m has 3. A query like this:
Would produce three points with values 2, 1, and 3. The cumulative output should produce three points with values 2, 3, and 6.
The tricky part is that most people want this type of cumulative function on the output of continuous queries. So they would have to handle reading the last cumulative value from the continuous query output instead of having it from what was computed before.
The text was updated successfully, but these errors were encountered: