hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harish Butani (JIRA)" <>
Subject [jira] [Commented] (HIVE-2340) optimize orderby followed by a groupby
Date Fri, 05 Apr 2013 22:27:17 GMT


Harish Butani commented on HIVE-2340:

The problem with PTF is in plan generation. In SemanticAnalyzer::genReduceSinkPlanForWindowing
line 10778, we are setting the RowSchema of the ReduceSinkOp that precedes a PTF to be the
same one as the Op that precedes it. In the e.g. that was failing the preceding Op was another
PTFOp. The fix is to set both the RowSchema and RowResolver by not pointing to the 'input'
Op's structures(same issue in genPTFPlanForComponentQuery). Will fix in the separate Jira.
Will add back 'schema.getSignature().remove(colInfo);' to ColumnPrunerProcFactory. Sorry about
> optimize orderby followed by a groupby
> --------------------------------------
>                 Key: HIVE-2340
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Query Processor
>            Reporter: Navis
>            Assignee: Navis
>            Priority: Minor
>              Labels: perfomance
>         Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2340.D1209.1.patch, ASF.LICENSE.NOT.GRANTED--HIVE-2340.D1209.2.patch,
ASF.LICENSE.NOT.GRANTED--HIVE-2340.D1209.5.patch, HIVE-2340.12.patch, HIVE-2340.13.patch,
HIVE-2340.14.patch, HIVE-2340.14.rebased_and_schema_clone.patch, HIVE-2340.1.patch.txt, HIVE-2340.D1209.10.patch,
HIVE-2340.D1209.11.patch, HIVE-2340.D1209.12.patch, HIVE-2340.D1209.13.patch, HIVE-2340.D1209.14.patch,
HIVE-2340.D1209.15.patch, HIVE-2340.D1209.6.patch, HIVE-2340.D1209.7.patch, HIVE-2340.D1209.8.patch,
HIVE-2340.D1209.9.patch, testclidriver.txt
> Before implementing optimizer for JOIN-GBY, try to implement RS-GBY optimizer(cluster-by
following group-by).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message