hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunther Hagleitner (JIRA)" <>
Subject [jira] [Commented] (HIVE-6098) Merge Tez branch into trunk
Date Wed, 25 Dec 2013 19:08:50 GMT


Gunther Hagleitner commented on HIVE-6098:

Still a classpath issue. This time compiling. I'll have a fix shortly. The trouble is this
shouldn't fail regardless. The reason it is failing is that LongWritable isn't binary compatible
between hadoop 1 and 2. The compareTo function signature has changed. This will need shimming.
I'll open a new ticket for that.

> Merge Tez branch into trunk
> ---------------------------
>                 Key: HIVE-6098
>                 URL:
>             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-6098.4.patch,
> 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

View raw message