Rong Rong created FLINK-11935: --------------------------------- Summary: Remove DateTimeUtils pull-in and fix datetime casting problem Key: FLINK-11935 URL: https://issues.apache.org/jira/browse/FLINK-11935 Project: Flink Issue Type: Sub-task Reporter: Rong Rong Assignee: Rong Rong
This {{DateTimeUtils}} was pulled in in FLINK-7235. Originally the time operation was not correctly done via the {{ymdToJulian}} function before the date {{1970-01-01}} thus we need the fix. similar to addressing this problem: {code:java} Optimized :1017-12-05 22:58:58.998 Expected :1017-11-29 22:58:58.998 Actual :1017-12-05 22:58:58.998 {code} However, after pulling in avatica 1.13, I found out that the optimized plans of the time operations are actually correct. it is in fact the casting part that creates problem: For example, the following: *{{(plus(-12000.months, cast('2017-11-29 22:58:58.998', TIMESTAMP))}}* result in a StringTestExpression of: *{{CAST(1017-11-29 22:58:58.998):VARCHAR(65536) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" NOT NULL}}* but the testing results are: {code:java} Optimized :1017-11-29 22:58:58.998 Expected :1017-11-29 22:58:58.998 Actual :1017-11-23 22:58:58.998 {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)