hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunther Hagleitner (JIRA)" <>
Subject [jira] [Updated] (HIVE-2340) optimize orderby followed by a groupby
Date Tue, 12 Feb 2013 09:25:13 GMT


Gunther Hagleitner updated HIVE-2340:

    Attachment: HIVE-2340.12.patch

[~navis]: Thanks that pointer helped. The column pruning did indeed not carry over the some
of the columns in the colExprMap. HIVE-2339 is in, but it was missing handling of the "KEY.*"

I've also looked at infer_bucket_sort and see what you're saying. Seems ok to have additional
sort columns/buckets as long as the ones that are explicitly asked for are there. I've updated
the golden file for that test.

Running full test suite on .12 now.
> 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.1.patch.txt,
HIVE-2340.D1209.10.patch, HIVE-2340.D1209.11.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