Skip to content

[#12069] fix(jdbc-starrocks): complete V3 type compatibility#12085

Draft
nevzheng wants to merge 5 commits into
apache:mainfrom
nevzheng:codex/v3-phase2-starrocks
Draft

[#12069] fix(jdbc-starrocks): complete V3 type compatibility#12085
nevzheng wants to merge 5 commits into
apache:mainfrom
nevzheng:codex/v3-phase2-starrocks

Conversation

@nevzheng

Copy link
Copy Markdown
Collaborator

What changes were proposed in this pull request?

Define and document StarRocks compatibility for the five Gravitino V3-native type families.

Precision-9 and timezone-aware timestamps, Variant, Unknown/Null, Geometry, and Geography are rejected before DDL. Existing unparameterized timezoneless timestamp behavior remains the supported control.

Why are the changes needed?

The connector cannot preserve V3 timestamp precision/timezone identity or the complete semantics of the other V3-native families. Explicit validation avoids silently changing the declared schema.

Fix: #12069

Related: #12056

Shared JDBC preflight: #12065

Shared JDBC preflight PR: #12081

Does this PR introduce any user-facing change?

Yes. Parameterized or timezone-aware V3 timestamp schemas and the other unsupported V3 families now fail before DDL.

How was this patch tested?

  • Compared unparameterized Timestamp controls with precision-3, precision-9, and timezone-aware cases.
  • Added converter and SQL-generation rejection coverage.
  • Covered Docker no-table behavior.
  • Updated docs/jdbc-starrocks-catalog.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Subtask] Complete V3 type compatibility for the StarRocks catalog

1 participant