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

Plans for splitting up PROCESS_QUEUE table #72

Open
ibodrov opened this issue Aug 18, 2020 · 1 comment
Open

Plans for splitting up PROCESS_QUEUE table #72

ibodrov opened this issue Aug 18, 2020 · 1 comment
Labels
wip Work in progress, do not merge

Comments

@ibodrov
Copy link
Collaborator

ibodrov commented Aug 18, 2020

We need to split the PROCESS_QUEUE table up.

In order to do that we need to plan some changes across several releases.

Here's the approximate plan:

  • release 1.63.0:
    • create a new PROCESS_STATUS table:
      • INSTANCE_ID
      • CREATED_AT
      • CURRENT_STATUS
      • LAST_UPDATED_AT
    • create necessary indicies;
    • create a trigger to fill PROCESS_STATUS table in.
  • release (+ 1 month from 1.63.0):
    • drop the trigger;
    • make PROCESS_QUEUE.CURRENT_STATUS and LAST_UPDATED_AT nullable, stop using those columns in the code;
    • (optionally) drop PROCESS_QUEUE.CURRENT_STATUS and LAST_UPDATED_AT columns.
@ibodrov ibodrov added the wip Work in progress, do not merge label Aug 18, 2020
@ibodrov
Copy link
Collaborator Author

ibodrov commented Aug 18, 2020

cc @brig, @mtkunkel, @benbroadaway

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wip Work in progress, do not merge
Development

No branches or pull requests

1 participant