You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Steve Carlin (Jira)" <ji...@apache.org> on 2019/11/05 01:45:00 UTC

[jira] [Created] (HIVE-22454) Remove subplan under "Limit 0"

Steve Carlin created HIVE-22454:
-----------------------------------

             Summary: Remove subplan under "Limit 0"
                 Key: HIVE-22454
                 URL: https://issues.apache.org/jira/browse/HIVE-22454
             Project: Hive
          Issue Type: Improvement
            Reporter: Steve Carlin


After the Calcite upgrade and some fixes, there are plans that have a "limit 0" but then do stuff after 0 rows are selected.

An example is in filter_union.q.out:
...

      Reduce Operator Tree:

        Group By Operator

          aggregations: count(VALUE._col0)

          keys: KEY._col0 (type: string)

          mode: mergepartial

          outputColumnNames: _col0, _col1

          Statistics: Num rows: 250 Data size: 23750 Basic stats: COMPLETE Column stats: COMPLETE

          Limit

            Number of rows: 0
...
We can simplify the plan by maybe creating a dummy table after the Limit 0.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)