Skip to content
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

schedule large connection jobs over the weekend #860

Open
2 tasks
Ishankoradia opened this issue Sep 18, 2024 · 1 comment
Open
2 tasks

schedule large connection jobs over the weekend #860

Ishankoradia opened this issue Sep 18, 2024 · 1 comment
Assignees

Comments

@Ishankoradia
Copy link
Contributor

Ishankoradia commented Sep 18, 2024

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 and flow_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 the flow_run_id for the upcoming reset job somewhere in the backend

@fatchat

@Ishankoradia Ishankoradia self-assigned this Sep 18, 2024
@Ishankoradia Ishankoradia converted this from a draft issue Sep 18, 2024
@fatchat fatchat moved this from In Progress to Discussion in Dalgo Oct 8, 2024
@fatchat fatchat moved this from Discussion to In Progress in Dalgo Oct 8, 2024
@nairabhishek73
Copy link
Contributor

nairabhishek73 commented Nov 7, 2024

Schema Change: https://jam.dev/c/3dbdf287-ea6d-4316-8128-9bac2c8d9bb0

  1. After I approve I still see it under pending actions, I can open it and then approve it again, confusing loop.
  • Once I approve it should indicate to me that its approved and scheduled, no pending action from the users end, only from the system's end.
  • If there is another schema change top the same connection it should show up separately as a pending action, if approved it should let me know that the other approval is overridden by the latest one and ask for confirmation
  1. Relatedly, but perhaps a separate issue, when I click on view I should see the connection name on the pop up box and then the details of the schema changes within that connection. Currently it doesn't show me connection name in the pop up box.

Tried connection reset, I don;t think that's done yet.

@fatchat fatchat moved this from In Progress to Hold in Dalgo Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Hold
Development

No branches or pull requests

2 participants