[#12067] fix(jdbc-postgresql): complete V3 type compatibility#12083
Draft
nevzheng wants to merge 5 commits into
Draft
[#12067] fix(jdbc-postgresql): complete V3 type compatibility#12083nevzheng 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 PostgreSQL compatibility for the five Gravitino V3-native type families.
Timestamp precision greater than 6, Variant, Unknown/Null, Geometry, and Geography writes are rejected before SQL. Native JSON and PostGIS reads remain explicit external types until their complete metadata can be recovered faithfully.
Why are the changes needed?
JSON/JSONB do not implement the complete Variant contract, and the current PostGIS read path cannot preserve all subtype, SRID, and Geography edge-algorithm semantics. Early rejection prevents a lossy write contract.
Fix: #12067
Related: #12056
Shared JDBC preflight: #12065
Shared JDBC preflight PR: #12081
Does this PR introduce any user-facing change?
Yes. Unsupported V3-native writes now fail before SQL generation instead of relying on an incomplete database mapping.
How was this patch tested?
docs/jdbc-postgresql-catalog.md.