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: upgrade SDKs for 21.1 #55748

Closed
6 tasks done
shermanCRL opened this issue Oct 20, 2020 · 6 comments
Closed
6 tasks done

bulkio: upgrade SDKs for 21.1 #55748

shermanCRL opened this issue Oct 20, 2020 · 6 comments
Assignees
Labels
A-disaster-recovery C-cleanup Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior. T-disaster-recovery

Comments

@shermanCRL
Copy link
Contributor

shermanCRL commented Oct 20, 2020

Let’s upgrade our dependencies for the following, for the 21.1 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
@blathers-crl
Copy link

blathers-crl bot commented Oct 20, 2020

Hi @shermanCRL, please add a C-ategory label to your issue. Check out the label system docs.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

@shermanCRL shermanCRL added the C-cleanup Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior. label Oct 20, 2020
@shermanCRL
Copy link
Contributor Author

shermanCRL commented Oct 20, 2020

VSCode makes this handy in go.mod FYI:

Screen Shot 2020-10-20 at 1 45 44 PM

@mwang1026 mwang1026 assigned dt and pbardea and unassigned dt Oct 20, 2020
@shermanCRL
Copy link
Contributor Author

Let’s have a look at our fork of Vitess in particular. We’re a couple of years behind (if I am reading correctly), and MySQL syntax changes cause future IMPORT failures.

@shermanCRL
Copy link
Contributor Author

Adding @HonoreDB to this issue, to have a look at Avro and Sarama (Kafka) libraries.

Not that there is a particular issue demanding such upgrades, but considering our long cycles, it’s best to not to get years behind.

@shermanCRL
Copy link
Contributor Author

Adding @miretskiy to have a look at the cloud SDKs. Best to do this earlier than later, if we are going to do this cycle.

@shermanCRL
Copy link
Contributor Author

cc’ing @bdarnell and @aaron-crl, please ping them on individual PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-disaster-recovery C-cleanup Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior. T-disaster-recovery
Projects
None yet
Development

No branches or pull requests

6 participants