-
Notifications
You must be signed in to change notification settings - Fork 10
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
We should provide time-out
functionality
#107
Comments
I think this should be possible to implement with something like I think there are some other questions about the default behaviour - I assume this is to have no timeout rather than assert that no cohort should take more than 10 hours to execute? |
Think we'll need to think about the behavior but seems possible and reasonable. I suppose we'd want to apply a uniform timeout to call cohort generations in this case. I agree with @azimov that we'd want to test this out to make sure that the timeout plays nicely with database connections. |
I have an initial implementation of this feature on the My main concern with the current implementation is the database connection handling. The The work on this branch could be further extended such that when a I was also having a bit of trouble with the unit tests for this functionality so stopped short of getting this into the v0.10 release. If there is a desire to move this functionality forward, please let me know and I can try to finish it up for another v0.x release. |
Really helpful in some data sources would be a
time-out
feature in which the package kills a query (and then importantly continues onto the next task) that executes for longer than a specified time.Might this be easily feasible @azimov @anthonysena ?
The text was updated successfully, but these errors were encountered: