Thibault Chataigner bf4a279a91 Remote storage reads based on oldest timestamp in primary storage (#3129) ... Currently all read queries are simply pushed to remote read clients. This is fine, except for remote storage for wich it unefficient and make query slower even if remote read is unnecessary. So we need instead to compare the oldest timestamp in primary/local storage with the query range lower boundary. If the oldest timestamp is older than the mint parameter, then there is no need for remote read. This is an optionnal behavior per remote read client. Signed-off-by: Thibault Chataigner <t.chataigner@criteo.com>		2017-10-18 12:08:14 +01:00
..
remote	Remote storage reads based on oldest timestamp in primary storage (#3129)	2017-10-18 12:08:14 +01:00
tsdb	Remote storage reads based on oldest timestamp in primary storage (#3129)	2017-10-18 12:08:14 +01:00
buffer.go	Fix error where we look into the future. (#2829)	2017-06-13 07:22:27 +02:00
buffer_test.go	Fix error where we look into the future. (#2829)	2017-06-13 07:22:27 +02:00
fanout.go	Remote storage reads based on oldest timestamp in primary storage (#3129)	2017-10-18 12:08:14 +01:00
fanout_test.go	Remove "package remote" garbage from license headers (#3304)	2017-10-17 02:26:38 +01:00
interface.go	Remote storage reads based on oldest timestamp in primary storage (#3129)	2017-10-18 12:08:14 +01:00