Krystal created DRILL-891:
-----------------------------

             Summary: Cast string to timestamp fails with split hbase table
                 Key: DRILL-891
                 URL: https://issues.apache.org/jira/browse/DRILL-891
             Project: Apache Drill
          Issue Type: Bug
          Components: Storage - HBase
            Reporter: Krystal


git.commit.id.abbrev=8490d74
git.commit.time=02.06.2014 @ 09\:15\:29 PDT

I have a split hbase table.  Here is one record in the table:

hbase(main):004:0> get 'voter', '1'
COLUMN                       CELL                                               
                              
 fourcf:create_date          timestamp=1400799413902, value=2014-05-25 03:41:54 
                              
 onecf:name                  timestamp=1400799413902, value=nick miller         
                              
 threecf:contributions       timestamp=1400799413902, value=717.12              
                              
 threecf:voterzone           timestamp=1400799413902, value=13809               
                              
 twocf:age                   timestamp=1400799413902, value=68                  
                              
 twocf:registration          timestamp=1400799413902, value=green               
                              
6 row(s) in 0.4660 seconds

The following sql query against this table failed.

0: jdbc:drill:schema=hbase> select date_add(cast(fourcf['create_date'] as 
timestamp), interval '3' hour) from voter where row_key=5;

message: "Failure while running fragment. < UnsupportedOperationException:[ 
CastExpression is not expected here. It should have been converted to 
FunctionHolderExpression in materialization ]"

The same query runs fine against a table without split:
0: jdbc:drill:schema=hbase> select date_add(cast(fourcf['create_date'] as 
timestamp), interval '3' hour) from s_voter where row_key=5;
+------------+
|   EXPR$0   |
+------------+
| 2015-02-01T05:02:37.000-08:00 |
+------------+




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

Reply via email to