hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-1694) Accelerate GROUP BY execution using indexes
Date Fri, 01 Feb 2013 00:03:14 GMT

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

Jakob Homan updated HIVE-1694:
------------------------------

    Description: 
The index building patch (Hive-417) is checked into trunk, this JIRA issue tracks supporting
indexes in Hive compiler & execution engine for SELECT queries.

This is in ref. to John's comment at


https://issues.apache.org/jira/browse/HIVE-417?focusedCommentId=12884869&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12884869

on creating separate JIRA issue for tracking index usage in optimizer & query execution.

The aim of this effort is to use indexes to accelerate query execution (for certain class
of queries). E.g.
- Filters and range scans (already being worked on by He Yongqiang as part of HIVE-417?)
- Joins (index based joins)
- Group By, Order By and other misc cases

The proposal is multi-step:
1. Building index based operators, compiler and execution engine changes
2. Optimizer enhancements (e.g. cost-based optimizer to compare and choose between index scans,
full table scans etc.)

This JIRA initially focuses on the first step. This JIRA is expected to hold the information
about index based plans & operator implementations for above mentioned cases.  

  was:
The index building patch (Hive-417) is checked into trunk, this JIRA issue tracks supporting
indexes in Hive compiler & execution engine for SELECT queries.

This is in ref. to John's comment at


https://issues.apache.org/jira/browse/HIVE-417?focusedCommentId=12884869&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12884869

on creating separate JIRA issue for tracking index usage in optimizer & query execution.

The aim of this effort is to use indexes to accelerate query execution (for certain class
of queries). E.g.
- Filters and range scans (already being worked on by He Yongqiang as part of HIVE-417?)
- Joins (index based joins)
- Group By, Order By and other misc cases

The proposal is multi-step:
1. Building index based operators, compiler and execution engine changes
2. Optimizer enhancements (e.g. cost-based optimizer to compare and choose between index scans,
full table scans etc.)

This JIRA initially focuses on the first step. This JIRA is expected to hold the information
about index based plans & operator implementations for above mentioned cases. 

    
> Accelerate GROUP BY execution using indexes
> -------------------------------------------
>
>                 Key: HIVE-1694
>                 URL: https://issues.apache.org/jira/browse/HIVE-1694
>             Project: Hive
>          Issue Type: New Feature
>          Components: Indexing, Query Processor
>    Affects Versions: 0.7.0
>            Reporter: Nikhil Deshpande
>            Assignee: Prajakta Kalmegh
>             Fix For: 0.8.0
>
>         Attachments: demo_q1.hql, demo_q2.hql, HIVE-1694.1.patch.txt, HIVE-1694_2010-10-28.diff,
HIVE-1694.2.patch.txt, HIVE-1694.3.patch.txt, HIVE-1694.4.patch, HIVE-1694.5.patch, HIVE-1694.6.patch,
HIVE-1694.7.patch, HIVE-1694.7.patch
>
>
> The index building patch (Hive-417) is checked into trunk, this JIRA issue tracks supporting
indexes in Hive compiler & execution engine for SELECT queries.
> This is in ref. to John's comment at
> https://issues.apache.org/jira/browse/HIVE-417?focusedCommentId=12884869&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12884869
> on creating separate JIRA issue for tracking index usage in optimizer & query execution.
> The aim of this effort is to use indexes to accelerate query execution (for certain class
of queries). E.g.
> - Filters and range scans (already being worked on by He Yongqiang as part of HIVE-417?)
> - Joins (index based joins)
> - Group By, Order By and other misc cases
> The proposal is multi-step:
> 1. Building index based operators, compiler and execution engine changes
> 2. Optimizer enhancements (e.g. cost-based optimizer to compare and choose between index
scans, full table scans etc.)
> This JIRA initially focuses on the first step. This JIRA is expected to hold the information
about index based plans & operator implementations for above mentioned cases.  

--
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

Mime
View raw message