forked from getredash/redash
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add 'expiration' to scheduled queries #15
Milestone
Comments
Merged
washort
pushed a commit
that referenced
this issue
Dec 12, 2017
washort
pushed a commit
that referenced
this issue
Dec 12, 2017
washort
pushed a commit
that referenced
this issue
Jan 8, 2018
washort
pushed a commit
that referenced
this issue
Jan 17, 2018
washort
pushed a commit
that referenced
this issue
Feb 6, 2018
washort
pushed a commit
that referenced
this issue
Feb 28, 2018
jezdez
pushed a commit
that referenced
this issue
Mar 5, 2018
emtwo
pushed a commit
that referenced
this issue
May 25, 2018
washort
pushed a commit
that referenced
this issue
Jul 25, 2018
jezdez
pushed a commit
that referenced
this issue
Aug 16, 2018
jezdez
pushed a commit
that referenced
this issue
Sep 6, 2018
jezdez
pushed a commit
that referenced
this issue
Nov 1, 2018
jezdez
pushed a commit
that referenced
this issue
Dec 12, 2018
jezdez
pushed a commit
that referenced
this issue
Dec 17, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes folks will set up a scheduled query with the intent of using it heavily for a short period of time, but after which it will be looked at sporadically or not at all. It might be useful to allow scheduled queries to have an expiration date, after which they will no longer be run.
The text was updated successfully, but these errors were encountered: