You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I think this should be possible to implement with something like R.utils::withTimeout though we would need to test how well this plays with DatabaseConnector and its calls to java.
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.
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: