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

bulkio,cdc: upgrade SDKs for 21.2 #65783

Closed
5 of 6 tasks
shermanCRL opened this issue May 27, 2021 · 5 comments
Closed
5 of 6 tasks

bulkio,cdc: upgrade SDKs for 21.2 #65783

shermanCRL opened this issue May 27, 2021 · 5 comments
Assignees
Labels
A-cdc Change Data Capture A-disaster-recovery C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-cdc

Comments

@shermanCRL
Copy link
Contributor

shermanCRL commented May 27, 2021

Let’s upgrade our dependencies for the following, for the 21.2 cycle:

Let’s be methodical, within reasonable time limits:

  • Pick a version that has baked for a while, not necessarily latest. Look for a high patch number.
  • Read the commit history between old and new version
    • Optionally, read the diff, though this may be too big
  • One commit for each, so we can bisect/revert

Have a look at how we did this in the previous cycle.

@shermanCRL shermanCRL added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-disaster-recovery labels May 27, 2021
@shermanCRL shermanCRL added A-cdc Change Data Capture and removed T-disaster-recovery labels May 27, 2021
@blathers-crl blathers-crl bot added the T-cdc label May 27, 2021
@amruss
Copy link
Contributor

amruss commented Jun 1, 2021

Going to leave in triage for now and revisit/assign in July

@adityamaru adityamaru self-assigned this Jun 28, 2021
@shermanCRL
Copy link
Contributor Author

Do we (did we) loop back to get the latest Google Cloud / GRPC? I see a note from @adityamaru that we should have an upstream fix.

@adityamaru
Copy link
Contributor

Yup it has been upgraded, I forgot to update this issue. Done now!

@shermanCRL
Copy link
Contributor Author

Did we intend to upgrade Vitess? Looks like we are using a fork? https://github.com/cockroachdb/vitess

@shermanCRL
Copy link
Contributor Author

Closing this as complete, even though we didn’t make a call on Vitess. Will create a new one for v22.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-cdc Change Data Capture A-disaster-recovery C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-cdc
Projects
No open projects
Archived in project
Development

No branches or pull requests

4 participants