Hi,
I would like to merge RabbitMqIO (we are doing the final touches) and we
have an issue about ParquetIO on HDFS/S3 that I would like to
investigate with the team.
I plan to start the release process asap, hopefully later today.
Regards
JB
On 29/05/2018 23:00, Ahmet Altay wrote:
> Thank you
Welcome !
Looking forward to work and discuss with you ;)
Regards
JB
On 29/05/2018 23:49, Rui Wang wrote:
> Hi there,
>
> I am Rui (pronounced as same as "Ray")!
>
> I recently joined Google Cloud. Beam is a very interesting project and I
> cannot wait to contribute to it!
>
>
> Thanks,
>
Thanks everyone for making comments and suggestions. I modified the
proposal that added dependency release time as the major criteria for
outdated package determination.
The revised doc is here:
https://docs.google.com/document/d/1rqr_8a9NYZCgeiXpTIwWLCL7X8amPAVfRXsO72BpBwA.
Any comments are
I've been looking into the beam-site merge automation reliability, and I'd
like to get some early feedback on ideas for improvement. Please take a
look at https://s.apache.org/beam-site-automation:
> Apache Beam's website is maintained via the beam-site Git repository,
with a set of automation
Great! Thx a lot for the update, Lukasz. Can’t wait for 2.5! Cheers
On Wed, 30 May 2018 at 1:17 am, Lukasz Cwik wrote:
> You are correct, the release has been being worked on for a couple of
> weeks but has stalled due to blockers that were discovered. The current
> status is that there are
Welcome Rui!
On Tue, May 29, 2018 at 2:49 PM, Rui Wang wrote:
> Hi there,
>
> I am Rui (pronounced as same as "Ray")!
>
> I recently joined Google Cloud. Beam is a very interesting project and I
> cannot wait to contribute to it!
>
>
> Thanks,
> Rui
>
My two cents:
https://github.com/apache/beam/pull/5341
https://issues.apache.org/jira/browse/BEAM-4257
On Tue, May 29, 2018 at 7:50 PM Kenneth Knowles wrote:
> Fair point!
>
> It is already on master and released so I'll come up with one or more
> concrete endeavors where someone could jump in
Hi there,
I am Rui (pronounced as same as "Ray")!
I recently joined Google Cloud. Beam is a very interesting project and I
cannot wait to contribute to it!
Thanks,
Rui
Thank you JB for the update. Could we start the release process now? Is
there anyway I could help with moving the release forward?
On Fri, May 25, 2018 at 8:19 AM, Lukasz Cwik wrote:
> Thanks for the update JB.
>
> Kenn, we have the post commit integration tests which run against shaded
>
Providing ownership to the PMC account allows others to take over ownership
of the document once a contributor stops being active. This allows docs to
be updated (even if just to point to a newer doc).
On Tue, May 29, 2018 at 1:20 PM Kenneth Knowles wrote:
> My position on ownership is design
My position on ownership is design docs are really documents "of the
moment" and authored by a particular individual or group. Experience shows
that even if you try, keeping it fresh is not likely to happen. Anything
that needs freshness (like end-user docs) should be in a different medium. I
I transferred ownership of the docs that I owned to the apacheb...@gmail.com
PMC account and put the ones that I owned into the drive folder.
Would it be a good idea for others to follow suit?
Instructions on how to transfer ownership are here:
I created a PR for the beam-site to link to the design docs and template
from the contribution guide:
https://github.com/apache/beam-site/pull/454
On Fri, May 25, 2018 at 10:23 AM Lukasz Cwik wrote:
> Here are some more links related to portability efforts:
>
>
>
Fair point!
It is already on master and released so I'll come up with one or more
concrete endeavors where someone could jump in and help.
On Tue, May 29, 2018 at 10:46 AM Robert Bradshaw
wrote:
> Surprised there's not an item about SQL support, Kenn :).
>
> On Mon, May 28, 2018 at 5:16 AM
Surprised there's not an item about SQL support, Kenn :).
On Mon, May 28, 2018 at 5:16 AM David Morávek
wrote:
> here you go: https://github.com/apache/beam-site/pull/453
>
> Thanks,
> D.
>
> On Tue, May 15, 2018 at 11:51 PM, Kenneth Knowles wrote:
>
>> I wanted to bring back to this thread
+1. I've opened BEAM-4423 to capture the discussion here:
https://issues.apache.org/jira/browse/BEAM-4423
On Thu, May 24, 2018 at 5:34 PM Chamikara Jayalath
wrote:
> +1 for automatically closing. Currently, contribution guide mentions that
> pull requests without responses to actionable
Thanks guys, I've created the following JIRA:
https://issues.apache.org/jira/browse/BEAM-4422
Colm.
On Mon, May 28, 2018 at 5:36 PM, Jean-Baptiste Onofré
wrote:
> ./gradlew build works but not check due to go:vet task.
>
> Let's check with Henning.
>
> Regards
> JB
>
> On 28/05/2018 16:57,
Also, you are able to use the nightly snapshot to continue developing.
On Tue, May 29, 2018 at 8:17 AM Lukasz Cwik wrote:
> You are correct, the release has been being worked on for a couple of
> weeks but has stalled due to blockers that were discovered. The current
> status is that there are
You are correct, the release has been being worked on for a couple of weeks
but has stalled due to blockers that were discovered. The current status is
that there are currently no known blockers for the 2.5.0 release. The next
steps are to build and validate a release candidate which are being
Hi team,
I need to develop streaming processing on Dataflow Runner with Beam Python
SDK. And I understand that 2.5 will start experimentally supporting this
feature.
So would like to ask when the Beam Python SDK 2.5 is expected to be
released? According to the previous release frequency, I
Hi all,
I opened this ticket https://issues.apache.org/jira/browse/BEAM-4418 .The aim
is to gather areas of improvement of the
IntelliJ/gradle integration discovered by people. Feel free to comment on what
you discovered.
Etienne
21 matches
Mail list logo
