beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-88) DataflowPipelineOptions.tempLocation doesn't really default to stagingLocation
Date Fri, 04 Mar 2016 03:02:40 GMT

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

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

Yup -- this is non-ideal. We should fix it.

> 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
>            Assignee: Davor Bonaci
>            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)

Mime
View raw message