[DRILL-2458] Extra hash column added when running CTAS with order by

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0
• Component/s: Query Planning & Optimization
• Assignee: Jinfeng Ni
• Reporter: Steven Phillips
• Created: 14/Mar/15 01:56
• Updated: 03/Apr/15 23:15
• Resolved: 03/Apr/15 23:15

Description

I created the table via the command:

create table dfs.tmp.lineitem_sort as select * from dfs.`/drill/SF10/lineitem` order by l_extendedprice desc

This resulted in an extra column when reading the data back:

0: jdbc:drill:> select * from `lineitem_sort/0_0_0.parquet` limit 1;
+---------------------------+------------+--------------+------------+-----------------+--------------+--------------+------------+------------+------------+---------------+--------------+------------+----------------+------------+------------+------------+------------------+
| E_X_P_R_H_A_S_H_F_I_E_L_D | L_COMMENT  | L_COMMITDATE | L_DISCOUNT | L_EXTENDEDPRICE | L_LINENUMBER | L_LINESTATUS | L_ORDERKEY | L_PARTKEY  | L_QUANTITY | L_RECEIPTDATE | L_RETURNFLAG | L_SHIPDATE | L_SHIPINSTRUCT | L_SHIPMODE | L_SUPPKEY  |   L_TAX    | l_extendedprice0 |
+---------------------------+------------+--------------+------------+-----------------+--------------+--------------+------------+------------+------------+---------------+--------------+------------+----------------+------------+------------+------------+------------------+
| -1909175176               | [B@187a06b6 | [B@734ea347  | 0.02       | 104949.5        | 2            | [B@2fc1c575  | 16734176   | 199999     | 50.0       | [B@5a8a9cd1   | [B@423d8bc7  | [B@56a3d7ca | [B@1eac3b36    | [B@3d6365f5 | 50002      | 0.05       | 104949.5         |
+---------------------------+------------+--------------+------------+-----------------+--------------+--------------+------------+------------+------------+---------------+--------------+------------+----------------+------------+------------+------------+------------------+