-
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 Finer-grained scheduling #187
Comments
Maybe add a refresh API call to the job that updates the dataset? Will give you the best result as it will always be in sync with the data update. |
@arikfr that is a good idea. We could build an Airflow operator that integrates with Re:dash, have you considered this before? |
I haven't but sounds like something that will be useful for many. Let me know if you need details on the refresh API. |
@fbertsch Based on the conversation above I'm pulling this out of the milestone 9 plan. I'm going to leave the ticket open for continued conversation. |
@arikfr mind pointing me at info on the API endpoints we would need for this task? |
The API call is: |
Upstream maintainers have been giving feedback on our proposed UI, we're currently integrating requested changes and will open a PR when the implementation is ready and tests are passing. |
Note: This probably needs a bit of a re-write and perhaps a change into React |
This has been ported to React and is undergoing final review upstream. |
* Closes #187: Add finer-grained scheduling - backend. * Closes getredash#2396 - Add finer-grained scheduling - frontend. * Fix linting issues * Rename ScheduleDialgo to .jsx
This is now done via getredash#2426. Awesome work @emtwo! 🎉 |
I just ran into a problem. I have a dataset that updates weekly, so I know at a certain time on Sundays the data will be ready. What I wanted to do was set my plots to update at that time, weekly; but all I could do was select "every 7 days", which doesn't indicate to me when that is. There could be a delay of up to 7 additional days with that option.
Instead I had to set them to update every day at XX:XX, which is not a great solution because now I'm running 7x the number of queries on the DB.
The text was updated successfully, but these errors were encountered: