[
https://issues.apache.org/jira/browse/BEAM-9218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027745#comment-17027745
]
Robert Bradshaw commented on BEAM-9218:
---------------------------------------
Thanks, Elias, for verifying this.
It's possible that some of the work triggered by requirements_file (e.g.
actually downloading the dependencies and staging them) could be deferred in
the template case, and simply has not been. I think it's fair to call this a
(separate) bug.
> Template staging broken on Beam 2.18.0
> --------------------------------------
>
> Key: BEAM-9218
> URL: https://issues.apache.org/jira/browse/BEAM-9218
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Affects Versions: 2.18.0
> Reporter: Michael Charkin
> Assignee: Robert Bradshaw
> Priority: Major
>
> beam 2.18.0 can not stage cloud Dataflow templates
>
> Looks like it is trying to access the RuntimeValueProvider during staging
> causing 'not accessible'
>
> Repo with code to reproduce the issue:
> [https://github.com/firemuzzy/dataflow-templates-bug]
>
> With the help of stack overflow narrowed the issue to the latest beam release
> and not python versions
> [https://stackoverflow.com/questions/59940069/how-do-you-create-a-google-cloud-dataflow-template-with-python-3?noredirect=1#59940069]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
