Thanks
I guess it would work but.. it would cause additional cpu usage as well.
In our case we can have data passing in up to 30 minutes late. If we do
resample every 6h it means then first 6h we'll have not very accurate data. And
then we'll also have 2 additional calls which won't do anything
CQs always run against an interval relative to now. There is no way to run
CQs on a delay, but simply set the RESAMPLE EVERY clause to make sure you
re-query after all the data has arrived.
For instance, assuming it's a one day CQ
CREATE CONTINUOUS QUERY MINUTE ON db RESAMPLE EVERY 6h FOR 2d
begi
Thanks
I guess it can work for 1h but I also have same queries for 1d and 30d
intervals. So I'm looking for a way to allow my data be little late (up to 30
mins) and recalculate cache after this 30-minutes windows closed.
--
Remember to include the InfluxDB version number with all issue report
On Wed, Sep 21, 2016 at 8:14 AM, wrote:
> Hi.
> I would like to solve following issue:
> I have data coming in to the system with some delays. So when CQ runs some
> data is missing. So I want to resample it.
>
> #1 runs every minute. I want to go back in time by 30 minutes
> CREATE CONTINUOUS QU
Hi.
I would like to solve following issue:
I have data coming in to the system with some delays. So when CQ runs some data
is missing. So I want to resample it.
#1 runs every minute. I want to go back in time by 30 minutes
CREATE CONTINUOUS QUERY MINUTE ON db RESAMPLE FOR 30m
begin
select ...
