Re: Beam 2.4.0

done Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book

Re: Beam 2.4.0

Romain - it looks like these JIRA tickets are on on the 2.4.0 burndown. Can you set their Fix Version field to make sure they are tracked and triaged? On Tue, Feb 20, 2018 at 10:22 PM, Reuven Lax wrote: > I think it's fair to request that the reviewers of these PRs help with

Re: Beam 2.4.0

*are _not_ on the burndown :-) On Wed, Feb 21, 2018 at 9:31 AM, Kenneth Knowles wrote: > Romain - it looks like these JIRA tickets are on on the 2.4.0 burndown. > Can you set their Fix Version field to make sure they are tracked and > triaged? > > > On Tue, Feb 20, 2018 at

Re: [DISCUSS] What to do about widespread KinesisIO breakage

Nice! Thanks both for taking this on. Kenn On Wed, Feb 21, 2018 at 7:00 AM, Alexey Romanenko wrote: > Hi all, > > Just an intermediate update on this. All (except only one) flaky KinesisIO > tests were fixed (thanks to Paweł Kaczmarczyk for help) and I didn’t see >

Re: [YouTube channel] Add video: Apache Beam meetup London 2: use case in finance + IO in Beam and Splittable DoFns

+1 to the proposal @Matthias could you share more about the dynamics in how people in the community would be able to add videos and who would be owning the curation of the channel? G On 21 February 2018 at 09:08, Matthias Baetens wrote: > Hi Gaurav, > >

Re: [YouTube channel] Add video: Apache Beam meetup London 2: use case in finance + IO in Beam and Splittable DoFns

Hi Gaurav, Thanks for pointing that out. The channel can be found here . No videos there yet though, waiting for approval to publish the first one! Cheers, Matthias On Wed, Feb 21, 2018 at 12:55 AM, Gaurav Thakur

Re: Jenkins job beam_PreCommit_Python_MavenInstall” still fails

Thanks for the info on this. I went ahead and merged it since it had good test coverage and was a simple change to fix the build. On Wed, Feb 21, 2018 at 9:03 AM, Pablo Estrada wrote: > Hello all! > As outlined in BEAM-3720, this is due to my adding Gauge metrics without >

Re: Jenkins job beam_PreCommit_Python_MavenInstall” still fails

Hello all! As outlined in BEAM-3720, this is due to my adding Gauge metrics without adding support for the portability framework around the same time that the direct runner was swapped. Please don't despair. PR https://github.com/apache/beam/pull/4719 fixes this, and hopefully will be merged soon.

Re: [DISCUSS] What to do about widespread KinesisIO breakage

Hi all, Just an intermediate update on this. All (except only one) flaky KinesisIO tests were fixed (thanks to Paweł Kaczmarczyk for help) and I didn’t see that they were failing anymore. Please, let me know if you did. That one, which was not fixed (BEAM-3317

Re: Jenkins job beam_PreCommit_Python_MavenInstall” still fails

For info, this issue is tracked and the fix is in progress: https://issues.apache.org/jira/browse/BEAM-3720 On Tue, Feb 20, 2018 at 4:43 PM, Jean-Baptiste Onofré wrote: > I would wait a feedback from the original author of the commit. > > Regards > JB > Le 20 févr. 2018, à

Build failed in Jenkins: beam_Release_NightlySnapshot #692

See Changes: [abhyankar] Add support for ValueProvider in JdbcIO.DataSourceConfiguration methods [kirpichov] Updates BigQuery dependency version [kenn] Ignore IntelliJ Gradle build outputs [kenn]

Re: @TearDown guarantees

Hello, thanks Eugene for improving the documentation so we can close this thread. Reuven, I understood the semantics of the methods, what surprised me was that I interpreted the new documentation as if a runner could simply ignore to call @Teardown, and we already have dealt with the issues of