You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kurt Young (JIRA)" <ji...@apache.org> on 2019/07/12 06:08:00 UTC
[jira] [Closed] (FLINK-13232)
TemporalTypesTest>ExpressionTestBase.evaluateExprs in blink planner fails
on PST Timezone
[ https://issues.apache.org/jira/browse/FLINK-13232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Young closed FLINK-13232.
------------------------------
Resolution: Fixed
merged in 1.9.0: 53a044c987718d74db3a9b6102f1fa27324a7fab
> TemporalTypesTest>ExpressionTestBase.evaluateExprs in blink planner fails on PST Timezone
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-13232
> URL: https://issues.apache.org/jira/browse/FLINK-13232
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.9.0
> Reporter: Bowen Li
> Assignee: Jingsong Lee
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> TemporalTypesTest>ExpressionTestBase.evaluateExprs in blink planner seems to have a bug on timezone.
> When I run it locally at PST timezone, it always fails as:
> {code:java}
> [ERROR] Failures:
> [ERROR] TemporalTypesTest>ExpressionTestBase.evaluateExprs:154 Wrong result for: [CURRENT_DATE] optimized to: [CURRENT_DATE] expected:<2019-07-1[2]> but was:<2019-07-1[1]>
> {code}
> I didn't find it fails on travis. Thus I suspect there's a bug w.r.t. timezone.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)