On Thursday, October 27, 2016 at 9:43:39 AM UTC-5, Sean Beckett wrote: > I'm not sure I understand. The COUNT() function is creating new data, and the > timestamps will the the start of the 1d interval over which the count is > being applied. > > > What timestamp are you trying to preserve? > > > On Wed, Oct 26, 2016 at 8:27 PM, <[email protected]> wrote: > On Wednesday, October 26, 2016 at 12:38:12 PM UTC-5, Sean Beckett wrote: > > > See Issue 3: Backfilling results for older data on > > https://docs.influxdata.com/influxdb/v1.0/query_language/continuous_queries/#common-issues-with-basic-syntax > > for details. Apologies it is difficult to find. > > > > > > > > > > > > On Wed, Oct 26, 2016 at 7:23 AM, <[email protected]> wrote: > > > On Tuesday, October 25, 2016 at 8:55:49 PM UTC-5, [email protected] wrote: > > > > > > > I have this continuous query in version 1.02 of influx > > > > > > > > > > > > > > CREATE CONTINUOUS QUERY cqDailyTasks ON r1metrics BEGIN SELECT count(*) > > > INTO metrics..dailyTasks FROM metrics..tasks GROUP BY time(1d), * END > > > > > > > > > > > > > > I have data since 12 of Oct > > > > > > > > > > > > > > This continous query did not back fill to the 12 as i expected. What did > > > i do wrong? > > > > > > > > > > > > > > I tried adding a RESAMPLE EVERY 1m and that did add some data but not > > > till the 12. > > > > > > > > > > > > > > Thanks > > > > > > > > > > > > I figure it out. It looks like you have to backfill manually by running an > > "into" query > > > > > > > > > > > > The query I ran is > > > > > > > > > > > > SELECT count(*) INTO r1metrics..dailyTasks FROM r1metrics..tasks where time > > < now() GROUP BY time(1d) > > > > > > > > > > > > -- > > > > > > Remember to include the version number! > > > > > > --- > > > > > > You received this message because you are subscribed to the Google Groups > > "InfluxData" group. > > > > > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > > > > > To post to this group, send email to [email protected]. > > > > > > Visit this group at https://groups.google.com/group/influxdb. > > > > > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/influxdb/9dee0832-f9d2-44e4-a3c8-e62c75440b0d%40googlegroups.com. > > > > > > > > > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Sean Beckett > > > Director of Support and Professional Services > > > InfluxDB > > > > The is one problem when you perform the "into" select. That is the > timestamps for the records are for the time you run the query so you will not > be able to use the time in the query. Is there anything to work around that? > > > > -- > > Remember to include the version number! > > --- > > You received this message because you are subscribed to the Google Groups > "InfluxData" group. > > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > > To post to this group, send email to [email protected]. > > Visit this group at https://groups.google.com/group/influxdb. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/influxdb/06ed902c-b13f-4e7c-bb91-af66386533fb%40googlegroups.com. > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > > Sean Beckett > Director of Support and Professional Services > InfluxDB
i recreated the continuous query and redid the back fill. Everything is working as expected. I thought the time stamps on the back fill records were incorrect. I was wrong, they are fine. -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/e240e8a5-1a86-4ae7-9076-be2341d12bd9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
