You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Vitalii Diravka (JIRA)" <ji...@apache.org> on 2017/06/27 10:14:00 UTC

[jira] [Resolved] (DRILL-4116) Inconsistent results with datetime functions on different machines

     [ https://issues.apache.org/jira/browse/DRILL-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vitalii Diravka resolved DRILL-4116.
------------------------------------
    Resolution: Duplicate

[DRILL-5002|https://issues.apache.org/jira/browse/DRILL-5002]  jira already involves this issue.
The workaround is in above comment.

> Inconsistent results with datetime functions on different machines
> ------------------------------------------------------------------
>
>                 Key: DRILL-4116
>                 URL: https://issues.apache.org/jira/browse/DRILL-4116
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Functions - Drill
>    Affects Versions: 1.3.0
>            Reporter: Rahul Challapalli
>            Assignee: Vitalii Diravka
>            Priority: Critical
>
> git.commit.id.abbrev=a6a0fc3
> The below query yields different results on different machines
> System 1 :
> {code}
> 0: jdbc:drill:zk=10.10.100.190:5181> select datediff(date '1996-03-01', timestamp '1997-02-10 17:32:00.0') from cp.`tpch/lineitem.parquet` limit 1;
> +---------+
> | EXPR$0  |
> +---------+
> | -346    |
> +---------+
> 1 row selected (1.57 seconds)
> {code}
> System 2 :
> {code}
> 0: jdbc:drill:drillbit=10.10.88.193> select datediff(date '1996-03-01', timestamp '1997-02-10 17:32:00.0') from cp.`tpch/lineitem.parquet` limit 1;
> +---------+
> | EXPR$0  |
> +---------+
> | -347    |
> +---------+
> 1 row selected (1.239 seconds)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)