Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 23 Dec 2013 23:06:50 +0000 (UTC)
From: "Gunther Hagleitner (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12686156.1387810544250.6238.1387840010926@arcas>
In-Reply-To: <JIRA.12686156.1387810544250@arcas>
References: <JIRA.12686156.1387810544250@arcas>
Subject: [jira] [Commented] (HIVE-6098) Merge Tez branch into trunk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856001#comment-13856001 ] 

Gunther Hagleitner commented on HIVE-6098:
------------------------------------------

[~vinodkv] - definitely not too late. I like it. Much more descriptive. I'll make the change.

> Merge Tez branch into trunk
> ---------------------------
>
>                 Key: HIVE-6098
>                 URL: https://issues.apache.org/jira/browse/HIVE-6098
>             Project: Hive
>          Issue Type: New Feature
>    Affects Versions: 0.12.0
>            Reporter: Gunther Hagleitner
>            Assignee: Gunther Hagleitner
>         Attachments: HIVE-6098.1.patch, HIVE-6098.2.patch, HIVE-6098.3.patch, hive-on-tez-conf.txt
>
>
> I think the Tez branch is at a point where we can consider merging it back into trunk after review. 
> Tez itself has had its first release, most hive features are available on Tez and the test coverage is decent. There are a few known limitations, all of which can be handled in trunk as far as I can tell (i.e.: None of them are large disruptive changes that still require a branch.)
> Limitations:
> - Union all is not yet supported on Tez
> - SMB is not yet supported on Tez
> - Bucketed map-join is executed as broadcast join (bucketing is ignored)
> Since the user is free to toggle hive.optimize.tez, it's obviously possible to just run these on MR.
> I am hoping to follow the approach that was taken with vectorization and shoot for a merge instead of single commit. This would retain history of the branch. Also in vectorization we required at least three +1s before merge, I'm hoping to go with that as well.
> I will add a combined patch to this ticket for review purposes (not for commit). I'll also attach instructions to run on a cluster if anyone wants to try.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)