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
..
client.go	Remote storage reads based on oldest timestamp in primary storage (#3129)	2017-10-18 12:08:14 +01:00
client_test.go	Remove "package remote" garbage from license headers (#3304)	2017-10-17 02:26:38 +01:00
ewma.go	Initial port of remote storage to v2.	2017-07-12 12:27:57 +01:00
queue_manager.go	Fix leak of ticker in remote storage queue manager.	2017-10-09 19:44:03 +01:00
queue_manager_test.go	*: migrate to go-kit/log	2017-09-08 22:01:51 +05:30
read.go	Remote storage reads based on oldest timestamp in primary storage (#3129)	2017-10-18 12:08:14 +01:00
read_test.go	Remote storage reads based on oldest timestamp in primary storage (#3129)	2017-10-18 12:08:14 +01:00
storage.go	Remote storage reads based on oldest timestamp in primary storage (#3129)	2017-10-18 12:08:14 +01:00
write.go	Adapt storage APIs to uint64 references	2017-09-07 14:14:41 +02:00