[
https://issues.apache.org/jira/browse/FLINK-21456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290639#comment-17290639
]
Jark Wu edited comment on FLINK-21456 at 2/25/21, 3:10 AM:
-----------------------------------------------------------
A simplest to fix all data types can be adding an implicit CAST TO STRING for
every column. This can make sure the string representation is exactly the same
with SQL behavior. However, this can only work for SQL Client, not work for
{{TableResult#print()}}.
was (Author: jark):
A simplest to fix all data types can be add a implicit CAST TO STRING for every
column. This can make sure the string representation is exactly the same with
SQL behavior. However, this can only work for SQL Client, not work for
{{TableResult#print()}}.
> TableResult#print() should correctly stringify values of TIMESTAMP type in
> SQL format
> -------------------------------------------------------------------------------------
>
> Key: FLINK-21456
> URL: https://issues.apache.org/jira/browse/FLINK-21456
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Jark Wu
> Priority: Major
>
> Currently {{TableResult#print()} simply use {{Object#toString()}} as the
> string representation of the fields. This is not SQL compliant, because for
> TIMESTAMP and TIMESTAMP_LZ, the string representation should be {{2021-02-23
> 17:30:00}} instead of {{2021-02-23T17:30:00Z}}.
> Note: we may need to update {{PrintUtils#rowToString(Row)}} and also SQL
> Client which invokes this method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
