[
https://issues.apache.org/jira/browse/CALCITE-5039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513116#comment-17513116
]
itxiangkui commented on CALCITE-5039:
-------------------------------------
Perhaps the most ideal way to solve this problem is to use the
"TIMESTAMP_WITH_LOCAL_TIME_ZONE" data type and support a standard time format
(such as ISO-8601) when querying, or a system-level configurable time parse
format.
By the way, dba is too lazy, they just want to
select * from table where ts<'2022-03-14 00:00:01' This usage, that is, the
parse format is "yyyy-MM-dd HH:mm:ss" or "ISO-8601" standard.. .
> View:Timestamp cannot query Data:Long in GMT+8 TimeZone Env
> -----------------------------------------------------------
>
> Key: CALCITE-5039
> URL: https://issues.apache.org/jira/browse/CALCITE-5039
> Project: Calcite
> Issue Type: Improvement
> Components: core, jdbc-driver
> Affects Versions: 1.29.0, 1.30.0
> Reporter: itxiangkui
> Priority: Major
> Labels: TimeZone, Timestamp
> Attachments: image-2022-03-15-17-07-39-917.png
>
>
> When I have a row like :
> |ts:TimeStamp|channel:String|pv:Long|
> |1647187200000|ios|10|
>
> while 1647187200000 is a timestamp in TimeZone of "GMT+8",the datetime is
> "2022-03-14 00:00:00"
> but you can not query the data using a sql like :
> ```sql
> select * from table where ts='2022-03-14 00:00:00';
> select * from table where ts<'2022-03-14 00:00:01' and ts>'2022-03-13
> 23:59:59' and channel='ios';
> ```
> it is like the jdbc-fether will filter the data when match the
> timestampString,while the timestamp String looks like '2022-03-13 16:00:00'
> or '2022-03-14 08:00:00'
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
