[
https://issues.apache.org/jira/browse/HIVE-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871196#comment-13871196
]
Gunther Hagleitner commented on HIVE-4660:
------------------------------------------
[~leftylev] - I've attached release notes to HIVE-6098. You should get the
right settings/flags from there. I will also update the design doc.
As for your questions:
- Yes hive.optimize.tez is gone if favor of hive.execution.engine=[mr, tez]
- mapreduce.framework.name is not a hive setting. You can use it with hive
though and if you set it to yarn-tez, you can use hive on MR and MR will be
emulated on tez. Probably best to not mention this - as it mostly just adds
confusion.
> 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
> Fix For: 0.13.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
