You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Gunther Hagleitner (JIRA)" <ji...@apache.org> on 2013/12/23 15:56:58 UTC

[jira] [Created] (HIVE-6098) Merge Tez branch into trunk

Gunther Hagleitner created HIVE-6098:
----------------------------------------

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


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)