beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Kirpichov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BEAM-88) DataflowPipelineOptions.tempLocation doesn't really default to stagingLocation
Date Wed, 02 Mar 2016 23:21:18 GMT
Eugene Kirpichov created BEAM-88:
------------------------------------

             Summary: 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


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