[
https://issues.apache.org/jira/browse/BEAM-9471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068010#comment-17068010
]
Udi Meiri commented on BEAM-9471:
---------------------------------
[~tvalentyn]
> Error "No files to stage has been found" on Windows machines running 2.19.0
> ---------------------------------------------------------------------------
>
> Key: BEAM-9471
> URL: https://issues.apache.org/jira/browse/BEAM-9471
> Project: Beam
> Issue Type: Bug
> Components: runner-core, runner-dataflow
> Affects Versions: 2.19.0
> Environment: Microsoft Windows 10, Java 8
> Reporter: Samuel Waggoner
> Priority: Major
>
> Windows users on our team have started encountering "No files to stage has
> been found" errors when attempting to run Beam pipelines on Dataflow. They
> are still able to run on the direct runner fine.
> It's difficult for me to provide a minimal reproduction case because I don't
> use a Windows machine. But I believe the failure happens when running _any_
> pipeline on Dataflow from a Windows machine without explicitly setting
> --filesToStage.
> I suspect this change is the cause, because it seems to completely change the
> code for gathering files to stage from the classpath:
> [https://github.com/apache/beam/commit/9629ff6c5bfd70770046468adf44e2eeb69e606d]
> I believe this stackoverflow is about the same issue:
> [https://stackoverflow.com/questions/60586141/dataflowrunner-exits-with-no-files-to-stage-has-been-found]
>
> {code:java}
> Caused by: java.lang.IllegalArgumentException: No files to stage has been
> found.
> at
> org.apache.beam.runners.dataflow.DataflowRunner.fromOptions(DataflowRunner.java:281)
> ... 30 more{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
