beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kamil Szewczyk (JIRA)" <>
Subject [jira] [Commented] (BEAM-1286) DataflowRunner handling of missing filesToStage
Date Tue, 11 Jul 2017 11:57:00 GMT


Kamil Szewczyk commented on BEAM-1286:

DataflowRunner allows to filesToStage to be missing, but then it automatically detects ClassPath
Resources to be staged, which are jar files. The same behaviour is in flink runner. So, part
of handling is done.

I have set up dataflow-runner and by default when “--gcpTempLocation” option is selected,
new staging folder is created and jar files are uploaded there. Without any “--tempLocation”
“--gcpTempLocation” or “--stagingLocation” set a new dataflow staging bucket is created
and files are uploaded there. 

Those files are available to workers, but not necessarily used by them. I am right?
Why we should fail when nothing to be staged is found? 

> DataflowRunner handling of missing filesToStage
> -----------------------------------------------
>                 Key: BEAM-1286
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>            Reporter: Daniel Halperin
>              Labels: newbie, starter
> DataflowRunner allows filesToStage to be missing -- it logs an error and moves on. Is
this the right behavior? It can complicate user experience.
> At least, I guess that if nothing to be staged is found, we should fail.

This message was sent by Atlassian JIRA

View raw message