drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vince Gonzalez <vince.gonza...@gmail.com>
Subject more on parsing timestamps
Date Wed, 01 Apr 2015 19:54:36 GMT
Is this a bug?

Created a parquet table (using CTAS) with one column containing text
timestamps.

0: jdbc:drill:zk=localhost:2181> select * from tstamp_test limit 1;
+------------+
|     t      |
+------------+
| 2015-01-27T13:43:53.000Z |
+------------+
1 row selected (0.119 seconds)

The below queries, identical apart from the limit clause, behave
differently. The one with the limit clause works, the one without doesn't.
The limit is larger than the total number of rows, so in both cases we
should be processing all rows.

No limit clause. It fails:

```
0: jdbc:drill:zk=localhost:2181> select to_timestamp(t.t,
'YYYY-MM-dd''T''HH:mm:ss.SSS''Z''') FROM (select t from tstamp_test) as t;
Query failed: RemoteRpcException: Failure while trying to start remote
fragment, Expression has syntax error! line 1:30:mismatched input 'T'
expecting CParen [ 7d30d753-0822-4820-afd0-b7e7fe5e639c on
192.168.99.1:31010 ]
```

Limit clause in the subselect (larger than the number of rows in the table)
succeeds.

```
0: jdbc:drill:zk=localhost:2181> select to_timestamp(t.t,
'YYYY-MM-dd''T''HH:mm:ss.SSS''Z''') FROM (select t from tstamp_test limit
100000000) as t;
...
| 2015-02-17 07:18:00.0 |
+------------+
13,015,350 rows selected (105.257 seconds)
```

Data can be downloaded here:

https://s3.amazonaws.com/vgonzalez/data/tstamp_test.tar.gz

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message