[
https://issues.apache.org/jira/browse/HIVE-11387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damien Carol updated HIVE-11387:
--------------------------------
Description: The main problem is that, due to return path, now we may have
{{(RS1-GBY2)\-(RS3-GBY4)}} when map.aggr=false, i.e., no map aggr. However, in
the non-return path, it will be treated as {{(RS1)-(GBY2-RS3-GBY4)}}. The main
problem is that it does not take into account of the setting. (was: {noformat}
The main problem is that, due to return path, now we may have
(RS1-GBY2)-(RS3-GBY4) when map.aggr=false, i.e., no map aggr. However, in the
non-return path, it will be treated as (RS1)-(GBY2-RS3-GBY4). The main problem
is that it does not take into account of the setting.
{noformat})
> CBO: Calcite Operator To Hive Operator (Calcite Return Path) : fix
> reduce_deduplicate optimization
> --------------------------------------------------------------------------------------------------
>
> Key: HIVE-11387
> URL: https://issues.apache.org/jira/browse/HIVE-11387
> Project: Hive
> Issue Type: Sub-task
> Components: CBO
> Reporter: Pengcheng Xiong
> Assignee: Pengcheng Xiong
> Attachments: HIVE-11387.01.patch, HIVE-11387.02.patch,
> HIVE-11387.03.patch, HIVE-11387.04.patch, HIVE-11387.05.patch,
> HIVE-11387.06.patch
>
>
> The main problem is that, due to return path, now we may have
> {{(RS1-GBY2)\-(RS3-GBY4)}} when map.aggr=false, i.e., no map aggr. However,
> in the non-return path, it will be treated as {{(RS1)-(GBY2-RS3-GBY4)}}. The
> main problem is that it does not take into account of the setting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
