IssueRaiser

Intelligent Rollups and Querying of Aggregated Data

### Feature Request The database should support more intelligent rollups and querying of aggregated data. Currently, the only way to rollup data is through manually setting up continuous queries and then manually modifying the select statements to query that data which requires the user to know which retention policies exist rather than it being discovered automatically. **Proposal:** It should be simple for an administrator to setup rollups for an entire database and users should not need knowledge of the rollups for them to automatically start using them. Using rollups should be automatic and performant. **Current behavior:** Rollups require an administrator to create a retention policy and a continuous query like this: ``` CREATE RETENTION POLICY "5m" ON mydb DURATION 0s REPLICATION 1; CREATE CONTINUOUS QUERY mycq ON mydb BEGIN SELECT mean(*) INTO mydb."5m".:MEASUREMENT FROM /.*/ GROUP BY time(5m) END; ``` It then requires the user to query the mean of a measurement like this: ``` SELECT mean_value FROM mydb."5m".cpu ``` If the server is not running when an interval should be calculated, that interval will never be run and the user needs to run that query manually. There is no way to automatically reuse the information in continuous queries to backfill data either. Also, if data is written after the last calculation, it will never enter the aggregation. It is possible to obtain partial data, but this involves telling the continuous query to resample more fre

Posted by jsternberg on Aug 24, 2016, 12:17 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments

support (Sysadmin)

Intelligent Rollups and Querying of Aggregated Data

jsternbergAug 24, 2016, 12:17 AM

### Feature Request The database should support more intelligent rollups and querying of aggregated data. Currently, the only way to rollup data is through manually setting up continuous queries and then manually modifying the select statements to query that data which requires the user to know which retention policies exist rather than it being discovered automatically. **Proposal:** It should be simple for an administrator to setup rollups for an entire database and users should not need knowledge of the rollups for them to automatically start using them. Using rollups should be automatic and performant. **Current behavior:** Rollups require an administrator to create a retention policy and a continuous query like this: ``` CREATE RETENTION POLICY "5m" ON mydb DURATION 0s REPLICATION 1; CREATE CONTINUOUS QUERY mycq ON mydb BEGIN SELECT mean(*) INTO mydb."5m".:MEASUREMENT FROM /.*/ GROUP BY time(5m) END; ``` It then requires the user to query the mean of a measurement like this: ``` SELECT mean_value FROM mydb."5m".cpu ``` If the server is not running when an interval should be calculated, that interval will never be run and the user needs to run that query manually. There is no way to automatically reuse the information in continuous queries to backfill data either. Also, if data is written after the last calculation, it will never enter the aggregation. It is possible to obtain partial data, but this involves telling the continuous query to resample more fre

Comments (0)

No comments yet. Start the discussion.

Comment on this issue