Khurram Faraaz created DRILL-3870:
-------------------------------------

             Summary: CONVERT_FROM(..., uint8_be) can not be used in project
                 Key: DRILL-3870
                 URL: https://issues.apache.org/jira/browse/DRILL-3870
             Project: Apache Drill
          Issue Type: Bug
          Components: Execution - Relational Operators
    Affects Versions: 1.2.0
         Environment: 4 node cluster CentOS
            Reporter: Khurram Faraaz


CONVERT_FROM(..., 'uint8_be') results in UNSUPPORTED_OPERATION when used in 
project. However, when it is used in the predicate in the WHERE clause no error 
is reported.

Data in the HBase table has long integer values.
{code}
0: jdbc:drill:schema=dfs.tmp> SELECT 
CONVERT_FROM(BYTE_SUBSTR(row_key,1,8),'bigint_be') AS RK from dt_Tbl T;
+----------------+
|       RK       |
+----------------+
| 1408924800000  |
| 1443240886094  |
| 1443413686094  |
| 1443491446094  |
| 1443500086094  |
+----------------+
5 rows selected (0.767 seconds)
{code}

The below query fails when CONVERT_FROM function is used in the project.

{code}
0: jdbc:drill:schema=dfs.tmp> SELECT 
CONVERT_FROM(BYTE_SUBSTR(row_key,1,8),'uint8_be') AS RK from dt_Tbl T;
Error: UNSUPPORTED_OPERATION ERROR: CONVERT_FROM does not support conversion 
from type 'uint8_be'.

Did you mean UINT8?

[Error Id: 1e58b2bb-73c3-4c55-84db-e59b80ea6dbb on centos-03.qa.lab:31010] 
(state=,code=0)
{code}

When the same CONVERT_FROM function is used in the predicate no error is 
reported.

{code}
0: jdbc:drill:schema=dfs.tmp> select * from dt_Tbl WHERE 
CONVERT_FROM(BYTE_SUBSTR(row_key,1,8),'uint8_be') < cast(1443500086094 as 
bigint);
+--------------+-----------------------+
|   row_key    |        colfam1        |
+--------------+-----------------------+
| [B@14c9d776  | {"qual1":"dmFsMQ=="}  |
| [B@4f608ea3  | {"qual1":"dmFsNQ=="}  |
| [B@4c34980b  | {"qual1":"dmFsNA=="}  |
| [B@10ea2143  | {"qual1":"dmFsMw=="}  |
+--------------+-----------------------+
4 rows selected (0.865 seconds)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to