Done. Welcome!
On Tue, Mar 9, 2021 at 8:05 PM Onur Ozer wrote:
> Hi There,
>
> Could you please add me as a contributor to ASF JIRA. My username is oozer.
>
> Thanks,
>
Hi There,
Could you please add me as a contributor to ASF JIRA. My username is oozer.
Thanks,
Done. Welcome!
On Tue, Mar 9, 2021 at 11:22 AM Eduardo Barrera <
eduardo.barr...@wizeline.com> wrote:
> Hello team,
>
> Can you please add 'ebarrera' to the JIRA contributor list?
>
> Thanks!
> Eduardo
>
>
>
>
>
>
>
>
> *This email and its contents (including any attachments) are being sent
> toy
Hello team,
Can you please add 'ebarrera' to the JIRA contributor list?
Thanks!
Eduardo
--
*This email and its contents (including any attachments) are being sent to
you on the condition of confidentiality and may be protected by legal
privilege. Access to this email by anyone other than the in
+1 (binding)
Thank you!
For anyone curious, validations of the vendoring process took place on
https://github.com/apache/beam/pull/14146
Kenn
On Tue, Mar 9, 2021 at 9:23 AM Brian Hulette wrote:
> There are several jiras blocked by a Calcite upgrade. See
> https://issues.apache.org/jira/browse
Thanks Pablo!
On Tue, Mar 9, 2021 at 11:35 AM Pablo Estrada wrote:
> Hi Benjamin!
> Welcome to Beam. I've added you as a contributor, and now you can assign
> issues to yourself on JIRA.
> Thanks,
> -P.
>
> On Tue, Mar 9, 2021 at 8:52 AM Benjamin Gonzalez Delgado <
> benjamin.gonza...@wizeline.c
Added. Welcome!
On Tue, Mar 9, 2021 at 7:51 AM Josias Rico García
wrote:
> josmrico
>
>
> Thanks,
>
>
>
>
>
>
>
>
> *This email and its contents (including any attachments) are being sent
> toyou on the condition of confidentiality and may be protected by
> legalprivilege. Access to this email b
Hi Miguel!
I've added you as a contributor to JIRA. Welcome!
Best
-P.
On Tue, Mar 9, 2021 at 9:34 AM Miguel Anzo Palomo
wrote:
> Hi, I'm Miguel from Wizeline, I would like to be added to the contributor
> list to be able to start assigning me some tickets and start working in
> them.
>
> Thanks
Hi Benjamin!
Welcome to Beam. I've added you as a contributor, and now you can assign
issues to yourself on JIRA.
Thanks,
-P.
On Tue, Mar 9, 2021 at 8:52 AM Benjamin Gonzalez Delgado <
benjamin.gonza...@wizeline.com> wrote:
> This is Benjamin from Wizeline. I will be working on some issues. Can
>
Hi Elena!
Welcome! I've added you as contributor. Let me know if you have any
questions!
Best
-P.
On Tue, Mar 9, 2021 at 8:55 AM Elena Nuzhdina
wrote:
>
> *Hi, I am Nuzhdina Elena. *
>
>
>
> *I am interested in contributing to develop the Apache Beam SDK. I'd like
> to be added as a Jira contrib
Hi, I'm Miguel from Wizeline, I would like to be added to the contributor
list to be able to start assigning me some tickets and start working in
them.
Thanks
--
Miguel Angel Anzo Palomo | WIZELINE
Software Engineer
miguel.a...@wizeline.com
Remote Office
--
*This email and its contents (inc
Hi Gunnar!
Thanks for reaching out. I worked with a few other people on developing
this integration, and we chose the name of DebeziumIO in part following
Beam convention, and also wanting to be transparent about what technologies
are underlying the connector (in my head, it was also about giving c
There are several jiras blocked by a Calcite upgrade. See
https://issues.apache.org/jira/browse/BEAM-9379
On Tue, Mar 9, 2021 at 5:17 AM Ismaël Mejía wrote:
> Just out of curiosity is there some feature we are expecting from
> Calcite that pushes this upgrade or is this just catching up for the
thanks
Hi, I am Nuzhdina Elena.
I am interested in contributing to develop the Apache Beam SDK. I'd like to be
added as a Jira contributor so that I can assign issues to myself. My ASF Jira
Username is "elena.nuzhdina".
Thank you!
This is Benjamin from Wizeline. I will be working on some issues. Can
someone add me as a contributor to Beam's Jira issue tracker? I would like
to create/assign tickets for my work.
My Jira ID is benglez
Thanks in advance!
--
*This email and its contents (including any attachments) are being se
Hi all,
The March report is due tomorrow. Through this link anyone should be able
to comment and make suggestions. Please help me out by adding highlights.
https://s.apache.org/beam-draft-report-2021-03
You can read past reports at
https://whimsy.apache.org/board/minutes/Beam.html to get a feel
Basically, you should not have a data loss because your pipeline will be
restarted from checkpoints. Do you experience another behaviour?
To avoid duplicates of written messages, you may want to use
“KafkaIO.Write.withEOS()” option but it will slow down the writes.
> On 4 Mar 2021, at 18:21,
josmrico
Thanks,
--
*This email and its contents (including any attachments) are being sent to
you on the condition of confidentiality and may be protected by legal
privilege. Access to this email by anyone other than the intended recipient
is unauthorized. If you are not the intended recipient
Hello Gunnar,
Thanks for the message and willingness to collaborate. Most connectors
on Beam are called based on the target system name + the IO suffix,
e.g. KafkaIO, PubsubIO, KinesisIO, etc. so naming it DebeziumIO makes
sense from the Beam side. So far nobody has requested us to rename a
Beam c
Just out of curiosity is there some feature we are expecting from
Calcite that pushes this upgrade or is this just catching up for the
sake of security improvements + not having old dependencies?
On Tue, Mar 9, 2021 at 12:23 AM Ahmet Altay wrote:
>
> +1 (binding)
>
> On Mon, Mar 8, 2021 at 3:21
Hi,
I'm the lead of the Debezium project and just saw that the Apache Beam
community is working on integrating Debezium into Beam. That's really
exciting. and I'd love to see a demo of this. If there's anything the
Debezium community can do in order to help with this, please let us know on
the Deb
+1 (binding)
Regards
JB
> Le 8 mars 2021 à 20:37, Andrew Pilloud a écrit :
>
> Hi everyone,
> Please review and vote on the release candidate #1 for
> beam-vendor-calcite-1_26_0 version 0.1, as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific
23 matches
Mail list logo