[
https://issues.apache.org/jira/browse/FLINK-32689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747557#comment-17747557
]
Timo Walther commented on FLINK-32689:
--------------------------------------
[~leonard] Could you give more context why FLINK-22349 was necessary? The check
above would fail for {{UTC-1}} and {{UT-1}} (which is also officially
supported). But current master accepts {{UT-1}}, is this a bug?
> Insufficient validation for table.local-time-zone
> -------------------------------------------------
>
> Key: FLINK-32689
> URL: https://issues.apache.org/jira/browse/FLINK-32689
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
>
> There are still cases where timezone information is lost silently due to the
> interaction between {{java.util.TimeZone}} and {{java.time.ZoneId}}.
> This might be theoretical problem, but I would feel safer if we change the
> check to:
> {code}
> if
> (!java.util.TimeZone.getTimeZone(zoneId).toZoneId().equals(ZoneId.of(zoneId)))
> {
> throw new ValidationException(errorMessage);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
