Hi everyone,
Please review and vote on the release candidate #1 for the version 2.25.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
Support for Flink 1.11 is
https://issues.apache.org/jira/browse/BEAM-10612 . It has been
implemented and will be included in the next release (Beam 2.25). In
the meantime, you could try building yourself from head.
On Fri, Oct 16, 2020 at 4:39 AM Kishor Joshi wrote:
>
> Hi Team,
>
> Since the
Thanks, Ning and Ahmet.
+1 (binding) Approve the release.
On Fri, Oct 16, 2020 at 1:34 PM Ning Kang wrote:
> Sorry, if you cannot see the missing thread history in the previous
> thread, here is another copy:
>
> On Fri, Oct 16, 2020 at 9:55 AM Robert Bradshaw
> wrote:
>
>> Thanks.
>>
>> +1
Sorry, if you cannot see the missing thread history in the previous thread,
here is another copy:
On Fri, Oct 16, 2020 at 9:55 AM Robert Bradshaw wrote:
> Thanks.
>
> +1 (binding) to this release.
>
> On Thu, Oct 15, 2020 at 7:06 PM Ahmet Altay wrote:
>
>> Here you go:
>>
Thanks Ahmet and Robert! Please see the quote attached for the missing
history of discussion and vote from Robert, sorry for the confusion.
Based on Robert's suggestion, we updated the original vote thread with a
new link to "the official Apache source release to be deployed to
dist.apache.org
Welcome to Beam!
Regards,
Alexey
> On 15 Oct 2020, at 16:06, Nam Bui wrote:
>
> Hi everyone,
>
> I'm Nam. I used to work on Apache Beam website migration. From now on, I will
> be responsible for website development. Thus, I will implement new designs
> and some of the functionalities on
Thanks Ahmet and Robert! Please see the quote attached for the missing
history of discussion and vote from Robert, sorry for the confusion.
On Fri, Oct 16, 2020 at 9:55 AM Robert Bradshaw wrote:
> Thanks.
>
> +1 (binding) to this release.
>
> On Thu, Oct 15, 2020 at 7:06 PM Ahmet Altay wrote:
Hi Everyone,
I’m Milka and I’m a UI & motion designer. I will be applying the designs on
Kasia’s wireframes and take care of the look and feel, as well as
accessible UI solutions. Looking forward to working with you!
Best,
--
Milka Toikkanen
UI & Motion Designer
+48 577 926 829
Welcome. I added you as a contributor to Jira.
On Fri, Oct 16, 2020 at 10:11 AM Aliraza Nagamia
wrote:
> Sorry I forgot to mention my jira account handle: alirazan
>
> On Fri, Oct 16, 2020 at 10:36 AM Aliraza Nagamia
> wrote:
>
>> Hello,
>>
>> I am working on a project related to Google Cloud
Sorry I forgot to mention my jira account handle: alirazan
On Fri, Oct 16, 2020 at 10:36 AM Aliraza Nagamia
wrote:
> Hello,
>
> I am working on a project related to Google Cloud Platform's Dicom api. I
> would like to contribute code for a Dicom IO connector. Could I please have
> permission to
Hello,
I am working on a project related to Google Cloud Platform's Dicom api. I
would like to contribute code for a Dicom IO connector. Could I please have
permission to add/assign tickets on the Beam Jira?
Thank you,
Aliraza
Hi Gris,
It’s done.
Regards,
Alexey
> On 16 Oct 2020, at 16:57, Gris Cuevas wrote:
>
> Hi folks, could someone in the PMC provide "Contributor" roles to the
> following folks who will be working on the website revamp?
>
> Usernames: nam.bui, Milka, AgnieszkaSell, kasiazjc
>
Hi folks, could someone in the PMC provide "Contributor" roles to the following
folks who will be working on the website revamp?
Usernames: nam.bui, Milka, AgnieszkaSell, kasiazjc
Thanks a lot for your comments!
I see your point regarding the location of such templates.
I moved the templates folder under the examples folder. Currently it looks like
/examples/templates/java/kafka-to-pubsub.
Does it look better?
Thank you,
Ilya
On 15 Oct 2020, 20:30 +0300, Kyle Weaver ,
Hi Team,
Since the beam has released the version 2.24 but it seems still the highest
version that is supported in beam 2.24 (>=2.21) is 1.10.So i would like to know
what is the plan to release beam with the support of latest flink i.e. 1.11.x.
Thanks & Regards,Kishor
the downstream consumer has these requirements.
Blocking should normally be avoided at all cost, but if the downstream
operator has the requirement to only emit a fixed number of messages per
second, it should enforce this, i.e. block once the maximum number of
messages for a time period
16 matches
Mail list logo