influxdb/coordinator
Jonathan A. Sternberg f20cab6e99 Implicitly decide on the lower limit for fill queries when none is present
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.
2017-10-05 15:56:44 -05:00
..
config.go Separate the query engine into a separate package 2017-08-16 13:38:43 -05:00
config_test.go Remove old cluster config options 2016-05-11 12:59:30 -06:00
meta_client.go initial fga work 2017-05-26 13:16:27 -07:00
meta_client_test.go initial fga work 2017-05-26 13:16:27 -07:00
points_writer.go Merge pull request #8481 from influxdata/jw-subscriber 2017-06-13 15:55:43 -06:00
points_writer_internal_test.go Fixes issue with point hitting wrong shard 2016-10-19 21:06:29 +01:00
points_writer_test.go Merge pull request #8481 from influxdata/jw-subscriber 2017-06-13 15:55:43 -06:00
shard_mapper.go Implicitly decide on the lower limit for fill queries when none is present 2017-10-05 15:56:44 -05:00
shard_mapper_test.go Pass the select options to the shard mapper again 2017-08-24 09:55:02 -05:00
statement_executor.go auth: add series auth to 'show tag values' 2017-09-27 20:01:18 -04:00
statement_executor_test.go auth: add series auth to 'show tag values' 2017-09-27 20:01:18 -04:00