[ https://issues.apache.org/jira/browse/FLINK-32689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747839#comment-17747839 ]
Timo Walther commented on FLINK-32689: -------------------------------------- Also this is incorrect: {code} tableEnv.getConfig().setLocalTimeZone(ZoneOffset.ofHours(2)); tableEnv.executeSql("SELECT TO_TIMESTAMP_LTZ(f0, 3) FROM t").print(); {code} The zone offset is ignored. > 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)