[
https://issues.apache.org/jira/browse/CALCITE-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045301#comment-17045301
]
Andrew Tsvelodub commented on CALCITE-3412:
-------------------------------------------
[~danny0405][~julianhyde] I see this bug is closed but it looks like the fix in
Julian's branch has not made its way into master. Was this ticket only created
to track changes in Avatica and we should create a new one apply the fix to
Calcite? Or should this one be reopened?
> FLOOR(timestamp TO WEEK) gives wrong result
> -------------------------------------------
>
> Key: CALCITE-3412
> URL: https://issues.apache.org/jira/browse/CALCITE-3412
> Project: Calcite
> Issue Type: Bug
> Components: avatica, core
> Reporter: huaicui
> Assignee: Julian Hyde
> Priority: Major
> Fix For: 1.22.0, avatica-1.17.0
>
> Attachments: image-2019-10-15-13-33-34-896.png
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Floor timestamp to week exist error:
> The start day of the week is not Sunday or Monday, calcite use Thursday to
> split a week.
> Example:
> sql: select FLOOR(CAST('2017-01-28' AS TIMESTAMP) TO WEEK);
> Response:
> 2017-01-26 00:00:00.0
>
> 2017-01-26 is Thursday that is not our expect result. As result, 2017-01-22
> is the first day that we expect.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
