Mailing-List: contact commits-help@pirk.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pirk.incubator.apache.org
Date: Thu, 8 Sep 2016 12:42:20 +0000 (UTC)
From: "Ellison Anne Williams (JIRA)" <jira@apache.org>
To: commits@pirk.incubator.apache.org
Message-ID: <JIRA.13003563.1473338222000.519540.1473338540508@Atlassian.JIRA>
In-Reply-To: <JIRA.13003563.1473338222000@Atlassian.JIRA>
References: <JIRA.13003563.1473338222000@Atlassian.JIRA> <JIRA.13003563.1473338222608@arcas>
Subject: [jira] [Updated] (PIRK-62) Local Properties Files Not Picked Up by
 Responder Using spark-submit
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 08 Sep 2016 12:42:25 -0000


     [ https://issues.apache.org/jira/browse/PIRK-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ellison Anne Williams updated PIRK-62:
--------------------------------------
    Fix Version/s: 0.1.1

> Local Properties Files Not Picked Up by Responder Using spark-submit
> --------------------------------------------------------------------
>
>                 Key: PIRK-62
>                 URL: https://issues.apache.org/jira/browse/PIRK-62
>             Project: PIRK
>          Issue Type: Bug
>            Reporter: Ellison Anne Williams
>            Assignee: Ellison Anne Williams
>             Fix For: 0.1.1
>
>
> When launching the Responder using spark-submit, the local property file given by the '--localPropFile' argument (within the localFS of the launching machine) is not picked up. This is due to the fact the localFS is not available to the instance launched by spark-submit.
> This can be fixed in one of two ways: 
> (1) Place the 'local' properties files in a directory in hdfs and have everything that ends in '.properties' be read and parsed into the system properties 
> or 
> (2) Leave the local properties file on the localFS and use the SparkLauncher to launch all spark jobs from the Responder (the local prop file will be parsed and the properties will be passed in as args to the instance).   
> I am leaning towards (1) as we have had some trouble with the SparkLauncher correctly picking up 'spark-home' (the directory containing the spark-submit script) on various cloud platforms (AWS and GCP).


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