New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update continuous queries to support different scheduling options #479

Closed
pauldix opened this Issue Apr 28, 2014 · 7 comments

Comments

Projects
None yet
7 participants
@pauldix
Member

pauldix commented Apr 28, 2014

Right now continuous queries run based on the group by interval given. They run after that period is elapsed. We should also support something in the syntax that lets the user specify how long after the group by interval has elapsed that they run the query.

Also, we should support not using a group by time interval at all and let them enter in a cron style syntax for when to run.

@jjmalina

This comment has been minimized.

jjmalina commented Apr 28, 2014

+1

I was trying to come up with a solution for having downsampled data that's specific to a timezone. So with something like this I think you could shift your group by interval by whatever your utc offset is and then include that in the series name.

edit: actually that wouldn't solve the whole problem since the group by time has to include your offset when it generates the intervals for the query.

@chobie

This comment has been minimized.

Contributor

chobie commented May 1, 2014

+1

also, it might add a function to getting exact time when the job was scheduled by continuous query.
as for now() returns current time when parsing query.

@saiaman

This comment has been minimized.

saiaman commented Jun 19, 2014

Any news about that, i'm experiencing issues with continuous queries not updating

@itayw

This comment has been minimized.

itayw commented Jun 26, 2014

+1

@pauldix

This comment has been minimized.

Member

pauldix commented Aug 19, 2014

I don't think this is the right fix for what's going on with continuous queries. Instead, they should actually be run online. Issue #510 tracks the development of that. Read through the description and my comment at the end and let me know if you think it will fix your issue related to this.

@pauldix pauldix closed this Aug 19, 2014

@aklmiu

This comment has been minimized.

aklmiu commented Nov 6, 2014

+1. Take for example utility company wanting to compute / plot electricity usage for each wall clock hour for a customer who subscribes to an on-peak/off-peak plan. I can imagine there is a way of doing this by doing some sort of fan out by the hour but it's much nicer to have a CQ with cron-like syntax that will fill the aggregated per hour usage into datetime and usage columns.

@fizerkhan

This comment has been minimized.

fizerkhan commented Nov 15, 2015

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment