apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pradeep A. Dalvi" <p...@apache.org>
Subject Re: custom JAVA_HOME
Date Wed, 03 Aug 2016 18:17:15 GMT
+1 for adding support for Application Environment variables.

--prad

On Wed, Aug 3, 2016 at 10:10 AM, Sanjay Pujare <sanjay@datatorrent.com>
wrote:

> +1 for Pramod’s idea of allowing all variables supported by YARN
>
> On 8/3/16, 12:56 AM, "Chinmay Kolhatkar" <chinmay@datatorrent.com> wrote:
>
>     +1 for the idea.
>     Are there any in the list that one can see as conflicting with our own
>     environment variables? For e.g. LOGNAME?
>
>
>     On Wed, Aug 3, 2016 at 4:49 AM, Pramod Immaneni <
> pramod@datatorrent.com>
>     wrote:
>
>     > How about allowing specification of all environment variables
> supported by
>     > YARN that are non-final described below
>     >
>     >
>     >
> http://atetric.com/atetric/javadoc/org.apache.hadoop/hadoop-yarn-api/0.23.3/org/apache/hadoop/yarn/api/ApplicationConstants.Environment.html
>     >
>     > Thanks
>     >
>     > On Tue, Aug 2, 2016 at 3:43 PM, Vlad Rozov <v.rozov@datatorrent.com>
>     > wrote:
>     >
>     > > Should Apex add JAVA_HOME to DAGContext and allow application to
> specify
>     > > which JDK to use if there are multiple JDK installations on Hadoop
>     > cluster?
>     > > Yarn already supports custom JAVA_HOME (please see
>     > > https://issues.apache.org/jira/browse/YARN-2481).
>     > >
>     > > Vlad
>     > >
>     >
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message