Hi,
Just a quick note in agreement with Kyle.
For many corporates that are behind the times, using docker is quite a
challenge and actually prevents me from running Beam Python against Flink.
Since the code is really just Java (I think?), could there be an option to just
build the jar and manu
I agree that loopback would be preferable for this purpose. I just wasn't
aware this even works with the portable Flink runner. Is it one of the best
guarded secrets? ;-)
Kyle, can you please post the pipeline options you would use for Flink?
On Thu, Sep 12, 2019 at 5:57 PM Kyle Weaver wrote:
And/or update the wiki/website with some how to's...
On Fri, Sep 13, 2019 at 7:51 AM Thomas Weise wrote:
> I agree that loopback would be preferable for this purpose. I just wasn't
> aware this even works with the portable Flink runner. Is it one of the best
> guarded secrets? ;-)
>
> Kyle, can
In general there is no generic source/sink fake/mock/emulator that runs for
all sources/sinks locally. Configuration and data is on a case by case
basis. Most of the Apache Beam integration tests either launch a local
implementation that is specific to the source/sink (such as a DB for
JdbcIO) or u
Note that loopback won't fix the problem for, say, cross-language IOs. But,
yes, it's really handy and should probably be used more.
On Fri, Sep 13, 2019 at 8:29 AM Lukasz Cwik wrote:
> And/or update the wiki/website with some how to's...
>
> On Fri, Sep 13, 2019 at 7:51 AM Thomas Weise wrote:
> Is it one of the best guarded secrets? ;-)
Apparently so!
Filed a few related jiras and assigned to myself.
[1] https://issues.apache.org/jira/browse/BEAM-8214
[2] https://issues.apache.org/jira/browse/BEAM-8232
[3] https://issues.apache.org/jira/browse/BEAM-8233
Kyle Weaver | Software Engineer
