This allows the query:
SELECT mean(value) FROM cpu GROUP BY time(1d)
To function in some way that makes sense. The upper limit is implicitly
the `now()` starting time and the lower limit will be whichever interval
the lowest point falls into.
When no lower bound is specified and `max-select-buckets` is specified,
the query will only consider points that would satisfy
`max-select-buckets`. So if you have one point written in 1970, have
another point within the last minute, and then do the above query with
`max-select-buckets` being equal to 10, the older point from 1970 will
not be considered.
|
||
|---|---|---|
| .. | ||
| config.go | ||
| config_test.go | ||
| meta_client.go | ||
| meta_client_test.go | ||
| points_writer.go | ||
| points_writer_internal_test.go | ||
| points_writer_test.go | ||
| shard_mapper.go | ||
| shard_mapper_test.go | ||
| statement_executor.go | ||
| statement_executor_test.go | ||