[
https://issues.apache.org/jira/browse/HIVE-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753844#comment-13753844
]
Bikas Saha commented on HIVE-4660:
----------------------------------
Folks, FYI, based on recent feedback we have changed the names used in some of
the TEZ API's. It a simple refactoring on the Tez side and should be a simple
refactoring fix on the Pig side too. Jira for reference. TEZ-410.
> Let there be Tez
> ----------------
>
> Key: HIVE-4660
> URL: https://issues.apache.org/jira/browse/HIVE-4660
> Project: Hive
> Issue Type: New Feature
> Reporter: Gunther Hagleitner
> Assignee: Gunther Hagleitner
>
> Tez is a new application framework built on Hadoop Yarn that can execute
> complex directed acyclic graphs of general data processing tasks. Here's the
> project's page: http://incubator.apache.org/projects/tez.html
> The interesting thing about Tez from Hive's perspective is that it will over
> time allow us to overcome inefficiencies in query processing due to having to
> express every algorithm in the map-reduce paradigm.
> The barrier to entry is pretty low as well: Tez can actually run unmodified
> MR jobs; But as a first step we can without much trouble start using more of
> Tez' features by taking advantage of the MRR pattern.
> MRR simply means that there can be any number of reduce stages following a
> single map stage - without having to write intermediate results to HDFS and
> re-read them in a new job. This is common when queries require multiple
> shuffles on keys without correlation (e.g.: join - grp by - window function -
> order by)
> For more details see the design doc here:
> https://cwiki.apache.org/confluence/display/Hive/Hive+on+Tez
--
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
