Re: Add oozer to JIRA contribution list

[Ahmet Altay]

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,
>

Add oozer to JIRA contribution list

[Onur Ozer]

Hi There,

Could you please add me as a contributor to ASF JIRA. My username is oozer.

Thanks,

Re: Add ebarrera to JIRA contributor list

[Ahmet Altay]

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
> toyou on the condition of confidentiality and may be protected by
> legalprivilege. Access to this email by anyone other than the intended
> recipientis unauthorized. If you are not the intended recipient, please
> immediatelynotify the sender by replying to this message and delete the
> materialimmediately from your system. Any further use, dissemination,
> distributionor reproduction of this email is strictly prohibited. Further,
> norepresentation is made with respect to any content contained in this
> email.*

Add ebarrera to JIRA contributor list

[Eduardo Barrera]

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 intended recipient
is unauthorized. If you are not the intended recipient, please immediately
notify the sender by replying to this message and delete the material
immediately from your system. Any further use, dissemination, distribution
or reproduction of this email is strictly prohibited. Further, no
representation is made with respect to any content contained in this email.*

Re: [VOTE] Release vendor-calcite-1_26_0 version 0.1, release candidate #1

[Kenneth Knowles]

+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/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
>> 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 PM Pablo Estrada 
>> wrote:
>> >>
>> >> +1 (binding) verified signature
>> >>
>> >> On Mon, Mar 8, 2021 at 12:05 PM Kai Jiang  wrote:
>> >>>
>> >>> +1 (non-binding)
>> >>>
>> >>> On Mon, Mar 8, 2021 at 11:37 AM Andrew Pilloud 
>> wrote:
>> 
>>  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 comments)
>> 
>> 
>>  Reviewers are encouraged to test their own use cases with the
>> release candidate, and vote +1 if no issues are found.
>> 
>>  The complete staging area is available for your review, which
>> includes:
>>  * the official Apache source release to be deployed to
>> dist.apache.org [1], which is signed with the key with fingerprint
>> 9E7CEC0661EFD610B632C610AE8FE17F9F8AE3D4 [2],
>>  * all artifacts to be deployed to the Maven Central Repository [3],
>>  * source code commit "0f52187e344dad9bca4c183fe51151b733b24e35" [4].
>> 
>>  The vote will be open for at least 72 hours. It is adopted by
>> majority approval, with at least 3 PMC affirmative votes.
>> 
>>  Thanks,
>>  Andrew
>> 
>>  [1]
>> https://dist.apache.org/repos/dist/dev/beam/vendor/beam-vendor-calcite-1_26_0/0.1/
>>  [2] https://dist.apache.org/repos/dist/release/beam/KEYS
>>  [3]
>> https://repository.apache.org/content/repositories/orgapachebeam-1163/
>>  [4]
>> https://github.com/apache/beam/tree/0f52187e344dad9bca4c183fe51151b733b24e35
>>
>

Re: Add benglez to JIRA contributor list

[Benjamin Gonzalez Delgado]

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.com> wrote:
>
>> 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 sent
>> toyou on the condition of confidentiality and may be protected by
>> legalprivilege. Access to this email by anyone other than the intended
>> recipientis unauthorized. If you are not the intended recipient, please
>> immediatelynotify the sender by replying to this message and delete the
>> materialimmediately from your system. Any further use, dissemination,
>> distributionor reproduction of this email is strictly prohibited. Further,
>> norepresentation is made with respect to any content contained in this
>> email.*
>
>

-- 
*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, please immediately
notify the sender by replying to this message and delete the material
immediately from your system. Any further use, dissemination, distribution
or reproduction of this email is strictly prohibited. Further, no
representation is made with respect to any content contained in this email.*

Re: Add username to JIRA contributor list

[Pablo Estrada]

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 by anyone other than the intended
> recipientis unauthorized. If you are not the intended recipient, please
> immediatelynotify the sender by replying to this message and delete the
> materialimmediately from your system. Any further use, dissemination,
> distributionor reproduction of this email is strictly prohibited. Further,
> norepresentation is made with respect to any content contained in this
> email.*

Re: Add to JIRA contributor list

[Pablo Estrada]

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
> --
>
> Miguel Angel Anzo Palomo | WIZELINE
>
> Software Engineer
>
> miguel.a...@wizeline.com
>
> Remote Office
>
>
>
>
>
>
>
>
> *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 by anyone other than the intended
> recipientis unauthorized. If you are not the intended recipient, please
> immediatelynotify the sender by replying to this message and delete the
> materialimmediately from your system. Any further use, dissemination,
> distributionor reproduction of this email is strictly prohibited. Further,
> norepresentation is made with respect to any content contained in this
> email.*

Re: Add benglez to JIRA contributor list

[Pablo Estrada]

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
> 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 sent
> toyou on the condition of confidentiality and may be protected by
> legalprivilege. Access to this email by anyone other than the intended
> recipientis unauthorized. If you are not the intended recipient, please
> immediatelynotify the sender by replying to this message and delete the
> materialimmediately from your system. Any further use, dissemination,
> distributionor reproduction of this email is strictly prohibited. Further,
> norepresentation is made with respect to any content contained in this
> email.*

Re: Ask to be added as Jira contributor

[Pablo Estrada]

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 contributor so that I can assign issues to myself. My
> ASF Jira Username is "elena.nuzhdina". *
>
>
> *Thank you!*
>

Add to JIRA contributor list

[Miguel Anzo Palomo]

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 (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, please immediately
notify the sender by replying to this message and delete the material
immediately from your system. Any further use, dissemination, distribution
or reproduction of this email is strictly prohibited. Further, no
representation is made with respect to any content contained in this email.*

Re: Debezium integration

[Pablo Estrada]

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 credit
to y'all for developing a valuable technology that we wanted to integrate
with).

I wonder if the context provided by Ismael, along with his suggestion of
clearly documenting that this is a Beam community effort makes you feel
differently about the naming of the integration?
Thanks again!
-P.

On Tue, Mar 9, 2021 at 5:55 AM Ismaël Mejía  wrote:

> 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 connector because it is assumed that if the code of the connector
> resides on the Apache project repository the maintenance comes from
> the Beam community.
>
> I don't know what others in the community think, I suppose it is still
> possible to rename it since the component has not been released yet,
> it will be released on Beam 2.29.0 (branch cut tomorrow).
>
> The real deal is what name would be appropriate that allows users to
> find it easily, specially as a single word name. Any suggestions? Or
> would making it clear in the component documentation + webpage that
> this component is not developed by the Debezium project be enough for
> the Debezium community so we (Beam) can use the name?
>
> Best,
> Ismaël
>
>
> On Tue, Mar 9, 2021 at 12:09 PM Gunnar Morling
>  wrote:
> >
> > 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 Debezium mailing list [1].
> >
> > What I'd like to kindly ask for though is finding a name for this
> component other than "DebeziumIO", as currently used in the README [2].
> This may suggest that this is an effort by the Debezium community itself,
> and we should avoid any potential confusion here. A name like "Apache Beam
> connector for Debezium" would be fine.
> >
> > Thanks a lot,
> >
> > --Gunnar
> >
> > [1] https://groups.google.com/g/debezium
> > [2] https://github.com/apache/beam/tree/master/sdks/java/io/debezium/src
> >
>

Re: [VOTE] Release vendor-calcite-1_26_0 version 0.1, release candidate #1

[Brian Hulette]

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
> 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 PM Pablo Estrada  wrote:
> >>
> >> +1 (binding) verified signature
> >>
> >> On Mon, Mar 8, 2021 at 12:05 PM Kai Jiang  wrote:
> >>>
> >>> +1 (non-binding)
> >>>
> >>> On Mon, Mar 8, 2021 at 11:37 AM Andrew Pilloud 
> wrote:
> 
>  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 comments)
> 
> 
>  Reviewers are encouraged to test their own use cases with the release
> candidate, and vote +1 if no issues are found.
> 
>  The complete staging area is available for your review, which
> includes:
>  * the official Apache source release to be deployed to
> dist.apache.org [1], which is signed with the key with fingerprint
> 9E7CEC0661EFD610B632C610AE8FE17F9F8AE3D4 [2],
>  * all artifacts to be deployed to the Maven Central Repository [3],
>  * source code commit "0f52187e344dad9bca4c183fe51151b733b24e35" [4].
> 
>  The vote will be open for at least 72 hours. It is adopted by
> majority approval, with at least 3 PMC affirmative votes.
> 
>  Thanks,
>  Andrew
> 
>  [1]
> https://dist.apache.org/repos/dist/dev/beam/vendor/beam-vendor-calcite-1_26_0/0.1/
>  [2] https://dist.apache.org/repos/dist/release/beam/KEYS
>  [3]
> https://repository.apache.org/content/repositories/orgapachebeam-1163/
>  [4]
> https://github.com/apache/beam/tree/0f52187e344dad9bca4c183fe51151b733b24e35
>

Subscribe

[Shameera Rathnayaka Yodage]

thanks

Ask to be added as Jira contributor

[Elena Nuzhdina]

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!

Add benglez to JIRA contributor list

[Benjamin Gonzalez Delgado]

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 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, please immediately
notify the sender by replying to this message and delete the material
immediately from your system. Any further use, dissemination, distribution
or reproduction of this email is strictly prohibited. Further, no
representation is made with respect to any content contained in this email.*

DRAFT - Beam board report March 2021

[Kenneth Knowles]

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 for it.
Here are some specific examples of things that are good to add:

 - highlights from CHANGES.md
 - interesting technical discussions that steer the project
 - major integrations with other projects
 - community events
 - major user facing addition/deprecation

Don't worry about exact wording or formatting. I will edit the words and
the tool accepts markdown so I reformat as well. It helps me if you use
https://s.apache.org to create short links for things, as the board report
tool is a bit strict about formatting and does not like long links.

Kenn

Re: Question regarding error raised in KafkaWriter processElement() and finishBundle()

[Alexey Romanenko]

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, Antonio Si  wrote:
> 
> Hi all,
> 
> I have a question regarding error being thrown in 
> KafkaWriter.processElement(). Let's say my pipeline eventually reached 
> KafkaWriter.processElement() twice. The first time is successful and the 
> second time, for some reason is not successful and set numSendFailures to 1.
> 
> After that  DoFnOperator.checkInvokeFinishBundleByTime kicks in and invokes 
> KafkaWriter.finishBundle() and it throws an IOException because 
> numSendFailures is not 0.
> 
> Does it mean that I will have some data lost and my application will need to 
> handle it somehow? What would be the a recommended way of error handling in 
> Beam pipelines?
> 
> Thanks in advance.
> 
> Antonio.
> 
> 
> 

Add username to JIRA contributor list

[Josias Rico García]

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, please immediately
notify the sender by replying to this message and delete the material
immediately from your system. Any further use, dissemination, distribution
or reproduction of this email is strictly prohibited. Further, no
representation is made with respect to any content contained in this email.*

Re: Debezium integration

[Ismaël Mejía]

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 connector because it is assumed that if the code of the connector
resides on the Apache project repository the maintenance comes from
the Beam community.

I don't know what others in the community think, I suppose it is still
possible to rename it since the component has not been released yet,
it will be released on Beam 2.29.0 (branch cut tomorrow).

The real deal is what name would be appropriate that allows users to
find it easily, specially as a single word name. Any suggestions? Or
would making it clear in the component documentation + webpage that
this component is not developed by the Debezium project be enough for
the Debezium community so we (Beam) can use the name?

Best,
Ismaël


On Tue, Mar 9, 2021 at 12:09 PM Gunnar Morling
 wrote:
>
> 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 Debezium mailing list [1].
>
> What I'd like to kindly ask for though is finding a name for this component 
> other than "DebeziumIO", as currently used in the README [2]. This may 
> suggest that this is an effort by the Debezium community itself, and we 
> should avoid any potential confusion here. A name like "Apache Beam connector 
> for Debezium" would be fine.
>
> Thanks a lot,
>
> --Gunnar
>
> [1] https://groups.google.com/g/debezium
> [2] https://github.com/apache/beam/tree/master/sdks/java/io/debezium/src
>

Re: [VOTE] Release vendor-calcite-1_26_0 version 0.1, release candidate #1

[Ismaël Mejía]

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 PM Pablo Estrada  wrote:
>>
>> +1 (binding) verified signature
>>
>> On Mon, Mar 8, 2021 at 12:05 PM Kai Jiang  wrote:
>>>
>>> +1 (non-binding)
>>>
>>> On Mon, Mar 8, 2021 at 11:37 AM Andrew Pilloud  wrote:

 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 comments)


 Reviewers are encouraged to test their own use cases with the release 
 candidate, and vote +1 if no issues are found.

 The complete staging area is available for your review, which includes:
 * the official Apache source release to be deployed to dist.apache.org 
 [1], which is signed with the key with fingerprint 
 9E7CEC0661EFD610B632C610AE8FE17F9F8AE3D4 [2],
 * all artifacts to be deployed to the Maven Central Repository [3],
 * source code commit "0f52187e344dad9bca4c183fe51151b733b24e35" [4].

 The vote will be open for at least 72 hours. It is adopted by majority 
 approval, with at least 3 PMC affirmative votes.

 Thanks,
 Andrew

 [1] 
 https://dist.apache.org/repos/dist/dev/beam/vendor/beam-vendor-calcite-1_26_0/0.1/
 [2] https://dist.apache.org/repos/dist/release/beam/KEYS
 [3] https://repository.apache.org/content/repositories/orgapachebeam-1163/
 [4] 
 https://github.com/apache/beam/tree/0f52187e344dad9bca4c183fe51151b733b24e35

Debezium integration

[Gunnar Morling]

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 Debezium mailing list [1].

What I'd like to kindly ask for though is finding a name for this component
other than "DebeziumIO", as currently used in the README [2]. This may
suggest that this is an effort by the Debezium community itself, and we
should avoid any potential confusion here. A name like "Apache Beam
connector for Debezium" would be fine.

Thanks a lot,

--Gunnar

[1] https://groups.google.com/g/debezium
[2] https://github.com/apache/beam/tree/master/sdks/java/io/debezium/src

Re: [VOTE] Release vendor-calcite-1_26_0 version 0.1, release candidate #1

[Jean-Baptiste Onofre]

+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 comments)
> 
> 
> Reviewers are encouraged to test their own use cases with the release 
> candidate, and vote +1 if no issues are found.
> 
> The complete staging area is available for your review, which includes:
> * the official Apache source release to be deployed to dist.apache.org 
>  [1], which is signed with the key with fingerprint 
> 9E7CEC0661EFD610B632C610AE8FE17F9F8AE3D4 [2],
> * all artifacts to be deployed to the Maven Central Repository [3],
> * source code commit "0f52187e344dad9bca4c183fe51151b733b24e35" [4].
> 
> The vote will be open for at least 72 hours. It is adopted by majority 
> approval, with at least 3 PMC affirmative votes.
> 
> Thanks,
> Andrew
> 
> [1] 
> https://dist.apache.org/repos/dist/dev/beam/vendor/beam-vendor-calcite-1_26_0/0.1/
>  
> 
> [2] https://dist.apache.org/repos/dist/release/beam/KEYS 
> 
> [3] https://repository.apache.org/content/repositories/orgapachebeam-1163/ 
> 
> [4] 
> https://github.com/apache/beam/tree/0f52187e344dad9bca4c183fe51151b733b24e35 
>