Re: [DISCUSS] Release Apache Pulsar 2.11.3

+1 Thanks, Zixuan Baodi Shi 于2023年10月16日周一 21:13写道： > > Hi all > > I would like to propose releasing the Pulsar 2.11.3 > > It's over one month since the release of 2.11.3, and there are 87 new > commits. > > in branch-2.11: > https://github.com/apache/pulsar/compare/v2.11.2...branch-2.11 > > We

Re: [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket

+1 Thanks, Zixuan guo jiwei 于2023年10月18日周三 20:45写道： > > Hi dev, >Currently WebSocket only supports the consumption of a single topic, > which cannot satisfy users' consumption scenarios of multiple topics. So > in order to support consumption of multiple topics or pattern topics, I > start

Re: [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket

+1 Best, Mattison > On 19 Oct 2023, at 11:38, Yubiao Feng > wrote: > > Hi @Jiwei > > +1 > It is a good feature, I think it will help users. > > Thanks > Yubiao Feng > > > On Wed, Oct 18, 2023 at 8:45 PM guo jiwei wrote: > >> Hi dev, >> Currently WebSocket only supports the consumption

Re: [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket

Hi @Jiwei +1 It is a good feature, I think it will help users. Thanks Yubiao Feng On Wed, Oct 18, 2023 at 8:45 PM guo jiwei wrote: > Hi dev, >Currently WebSocket only supports the consumption of a single topic, > which cannot satisfy users' consumption scenarios of multiple topics. So >

Re: [DISCUSS] Release Apache Pulsar 2.11.3

+1 Thanks Yubiao Feng On Mon, Oct 16, 2023 at 9:13 PM Baodi Shi wrote: > Hi all > > I would like to propose releasing the Pulsar 2.11.3 > > It's over one month since the release of 2.11.3, and there are 87 new > commits. > > in branch-2.11: > https://github.com/apache/pulsar/compare/v2.11.2...b

Re: [DISCUSS] Release Apache Pulsar 2.11.3

+1 Thanks for your contribution. Best, Mattison > On 19 Oct 2023, at 11:23, PengHui Li wrote: > > +1 > > Thanks, > Penghui > > On Mon, Oct 16, 2023 at 9:13 PM Baodi Shi wrote: > >> Hi all >> >> I would like to propose releasing the Pulsar 2.11.3 >> >> It's over one month since the releas

Re: [DISCUSS] Release Apache Pulsar 2.11.3

+1 Thanks, Penghui On Mon, Oct 16, 2023 at 9:13 PM Baodi Shi wrote: > Hi all > > I would like to propose releasing the Pulsar 2.11.3 > > It's over one month since the release of 2.11.3, and there are 87 new > commits. > > in branch-2.11: > https://github.com/apache/pulsar/compare/v2.11.2...bran

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

> I think Java 21 can open the door for Virtual Threads[1]. Yep. This should be a good motivation for using JDK 21. We may start a survey in the community a few months later for JDK 21 feedback (as we /will/ switch the runtime to JDK 21 in Docker) and try to switch the toolkit. Best, tison. Zi

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

+1 for compatibility with Java 21. Next step: Migrating the Pulsar Server runtime to Java 21 from Java 17 in the Docker image and CI. Pulsar Client/Admin continues to use Java 8. Thanks, Zixuan Lari Hotari 于2023年10月18日周三 06:02写道： > > Dear Pulsar community, > > Java 21 was released on September

Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client

+1 (binding) Regards, Penghui On Thu, Oct 19, 2023 at 10:45 AM guo jiwei wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Thu, Oct 19, 2023 at 10:11 AM Zili Chen wrote: > > > +1 binding > > > > On 2023/10/17 07:23:29 Diego Salvi wrote: > > > Hi Community, > > > > > > This thread

Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client

+1 (binding) Regards Jiwei Guo (Tboy) On Thu, Oct 19, 2023 at 10:11 AM Zili Chen wrote: > +1 binding > > On 2023/10/17 07:23:29 Diego Salvi wrote: > > Hi Community, > > > > This thread is to start a vote for PIP-305. > > > > PIP: https://github.com/apache/pulsar/pull/21352 > > Discussion thre

Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client

+1(non-binding) Zili Chen 于2023年10月19日周四 10:10写道： > > +1 binding > > On 2023/10/17 07:23:29 Diego Salvi wrote: > > Hi Community, > > > > This thread is to start a vote for PIP-305. > > > > PIP: https://github.com/apache/pulsar/pull/21352 > > Discussion thread: > > https://lists.apache.org/thread/

Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client

+1 binding On 2023/10/17 07:23:29 Diego Salvi wrote: > Hi Community, > > This thread is to start a vote for PIP-305. > > PIP: https://github.com/apache/pulsar/pull/21352 > Discussion thread: > https://lists.apache.org/thread/p0870y7o6brv5y1ghn5tz9hvs24bl1k4 > > Best regards > Diego Salvi >

[VOTE] PIP-298 Consumer supports specifying consumption isolation level

Hi dev, This thread is to start a vote for PIP-298 Consumer supports specifying consumption isolation level. Discuss thread: https://lists.apache.org/thread/8ny0qtp7m9qcdbvnfjdvpnkc4c5ssyld PIP: https://github.com/apache/pulsar/pull/21114 Doc: https://github.com/apache/pulsar-site/pull/712 BR,

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

Hi, +1 for Java 21. I think Java 21 can open the door for Virtual Threads[1]. [1] https://openjdk.org/jeps/444 Thanks, Heesung On Wed, Oct 18, 2023 at 10:33 AM Lari Hotari wrote: > Yes, I agree that we don't need to rush in making Java 21 the default > runtime in docker images and the default

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

Yes, I agree that we don't need to rush in making Java 21 the default runtime in docker images and the default JVM to run tests on in CI. It seems that supporting Java 21 for build and tests in CI is not too far away. My intention is to make the master code base compatible with Java 21 as the f

[DISCUSS] PIP-308: Support share Retry and DLQ topic producers for MultiTopicConsumer instance

Hi dev,When subscribe to multi-partitioned topic and set user-defined partitioned retry and dlq topic in deadLetterPolicy,the producer instances are multipled by partitions, In order to reduce the resource usage at both client and server side, I start discussing PIP-308

Re: Pulsar CI partially blocked because "Broker Group 1" CI job times out frequently, adding new run group

I merged the PR to master since it solves the problem. The execution time of "Broker Group 4" was over 27 minutes in the PR run: https://github.com/apache/pulsar/actions/runs/6561088390/job/17824768614?pr=21391 "Broker Group 1" execution time was about 33 minutes: https://github.com/apache/pulsar

Upgrading Mockito to 5.6.0 in master branch for Java 21 compatibility

Hi all, There's PR https://github.com/apache/pulsar/pull/21385 ready to be merged to master branch. It upgrades Mockito to 5.6.0 version. Mockito API hasn't significantly changed. A few changes were made in master branch to fix the Mockito usage. The newer version is stricter than the previousl

Pulsar CI partially blocked because "Broker Group 1" CI job times out frequently, adding new run group

Hi, I've created a PR for introducing a new unit test CI job, "Broker Group 4". This is in response to the frequent timeouts of the "Broker Group 1" build, which often exceeds 60 minutes. You can find the PR at https://github.com/apache/pulsar/pull/21391. The comments within the PR provide fur

[DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket

Hi dev, Currently WebSocket only supports the consumption of a single topic, which cannot satisfy users' consumption scenarios of multiple topics. So in order to support consumption of multiple topics or pattern topics, I start discussing PIP-307 .

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

It's different to 1. be compatible with JDK 21 2. switch the runtime to JDK 21 The latter means we can break compatibility with early JRE. I totally support to be compatible with JDK 21 and saw your PRs to upgrade mockito version for so. But perhaps it's better to wait a bit for users feedback o

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

I support the idea of moving to JDK21, as far as we continue to support JDK8 for the clients Thanks for bringing up this topic Enrico Il giorno mer 18 ott 2023 alle ore 13:37 mattison chao ha scritto: > > Thanks for your answer. > > > > We have the PIP, but that doesn't answer the question abo

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

Thanks for your answer. > We have the PIP, but that doesn't answer the question about the current > schedule and plan for Pulsar 3.2 . There have been delays in past release > schedules so the PIP document doesn't really provide a great answer to > timeline. When is it time to start discussing

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

Hi, > 1. What are the significant benefits of upgrading? There are 2 parts to how Java 21 could be supported. One level is that we simply add support for developing and running Pulsar on Java 21 runtime without switching the language level of the Pulsar components. This is how Java 11 was us

Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView

Close this vote with 3 +1(binding) - Penghui - Jiwei Guo (Tboy) - Mattison On Sun, Oct 8, 2023 at 5:02 PM mattison chao wrote: > > +1(binding) > > Best, > Mattison > On 8 Oct 2023 at 14:49 +0800, Yunze Xu , wrote: > > Totally I'm +0 at the moment. I'm still wondering which issue you > > really wa