hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yin Huai (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HIVE-3430) group by followed by join with the same key should be optimized
Date Thu, 18 Jul 2013 14:54:48 GMT

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

Yin Huai resolved HIVE-3430.
----------------------------

    Resolution: Not A Problem

With HIVE-2206, cases mentioned in this jira will be optimized by Correlation Optimizer. Please
check [correlationoptimizer2.q|https://github.com/apache/hive/blob/trunk/ql/src/test/queries/clientpositive/correlationoptimizer2.q]
and [correlationoptimizer6.q|https://github.com/apache/hive/blob/trunk/ql/src/test/queries/clientpositive/correlationoptimizer6.q]
([~lianhuiwang] Your case is in this file) for most relevant unit tests to this jira.

I am closing it as "Not A Problem".
                
> group by followed by join with the same key should be optimized
> ---------------------------------------------------------------
>
>                 Key: HIVE-3430
>                 URL: https://issues.apache.org/jira/browse/HIVE-3430
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>    Affects Versions: 0.10.0
>            Reporter: Namit Jain
>


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