Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D5BF1109D4 for ; Mon, 9 Dec 2013 13:14:08 +0000 (UTC) Received: (qmail 99168 invoked by uid 500); 9 Dec 2013 13:13:58 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 99035 invoked by uid 500); 9 Dec 2013 13:13:57 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 99027 invoked by uid 99); 9 Dec 2013 13:13:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Dec 2013 13:13:56 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tmp5330@gmail.com designates 209.85.215.43 as permitted sender) Received: from [209.85.215.43] (HELO mail-la0-f43.google.com) (209.85.215.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Dec 2013 13:13:51 +0000 Received: by mail-la0-f43.google.com with SMTP id n7so1547036lam.2 for ; Mon, 09 Dec 2013 05:13:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Jm3u9RsP2QX9Y9d6lef5HzxWrqs02zJatz7QfifV7kY=; b=sAoovAka3XQT2D57qud4ZYu86owl4EPxkgtt1N8QLdilbPyK0yHFDsDbL6myBV69YW lFsQ0InnpyykHfE54wOYOIpOSBA4k+C5xAQeOtlCIJdD3o0Nkte3gtIPTaWtoW+gBt3y 7N0taQS2Fzy/HkAd0T7OIBwlnMMsID5BUAIKC6V+WD8WcyOex1T5pIbqR8udGaezE5Hf UifHLYGS2/2roLdgSe1wcgIBBvwdhVbkGe6EXYvah5jNV4SKP0uvkqyj8sUlkUvbSbAU 1nGnmH0bCRh5YnZJLT6BatXSA1uaf6rer+fk8+EDYpZykbEub4niNPhzfZd0KekBp6qW ogqQ== MIME-Version: 1.0 X-Received: by 10.152.116.46 with SMTP id jt14mr5281851lab.31.1386594810028; Mon, 09 Dec 2013 05:13:30 -0800 (PST) Received: by 10.114.18.14 with HTTP; Mon, 9 Dec 2013 05:13:30 -0800 (PST) Date: Mon, 9 Dec 2013 14:13:30 +0100 Message-ID: Subject: Passing Configuration between Driver/AM/Children From: Rob Blah To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c3562419692b04ed19c335 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3562419692b04ed19c335 Content-Type: text/plain; charset=ISO-8859-1 Hi I am using trunk version of YARN. How can/should I pass YarnConfiguration/Configuration between Driver/AM/Children? I have a class MyConfiguration which extends YarnConfiguration. I would like to add/modify few keys in the Driver/Client. Then pass the class to AM, which can further work on the configuration. In the end the Configuration instance should be passed from AM to Children and read by them. How I can do this? Code snippets or code guidelines are welcomed. regrds tmp --001a11c3562419692b04ed19c335 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi

I am using trunk version of YARN= .

How can/should I pass YarnConfiguration/Conf= iguration between Driver/AM/Children?

I have a class MyCo= nfiguration which extends YarnConfiguration. I would like to add/modify few= keys in the Driver/Client. Then pass the class to AM, which can further wo= rk on the configuration. In the end the Configuration instance should be pa= ssed from AM to Children and read by them. How I can do this? Code snippets= or code guidelines are welcomed.

regrds
tmp
--001a11c3562419692b04ed19c335--