Re: [VOTE] PIP-326: Create a BOM to ease dependency management

[houxiaoyu]

+1 non-binding

Best,
houxiaoyu

tison  于2023年12月23日周六 10:10写道：

> +1 binding
>
> Best,
> tison.
>
> 太上玄元道君  于2023年12月23日周六 09:06写道：
> >
> > +1 nonbinding
> >
> > Umut Bilal Okur 于2023年12月23日 周六00:13写道：
> >
> > > +1 (non-binding)
> > >
> > > Enrico Olivelli , 22 Ara 2023 Cum, 18:26
> tarihinde
> > > şunu yazdı:
> > >
> > > > +1 (binding)
> > > >
> > > > Enrico
> > > >
> > > > Il giorno ven 22 dic 2023 alle ore 02:46 Apurva Telang
> > > >  ha scritto:
> > > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > On Thu, Dec 21, 2023 at 4:30 PM Matteo Merli 
> > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Matteo Merli
> > > > > > 
> > > > > >
> > > > > >
> > > > > > On Thu, Dec 21, 2023 at 4:24 PM Nicolò Boschi <
> boschi1...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > +1 binding
> > > > > > >
> > > > > > > Nicolò Boschi
> > > > > > >
> > > > > > >
> > > > > > > Il giorno gio 21 dic 2023 alle 21:21 Lari Hotari <
> > > lhot...@apache.org>
> > > > ha
> > > > > > > scritto:
> > > > > > >
> > > > > > > > +1 (binding)
> > > > > > > >
> > > > > > > > -Lari
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, 21 Dec 2023 at 22:10, Chris Bono 
> > > wrote:
> > > > > > > > >
> > > > > > > > > I'm starting the vote for PIP-326, since it has been
> reviewed
> > > by
> > > > > > > > > several members with no objections.
> > > > > > > > >
> > > > > > > > > PIP link: https://github.com/apache/pulsar/pull/21747
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > >
> > > > > > > > > Chris
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
> > > > > Apurva Telang.
> > > >
> > >
>

Re: [DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it

[Matteo Merli]

Good point. I have created a PR here:
https://github.com/apache/pulsar/pull/21795

We can always cherry-pick changes into the release branch, during the code
freeze, with the appropriate precautions :)

Matteo


--
Matteo Merli



On Fri, Dec 22, 2023 at 9:41 AM Lari Hotari  wrote:

> Do we target release 3.2.0 if this change gets accepted?
>
> The code freeze for 3.2.0 was about to start today and I blocked that. I
> removed the already started branch-3.2 (which didn't contain any changes)
> until the decision has been made. I hope this makes sense. If not, we can
> always cut the branch again, nothing has been lost.
>
> re: https://lists.apache.org/thread/0pl9by5c53nkjp7vld3x89c8nqjrx9on
>
> -Lari
>
> On 2023/12/22 17:09:19 Matteo Merli wrote:
> > I want to start a discussion regarding the removal of all the code
> related
> > to the Trino (PrestoDB) plugin from the Pulsar main repository.
> >
> > This topic was already discussed and approved long time ago in PIP-62 (
> >
> https://github.com/apache/pulsar/wiki/PIP-62%3A-Move-connectors%2C-adapters-and-Pulsar-Presto-to-separate-repositories
> > )
> >
> > The main reasons for not having Presto plugin as part of the main
> > distribution of Pulsar were (and still are valid):
> >
> >  1. We need to ship the entire Presto runtime which is ~400 MB. This
> makes
> > our tgz and Docker images huge
> >  3. There is no strict need for this component to be in the same
> > distribution / image: it could easily be provided in a different release
> > tgz or Docker image
> >
> > Though I think that since then it became more clear that the current
> state
> > of this plugin has been stagnating over the years.
> >
> > 1. There are not many active users of Pulsar-SQL component (I'd be very
> > happy to be contradicted here)
> > 2. The plugin code has not been improved in a long time
> > 3. There are several open security issues (actually, almost the totality
> of
> > current dependencies issues are today coming from Trino).
> >
> > My suggestion would be that, if there is any volunteer willing to pick
> this
> > plugin up and maintain it in a separate repository (within the Apache
> > Pulsar project) and with a separate release schedule, we should go ahead
> > and move it.
> > If there are no volunteers, we should just remove it as it is. If later
> on
> > we want to revive it, we can always import the code from the last commit.
> >
> > Thoughts?
> >
> >
> > --
> > Matteo Merli
> > 
> >
>

Re: [VOTE] PIP-326: Create a BOM to ease dependency management

[tison]

+1 binding

Best,
tison.

太上玄元道君  于2023年12月23日周六 09:06写道：
>
> +1 nonbinding
>
> Umut Bilal Okur 于2023年12月23日 周六00:13写道：
>
> > +1 (non-binding)
> >
> > Enrico Olivelli , 22 Ara 2023 Cum, 18:26 tarihinde
> > şunu yazdı:
> >
> > > +1 (binding)
> > >
> > > Enrico
> > >
> > > Il giorno ven 22 dic 2023 alle ore 02:46 Apurva Telang
> > >  ha scritto:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > On Thu, Dec 21, 2023 at 4:30 PM Matteo Merli 
> > wrote:
> > > >
> > > > > +1
> > > > >
> > > > >
> > > > > --
> > > > > Matteo Merli
> > > > > 
> > > > >
> > > > >
> > > > > On Thu, Dec 21, 2023 at 4:24 PM Nicolò Boschi 
> > > > > wrote:
> > > > >
> > > > > > +1 binding
> > > > > >
> > > > > > Nicolò Boschi
> > > > > >
> > > > > >
> > > > > > Il giorno gio 21 dic 2023 alle 21:21 Lari Hotari <
> > lhot...@apache.org>
> > > ha
> > > > > > scritto:
> > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > -Lari
> > > > > > >
> > > > > > >
> > > > > > > On Thu, 21 Dec 2023 at 22:10, Chris Bono 
> > wrote:
> > > > > > > >
> > > > > > > > I'm starting the vote for PIP-326, since it has been reviewed
> > by
> > > > > > > > several members with no objections.
> > > > > > > >
> > > > > > > > PIP link: https://github.com/apache/pulsar/pull/21747
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > >
> > > > > > > > Chris
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Apurva Telang.
> > >
> >

Re: [VOTE] PIP-326: Create a BOM to ease dependency management

[太上玄元道君]

+1 nonbinding

Umut Bilal Okur 于2023年12月23日 周六00:13写道：

> +1 (non-binding)
>
> Enrico Olivelli , 22 Ara 2023 Cum, 18:26 tarihinde
> şunu yazdı:
>
> > +1 (binding)
> >
> > Enrico
> >
> > Il giorno ven 22 dic 2023 alle ore 02:46 Apurva Telang
> >  ha scritto:
> > >
> > > +1 (non-binding)
> > >
> > > On Thu, Dec 21, 2023 at 4:30 PM Matteo Merli 
> wrote:
> > >
> > > > +1
> > > >
> > > >
> > > > --
> > > > Matteo Merli
> > > > 
> > > >
> > > >
> > > > On Thu, Dec 21, 2023 at 4:24 PM Nicolò Boschi 
> > > > wrote:
> > > >
> > > > > +1 binding
> > > > >
> > > > > Nicolò Boschi
> > > > >
> > > > >
> > > > > Il giorno gio 21 dic 2023 alle 21:21 Lari Hotari <
> lhot...@apache.org>
> > ha
> > > > > scritto:
> > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > -Lari
> > > > > >
> > > > > >
> > > > > > On Thu, 21 Dec 2023 at 22:10, Chris Bono 
> wrote:
> > > > > > >
> > > > > > > I'm starting the vote for PIP-326, since it has been reviewed
> by
> > > > > > > several members with no objections.
> > > > > > >
> > > > > > > PIP link: https://github.com/apache/pulsar/pull/21747
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Chris
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Apurva Telang.
> >
>

Re: [DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it

[Lari Hotari]

Do we target release 3.2.0 if this change gets accepted?

The code freeze for 3.2.0 was about to start today and I blocked that. I 
removed the already started branch-3.2 (which didn't contain any changes)
until the decision has been made. I hope this makes sense. If not, we can 
always cut the branch again, nothing has been lost.

re: https://lists.apache.org/thread/0pl9by5c53nkjp7vld3x89c8nqjrx9on

-Lari

On 2023/12/22 17:09:19 Matteo Merli wrote:
> I want to start a discussion regarding the removal of all the code related
> to the Trino (PrestoDB) plugin from the Pulsar main repository.
> 
> This topic was already discussed and approved long time ago in PIP-62 (
> https://github.com/apache/pulsar/wiki/PIP-62%3A-Move-connectors%2C-adapters-and-Pulsar-Presto-to-separate-repositories
> )
> 
> The main reasons for not having Presto plugin as part of the main
> distribution of Pulsar were (and still are valid):
> 
>  1. We need to ship the entire Presto runtime which is ~400 MB. This makes
> our tgz and Docker images huge
>  3. There is no strict need for this component to be in the same
> distribution / image: it could easily be provided in a different release
> tgz or Docker image
> 
> Though I think that since then it became more clear that the current state
> of this plugin has been stagnating over the years.
> 
> 1. There are not many active users of Pulsar-SQL component (I'd be very
> happy to be contradicted here)
> 2. The plugin code has not been improved in a long time
> 3. There are several open security issues (actually, almost the totality of
> current dependencies issues are today coming from Trino).
> 
> My suggestion would be that, if there is any volunteer willing to pick this
> plugin up and maintain it in a separate repository (within the Apache
> Pulsar project) and with a separate release schedule, we should go ahead
> and move it.
> If there are no volunteers, we should just remove it as it is. If later on
> we want to revive it, we can always import the code from the last commit.
> 
> Thoughts?
> 
> 
> --
> Matteo Merli
> 
> 

Re: [DISCUSS] Apache Pulsar 3.2.0 release

[Lari Hotari]

There was a discussion yesterday in the community meeting to make the proposed 
change
to drop Pulsar SQL (Trino/Presto), already in the 3.2.0 release.

Matteo started the discussion thread: 
https://lists.apache.org/thread/4f1cco12cycq36m7vtyjs2j5q5975666

I deleted branch-3.2 for now so that we don't spend unnecessary time 
backporting these changes from master to branch-3.2. Let's cut branch-3.2 when 
we have voted about the Pulsar SQL removal and made the changes in master 
branch. I hope this makes sense.

-Lari

On 2023/12/22 03:14:01 guo jiwei wrote:
> Hi community
>   I have cut branch 3.2 and will freeze the code for the next two weeks.
> 
> Regards
> Jiwei Guo (Tboy)
> 
> 
> On Thu, Dec 14, 2023 at 11:40 AM guo jiwei  wrote:
> 
> > Hi community,
> >It has been more than three months since the release of 3.1.0.  we now
> > have more than 305 commits
> > 
> >  and
> > 26 PIPs
> > 
> > merged.  We'd better prepare for the 3.2.0 release. I would like to cut
> > branch-3.2 in the next week and freeze the code for two weeks.
> >Please leave any ideas or concerns.
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> 

Re: [DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it

[Lari Hotari]

Good plan!

-Lari

On Fri, 22 Dec 2023 at 19:09, Matteo Merli  wrote:
>
> I want to start a discussion regarding the removal of all the code related
> to the Trino (PrestoDB) plugin from the Pulsar main repository.
>
> This topic was already discussed and approved long time ago in PIP-62 (
> https://github.com/apache/pulsar/wiki/PIP-62%3A-Move-connectors%2C-adapters-and-Pulsar-Presto-to-separate-repositories
> )
>
> The main reasons for not having Presto plugin as part of the main
> distribution of Pulsar were (and still are valid):
>
>  1. We need to ship the entire Presto runtime which is ~400 MB. This makes
> our tgz and Docker images huge
>  3. There is no strict need for this component to be in the same
> distribution / image: it could easily be provided in a different release
> tgz or Docker image
>
> Though I think that since then it became more clear that the current state
> of this plugin has been stagnating over the years.
>
> 1. There are not many active users of Pulsar-SQL component (I'd be very
> happy to be contradicted here)
> 2. The plugin code has not been improved in a long time
> 3. There are several open security issues (actually, almost the totality of
> current dependencies issues are today coming from Trino).
>
> My suggestion would be that, if there is any volunteer willing to pick this
> plugin up and maintain it in a separate repository (within the Apache
> Pulsar project) and with a separate release schedule, we should go ahead
> and move it.
> If there are no volunteers, we should just remove it as it is. If later on
> we want to revive it, we can always import the code from the last commit.
>
> Thoughts?
>
>
> --
> Matteo Merli
> 

[DISCUSS] Removing Pulsar-Trino plugin from main repo and call for volunteers to maintain it

[Matteo Merli]

I want to start a discussion regarding the removal of all the code related
to the Trino (PrestoDB) plugin from the Pulsar main repository.

This topic was already discussed and approved long time ago in PIP-62 (
https://github.com/apache/pulsar/wiki/PIP-62%3A-Move-connectors%2C-adapters-and-Pulsar-Presto-to-separate-repositories
)

The main reasons for not having Presto plugin as part of the main
distribution of Pulsar were (and still are valid):

 1. We need to ship the entire Presto runtime which is ~400 MB. This makes
our tgz and Docker images huge
 3. There is no strict need for this component to be in the same
distribution / image: it could easily be provided in a different release
tgz or Docker image

Though I think that since then it became more clear that the current state
of this plugin has been stagnating over the years.

1. There are not many active users of Pulsar-SQL component (I'd be very
happy to be contradicted here)
2. The plugin code has not been improved in a long time
3. There are several open security issues (actually, almost the totality of
current dependencies issues are today coming from Trino).

My suggestion would be that, if there is any volunteer willing to pick this
plugin up and maintain it in a separate repository (within the Apache
Pulsar project) and with a separate release schedule, we should go ahead
and move it.
If there are no volunteers, we should just remove it as it is. If later on
we want to revive it, we can always import the code from the last commit.

Thoughts?


--
Matteo Merli

Re: [VOTE] PIP-326: Create a BOM to ease dependency management

[Umut Bilal Okur]

+1 (non-binding)

Enrico Olivelli , 22 Ara 2023 Cum, 18:26 tarihinde
şunu yazdı:

> +1 (binding)
>
> Enrico
>
> Il giorno ven 22 dic 2023 alle ore 02:46 Apurva Telang
>  ha scritto:
> >
> > +1 (non-binding)
> >
> > On Thu, Dec 21, 2023 at 4:30 PM Matteo Merli  wrote:
> >
> > > +1
> > >
> > >
> > > --
> > > Matteo Merli
> > > 
> > >
> > >
> > > On Thu, Dec 21, 2023 at 4:24 PM Nicolò Boschi 
> > > wrote:
> > >
> > > > +1 binding
> > > >
> > > > Nicolò Boschi
> > > >
> > > >
> > > > Il giorno gio 21 dic 2023 alle 21:21 Lari Hotari 
> ha
> > > > scritto:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > -Lari
> > > > >
> > > > >
> > > > > On Thu, 21 Dec 2023 at 22:10, Chris Bono  wrote:
> > > > > >
> > > > > > I'm starting the vote for PIP-326, since it has been reviewed by
> > > > > > several members with no objections.
> > > > > >
> > > > > > PIP link: https://github.com/apache/pulsar/pull/21747
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Chris
> > > > >
> > > >
> > >
> >
> >
> > --
> > Best regards,
> > Apurva Telang.
>

Meet our keynote speakers and register to Community Over Code EU!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one or
more project dev@ mailing lists at the Apache Software Foundation.]











*
Merge
with the ASF EUniverse!The registration for Community Over Code Europe is
finally open! Get your tickets now and save your spot!
We are happy to announce that we
have confirmed the first featured speakers
!  - Asim Hussain, Executive
Director at Green Software Foundation- Dirk-Willem Van Gulik, VP of Public
Policy at The Apache Software Foundation- Ruth Ikega, Community Lead at
CHAOSS Africa Visit our website
 to learn more about this
amazing lineup.CFP is openWe are looking forward to hearing all you have to
share with the Apache Community. Please submit your talk proposal
 before January 12, 2024.Interested in
boosting your brand?Take a look at our prospectus

and find out the opportunities we have for you. Be one step ahead and book
your room at the hotel venueWe have a special rate for you at the Radisson
Blu Carlton, the hotel that will hold Community Over Code EU. Learn more
about the location and venue 
and book your accommodation. Should you have any questions, please do not
hesitate to contact us. We wish you Happy Holidays in the company of your
loved ones! See you in Bratislava next year!Community Over Code EU
Organizer Committee*

Re: [VOTE] PIP-326: Create a BOM to ease dependency management

[Enrico Olivelli]

+1 (binding)

Enrico

Il giorno ven 22 dic 2023 alle ore 02:46 Apurva Telang
 ha scritto:
>
> +1 (non-binding)
>
> On Thu, Dec 21, 2023 at 4:30 PM Matteo Merli  wrote:
>
> > +1
> >
> >
> > --
> > Matteo Merli
> > 
> >
> >
> > On Thu, Dec 21, 2023 at 4:24 PM Nicolò Boschi 
> > wrote:
> >
> > > +1 binding
> > >
> > > Nicolò Boschi
> > >
> > >
> > > Il giorno gio 21 dic 2023 alle 21:21 Lari Hotari  ha
> > > scritto:
> > >
> > > > +1 (binding)
> > > >
> > > > -Lari
> > > >
> > > >
> > > > On Thu, 21 Dec 2023 at 22:10, Chris Bono  wrote:
> > > > >
> > > > > I'm starting the vote for PIP-326, since it has been reviewed by
> > > > > several members with no objections.
> > > > >
> > > > > PIP link: https://github.com/apache/pulsar/pull/21747
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Chris
> > > >
> > >
> >
>
>
> --
> Best regards,
> Apurva Telang.