Vamsi-klu opened a new pull request, #28492: URL: https://github.com/apache/flink/pull/28492
## What is the purpose of the change The data types reference page documents `TIMESTAMP WITH TIME ZONE` with full declaration syntax (`TIMESTAMP(p) WITH TIME ZONE`), which makes it look like a usable SQL type. In reality the type currently **only exists as a logical type** and is not supported by Flink SQL yet — reading/casting it is unimplemented (tracked by [FLINK-20869](https://issues.apache.org/jira/browse/FLINK-20869)), and the SQL JDBC driver explicitly throws: > `TIMESTAMP WITH TIME ZONE is not supported, use TIMESTAMP or TIMESTAMP_LTZ instead` The missing caveat has repeatedly confused users (see [FLINK-23882](https://issues.apache.org/jira/browse/FLINK-23882)), who reach for `TIMESTAMP WITH TIME ZONE` expecting it to work and then hit timestamp-correctness surprises. ## Brief change log - Add a `{{< hint warning >}}` callout to the `TIMESTAMP WITH TIME ZONE` section of the data types reference stating the type only exists as a logical type, is not supported by Flink SQL yet (linking FLINK-20869), and pointing users to `TIMESTAMP_LTZ` when time zone information must be retained. - Apply the same note to the Chinese (`content.zh`) mirror of the page. ## Verifying this change This change is a documentation-only update without test coverage. The claim was verified against the codebase: `FlinkResultSet` rejects `TIMESTAMP_WITH_TIME_ZONE`, and `CastFunctionITCase` leaves the casts unimplemented pending FLINK-20869. The note reuses the `{{< hint warning >}}` shortcode already present elsewhere on the same page. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): **no** - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: **no** - The serializers: **no** - The runtime per-record code paths (performance sensitive): **no** - Anything that affects deployment or recovery: **no** - The S3 file system connector: **no** ## Documentation - Does this pull request introduce a new feature? **no** - If yes, how is the feature documented? **docs** (this PR is the doc change) --- _This documentation change was prepared with AI assistance (Claude Code)._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
