On Fri, Sep 11, 2020 at 3:02 PM Robert Bradshaw wrote:
> The long term goal is for Dataflow to use the external containers rather
> than its own. Hopefully this happened sooner rather than later, and until
> then you can specify the beam container as a custom container.
>
> On Fri, Sep 11, 2020
Ok great. Next question:
What is the relationship between sdks/python/container/boot.go and
Dataflow? Is this file used within the Dataflow bootstrapping process?
We're currently investigating a switch from Flink to Dataflow, and in doing
so we hope to be able to work our way back to using
On Fri, Sep 11, 2020 at 2:11 PM Robert Bradshaw wrote:
> Hmm... this is a difficult question. I think adding support for a pip.conf
> probably makes the most sense, despite it being yet another option.
>
+1 - I think this is a good flag to add. I heard similar user requests for
passing specific
Hmm... this is a difficult question. I think adding support for a pip.conf
probably makes the most sense, despite it being yet another option.
Another alternative is to simply pre-install the dependencies you want (or
even just override /etc/pip.conf) in a custom container.
On Wed, Sep 9, 2020
Hi all,
We are running into problems trying to use our own pypi mirror with Beam.
For those who are not well versed in the esotera of python package
management, pip provides a few ways to specify urls for the pypi index
server:
- command line
