[
https://issues.apache.org/jira/browse/BEAM-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997704#comment-15997704
]
ASF GitHub Bot commented on BEAM-2143:
--------------------------------------
GitHub user vikkyrk opened a pull request:
https://github.com/apache/beam/pull/2907
[BEAM-2143]: Fix default temp location for DataflowRunner
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [ ] Make sure the PR title is formatted like:
`[BEAM-<Jira issue #>] Description of pull request`
- [ ] Make sure tests pass via `mvn clean verify`.
- [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [ ] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf).
---
- https://github.com/apache/beam/pull/2602 made `gs://some-bucket` path
invalid and expects it to be of the form `gs://some-bucket/basename`. So adding
`/temp` as the basename for the default `tempLocation`.
- Also fix log messages.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vikkyrk/incubator-beam df_temp_loc
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2907.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2907
----
commit ea165bfba449cd5572f9342bf8107018dc584a30
Author: Vikas Kedigehalli <[email protected]>
Date: 2017-05-05T01:30:35Z
Fix default temp location for DataflowRunner
----
> (Mis)Running Dataflow Wordcount gives non-helpful errors
> --------------------------------------------------------
>
> Key: BEAM-2143
> URL: https://issues.apache.org/jira/browse/BEAM-2143
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, sdk-java-gcp
> Reporter: Ben Chambers
> Assignee: Vikas Kedigehalli
> Priority: Blocker
> Fix For: First stable release
>
>
> If you run a pipeline and forget to specify `tempLocation` (but specify
> something else, such as `stagingLocation`) you get two messages indicating
> you forgot to specify `stagingLocation`.
> One says "no stagingLocation specified, choosing ..." the other says "error,
> the staging location isn't readable" (if you give it just a bucket and not an
> object within a bucket).
> This is surprising to me as a user, since (1) I specified a staging location
> and (2) the flag I actually need to modify is `--tempLocation`.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
