Description
For connections syncing large data, certain jobs that might break the machine can be pushed off to the weekend.
This will only be for select connection_ids which can be called large
-
Schema change
-
When user opens the schema changes modal, he will see all the changes along with a message
Accepting these changes, will schedule a schema job on {Date}
-
As soon as user accepts the schema change updates, we will schedule the schema change job (update catalog + reset + sync ) on the nearest Sunday.
-
The schema changes will still appear in the
Pending Action
tab along with the datetime of when it is scheduled. -
If before the next scheduled time, there is a new schema change and the user wants to accept those changes. He can do it and we will update the flow_run params & make sure it again scheduled on the nearest Sunday.
-
Store the
scheduled_at
andflow_run_id
in the backend. -
Connection Reset
-
When the user presses on the
Reset
connection button on the ingest page. A modal appears that asks for confirmation. -
The confirmation modal will also have the message
On clicking confirm, this will schedule a reset connection job on {Date}
-
Store the
scheduled_at
and theflow_run_id
for the upcoming reset job somewhere in the backend
Metadata
Assignees
Labels
Type
Projects
Status
Hold