[
https://issues.apache.org/jira/browse/FLINK-23882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-23882:
-----------------------------------
Labels: auto-deprioritized-major stale-assigned starter (was:
auto-deprioritized-major starter)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> Documentation of TIMESTAMP WITH TIME ZONE should state that it is currently
> not supported by Flink SQL
> ------------------------------------------------------------------------------------------------------
>
> Key: FLINK-23882
> URL: https://issues.apache.org/jira/browse/FLINK-23882
> Project: Flink
> Issue Type: Bug
> Components: Documentation, Table SQL / API
> Affects Versions: 1.14.0
> Reporter: Caizhi Weng
> Assignee: TANG ZHAO
> Priority: Minor
> Labels: auto-deprioritized-major, stale-assigned, starter
>
> Currently TIMESTAMP WITH TIME ZONE type only exists as a logical type and is
> not supported by Flink SQL. However its
> [documentation|https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/dev/table/types/#timestamp-with-time-zone]
> does not state this, which confuses the user in the [mailing
> list|https://lists.apache.org/thread.html/r906131fdfba1295bb07953e10063068c786cf918c03017aab0766c2e%40%3Cuser-zh.flink.apache.org%3E].
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
