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

[PengHui Li]

+1 (binding)

It's a straightforward change for WebSocket Proxy to catch up on features.

Thanks,
Penghui

On Fri, Oct 20, 2023 at 12:55 PM Yunze Xu  wrote:

> +1 (binding)
>
> Thanks,
> Yunze
>
> On Fri, Oct 20, 2023 at 10:59 AM mattison chao 
> wrote:
> >
> > +1(binding)
> >
> > Best,
> > Mattison
> >
> > > On 19 Oct 2023, at 20:47, 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
> > > in order to support consumption of multiple topics or pattern topics, I
> > > would like to start a vote for PIP-307
> > > .
> > >
> > >
> > > Ref:
> > > • Discuss Mail:
> > > https://lists.apache.org/thread/co8396ywny161x91dffzvxlt993mo1ht
> > > • PIP-307: https://github.com/apache/pulsar/pull/21390
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> >
>

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

[Yunze Xu]

+1 (binding)

Thanks,
Yunze

On Fri, Oct 20, 2023 at 10:59 AM mattison chao  wrote:
>
> +1(binding)
>
> Best,
> Mattison
>
> > On 19 Oct 2023, at 20:47, 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
> > in order to support consumption of multiple topics or pattern topics, I
> > would like to start a vote for PIP-307
> > .
> >
> >
> > Ref:
> > • Discuss Mail:
> > https://lists.apache.org/thread/co8396ywny161x91dffzvxlt993mo1ht
> > • PIP-307: https://github.com/apache/pulsar/pull/21390
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
>

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

[mattison chao]

+1(binding)

Best,
Mattison

> On 19 Oct 2023, at 20:47, 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
> in order to support consumption of multiple topics or pattern topics, I
> would like to start a vote for PIP-307
> .
> 
> 
> Ref:
> • Discuss Mail:
> https://lists.apache.org/thread/co8396ywny161x91dffzvxlt993mo1ht
> • PIP-307: https://github.com/apache/pulsar/pull/21390
> 
> 
> Regards
> Jiwei Guo (Tboy)

[VOTE] PIP-304: Make PublishContext provide the message metadata

[kecona]

Hi all,

This thread is to start a vote for PIP-304.

PIP: https://github.com/apache/pulsar/pull/21311
Discussion thread:
https://lists.apache.org/thread/72szlzc0rw1hbn4v0w54qgq93cn9k4px

Thanks,
kecona

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

[hzh0425]

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

[DISCUSS] PIP-309: Adding Pulsar Client Stats Reporter

[Ying]

Hi dev,

Currently, Pulsar Client can provide recorded stats for both Producer and
Consumer, but not all stats are fixed values during the statsInterval. So
start the PIP-309 to add the Pulsar Client Stats Reporter to allow all
stats being reported precisely at the end of each interval.

Please share your thoughts!

Ref:
PIP-309 https://github.com/apache/pulsar/pull/21393

Thanks,
ywango

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

[Lari Hotari]

Hi all,

I can now confirm that apache/pulsar master branch compiles and runs all tests 
in Pulsar CI successfully with Java 21. Therefore, we have already accomplished 
the first level of Java 21 support.

Example of Pulsar CI build with Java 21: 
https://github.com/lhotari/pulsar/actions/runs/6577911040

This experiment was run with PR #21400 changes which adds an option in manually 
triggered GitHub Actions based Pulsar CI builds with Java 21 selected as the 
runtime for the build and test runtime and also as the Java runtime for docker 
images/containers used in integration & system tests which are part of the 
Pulsar CI build. 

Please review the PR https://github.com/apache/pulsar/pull/21400, let's get it 
merged. 
By default, Java 17 will be used, so it should be ok to merge this to master 
branch without any separate decisions such as PIPs.

-Lari

On 2023/10/19 12:23:03 Lari Hotari wrote:
> I have created https://github.com/apache/pulsar/pull/21400 which 
> parameterizes the JDK version used for the Pulsar CI GitHub Actions workflow. 
> When triggering the workflow
> manually, it's possible to choose between JDK 17 and JDK 21 from a dropdown 
> menu.
> The PR contains more details, please review. Once we have this merged, it 
> will be easy to experiment with Java 21 when needed.
> 
> -Lari
> 
> On 2023/10/19 03:06:39 tison wrote:
> > > 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.
> > 
> > 
> > Zixuan Liu  于2023年10月19日周四 10:56写道：
> > 
> > > +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 19th and has now become the current
> > > Java LTS release.
> > > >
> > > > I've begun preparations in the Pulsar code base to allow for Java 21 to
> > > be used as the development runtime for compiling the code and running 
> > > tests
> > > in the master branch. This is a proactive measure to gear up for Java 21
> > > without committing to the switch just yet. It will help us understand the
> > > necessary changes when we are able to compile the code and run all tests
> > > with Java 21.
> > > >
> > > > For instance, I initiated the process with the following PRs:
> > > > - Upgrade Mockito to 5.6.0 to support Java 21 [1]
> > > > - Upgrade Gradle Enterprise Maven Extension to support Java 21 [2]
> > > > After these are merged, it should be possible to start running tests
> > > with Java 21 to see what is possibly broken and continue iterating.
> > > > Moreover, the upgrade to Lombok 1.18.30 for Java 21 support has already
> > > been merged [3].
> > > >
> > > > Java 17 has been the recommended runtime for Pulsar server components
> > > since the Pulsar 2.11 release [4]. Meanwhile, the Pulsar client continues
> > > to be supported on Java 8+.
> > > >
> > > > I would like to initiate discussions about making Java 21 the
> > > recommended and default runtime for Pulsar server components. Note that
> > > there will be no change to the Pulsar client, which will remain on Java 
> > > 8+.
> > > >
> > > > I guess we could come up with a PIP to document the decision once we
> > > have had this discussion.
> > > >
> > > > Do you think we can target the switch from Java 17 to Java 21 for the
> > > Pulsar 3.2 release?
> > > > Could anyone update me on the current schedule for Pulsar 3.2?
> > > >
> > > > -Lari
> > > >
> > > > [1] - https://github.com/apache/pulsar/pull/21385
> > > > [2] - https://github.com/apache/pulsar/pull/21384
> > > > [3] - https://github.com/apache/pulsar/pull/21278
> > > > [4] -
> > > https://github.com/apache/pulsar#pulsar-runtime-java-version-recommendation
> > >
> > 
> 

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

[Christophe Bornet]

+1.
It's important to support the latest JDK LTS.

Le mer. 18 oct. 2023 à 00:02, Lari Hotari  a écrit :
>
> Dear Pulsar community,
>
> Java 21 was released on September 19th and has now become the current Java 
> LTS release.
>
> I've begun preparations in the Pulsar code base to allow for Java 21 to be 
> used as the development runtime for compiling the code and running tests in 
> the master branch. This is a proactive measure to gear up for Java 21 without 
> committing to the switch just yet. It will help us understand the necessary 
> changes when we are able to compile the code and run all tests with Java 21.
>
> For instance, I initiated the process with the following PRs:
> - Upgrade Mockito to 5.6.0 to support Java 21 [1]
> - Upgrade Gradle Enterprise Maven Extension to support Java 21 [2]
> After these are merged, it should be possible to start running tests with 
> Java 21 to see what is possibly broken and continue iterating.
> Moreover, the upgrade to Lombok 1.18.30 for Java 21 support has already been 
> merged [3].
>
> Java 17 has been the recommended runtime for Pulsar server components since 
> the Pulsar 2.11 release [4]. Meanwhile, the Pulsar client continues to be 
> supported on Java 8+.
>
> I would like to initiate discussions about making Java 21 the recommended and 
> default runtime for Pulsar server components. Note that there will be no 
> change to the Pulsar client, which will remain on Java 8+.
>
> I guess we could come up with a PIP to document the decision once we have had 
> this discussion.
>
> Do you think we can target the switch from Java 17 to Java 21 for the Pulsar 
> 3.2 release?
> Could anyone update me on the current schedule for Pulsar 3.2?
>
> -Lari
>
> [1] - https://github.com/apache/pulsar/pull/21385
> [2] - https://github.com/apache/pulsar/pull/21384
> [3] - https://github.com/apache/pulsar/pull/21278
> [4] - 
> https://github.com/apache/pulsar#pulsar-runtime-java-version-recommendation

[DISCUSS] PIP-310: Support custom publish rate limiters

[Girish Sharma]

Hi,
Currently, there are only 2 kinds of publish rate limiters - polling based
and precise. Users have an option to use either one of them in the topic
publish rate limiter, but the resource group rate limiter only uses polling
one.

There are challenges with both the rate limiters and the fact that we can't
use precise rate limiter in the resource group level.

Thus, in order to support custom rate limiters, I've created the PIP-310

This is the discussion thread. Please go through the PIP and provide your
inputs.

Link - https://github.com/apache/pulsar/pull/21399

Regards
-- 
Girish Sharma

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

[guo jiwei]

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
would like to start a vote for PIP-307
.


Ref:
• Discuss Mail:
https://lists.apache.org/thread/co8396ywny161x91dffzvxlt993mo1ht
• PIP-307: https://github.com/apache/pulsar/pull/21390


Regards
Jiwei Guo (Tboy)

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

[guo jiwei]

Thanks, I will send out the vote mail.


Regards
Jiwei Guo (Tboy)


On Thu, Oct 19, 2023 at 11:50 AM Zixuan Liu  wrote:

> +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 discussing PIP-307 .
> >
> >
> > Ref:
> > • PIP-307: https://github.com/apache/pulsar/pull/21390
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
>

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

[Lari Hotari]

I have created https://github.com/apache/pulsar/pull/21400 which parameterizes 
the JDK version used for the Pulsar CI GitHub Actions workflow. When triggering 
the workflow
manually, it's possible to choose between JDK 17 and JDK 21 from a dropdown 
menu.
The PR contains more details, please review. Once we have this merged, it will 
be easy to experiment with Java 21 when needed.

-Lari

On 2023/10/19 03:06:39 tison wrote:
> > 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.
> 
> 
> Zixuan Liu  于2023年10月19日周四 10:56写道：
> 
> > +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 19th and has now become the current
> > Java LTS release.
> > >
> > > I've begun preparations in the Pulsar code base to allow for Java 21 to
> > be used as the development runtime for compiling the code and running tests
> > in the master branch. This is a proactive measure to gear up for Java 21
> > without committing to the switch just yet. It will help us understand the
> > necessary changes when we are able to compile the code and run all tests
> > with Java 21.
> > >
> > > For instance, I initiated the process with the following PRs:
> > > - Upgrade Mockito to 5.6.0 to support Java 21 [1]
> > > - Upgrade Gradle Enterprise Maven Extension to support Java 21 [2]
> > > After these are merged, it should be possible to start running tests
> > with Java 21 to see what is possibly broken and continue iterating.
> > > Moreover, the upgrade to Lombok 1.18.30 for Java 21 support has already
> > been merged [3].
> > >
> > > Java 17 has been the recommended runtime for Pulsar server components
> > since the Pulsar 2.11 release [4]. Meanwhile, the Pulsar client continues
> > to be supported on Java 8+.
> > >
> > > I would like to initiate discussions about making Java 21 the
> > recommended and default runtime for Pulsar server components. Note that
> > there will be no change to the Pulsar client, which will remain on Java 8+.
> > >
> > > I guess we could come up with a PIP to document the decision once we
> > have had this discussion.
> > >
> > > Do you think we can target the switch from Java 17 to Java 21 for the
> > Pulsar 3.2 release?
> > > Could anyone update me on the current schedule for Pulsar 3.2?
> > >
> > > -Lari
> > >
> > > [1] - https://github.com/apache/pulsar/pull/21385
> > > [2] - https://github.com/apache/pulsar/pull/21384
> > > [3] - https://github.com/apache/pulsar/pull/21278
> > > [4] -
> > https://github.com/apache/pulsar#pulsar-runtime-java-version-recommendation
> >
> 

Re: [VOTE] Pulsar Release 3.1.1 Candidate 1

[mattison chao]

+1 (binding)


- Built from source code. (Java version: 17.0.8.1, Apache Maven 3.9.4, OS name: 
"mac os x", version: "13.4.1", arch: "x86_64")
- Checked binary license
- Started Standalone
- Ran a round of publish and consume

Best,
Mattison

> On 7 Oct 2023, at 09:09, guo jiwei  wrote:
> 
> This is the first release candidate for Apache Pulsar version 3.1.1.
> 
> It fixes the following issues:
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.1+label%3Acherry-picked%2Fbranch-3.1+
> 
> *** Please download, test and vote on this release. This vote will
> stay open for at least 72 hours ***
> 
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.1-candidate-1/
> 
> SHA-512 checksums:
> 
> af79f970c8835320584faf58c85bfc5cd12261f5e366c2c16bce2f7628d769ef7374a3c0e383ff443519e484a35a23e86415e0156a0f35dd3bc1f606d2fa0421
> 
> apache-pulsar-3.1.1-bin.tar.gz
> 
> a43306b8a08a330c721ca96501c0c4285e5c47cfab4a037034148401afc4dbd65e505da591ef9ca76ca5acf39d6fd9c96537a08956ad6fb37f7c70d8ab747510
> 
> apache-pulsar-3.1.1-src.tar.gz
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1243/
> 
> The tag to verify:
> v3.1.1-candidate-1 (80fb39085b4e49ff31f2df17b10addcca5abdccb)
> https://github.com/apache/pulsar/releases/tag/v3.1.1-candidate-1
> 
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> 
> Docker images:
> 
> pulsar images:
> https://hub.docker.com/layers/mattison/pulsar-all/3.1.1-80fb390/images/sha256-1088b07fd2448733db1d165676b82c1278f2940cb0861c704450ef2be5c2fa1c?context=explore
> 
> pulsar-all images:
> https://hub.docker.com/layers/mattison/pulsar/3.1.1-80fb390/images/sha256-21e8bf1571e4ab559a51b3f6e524d725cffabe3c6836101f9d7ea7eb1e2bf62c?context=explore
> 
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
> 
> 
> 
> Regards
> Jiwei Guo (Tboy)