Parth Chandra created DRILL-585:
-----------------------------------

             Summary: timestamp and time data not showing up correctly in 
sqlline
                 Key: DRILL-585
                 URL: https://issues.apache.org/jira/browse/DRILL-585
             Project: Apache Drill
          Issue Type: Bug
            Reporter: Parth Chandra


Executing the following query -
select first, last, age, sex, salary, registered, cast(join_date as timestamp) 
TIMEST, cast(join_date as date) DT, cast(join_time as TIME) TM   from 
dfs.`testTypes.json`

returned the following results in sqlline- 
+------------+------------+------------+------------+------------+------------+------------+------------+------------+
|   first    |    last    |    age     |    sex     |   salary   | registered | 
  TIMEST   |     DT     |     TM     |
+------------+------------+------------+------------+------------+------------+------------+------------+------------+
| Jimmy      | James      | 29         | M          | 6300.1     | false      | 
2011-11-30 | 2011-11-30 | 00:00:00   |
| anderson   | carr       | null       | M          | 6300.1     | false      | 
null       | null       | null       |
| John       | James      | 29         | M          | 6300.1     | true       | 
2011-11-30 | 2011-11-30 | 00:00:00   |
+------------+------------+------------+------------+------------+------------+------------+------------+------------+

The timestamp column does not have time, and the time column has incorrect 
values.

Data file contains the following data -

{
 "first": "Jimmy",
 "last": "James",
 "age": 29,
 "sex": "M",
 "salary": 6300.10,
 "registered": false,
 "join_date": "2011-11-30",
 "join_time": "9:11:10.000"
}
{
 "first": "anderson",
 "last": "carr",
 "sex": "M",
 "salary": 6300.10,
 "registered": false
}
{
 "first": "John",
 "last": "James",
 "age": 29,
 "sex": "M",
 "salary": 6300.10,
 "registered": true,
 "join_date": "2011-11-30",
 "join_time": "8:59:32.000"
}








--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to