Dynamic file-based sinks

While Beam now supports file-based sinks that can depend on the current window, I've seen interest in value-dependent sinks as well (and there's a long-standing JIRA for this). I wrote up a short API proposal for this for discussion on the list. https://docs.google.com/document/d/1Bd9mJO1YC8vOoFOb

Re: How can I disable running Python SDK tests when testing my Java change?

We could consider splitting Python up into the four things it runs: all tests with Cython, all tests without Cython, docs, and checkstyle. However, I never use Maven when developing the python portions. On Thu, May 18, 2017 at 6:35 PM, Thomas Groh wrote: > Generally I pass "-am -amd -pl sdks/java

Re: How can I disable running Python SDK tests when testing my Java change?

Generally I pass "-am -amd -pl sdks/java/core" to my maven invocation. -pl is the module to build, -am indicates to also make all modules my target depends upon, and -amd indicates to also make all of the dependencies; so if you're only modifying java, that should hit everything. If you're making a

Re: Beam Example 2.0 Update

Looks great, thanks Jesse! On Thu, May 18, 2017 at 4:59 PM Jesse Anderson wrote: > Could I get a pair of eyeballs (or more) to look over the 2.0 updates I > made to the Beam example? This is the commit > < > https://github.com/eljefe6a/beamexample/commit/b0a5988263cec451efdc060326ccc2bd622066b3

Beam Example 2.0 Update

Could I get a pair of eyeballs (or more) to look over the 2.0 updates I made to the Beam example? This is the commit . Thanks, Jesse -- Thanks, Jesse

How can I disable running Python SDK tests when testing my Java change?

I've noticed that when I run "mvn verify", most of the time when I look at the screen it's running Python tests. Indeed, the Reactor Summary says: ... [INFO] Apache Beam :: SDKs :: Python .. SUCCESS [11:56 min] ... [INFO] Total time: 12:03 min (Wall Clock) i.e. it's clearly on

Re: Beam Fn API

Now that I'm back from vacation and the 2.0.0 release is not taking all my time, I am focusing my attention on working on the Beam Portability framework, specifically the Fn API so that we can get Python and other language integrations work with any runner. For new comers, I would like to reshare

Re: First stable release completed!

Well done everyone. Thanks to all who helped make this happen. :-) -Tyler On Thu, May 18, 2017 at 6:52 PM Etienne Chauchot wrote: > This is awesome! Congrats to everyone! > > Etienne > > > Le 17/05/2017 à 18:34, Thomas Groh a écrit : > > Well done all! > > > > On Wed, May 17, 2017 at 9:31 AM, S

Re: First stable release completed!

This is awesome! Congrats to everyone! Etienne Le 17/05/2017 à 18:34, Thomas Groh a écrit : Well done all! On Wed, May 17, 2017 at 9:31 AM, Sourabh Bajaj < sourabhba...@google.com.invalid> wrote: Congrats !! On Wed, May 17, 2017 at 9:02 AM Mingmin Xu wrote: Congratulations to everyone!

Re: Jenkins build became unstable: beam_Release_NightlySnapshot #419

This was HBaseIOTest.testWritingFailsTableDoesNotExist not actually failing. It does not appear related to any changes since the last success. This did not immediately reproduce at HEAD so I have filed to track deflaking https://issues.apache.org/jira/browse/BEAM-2318 Deep link to build break: ht

Jenkins build became unstable: beam_Release_NightlySnapshot #419

See