You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2017/05/29 01:29:04 UTC

[jira] [Commented] (OOZIE-2919) make Pig run with Tez execution launcher easier

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

Rohini Palaniswamy commented on OOZIE-2919:
-------------------------------------------

bq. There's a workaround that requires Tez libs added to oozie sharelib rather having its own directory and also requires some properties in the oozie wf xml.
   At Yahoo, we deploy tez libs and tez-site.xml part of pig sharelib itself so that users don't have to specify an additional sharelib for tez. Probably we can add some kind of support for that for Pig and Hive sharelibs in Oozie sharelib deployment through configuration. What is the oozie wf xml property that you are talking about?

> make Pig run with Tez execution launcher easier
> -----------------------------------------------
>
>                 Key: OOZIE-2919
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2919
>             Project: Oozie
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 4.3.0
>            Reporter: Artem Ervits
>
> I've been trying to make Pig run with Tez via Oozie and was not able to do so easily. There's a workaround that requires Tez libs added to oozie sharelib rather having its own directory and also requires some properties in the oozie wf xml. I propose to have Tez treated as first class citizen as per Yahoo talk at Hadoop Summit, they moved off of MR to TEZ for all of their Pig workloads.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)