[
https://issues.apache.org/jira/browse/HIVE-11880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905982#comment-14905982
]
WangMeng commented on HIVE-11880:
---------------------------------
[~ashutoshc] I tried the patch of HIVE-11919, it can not fix this bug.
The two bugs are different.I think HIVE-11919 focuses on type mismatch and
HIVE-11880 focuses on filter bug when hive.ppd.remove.duplicatefilters=true
> IndexOutOfBoundsException when query with filter condition on type
> incompatible column of UNION ALL when hive.ppd.remove.duplicatefilters=true
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-11880
> URL: https://issues.apache.org/jira/browse/HIVE-11880
> Project: Hive
> Issue Type: Bug
> Components: Logical Optimizer
> Affects Versions: 1.2.1
> Reporter: WangMeng
> Assignee: WangMeng
> Attachments: HIVE-11880.01.patch
>
>
> For Hive UNION ALL , when an union column is constant(column a such as
> '0L') and it has incompatible type with the corresponding column A(INT
> Type).
> Query with filter condition on type incompatible column a on this UNION ALL
> will cause IndexOutOfBoundsException.
> Such as TPC-H table "orders", we create View by :
> {code}
> CREATE VIEW `view_orders` AS
> SELECT `oo`.`o_orderkey` ,
> `oo`.`o_custkey`
> FROM (
> SELECT `o_orderkey` , `0L AS `o_custkey`
> FROM `rcfileorders`
> UNION ALL
> SELECT `o_orderkey` ,`o_custkey`
> FROM `textfileorders`) `oo`.
> {code}
> In VIEW view_orders , type of 'o_custkey' is INT normally, while the type
> of corresponding column constant "0" is BIGINT( `0L AS `o_custkey` ).
> When
> {code}
> set hive.ppd.remove.duplicatefilters=true
> {code}
> the fllowing query (with filter " incompatible column 'o_custkey' ") will
> fail with java.lang.IndexOutOfBoundsException:
> {code}
> select count(1) from view_orders where o_custkey<100000
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
