[
https://issues.apache.org/jira/browse/DRILL-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deneche A. Hakim updated DRILL-3281:
------------------------------------
Description:
Computing a MAX or MIN of a TIME column using the OVER clause seem to generate
wrong results compared to Postgres. Example of such queries:
{noformat}
SELECT MIN(CAST(columns[1] AS TIME)) OVER(PARTITION BY columns[0]) FROM
`3281.csv`;
{noformat}
{noformat}
SELECT MAX(CAST(columns[1] AS TIME)) OVER(PARTITION BY columns[0]) FROM
`3281.csv`; {noformat}
was:
Computing a MAX or MIN of a TIME column using the OVER clause seem to generate
wrong results compared to Postgres. Example of such queries:
{noformat}
SELECT MIN(cast( columns[8] as TIME )) OVER(PARTITION BY cast( columns[2] as
CHAR(2)) ORDER BY cast( columns[0] as INT )) FROM `allData.csv`;
{noformat}
SELECT MAX(cast( columns[8] as TIME )) OVER(PARTITION BY cast( columns[2] as
CHAR(2)) ORDER BY cast( columns[0] as INT )) FROM `allData.csv`;
{noformat}
{noformat}
> window functions that involve TIME columns generate wrong results
> -----------------------------------------------------------------
>
> Key: DRILL-3281
> URL: https://issues.apache.org/jira/browse/DRILL-3281
> Project: Apache Drill
> Issue Type: Sub-task
> Components: Execution - Flow
> Reporter: Deneche A. Hakim
> Assignee: Deneche A. Hakim
> Fix For: 1.1.0
>
> Attachments: 3281.csv
>
>
> Computing a MAX or MIN of a TIME column using the OVER clause seem to
> generate wrong results compared to Postgres. Example of such queries:
> {noformat}
> SELECT MIN(CAST(columns[1] AS TIME)) OVER(PARTITION BY columns[0]) FROM
> `3281.csv`;
> {noformat}
> {noformat}
> SELECT MAX(CAST(columns[1] AS TIME)) OVER(PARTITION BY columns[0]) FROM
> `3281.csv`; {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
