You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Kevin Wilfong (JIRA)" <ji...@apache.org> on 2013/03/12 03:59:13 UTC

[jira] [Updated] (HIVE-3968) Enhance logging in TableAccessInfo

     [ https://issues.apache.org/jira/browse/HIVE-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Wilfong updated HIVE-3968:
--------------------------------

    Attachment: HIVE-3968.5.patch.txt
    
> Enhance logging in TableAccessInfo
> ----------------------------------
>
>                 Key: HIVE-3968
>                 URL: https://issues.apache.org/jira/browse/HIVE-3968
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Kevin Wilfong
>            Assignee: Kevin Wilfong
>         Attachments: HIVE-3968.1.patch.txt, HIVE-3968.2.patch.txt, HIVE-3968.3.patch.txt, HIVE-3968.4.patch.txt, HIVE-3968.5.patch.txt
>
>
> Based on what is currently available in the TableAccessInfo we can infer when it would be a good idea to add bucketing/sorting metadata for tables.  However, we can't easily tell if we're already getting the benefits of bucketing/sorting.
> This information can be improved by
> a) storing the input table/partition objects so that we can tell if the tables/partitions are already bucketed/sorted
> b) running the TableAccessAnalyzer after the logical optimizer, so that we can tell from the operators whether or not we are already getting benefits (bucketed/sort merge map joins or map group bys)

--
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: http://www.atlassian.com/software/jira