[#12066] fix(jdbc-mysql): complete V3 type compatibility#12082
Draft
nevzheng wants to merge 5 commits into
Draft
[#12066] fix(jdbc-mysql): complete V3 type compatibility#12082nevzheng wants to merge 5 commits into
nevzheng wants to merge 5 commits into
Conversation
Code Coverage Report
Files
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
Define and document MySQL compatibility for the five Gravitino V3-native type families.
Nanosecond timestamps above MySQL's faithful precision, Variant, Unknown/Null, Geometry, and Geography are rejected before DDL. Existing timestamp precision 6 and below remains unchanged.
Why are the changes needed?
MySQL cannot recover the full identity and parameters of these V3-native families through the connector's current schema contract. Explicit rejection prevents silent narrowing and partial table creation.
Fix: #12066
Related: #12056
Shared JDBC preflight: #12065
Shared JDBC preflight PR: #12081
Does this PR introduce any user-facing change?
Yes. Unsupported V3-native schemas fail before DDL, while existing supported timestamp behavior is preserved.
How was this patch tested?
docs/jdbc-mysql-catalog.md.