[jira] [Comment Edited] (OOZIE-2687) OYA: Figure out how to handle MR-specific properties

[Peter Bacsko (JIRA)]

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

Peter Bacsko edited comment on OOZIE-2687 at 11/25/16 11:12 AM:
----------------------------------------------------------------

Some variations:

{code}
<env>
    <key>ENV_VARIABLE_KEY</key>
    <value>someValue</value>
</env>
<env>
    <key>ANOTHER_KEY</key>
    <value>anotherValue</value>
</env>
{code}

or

{code}
<env>ENV_VARIABLE_KEY=someValue</env>
<env>ANOTHER_KEY=anotherValue</env>
{code}

Memory settings:

{code}
<memory>1024</memory>    <!-- Always in MB -->
{code}

or 

{code}
<memory>1024M</memory> 
<memory>1G</memory>
{code}


was (Author: pbacsko):
Some variations:

{code}
<env>
    <key>ENV_VARIABLE_KEY</key>
    <value>someValue</value>
<env>
<env>
    <key>ANOTHER_KEY</key>
    <value>anotherValue</value>
<env>
{code}

or

{code}
<env>ENV_VARIABLE_KEY=someValue</env>
<env>ANOTHER_KEY=anotherValue</env>
{code}

Memory settings:

{code}
<memory>1024</memory>    <!-- Always in MB -->
{code}

or 

{code}
<memory>1024M</memory> 
<memory>1G</memory>
{code}

> OYA: Figure out how to handle MR-specific properties
> ----------------------------------------------------
>
>                 Key: OOZIE-2687
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2687
>             Project: Oozie
>          Issue Type: Sub-task
>            Reporter: Peter Cseh
>
> It was possible to manipulate the MapperLauncher's environment through 
> properties like:
> # mapreduce.map.memory.mb     
> # mapreduce.map.cpu.vcores
> # mapred.child.env
> # mapred.child.java.opts      
> # mapred.job.queue.name  - ability to set launcher queue
> E.g. We were using mapred.child.env to pass SPARK_HOME to the LauncherMapper 
> and make PySpark work. 
> Fixing OOZIE-2596 added a hack. We should decide how we support or break 
> compatibility and how we allow the manipulation of the Launcher environment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)