Hi team, I found the string representation of TIMESTAMP_LTZ kind of confusing.
SQL client doesn’t display the zone part of TIMESTAMP_LTZ[1], while the serializers do[2]. I did some searching and found that plenty of db clients would display the zone part (handled implicitly), such as Beeline and Snowflake[3]. Considering we have plans for Beeline support, I think SQL client could also display the zone part to keep the user experience aligned. WDYT? [1] https://nightlies.apache.org/flink/flink-docs-release-1.17/docs/dev/table/timezone/#timestamp_ltz-type <https://nightlies.apache.org/flink/flink-docs-release-1.17/docs/dev/table/timezone/> [2] https://github.com/apache/flink/blob/master/flink-formats/flink-format-common/src/main/java/org/apache/flink/formats/common/TimeFormats.java#L82 <https://github.com/apache/flink/blob/master/flink-formats/flink-format-common/src/main/java/org/apache/flink/formats/common/TimeFormats.java#L82> [3] https://docs.snowflake.com/en/sql-reference/data-types-datetime#timestamp-examples <https://docs.snowflake.com/en/sql-reference/data-types-datetime#timestamp-examples> Best, Paul Lam
