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
Changing schema like adding a new field could take some time. Currently the timeout is hardcoded.
This is a problem for sql tool because one of the steps could get timeout and fails. Then the sql couldn’t rerun because some steps are already executed.
Making sql tool to be idempotent is ideal way but it’s a lot of work to do. The easier way to mitigate for now is allowing passing a timeout value for the command. The timeout value will be used for executing any sql query.
This will be much easier done after this PR to introduce passing a context.Context into the interface #4561
The text was updated successfully, but these errors were encountered:
While this has not been implemented, I found no reports of a timeout during a schema change. I think since we prefer adding new columns over changing data types for the fields.
Changing schema like adding a new field could take some time. Currently the timeout is hardcoded.
This is a problem for sql tool because one of the steps could get timeout and fails. Then the sql couldn’t rerun because some steps are already executed.
Making sql tool to be idempotent is ideal way but it’s a lot of work to do. The easier way to mitigate for now is allowing passing a timeout value for the command. The timeout value will be used for executing any sql query.
This will be much easier done after this PR to introduce passing a context.Context into the interface #4561
The text was updated successfully, but these errors were encountered: