Mailing-List: contact commits-help@beam.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.incubator.apache.org
Date: Mon, 23 May 2016 22:43:12 +0000 (UTC)
From: "Davor Bonaci (JIRA)" <jira@apache.org>
To: commits@beam.incubator.apache.org
Message-ID: <JIRA.12946324.1456960836000.270905.1464043392842@Atlassian.JIRA>
In-Reply-To: <JIRA.12946324.1456960836000@Atlassian.JIRA>
References: <JIRA.12946324.1456960836000@Atlassian.JIRA> <JIRA.12946324.1456960836945@arcas>
Subject: [jira] [Commented] (BEAM-88) DataflowPipelineOptions.tempLocation
 doesn't really default to stagingLocation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 23 May 2016 22:43:17 -0000


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

Davor Bonaci commented on BEAM-88:
----------------------------------

[~ilganeli], awesome! We look forward to your contributions.

[~peihe], is this still up to date?

> DataflowPipelineOptions.tempLocation doesn't really default to stagingLocation
> ------------------------------------------------------------------------------
>
>                 Key: BEAM-88
>                 URL: https://issues.apache.org/jira/browse/BEAM-88
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Eugene Kirpichov
>            Priority: Trivial
>
> The documentation of DataflowPipelineOptions.tempLocation says: ..."defaults to using stagingLocation."...
> However calling .getTempLocation() when only --stagingLocation is specified on the command line gives null.
> The "defaulting" is really done in DataflowPipelineRunner.fromOptions():
> {code}
>     if (Strings.isNullOrEmpty(dataflowOptions.getTempLocation())) {
>       dataflowOptions.setTempLocation(dataflowOptions.getStagingLocation());
> {code}


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