merge mysql v2 into v1 #48369
merge mysql v2 into v1 #48369
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
octavia-squidington-iii
added
area/connectors
octavia-squidington-iii
added
the
area/documentation
|
@clnoll I would like to try to merge this to master to test progressive rollout. |
There was a problem hiding this comment.
@clnoll I wanted to make sure that once merged to master, this won't upgrade all existing cloud connections.
There was a problem hiding this comment.
@rodireich that's right. The -rc suffix + enableProgressiveRollout: true will prevent it from upgrading any connections until some are pinned.
| @@ -23,7 +23,7 @@ jobs: | |||
| name: Connectors Version Increment Check | |||
| runs-on: connector-test-large | |||
| if: github.event.pull_request.head.repo.fork != true | |||
| timeout-minutes: 12 | |||
| timeout-minutes: 22 | |||
There was a problem hiding this comment.
This was timing out
| 3.0.0: | ||
| message: Add default cursor for cdc | ||
| upgradeDeadline: "2023-08-17" | ||
| releaseStage: alpha |
There was a problem hiding this comment.
@clnoll Should this return to alpha? I wasn't sure as source-mysql was already generally_available
There was a problem hiding this comment.
I'm not sure what the releaseStage refers to - it's not related to progressive rollouts. Maybe @alafanechere knows?
There was a problem hiding this comment.
Oh this is my favorite genre! /cc @nataliekwong and @alex-gron. TLDR I think is just keep it what it was :D
There was a problem hiding this comment.
I think it only affects internal reporting, not actual product behavior
There was a problem hiding this comment.
I'm not sure actually what this affects, sorry I can't be of more help!
|
/giphy HUGE |
What
Progressive rollout to source-mysql V2