Re: Agenda for the Beam Summit London 2018

This is great. Any chance it will be recorded or at a minimum the slides made available after. Unfortunately, I won't be able to make it to London next week. Best, Andrew On Fri, Sep 28, 2018 at 10:11 AM Pablo Estrada wrote: > Very exciting. I will have to miss it, but I'm excited to see what c

Re: Portable Flink runner: Generator source for testing

Hi Thomas, all, yes, this is quite important for testing, and in fact I'd think it's important to streamline the insertion of native sources from different runners to make the current runners more usable. But that's another topic. For generators of synthetic data, I had a couple ideas (and this wi

Re: Python typing library is not provisional in Python 3.7

Hi Valentyn, I'm aware there is Python 3 environment and have worked on the options module. Yes, I'd love to contribute more. The issue I raise here is specifically about Python 3.7, where the dependency on typing library would fail all the tests. Do you

Portable Flink runner: Generator source for testing

There were a few discussions how we can facilitate testing for portable streaming pipelines with the Flink runner. The problem is that we currently don't have streaming sources in the Python SDK. One way to support testing could be a generator that extends the idea of Impulse to provide a Flink na

Re: Agenda for the Beam Summit London 2018

Very exciting. I will have to miss it, but I'm excited to see what comes out of it:) Thanks to Gris, Matthias and other organizers. Best -P. On Thu, Sep 27, 2018, 4:26 PM Jean-Baptiste Onofré wrote: > Great !! Thanks Gris. > > Looking forward to see you all next Monday in London. > > Regards > >

Re: Python typing library is not provisional in Python 3.7

Hi Manu, We have added Python 3 environment to our tests see [1], and we are actively making changes to Beam code to make it Python 3-compatible. We are enabling tests module by module, although we have to disable some of the tests initially, when failures are likely introduced in other modules.

Re: Agenda for the Beam Summit London 2018

Great !! Thanks Gris. Looking forward to see you all next Monday in London. Regards JB Le 27 sept. 2018 à 18:03, à 18:03, Griselda Cuevas a écrit: >Hi Beam Community, > >We have finalized the agenda for the Beam Summit London 2018, it's >here: >https://www.linkedin.com/feed/update/urn:li:activi

Re: Bug of the MqttIO.java

Thanks Luke Regards JB Le 27 sept. 2018 à 18:41, à 18:41, Lukasz Cwik a écrit: >Thanks, I assigned BEAM-5496. Feel free to ask questions on dev@ as >needed. > >On Wed, Sep 26, 2018 at 7:11 PM flyisland wrote: > >> Hi, My jira id is "flyisland", thanks! >> >> On Thu, Sep 27, 2018 at 3:25 AM Jean

Python typing library is not provisional in Python 3.7

Hi all, I failed to run Python tests in 3.7 with the following error. File "/Users/doria/git/incubator-beam/sdks/python/apache_beam/typehints/native_type_compatibility.py", line 23, in import typing File "/Users/doria/git/incubator-beam/sdks/python/.eggs/typing-3.6.6-py3.7.egg/typing.p

Re: Bug of the MqttIO.java

Thanks, I assigned BEAM-5496. Feel free to ask questions on dev@ as needed. On Wed, Sep 26, 2018 at 7:11 PM flyisland wrote: > Hi, My jira id is "flyisland", thanks! > > On Thu, Sep 27, 2018 at 3:25 AM Jean-Baptiste Onofré > wrote: > >> Yes please. Create a jira, I will tackle that. Thanks. >>

Agenda for the Beam Summit London 2018

Hi Beam Community, We have finalized the agenda for the Beam Summit London 2018, it's here: https://www.linkedin.com/feed/update/urn:li:activity:6450125487321735168/ We had a great amount of talk proposals, thank you so much to everyone who submitted one! We also sold out the event, so we're ver

Re: Modular IO presentation at Apachecon

Thanks Ismael and everyone else! Unfortunately I do not believe that this session was recorded on video :( Juan - yes, this is some of the important future work, and I think it's not hard to add to many connectors; contributions would be welcome. In terms of a "per-key" Wait transform, yeah, that d

Re: Removing documentation for old Beam versions

On Thu, Sep 27, 2018 at 7:25 PM Melissa Pashniak wrote: > > Ideally (IMO anyway), we would have versioned entire doc sets like most > Apache projects that I looked at do (Spark [1], Flink, Hadoop, etc.) with a > Latest + past releases, so users can read Beam docs appropriate to the > version they

Re: Removing documentation for old Beam versions

Ideally (IMO anyway), we would have versioned entire doc sets like most Apache projects that I looked at do (Spark [1], Flink, Hadoop, etc.) with a Latest + past releases, so users can read Beam docs appropriate to the version they are using. Would this run into the same situation as the javadoc/py

Re: Modular IO presentation at Apachecon

I'll take this chance to plug in my little directory of Beam tools/materials: https://github.com/pabloem/awesome-beam Please feel free to send PRs : ) On Wed, Sep 26, 2018 at 10:29 PM Ankur Goenka wrote: > Thanks for sharing. Great slides and looking for the recorded session. > > Do we have a c

Re: [DISCUSS] Committer Guidelines / Hygene before merging PRs

I agree that we should create a good pointer for cleaning up PRs, and request (though not require) that authors do it. It's unfortunate though that squashing during a review makes things difficult to follow, so adds one more round trip. We could consider for those PRs that make sense as a single l

Re: Are there plans for removing joda-time from the beam java SDK?

I agree that there's no path to removing joda-time as a dependency in 2.x. If we can it a goal for 3.0 to use java.time consistently and remove joda-time at that point, I'd be very happy. I have no context, though, on timeline for a 3.0 release. If that's sometime in the next year, then there's li

Re: Are there plans for removing joda-time from the beam java SDK?

As long as joda stays anywhere in the public API (and removing it would be a backwards incompatible change) we can't drop it as a dependency. While we could provide java.time overloads for time-accepting methods, time-returning methods can't be as transparently interchangeable. I'm not sure whethe

Re: Are there plans for removing joda-time from the beam java SDK?

+1 to removing joda. IMO from now on we should favor java.time in reviews over joda.time in new features and feel free to replace joda when refactoring is done in places where code stays backward-compatibile and doesn't get duplicated (eg. some class internals, not exposed through class interface).

Re: [VOTE] Release 2.7.0, release candidate #3

+1 I once again looked at the Nexmark dashboards, it seems that there are no performance regressions. czw., 27 wrz 2018, 00:02 użytkownik Jean-Baptiste Onofré napisał: > +1 (binding) > > Regards > JB > Le 26 sept. 2018, à 18:00, Ahmet Altay a écrit: >> >> +1. Thank you all! >> >> On Wed, Sep 2

Build failed in Jenkins: beam_Release_Gradle_NightlySnapshot #185

See Changes: [jeff] Composite transform lambdas via PTransform::compose [pablo] Updating BigQuerySink pydoc [github] Fix sliding time windows example documentation [github] Update session win