-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Destination Mysql: DV2 #36936
Merged
Merged
Destination Mysql: DV2 #36936
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
8236517
to
2965541
Compare
2965541
to
f40161c
Compare
This was referenced Apr 12, 2024
This stack of pull requests is managed by Graphite. Learn more about stacking. |
f40161c
to
129aa86
Compare
129aa86
to
c0b31d2
Compare
c0b31d2
to
94a3dc0
Compare
7a3147d
to
b15916f
Compare
a8dc68e
to
0a27153
Compare
This was referenced Apr 30, 2024
katmarkham
approved these changes
Apr 30, 2024
be73530
to
55e7bf2
Compare
55e7bf2
to
bdf95d2
Compare
bdf95d2
to
1dfc87d
Compare
be36130
to
9bb61fe
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/connectors
Connector related issues
area/documentation
Improvements or additions to documentation
breaking-change
Don't merge me unless you are ready.
connectors/destination/mysql
connectors/destination/mysql-strict-encrypt
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ported from #34609 to use the kotlin cdk.
As a reminder, we're not doing any safe_cast stuff for mysql. I ran some manual tests in the perf test workspace; see Slack for summary.
We're generating (basically) the same data types as legacy normalization. The only diffs are numbers changing from
float
->decimal(38, 9)
(float only has 32-bit precision, so was causing problems) and timestamps changing from text ->varchar(1024)
.Also we're adding new indexes - normalization was previously creating no indexes at all on the final table; we now have indexes on
(extracted_at, pk, cursor)
,(extracted_at)
, and(raw_id)
. Legacy normalization and dv2 both index the raw table on raw_id; dv2 also indexes onloaded_at, extracted_at
andextracted_at
.