Re: [VOTE] Release 2.63.0, release candidate #2

2025-02-13 Thread Jan Lukavský 

+1 (binding)

Tested Java SDK with Flink Runner.

 Jan

On 2/12/25 19:46, XQ Hu via dev wrote:
+1 (non-binding). Tested the Python SDK with a simple Dataflow ML 
pipeline: 
https://github.com/google/dataflow-ml-starter/actions/runs/13291770412/job/37114110434


On Wed, Feb 12, 2025 at 12:05 PM Jack McCluskey via dev 
 wrote:


Hi everyone,

Please review and vote on the release candidate #2 for the version
2.63.0, 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. Only PMC
member votes will count towards the final vote, but votes from all
community members are encouraged and helpful for finding
regressions; you can either test your own use cases [13] or use
cases from the validation sheet [10].

The complete staging area is available for your review, which
includes:
* GitHub Release notes [1],
* the official Apache source release to be deployed to
dist.apache.org  [2], which is signed
with the key with fingerprint D20316F712213422 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v2.63.0-RC2" [5],
* website pull request listing the release [6], the blog post [6],
and publishing the API reference manual [7].
* Python artifacts are deployed along with the source release to
dist.apache.org  [2] and PyPI[8].
* Go artifacts and documentation are available at pkg.go.dev
 [9]
* Validation sheet with a tab for 2.63.0 release to help with
validation [10].
* Docker images published to Docker Hub [11].
* PR to run tests against release branch [12].
* Github Release pre-release page for v2.63.0-RC2 [13].

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

For guidelines on how to try the release in your projects, check
out our RC testing guide [13].

Thanks,

Jack McCluskey

[1] https://github.com/apache/beam/milestone/27
[2] https://dist.apache.org/repos/dist/dev/beam/2.63.0/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
[4]
https://repository.apache.org/content/repositories/orgapachebeam-1400/
[5] https://github.com/apache/beam/tree/v2.63.0-RC2
[6] https://github.com/apache/beam/pull/33905
[7] https://github.com/apache/beam-site/pull/677
[8] https://pypi.org/project/apache-beam/2.63.0rc2/
[9]
https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.63.0-RC2/go/pkg/beam
[10]

https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1785697132
[11] https://hub.docker.com/search?q=apache%2Fbeam&type=image

[12] https://github.com/apache/beam/pull/33870
[13] https://github.com/apache/beam/releases/tag/v2.63.0-RC2
[14]

https://github.com/apache/beam/blob/master/contributor-docs/rc-testing-guide.md


-- 




Jack McCluskey
SWE - DataPLS PLAT/ Dataflow ML
RDU
jrmcclus...@google.com

Re: [VOTE] Release 2.63.0, release candidate #2

2025-02-13 Thread Rohit Sinha via dev 
+1 (non-binding). Tested Java SDK with batch, streaming pipelines both on
legacy and runner_V2.



On Thu, Feb 13, 2025 at 12:36 AM Jan Lukavský  wrote:

> +1 (binding)
>
> Tested Java SDK with Flink Runner.
>
>  Jan
> On 2/12/25 19:46, XQ Hu via dev wrote:
>
> +1 (non-binding). Tested the Python SDK with a simple Dataflow ML
> pipeline:
> https://github.com/google/dataflow-ml-starter/actions/runs/13291770412/job/37114110434
>
> On Wed, Feb 12, 2025 at 12:05 PM Jack McCluskey via dev <
> dev@beam.apache.org> wrote:
>
>> Hi everyone,
>>
>> Please review and vote on the release candidate #2 for the version
>> 2.63.0, 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. Only PMC member votes will
>> count towards the final vote, but votes from all community members are
>> encouraged and helpful for finding regressions; you can either test your
>> own use cases [13] or use cases from the validation sheet [10].
>>
>> The complete staging area is available for your review, which includes:
>> * GitHub Release notes [1],
>> * the official Apache source release to be deployed to dist.apache.org [2],
>> which is signed with the key with fingerprint D20316F712213422 [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.63.0-RC2" [5],
>> * website pull request listing the release [6], the blog post [6], and
>> publishing the API reference manual [7].
>> * Python artifacts are deployed along with the source release to
>> dist.apache.org [2] and PyPI[8].
>> * Go artifacts and documentation are available at pkg.go.dev [9]
>> * Validation sheet with a tab for 2.63.0 release to help with validation
>> [10].
>> * Docker images published to Docker Hub [11].
>> * PR to run tests against release branch [12].
>> * Github Release pre-release page for v2.63.0-RC2 [13].
>>
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PMC affirmative votes.
>>
>> For guidelines on how to try the release in your projects, check out our
>> RC testing guide [13].
>>
>> Thanks,
>>
>> Jack McCluskey
>>
>> [1] https://github.com/apache/beam/milestone/27
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.63.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1400/
>> [5] https://github.com/apache/beam/tree/v2.63.0-RC2
>> [6] https://github.com/apache/beam/pull/33905
>> [7] https://github.com/apache/beam-site/pull/677
>> [8] https://pypi.org/project/apache-beam/2.63.0rc2/
>> [9]
>> https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.63.0-RC2/go/pkg/beam
>> [10]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1785697132
>> [11] https://hub.docker.com/search?q=apache%2Fbeam&type=image
>> [12] https://github.com/apache/beam/pull/33870
>> [13] https://github.com/apache/beam/releases/tag/v2.63.0-RC2
>> [14]
>> https://github.com/apache/beam/blob/master/contributor-docs/rc-testing-guide.md
>>
>>
>> --
>>
>>
>> Jack McCluskey
>> SWE - DataPLS PLAT/ Dataflow ML
>> RDU
>> jrmcclus...@google.com
>>
>>
>>

Re: [URGENT] Re: [Action Required] GSoC 2025 is coming

2025-02-13 Thread XQ Hu via dev 
We have proposed several ideas here:
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2025+Ideas+list#GSoC2025Ideaslist-Beam

Not sure you can access it.

On Thu, Feb 13, 2025 at 1:35 AM SIDDHARTH SALIAN <
siddharthsalia...@gmail.com> wrote:

> Hi,
>
> Well they are interesting projects, if you could tell me language for
> example if these are java projects or c/c++?
>
>
>
> Thanks,
>
> Siddharth
>
>
>
> *From: *Talat Uyarer via dev 
> *Date: *Thursday, 13 February 2025 at 12:01 PM
> *To: *dev@beam.apache.org 
> *Cc: *Talat Uyarer 
> *Subject: *Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
>
> Hi All,
>
> I have few ideas for projects that we can put forward for Google Summer of
> Code. Here are some thoughts:
>
> *   English SDK for Apache Beam.
> *   Apache Polaris Catalog Support
> *   Support Call Stored Procedure for Beam SQL
> *   ML Support on Beam SQL
>
> I will create tickets for these, if the community is also ok for those
> projects.
>
>
>
> Talat
>
>
>
> On Wed, Feb 12, 2025 at 10:20 PM SIDDHARTH SALIAN <
> siddharthsalia...@gmail.com> wrote:
>
> Hello people,
>
>1. Any updates on GSOC projects? Any project finalised? Also we need
>to decide and form team too.
>2. Does anyone have a project in their mind?
>3. Also not much of a time is left.
>
>
>
> Thanks,
>
> Siddharth
>
>
>
> *From: *Yi Hu via dev 
> *Date: *Thursday, 13 February 2025 at 1:01 AM
> *To: *dev@beam.apache.org 
> *Cc: *Yi Hu 
> *Subject: *Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
>
> Hi there,
>
>
>
> For those who are looking for project ideas, Beam has migrated from Jira
> to GitHub Issue for tracking issues, and the former was read only.
>
>
>
> e.g. BEAM-3767 has been moved to
> https://github.com/apache/beam/issues/18730
>
>
>
> There is a "gsoc" label marks potential projects:
> https://github.com/apache/beam/issues?q=state%3Aopen%20label%3A%22gsoc%22
>
>
>
> However I see some Issues are stale. Going to clean up and add some new
> Issues into this label.
>
>
>
> Regards,
>
>
>
> Yi
>
>
>
>
>
> On Wed, Feb 12, 2025 at 1:30 PM Ahmet Altay via dev 
> wrote:
>
> Hi Charles,
>
>
>
> Thank you for your interest!
>
>
>
> I think CEP is still an open project. We have made some progress on
> managed IO but there is still more to be done there.
>
>
>
> Adding folks, who can help you with these questions and see if these
> projects still makes sense this year as well. : @Danny McCormick
>  @Talat Uyarer  @Chamikara
> Jayalath 
>
>
>
> Ahmet
>
>
>
> On Wed, Feb 12, 2025 at 10:26 AM Charles Nguyen 
> wrote:
>
> Hi all,
>
>
>
> I've been lurking around the project for a while and, if there haven't
> been any more ideas, I'd like to mention a few that I find interesting.
> These are just from past GSoC, and I'm happy to contribute to any one of
> these:
>
>- Complex Event Processing [1]: This was all the way back in 2022 and
>I guess it was related/partially done with match_recognize in BeamSQL [2]
>
>
>- ManagedIO [3]: This was a project idea from just last year. I don't
>think anyone did this, and ManagedIO seems new so there are always tons of
>other IO integrations we can add to.
>
> They're all seem large projects to me. Hopefully these are still relevant
> ideas for this year!
>
>
>
> [1] https://issues.apache.org/jira/browse/BEAM-3767
>
> [2] https://issues.apache.org/jira/browse/BEAM-9543
>
> [3]
> https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2024+Ideas+list#GSoC2024Ideaslist-[GSOC][Beam]AddconnectorstoBeamManagedIO
>
>
> --
>
> *From:* Ahmet Altay via dev 
> *Sent:* Wednesday, February 12, 2025 12:33 PM
> *To:* dev 
> *Cc:* Ahmet Altay 
> *Subject:* Fwd: [URGENT] Re: [Action Required] GSoC 2025 is coming
>
>
>
> Hi all,
>
>
>
> We need a few GSoC 2025 projects urgently. If you are willing to host a
> project, this is a great opportunity for us to make some important
> improvements to Beam and also have new engaged contributors. GSoC, in my
> own words, is open source internships, paid by Google, scoped for 90, 175,
> or 350 hours that happen over summer. If you have any questions, we will be
> happy to help.
>
>
>
> *Call to action:* As soon as possible, please add ideas here to jira,
> ideally today.
>
>
>
> From Danny: "We file jiras like
> https://issues.apache.org/jira/browse/GSOC-273 in the `Comdev GSOC
> (GSOC)` project with the `Beam`, `gsoc`, `gsoc2025`, and `mentor` labels."
>
>
>
> Ahmet
>
>
>
> -- Forwarded message -
> From: *Sanyam Goel* 
> Date: Tue, Feb 11, 2025 at 10:40 PM
> Subject: [URGENT] Re: [Action Required] GSoC 2025 is coming
> To: , , private
> hugegraph , , <
> priv...@shardingsphere.apache.org>, private ,
> , , private <
> priv...@shenyu.apache.org>, private , <
> priv...@eventmesh.apache.org>, , private <
> priv...@rocketmq.apache.org>, , <
> priv...@dubbo.apache.org>, , Airavata Private
> , , private <
> priv...@beam.apache.org>, , <
> priv...@streampipes.apache.org>, ,
> private ,

Re: [URGENT] Re: [Action Required] GSoC 2025 is coming

2025-02-13 Thread Rohit Sinha via dev 
I created three gsoc2025 project ideas:
1. https://github.com/apache/beam/issues/33980
2. https://github.com/apache/beam/issues/33981
3. https://github.com/apache/beam/issues/33982

I added the label gsoc but github says it can't be added. Does anyone know
whats going on?

On Thu, Feb 13, 2025 at 6:50 AM XQ Hu via dev  wrote:

> We have proposed several ideas here:
> https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2025+Ideas+list#GSoC2025Ideaslist-Beam
>
> Not sure you can access it.
>
> On Thu, Feb 13, 2025 at 1:35 AM SIDDHARTH SALIAN <
> siddharthsalia...@gmail.com> wrote:
>
>> Hi,
>>
>> Well they are interesting projects, if you could tell me language for
>> example if these are java projects or c/c++?
>>
>>
>>
>> Thanks,
>>
>> Siddharth
>>
>>
>>
>> *From: *Talat Uyarer via dev 
>> *Date: *Thursday, 13 February 2025 at 12:01 PM
>> *To: *dev@beam.apache.org 
>> *Cc: *Talat Uyarer 
>> *Subject: *Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
>>
>> Hi All,
>>
>> I have few ideas for projects that we can put forward for Google Summer
>> of Code. Here are some thoughts:
>>
>> *   English SDK for Apache Beam.
>> *   Apache Polaris Catalog Support
>> *   Support Call Stored Procedure for Beam SQL
>> *   ML Support on Beam SQL
>>
>> I will create tickets for these, if the community is also ok for those
>> projects.
>>
>>
>>
>> Talat
>>
>>
>>
>> On Wed, Feb 12, 2025 at 10:20 PM SIDDHARTH SALIAN <
>> siddharthsalia...@gmail.com> wrote:
>>
>> Hello people,
>>
>>1. Any updates on GSOC projects? Any project finalised? Also we need
>>to decide and form team too.
>>2. Does anyone have a project in their mind?
>>3. Also not much of a time is left.
>>
>>
>>
>> Thanks,
>>
>> Siddharth
>>
>>
>>
>> *From: *Yi Hu via dev 
>> *Date: *Thursday, 13 February 2025 at 1:01 AM
>> *To: *dev@beam.apache.org 
>> *Cc: *Yi Hu 
>> *Subject: *Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
>>
>> Hi there,
>>
>>
>>
>> For those who are looking for project ideas, Beam has migrated from Jira
>> to GitHub Issue for tracking issues, and the former was read only.
>>
>>
>>
>> e.g. BEAM-3767 has been moved to
>> https://github.com/apache/beam/issues/18730
>>
>>
>>
>> There is a "gsoc" label marks potential projects:
>> https://github.com/apache/beam/issues?q=state%3Aopen%20label%3A%22gsoc%22
>>
>>
>>
>> However I see some Issues are stale. Going to clean up and add some new
>> Issues into this label.
>>
>>
>>
>> Regards,
>>
>>
>>
>> Yi
>>
>>
>>
>>
>>
>> On Wed, Feb 12, 2025 at 1:30 PM Ahmet Altay via dev 
>> wrote:
>>
>> Hi Charles,
>>
>>
>>
>> Thank you for your interest!
>>
>>
>>
>> I think CEP is still an open project. We have made some progress on
>> managed IO but there is still more to be done there.
>>
>>
>>
>> Adding folks, who can help you with these questions and see if these
>> projects still makes sense this year as well. : @Danny McCormick
>>  @Talat Uyarer  @Chamikara
>> Jayalath 
>>
>>
>>
>> Ahmet
>>
>>
>>
>> On Wed, Feb 12, 2025 at 10:26 AM Charles Nguyen 
>> wrote:
>>
>> Hi all,
>>
>>
>>
>> I've been lurking around the project for a while and, if there haven't
>> been any more ideas, I'd like to mention a few that I find interesting.
>> These are just from past GSoC, and I'm happy to contribute to any one of
>> these:
>>
>>- Complex Event Processing [1]: This was all the way back in 2022 and
>>I guess it was related/partially done with match_recognize in BeamSQL [2]
>>
>>
>>- ManagedIO [3]: This was a project idea from just last year. I don't
>>think anyone did this, and ManagedIO seems new so there are always tons of
>>other IO integrations we can add to.
>>
>> They're all seem large projects to me. Hopefully these are still relevant
>> ideas for this year!
>>
>>
>>
>> [1] https://issues.apache.org/jira/browse/BEAM-3767
>>
>> [2] https://issues.apache.org/jira/browse/BEAM-9543
>>
>> [3]
>> https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2024+Ideas+list#GSoC2024Ideaslist-[GSOC][Beam]AddconnectorstoBeamManagedIO
>>
>>
>> --
>>
>> *From:* Ahmet Altay via dev 
>> *Sent:* Wednesday, February 12, 2025 12:33 PM
>> *To:* dev 
>> *Cc:* Ahmet Altay 
>> *Subject:* Fwd: [URGENT] Re: [Action Required] GSoC 2025 is coming
>>
>>
>>
>> Hi all,
>>
>>
>>
>> We need a few GSoC 2025 projects urgently. If you are willing to host a
>> project, this is a great opportunity for us to make some important
>> improvements to Beam and also have new engaged contributors. GSoC, in my
>> own words, is open source internships, paid by Google, scoped for 90, 175,
>> or 350 hours that happen over summer. If you have any questions, we will be
>> happy to help.
>>
>>
>>
>> *Call to action:* As soon as possible, please add ideas here to jira,
>> ideally today.
>>
>>
>>
>> From Danny: "We file jiras like
>> https://issues.apache.org/jira/browse/GSOC-273 in the `Comdev GSOC
>> (GSOC)` project with the `Beam`, `gsoc`, `gsoc2025`, and `mentor` labels."
>>
>>
>>
>> Ahmet
>>
>>

Re: [VOTE] Release 2.63.0, release candidate #2

2025-02-13 Thread Chamikara Jayalath via dev 
+1 (binding)

Tested some pipelines that use the Managed API and multi-lang.

Thanks,
Cham

On Thu, Feb 13, 2025 at 11:57 AM Yi Hu via dev  wrote:

> +1 (non-binding)
>
> Tested Dataflow Templates Integration tests (Java 17, Dataflow runner v2)
> - https://github.com/GoogleCloudPlatform/DataflowTemplates/pull/2177
>
> On Thu, Feb 13, 2025 at 3:41 AM Rohit Sinha via dev 
> wrote:
>
>> +1 (non-binding). Tested Java SDK with batch, streaming pipelines both on
>> legacy and runner_V2.
>>
>>
>>
>> On Thu, Feb 13, 2025 at 12:36 AM Jan Lukavský  wrote:
>>
>>> +1 (binding)
>>>
>>> Tested Java SDK with Flink Runner.
>>>
>>>  Jan
>>> On 2/12/25 19:46, XQ Hu via dev wrote:
>>>
>>> +1 (non-binding). Tested the Python SDK with a simple Dataflow ML
>>> pipeline:
>>> https://github.com/google/dataflow-ml-starter/actions/runs/13291770412/job/37114110434
>>>
>>> On Wed, Feb 12, 2025 at 12:05 PM Jack McCluskey via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Hi everyone,

 Please review and vote on the release candidate #2 for the version
 2.63.0, 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. Only PMC member votes will
 count towards the final vote, but votes from all community members are
 encouraged and helpful for finding regressions; you can either test your
 own use cases [13] or use cases from the validation sheet [10].

 The complete staging area is available for your review, which includes:
 * GitHub Release notes [1],
 * the official Apache source release to be deployed to dist.apache.org [2],
 which is signed with the key with fingerprint D20316F712213422 [3],
 * all artifacts to be deployed to the Maven Central Repository [4],
 * source code tag "v2.63.0-RC2" [5],
 * website pull request listing the release [6], the blog post [6], and
 publishing the API reference manual [7].
 * Python artifacts are deployed along with the source release to
 dist.apache.org [2] and PyPI[8].
 * Go artifacts and documentation are available at pkg.go.dev [9]
 * Validation sheet with a tab for 2.63.0 release to help with
 validation [10].
 * Docker images published to Docker Hub [11].
 * PR to run tests against release branch [12].
 * Github Release pre-release page for v2.63.0-RC2 [13].

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

 For guidelines on how to try the release in your projects, check out
 our RC testing guide [13].

 Thanks,

 Jack McCluskey

 [1] https://github.com/apache/beam/milestone/27
 [2] https://dist.apache.org/repos/dist/dev/beam/2.63.0/
 [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 [4]
 https://repository.apache.org/content/repositories/orgapachebeam-1400/
 [5] https://github.com/apache/beam/tree/v2.63.0-RC2
 [6] https://github.com/apache/beam/pull/33905
 [7] https://github.com/apache/beam-site/pull/677
 [8] https://pypi.org/project/apache-beam/2.63.0rc2/
 [9]
 https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.63.0-RC2/go/pkg/beam
 [10]
 https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1785697132
 [11] https://hub.docker.com/search?q=apache%2Fbeam&type=image
 [12] https://github.com/apache/beam/pull/33870
 [13] https://github.com/apache/beam/releases/tag/v2.63.0-RC2
 [14]
 https://github.com/apache/beam/blob/master/contributor-docs/rc-testing-guide.md


 --


 Jack McCluskey
 SWE - DataPLS PLAT/ Dataflow ML
 RDU
 jrmcclus...@google.com

Re: [URGENT] Re: [Action Required] GSoC 2025 is coming

2025-02-13 Thread SIDDHARTH SALIAN 
Hello,
Ok I shall go through it. I think I’m not sure of getting access to the project.

Best regards,
Siddharth

From: XQ Hu via dev 
Date: Thursday, 13 February 2025 at 8:20 PM
To: dev@beam.apache.org 
Cc: XQ Hu 
Subject: Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
We have proposed several ideas here: 
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2025+Ideas+list#GSoC2025Ideaslist-Beam

Not sure you can access it.

On Thu, Feb 13, 2025 at 1:35 AM SIDDHARTH SALIAN 
mailto:siddharthsalia...@gmail.com>> wrote:
Hi,
Well they are interesting projects, if you could tell me language for example 
if these are java projects or c/c++?

Thanks,
Siddharth

From: Talat Uyarer via dev mailto:dev@beam.apache.org>>
Date: Thursday, 13 February 2025 at 12:01 PM
To: dev@beam.apache.org 
mailto:dev@beam.apache.org>>
Cc: Talat Uyarer mailto:tal...@google.com>>
Subject: Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
Hi All,

I have few ideas for projects that we can put forward for Google Summer of 
Code. Here are some thoughts:

*   English SDK for Apache Beam.
*   Apache Polaris Catalog Support
*   Support Call Stored Procedure for Beam SQL
*   ML Support on Beam SQL

I will create tickets for these, if the community is also ok for those projects.

Talat

On Wed, Feb 12, 2025 at 10:20 PM SIDDHARTH SALIAN 
mailto:siddharthsalia...@gmail.com>> wrote:
Hello people,

  1.  Any updates on GSOC projects? Any project finalised? Also we need to 
decide and form team too.
  2.  Does anyone have a project in their mind?
  3.  Also not much of a time is left.

Thanks,
Siddharth

From: Yi Hu via dev mailto:dev@beam.apache.org>>
Date: Thursday, 13 February 2025 at 1:01 AM
To: dev@beam.apache.org 
mailto:dev@beam.apache.org>>
Cc: Yi Hu mailto:ya...@google.com>>
Subject: Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
Hi there,

For those who are looking for project ideas, Beam has migrated from Jira to 
GitHub Issue for tracking issues, and the former was read only.

e.g. BEAM-3767 has been moved to https://github.com/apache/beam/issues/18730

There is a "gsoc" label marks potential projects: 
https://github.com/apache/beam/issues?q=state%3Aopen%20label%3A%22gsoc%22

However I see some Issues are stale. Going to clean up and add some new Issues 
into this label.

Regards,

Yi


On Wed, Feb 12, 2025 at 1:30 PM Ahmet Altay via dev 
mailto:dev@beam.apache.org>> wrote:
Hi Charles,

Thank you for your interest!

I think CEP is still an open project. We have made some progress on managed IO 
but there is still more to be done there.

Adding folks, who can help you with these questions and see if these projects 
still makes sense this year as well. : @Danny 
McCormick @Talat 
Uyarer @Chamikara 
Jayalath

Ahmet

On Wed, Feb 12, 2025 at 10:26 AM Charles Nguyen 
mailto:phucnh...@gmail.com>> wrote:
Hi all,

I've been lurking around the project for a while and, if there haven't been any 
more ideas, I'd like to mention a few that I find interesting. These are just 
from past GSoC, and I'm happy to contribute to any one of these:

  *   Complex Event Processing [1]: This was all the way back in 2022 and I 
guess it was related/partially done with match_recognize in BeamSQL [2]

  *   ManagedIO [3]: This was a project idea from just last year. I don't think 
anyone did this, and ManagedIO seems new so there are always tons of other IO 
integrations we can add to.
They're all seem large projects to me. Hopefully these are still relevant ideas 
for this year!

[1] https://issues.apache.org/jira/browse/BEAM-3767
[2] https://issues.apache.org/jira/browse/BEAM-9543
[3] 
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2024+Ideas+list#GSoC2024Ideaslist-[GSOC][Beam]AddconnectorstoBeamManagedIO


From: Ahmet Altay via dev mailto:dev@beam.apache.org>>
Sent: Wednesday, February 12, 2025 12:33 PM
To: dev mailto:dev@beam.apache.org>>
Cc: Ahmet Altay mailto:al...@google.com>>
Subject: Fwd: [URGENT] Re: [Action Required] GSoC 2025 is coming

Hi all,

We need a few GSoC 2025 projects urgently. If you are willing to host a 
project, this is a great opportunity for us to make some important improvements 
to Beam and also have new engaged contributors. GSoC, in my own words, is open 
source internships, paid by Google, scoped for 90, 175, or 350 hours that 
happen over summer. If you have any questions, we will be happy to help.

Call to action: As soon as possible, please add ideas here to jira, ideally 
today.

From Danny: "We file jiras like https://issues.apache.org/jira/browse/GSOC-273 
in the `Comdev GSOC (GSOC)` project with the `Beam`, `gsoc`, `gsoc2025`, and 
`mentor` labels."

Ahmet

-- Forwarded message -
From: Sanyam Goel mailto:san...@apache.org>>
Date: Tue, Feb 11, 2025 at 10:40 PM
Subject: [URGENT] Re: [Action Required] GS

Re: [URGENT] Re: [Action Required] GSoC 2025 is coming

2025-02-13 Thread Ahmet Altay via dev 
This is a publicly accessible page:
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2025+Ideas+list#GSoC2025Ideaslist-Beam

On Thu, Feb 13, 2025 at 8:45 AM SIDDHARTH SALIAN <
siddharthsalia...@gmail.com> wrote:

> Hello,
>
> Ok I shall go through it. I think I’m not sure of getting access to the
> project.
>
>
>
> Best regards,
>
> Siddharth
>
>
>
> *From: *XQ Hu via dev 
> *Date: *Thursday, 13 February 2025 at 8:20 PM
> *To: *dev@beam.apache.org 
> *Cc: *XQ Hu 
> *Subject: *Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
>
> We have proposed several ideas here:
> https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2025+Ideas+list#GSoC2025Ideaslist-Beam
>
>
>
> Not sure you can access it.
>
>
>
> On Thu, Feb 13, 2025 at 1:35 AM SIDDHARTH SALIAN <
> siddharthsalia...@gmail.com> wrote:
>
> Hi,
>
> Well they are interesting projects, if you could tell me language for
> example if these are java projects or c/c++?
>
>
>
> Thanks,
>
> Siddharth
>
>
>
> *From: *Talat Uyarer via dev 
> *Date: *Thursday, 13 February 2025 at 12:01 PM
> *To: *dev@beam.apache.org 
> *Cc: *Talat Uyarer 
> *Subject: *Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
>
> Hi All,
>
> I have few ideas for projects that we can put forward for Google Summer of
> Code. Here are some thoughts:
>
> *   English SDK for Apache Beam.
> *   Apache Polaris Catalog Support
> *   Support Call Stored Procedure for Beam SQL
> *   ML Support on Beam SQL
>
> I will create tickets for these, if the community is also ok for those
> projects.
>
>
They are interesting. Go for it, if you are willing to mentor at least one
:)


>
>
> Talat
>
>
>
> On Wed, Feb 12, 2025 at 10:20 PM SIDDHARTH SALIAN <
> siddharthsalia...@gmail.com> wrote:
>
> Hello people,
>
>1. Any updates on GSOC projects? Any project finalised? Also we need
>to decide and form team too.
>2. Does anyone have a project in their mind?
>3. Also not much of a time is left.
>
>
>
> Thanks,
>
> Siddharth
>
>
>
> *From: *Yi Hu via dev 
> *Date: *Thursday, 13 February 2025 at 1:01 AM
> *To: *dev@beam.apache.org 
> *Cc: *Yi Hu 
> *Subject: *Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
>
> Hi there,
>
>
>
> For those who are looking for project ideas, Beam has migrated from Jira
> to GitHub Issue for tracking issues, and the former was read only.
>
>
>
> e.g. BEAM-3767 has been moved to
> https://github.com/apache/beam/issues/18730
>
>
>
> There is a "gsoc" label marks potential projects:
> https://github.com/apache/beam/issues?q=state%3Aopen%20label%3A%22gsoc%22
>
>
>
> However I see some Issues are stale. Going to clean up and add some new
> Issues into this label.
>
>
>
> Regards,
>
>
>
> Yi
>
>
>
>
>
> On Wed, Feb 12, 2025 at 1:30 PM Ahmet Altay via dev 
> wrote:
>
> Hi Charles,
>
>
>
> Thank you for your interest!
>
>
>
> I think CEP is still an open project. We have made some progress on
> managed IO but there is still more to be done there.
>
>
>
> Adding folks, who can help you with these questions and see if these
> projects still makes sense this year as well. : @Danny McCormick
>  @Talat Uyarer  @Chamikara
> Jayalath 
>
>
>
> Ahmet
>
>
>
> On Wed, Feb 12, 2025 at 10:26 AM Charles Nguyen 
> wrote:
>
> Hi all,
>
>
>
> I've been lurking around the project for a while and, if there haven't
> been any more ideas, I'd like to mention a few that I find interesting.
> These are just from past GSoC, and I'm happy to contribute to any one of
> these:
>
>- Complex Event Processing [1]: This was all the way back in 2022 and
>I guess it was related/partially done with match_recognize in BeamSQL [2]
>
>
>- ManagedIO [3]: This was a project idea from just last year. I don't
>think anyone did this, and ManagedIO seems new so there are always tons of
>other IO integrations we can add to.
>
> They're all seem large projects to me. Hopefully these are still relevant
> ideas for this year!
>
>
>
> [1] https://issues.apache.org/jira/browse/BEAM-3767
>
> [2] https://issues.apache.org/jira/browse/BEAM-9543
>
> [3]
> https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2024+Ideas+list#GSoC2024Ideaslist-[GSOC][Beam]AddconnectorstoBeamManagedIO
>
>
> --
>
> *From:* Ahmet Altay via dev 
> *Sent:* Wednesday, February 12, 2025 12:33 PM
> *To:* dev 
> *Cc:* Ahmet Altay 
> *Subject:* Fwd: [URGENT] Re: [Action Required] GSoC 2025 is coming
>
>
>
> Hi all,
>
>
>
> We need a few GSoC 2025 projects urgently. If you are willing to host a
> project, this is a great opportunity for us to make some important
> improvements to Beam and also have new engaged contributors. GSoC, in my
> own words, is open source internships, paid by Google, scoped for 90, 175,
> or 350 hours that happen over summer. If you have any questions, we will be
> happy to help.
>
>
>
> *Call to action:* As soon as possible, please add ideas here to jira,
> ideally today.
>
>
>
> From Danny: "We file jiras like
> https://issues.apache.org/jira/browse/GSOC-273 i

Re: [VOTE] Release 2.63.0, release candidate #2

2025-02-13 Thread Yi Hu via dev 
+1 (non-binding)

Tested Dataflow Templates Integration tests (Java 17, Dataflow runner v2) -
https://github.com/GoogleCloudPlatform/DataflowTemplates/pull/2177

On Thu, Feb 13, 2025 at 3:41 AM Rohit Sinha via dev 
wrote:

> +1 (non-binding). Tested Java SDK with batch, streaming pipelines both on
> legacy and runner_V2.
>
>
>
> On Thu, Feb 13, 2025 at 12:36 AM Jan Lukavský  wrote:
>
>> +1 (binding)
>>
>> Tested Java SDK with Flink Runner.
>>
>>  Jan
>> On 2/12/25 19:46, XQ Hu via dev wrote:
>>
>> +1 (non-binding). Tested the Python SDK with a simple Dataflow ML
>> pipeline:
>> https://github.com/google/dataflow-ml-starter/actions/runs/13291770412/job/37114110434
>>
>> On Wed, Feb 12, 2025 at 12:05 PM Jack McCluskey via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Hi everyone,
>>>
>>> Please review and vote on the release candidate #2 for the version
>>> 2.63.0, 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. Only PMC member votes will
>>> count towards the final vote, but votes from all community members are
>>> encouraged and helpful for finding regressions; you can either test your
>>> own use cases [13] or use cases from the validation sheet [10].
>>>
>>> The complete staging area is available for your review, which includes:
>>> * GitHub Release notes [1],
>>> * the official Apache source release to be deployed to dist.apache.org [2],
>>> which is signed with the key with fingerprint D20316F712213422 [3],
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> * source code tag "v2.63.0-RC2" [5],
>>> * website pull request listing the release [6], the blog post [6], and
>>> publishing the API reference manual [7].
>>> * Python artifacts are deployed along with the source release to
>>> dist.apache.org [2] and PyPI[8].
>>> * Go artifacts and documentation are available at pkg.go.dev [9]
>>> * Validation sheet with a tab for 2.63.0 release to help with validation
>>> [10].
>>> * Docker images published to Docker Hub [11].
>>> * PR to run tests against release branch [12].
>>> * Github Release pre-release page for v2.63.0-RC2 [13].
>>>
>>> The vote will be open for at least 72 hours. It is adopted by majority
>>> approval, with at least 3 PMC affirmative votes.
>>>
>>> For guidelines on how to try the release in your projects, check out our
>>> RC testing guide [13].
>>>
>>> Thanks,
>>>
>>> Jack McCluskey
>>>
>>> [1] https://github.com/apache/beam/milestone/27
>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.63.0/
>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> [4]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1400/
>>> [5] https://github.com/apache/beam/tree/v2.63.0-RC2
>>> [6] https://github.com/apache/beam/pull/33905
>>> [7] https://github.com/apache/beam-site/pull/677
>>> [8] https://pypi.org/project/apache-beam/2.63.0rc2/
>>> [9]
>>> https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.63.0-RC2/go/pkg/beam
>>> [10]
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1785697132
>>> [11] https://hub.docker.com/search?q=apache%2Fbeam&type=image
>>> [12] https://github.com/apache/beam/pull/33870
>>> [13] https://github.com/apache/beam/releases/tag/v2.63.0-RC2
>>> [14]
>>> https://github.com/apache/beam/blob/master/contributor-docs/rc-testing-guide.md
>>>
>>>
>>> --
>>>
>>>
>>> Jack McCluskey
>>> SWE - DataPLS PLAT/ Dataflow ML
>>> RDU
>>> jrmcclus...@google.com
>>>
>>>
>>>

Re: [URGENT] Re: [Action Required] GSoC 2025 is coming

2025-02-13 Thread SIDDHARTH SALIAN 
Hello,

  1.  I shall go through the page. Another thing wanted to ask, how about 
contributing in CEP(Complex event processing) in GSOC?
  2.  As mentioned before that it needs improvements. So what is the current 
situation?
  3.  Also after reading the pages if a good project is present, lets finalise 
it and start working.

Thanks,
Siddharth

From: Ahmet Altay via dev 
Date: Thursday, 13 February 2025 at 10:43 PM
To: dev@beam.apache.org 
Cc: Ahmet Altay 
Subject: Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
This is a publicly accessible page: 
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2025+Ideas+list#GSoC2025Ideaslist-Beam

On Thu, Feb 13, 2025 at 8:45 AM SIDDHARTH SALIAN 
mailto:siddharthsalia...@gmail.com>> wrote:
Hello,
Ok I shall go through it. I think I’m not sure of getting access to the project.

Best regards,
Siddharth

From: XQ Hu via dev mailto:dev@beam.apache.org>>
Date: Thursday, 13 February 2025 at 8:20 PM
To: dev@beam.apache.org 
mailto:dev@beam.apache.org>>
Cc: XQ Hu mailto:x...@google.com>>
Subject: Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
We have proposed several ideas here: 
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2025+Ideas+list#GSoC2025Ideaslist-Beam

Not sure you can access it.

On Thu, Feb 13, 2025 at 1:35 AM SIDDHARTH SALIAN 
mailto:siddharthsalia...@gmail.com>> wrote:
Hi,
Well they are interesting projects, if you could tell me language for example 
if these are java projects or c/c++?

Thanks,
Siddharth

From: Talat Uyarer via dev mailto:dev@beam.apache.org>>
Date: Thursday, 13 February 2025 at 12:01 PM
To: dev@beam.apache.org 
mailto:dev@beam.apache.org>>
Cc: Talat Uyarer mailto:tal...@google.com>>
Subject: Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
Hi All,

I have few ideas for projects that we can put forward for Google Summer of 
Code. Here are some thoughts:

*   English SDK for Apache Beam.
*   Apache Polaris Catalog Support
*   Support Call Stored Procedure for Beam SQL
*   ML Support on Beam SQL

I will create tickets for these, if the community is also ok for those projects.

They are interesting. Go for it, if you are willing to mentor at least one :)


Talat

On Wed, Feb 12, 2025 at 10:20 PM SIDDHARTH SALIAN 
mailto:siddharthsalia...@gmail.com>> wrote:
Hello people,

  1.  Any updates on GSOC projects? Any project finalised? Also we need to 
decide and form team too.
  2.  Does anyone have a project in their mind?
  3.  Also not much of a time is left.

Thanks,
Siddharth

From: Yi Hu via dev mailto:dev@beam.apache.org>>
Date: Thursday, 13 February 2025 at 1:01 AM
To: dev@beam.apache.org 
mailto:dev@beam.apache.org>>
Cc: Yi Hu mailto:ya...@google.com>>
Subject: Re: [URGENT] Re: [Action Required] GSoC 2025 is coming
Hi there,

For those who are looking for project ideas, Beam has migrated from Jira to 
GitHub Issue for tracking issues, and the former was read only.

e.g. BEAM-3767 has been moved to https://github.com/apache/beam/issues/18730

There is a "gsoc" label marks potential projects: 
https://github.com/apache/beam/issues?q=state%3Aopen%20label%3A%22gsoc%22

However I see some Issues are stale. Going to clean up and add some new Issues 
into this label.

Regards,

Yi


On Wed, Feb 12, 2025 at 1:30 PM Ahmet Altay via dev 
mailto:dev@beam.apache.org>> wrote:
Hi Charles,

Thank you for your interest!

I think CEP is still an open project. We have made some progress on managed IO 
but there is still more to be done there.

Adding folks, who can help you with these questions and see if these projects 
still makes sense this year as well. : @Danny 
McCormick @Talat 
Uyarer @Chamikara 
Jayalath

Ahmet

On Wed, Feb 12, 2025 at 10:26 AM Charles Nguyen 
mailto:phucnh...@gmail.com>> wrote:
Hi all,

I've been lurking around the project for a while and, if there haven't been any 
more ideas, I'd like to mention a few that I find interesting. These are just 
from past GSoC, and I'm happy to contribute to any one of these:

  *   Complex Event Processing [1]: This was all the way back in 2022 and I 
guess it was related/partially done with match_recognize in BeamSQL [2]

  *   ManagedIO [3]: This was a project idea from just last year. I don't think 
anyone did this, and ManagedIO seems new so there are always tons of other IO 
integrations we can add to.
They're all seem large projects to me. Hopefully these are still relevant ideas 
for this year!

[1] https://issues.apache.org/jira/browse/BEAM-3767
[2] https://issues.apache.org/jira/browse/BEAM-9543
[3] 
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2024+Ideas+list#GSoC2024Ideaslist-[GSOC][Beam]AddconnectorstoBeamManagedIO


From: Ahmet Altay via dev mailto:dev@beam.apache.org>>
Sent: Wednesday, February 12, 2025 12:33 PM
To: dev mailto:dev@beam.a