You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Aman Sinha (JIRA)" <ji...@apache.org> on 2018/07/13 15:12:00 UTC
[jira] [Commented] (DRILL-6606) Hash Join returns incorrect data
types when joining subqueries with limit 0
[ https://issues.apache.org/jira/browse/DRILL-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543323#comment-16543323 ]
Aman Sinha commented on DRILL-6606:
-----------------------------------
I don't think LIMIT 0 in the subqueries or Views is common. For instance, Tableau generates a wrapper LIMIT 0 on the entire query, not within each subquery. What is the data type of columns if you only have the outer LIMIT 0 after the join of the subqueries ?
> Hash Join returns incorrect data types when joining subqueries with limit 0
> ---------------------------------------------------------------------------
>
> Key: DRILL-6606
> URL: https://issues.apache.org/jira/browse/DRILL-6606
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Bohdan Kazydub
> Assignee: Timothy Farkas
> Priority: Blocker
> Fix For: 1.14.0
>
>
> PreparedStatement for query
> {code:sql}
> SELECT l.l_quantity, l.l_shipdate, o.o_custkey
> FROM (SELECT * FROM cp.`tpch/lineitem.parquet` LIMIT 0) l
> JOIN (SELECT * FROM cp.`tpch/orders.parquet` LIMIT 0) o
> ON l.l_orderkey = o.o_orderkey
> LIMIT 0
> {code}
> is created with wrong types (nullable INTEGER) for all selected columns, no matter what their actual type is. This behavior reproduces with hash join only and is very likely to be caused by DRILL-6027 as the query works fine before this feature was implemented.
> To reproduce the problem you can put the aforementioned query into TestPreparedStatementProvider#joinOrderByQuery() test method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)