[VOTE] PIP-329: Strategy for maintaining the latest tag to Pulsar docker images

[Zike Yang]

Hi, all

I'm starting the vote for PIP-329: Strategy for maintaining the latest
tag to Pulsar docker images

PIP link: https://github.com/apache/pulsar/pull/21872

Thanks,
Zike Yang

[VOTE] PIP-330: getMessagesById gets all messages

[Zixuan Liu]

Hi Pulsar Community,

Voting for PIP-330: getMessagesById gets all messages

PIP: https://github.com/apache/pulsar/pull/21873
Discussion thread:
https://lists.apache.org/thread/vqyh3mvtvovd383sd8zxnlzsspdr863z

Thanks,
Zixuan

Re: [VOTE] PIP-330: getMessagesById gets all messages

[Zike Yang]

+1 (non-binding)

Thanks,
Zike Yang

On Mon, Jan 15, 2024 at 5:34 PM Zixuan Liu  wrote:
>
> Hi Pulsar Community,
>
> Voting for PIP-330: getMessagesById gets all messages
>
> PIP: https://github.com/apache/pulsar/pull/21873
> Discussion thread:
> https://lists.apache.org/thread/vqyh3mvtvovd383sd8zxnlzsspdr863z
>
> Thanks,
> Zixuan

Re: [VOTE] PIP-329: Strategy for maintaining the latest tag to Pulsar docker images

[Zixuan Liu]

+1(non-binding)

Thanks,
Zixuan

Zike Yang  于2024年1月15日周一 16:14写道：

> Hi, all
>
> I'm starting the vote for PIP-329: Strategy for maintaining the latest
> tag to Pulsar docker images
>
> PIP link: https://github.com/apache/pulsar/pull/21872
>
> Thanks,
> Zike Yang
>

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.2 Candidate 1

[Lari Hotari]

+1 (binding)

- verified source package checksum and signature.
- verified staged maven artifacts by running a test app built with Gradle.
  - used "./scripts/validate_staging_repo.sh 0.5.2 
https://repository.apache.org/content/repositories/orgapachepulsar-1261"; 
command for an automated check

-Lari

On 2024/01/12 20:24:36 Chris Bono wrote:
> Following PIP-205: Reactive Java client for Apache Pulsar (
> https://github.com/apache/pulsar/issues/17335), this is release
> candidate 1 for the Reactive Java client for Apache Pulsar, version 0.5.2.
> 
> *** 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 in the Maven 
> repository
> are provided for convenience.
> 
> Source package:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.2-candidate-1/
> 
> SHA-512 checksums:
> 206a790ef54a20683a26e5c585676ca4a4c4410468cc5a9eec2a2331778f17bbd42b82a4d5b4440fa8aa7059e66c2227ad9e55588202e80b7ea72a589b6466ed
>  pulsar-client-reactive-0.5.2-src.tar.gz
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1261/
> 
> The tag to be voted upon:
> v0.5.2-candidate-1 (0ec250d65868d61c64333f7f3b0c439b54257da7)
> https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.2-candidate-1
> 
> Please download the source package, and follow detailed instructions
> for pulsar-client-reactive release validation at
> https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> .
> 
> Best regards
> 
> Chris Bono
> 

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.2 Candidate 1

[guo jiwei]

+1 (binding)

- verified source package checksum and signature.
- verified binary `./scripts/validate_staging_repo.sh 0.5.2
https://repository.apache.org/content/repositories/orgapachepulsar-1261`
- verified the HelloPulsarClientReactive with maven artifacts


Regards
Jiwei Guo (Tboy)


On Mon, Jan 15, 2024 at 7:00 PM Lari Hotari  wrote:

> +1 (binding)
>
> - verified source package checksum and signature.
> - verified staged maven artifacts by running a test app built with Gradle.
>   - used "./scripts/validate_staging_repo.sh 0.5.2
> https://repository.apache.org/content/repositories/orgapachepulsar-1261";
> command for an automated check
>
> -Lari
>
> On 2024/01/12 20:24:36 Chris Bono wrote:
> > Following PIP-205: Reactive Java client for Apache Pulsar (
> > https://github.com/apache/pulsar/issues/17335), this is release
> > candidate 1 for the Reactive Java client for Apache Pulsar, version
> 0.5.2.
> >
> > *** 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 in the Maven
> repository
> > are provided for convenience.
> >
> > Source package:
> >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.2-candidate-1/
> >
> > SHA-512 checksums:
> >
> 206a790ef54a20683a26e5c585676ca4a4c4410468cc5a9eec2a2331778f17bbd42b82a4d5b4440fa8aa7059e66c2227ad9e55588202e80b7ea72a589b6466ed
> >  pulsar-client-reactive-0.5.2-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1261/
> >
> > The tag to be voted upon:
> > v0.5.2-candidate-1 (0ec250d65868d61c64333f7f3b0c439b54257da7)
> >
> https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.2-candidate-1
> >
> > Please download the source package, and follow detailed instructions
> > for pulsar-client-reactive release validation at
> >
> https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> > .
> >
> > Best regards
> >
> > Chris Bono
> >
>

Re: [DISCUSS] Always set a broker side timestamp for message and deprecate some API

[Lin Lin]

User disabling `AppendBrokerTimestampMetadataInterceptor` does not mean that 
they allow this bug.
This is a configuration, not an API. It is difficult to use documentation to 
regulate user behavior.

Maybe we can add a new field (BrokerTimestamp) to save the timestamp on the 
Broker side. 
The time priority for trimming Ledger is as follows:

BrokerPublishTime > BrokerTimestamp

If `BrokerPublishTime` exists, `BrokerReceiveTime` is not set. 
If not, we set `BrokerReceiveTime`  and is no longer affected by client time.

On 2024/01/15 02:15:17 PengHui Li wrote:
> IMO, we should enable `AppendBrokerTimestampMetadataInterceptor` by default.
> Users can still have a way to disable it if they care about the additional
> metadata stored
> in each entry.
> 
> For the `hasBrokerPublishTime` API. The topic might also have historical
> data without
> broker publish time. So, it should be fine to keep this API because we
> don't know how
> long users will retain their data.
> 
> Regards,
> Penghui
> 
> On Sat, Jan 6, 2024 at 10:35 PM linlin  wrote:
> 
> > Now, if the message's metadata does not set a broker side timestamp, the
> > ledger expiration check is based on the client's publish time.
> >
> > When the client machine's clock is incorrect (eg: set to 1 year later) ,
> > the ledger can not be cleaned up. Issue
> > https://github.com/apache/pulsar/issues/21347
> >
> > `AppendBrokerTimestampMetadataInterceptor` can set timestamp for messages
> > on the broker side, but we can not ensure that the
> > `AppendBrokerTimestampMetadataInterceptor` is always enable
> >
> > Therefore, I open this PR(https://github.com/apache/pulsar/pull/21835) to
> > always set the broker timestamp for messages on the broker side.
> >
> > With this change , firstly we should deprecate
> > AppendBrokerTimestampMetadataInterceptor.
> > It no longer needs to exist
> >
> > Secondly, we should deprecate `hasBrokerPublishTime` in interface Message.
> > It always returns true.
> > This API is created in PR (https://github.com/apache/pulsar/pull/11553)
> > This PR is for the client to obtain BrokerPublishTime, so the
> > `hasBrokerPublishTime` API is not necessary.
> >
> 

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.2 Candidate 1

[Enrico Olivelli]

+1 (binding)

- verified checksums
- run all tests, on JDK 11

Thanks for putting up the release

Enrico

Il giorno lun 15 gen 2024 alle ore 13:08 guo jiwei
 ha scritto:
>
> +1 (binding)
>
> - verified source package checksum and signature.
> - verified binary `./scripts/validate_staging_repo.sh 0.5.2
> https://repository.apache.org/content/repositories/orgapachepulsar-1261`
> - verified the HelloPulsarClientReactive with maven artifacts
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Mon, Jan 15, 2024 at 7:00 PM Lari Hotari  wrote:
>
> > +1 (binding)
> >
> > - verified source package checksum and signature.
> > - verified staged maven artifacts by running a test app built with Gradle.
> >   - used "./scripts/validate_staging_repo.sh 0.5.2
> > https://repository.apache.org/content/repositories/orgapachepulsar-1261";
> > command for an automated check
> >
> > -Lari
> >
> > On 2024/01/12 20:24:36 Chris Bono wrote:
> > > Following PIP-205: Reactive Java client for Apache Pulsar (
> > > https://github.com/apache/pulsar/issues/17335), this is release
> > > candidate 1 for the Reactive Java client for Apache Pulsar, version
> > 0.5.2.
> > >
> > > *** 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 in the Maven
> > repository
> > > are provided for convenience.
> > >
> > > Source package:
> > >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-reactive-0.5.2-candidate-1/
> > >
> > > SHA-512 checksums:
> > >
> > 206a790ef54a20683a26e5c585676ca4a4c4410468cc5a9eec2a2331778f17bbd42b82a4d5b4440fa8aa7059e66c2227ad9e55588202e80b7ea72a589b6466ed
> > >  pulsar-client-reactive-0.5.2-src.tar.gz
> > >
> > > Maven staging repo:
> > > https://repository.apache.org/content/repositories/orgapachepulsar-1261/
> > >
> > > The tag to be voted upon:
> > > v0.5.2-candidate-1 (0ec250d65868d61c64333f7f3b0c439b54257da7)
> > >
> > https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.2-candidate-1
> > >
> > > Please download the source package, and follow detailed instructions
> > > for pulsar-client-reactive release validation at
> > >
> > https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation
> > > .
> > >
> > > Best regards
> > >
> > > Chris Bono
> > >
> >

[ANNOUNCE] Released Reactive client for Apache Pulsar, version 0.5.2

[Chris Bono]

The Apache Pulsar team is proud to announce the Reactive client for
Apache Pulsar, version 0.5.2.

The Reactive client for Apache Pulsar can be used together with any
Reactive Streams implementation on the JVM. Examples include Project
Reactor / Spring Reactive, Akka Streams, RxJava 3, Vert.x, SmallRye
Mutiny (RedHat/Quarkus), ServiceTalk and others. (Reactive Streams to
JDK Flow adapters might be needed in some cases.)

Reactive programming is about non-blocking applications that are
asynchronous and event-driven and require a small number of threads to
scale.
The Reactive client for Apache Pulsar supports non-blocking, reactive
& asynchronous back pressure for producing and consuming messages.
The library provides an interface module "pulsar-client-reactive-api"
that abstracts the Reactive client API. This interface is currently
implemented by wrapping the Apache Pulsar Java client and adapting the
existing asynchronous Java API to the Reactive client API. The
decoupled reactive interfaces makes it possible to implement a fully
native reactive client in the future.

Source package is available for download at
https://downloads.apache.org/pulsar/pulsar-client-reactive-0.5.2/

Maven packages are available in Maven central. Please check
https://github.com/apache/pulsar-client-reactive#getting-it for usage
with Maven or Gradle builds.

Release Notes are at:
https://github.com/apache/pulsar-client-reactive/releases/tag/v0.5.2

We would like to thank the contributors that made the release possible.

Regards,

The Pulsar Team

Re: [VOTE] PIP-330: getMessagesById gets all messages

[Dezhi Liu]

+1 (non-binding)

Thanks,
Dezhi Liu

On 2024/01/15 09:33:48 Zixuan Liu wrote:
> Hi Pulsar Community,
> 
> Voting for PIP-330: getMessagesById gets all messages
> 
> PIP: https://github.com/apache/pulsar/pull/21873
> Discussion thread:
> https://lists.apache.org/thread/vqyh3mvtvovd383sd8zxnlzsspdr863z
> 
> Thanks,
> Zixuan
> 

[VOTE]PIP-321: Split the responsibilities of namespace replication-clusters

[Xiangying Meng]

Dear Pulsar community,

I am initiating a voting thread for "PIP-321: Split the responsibilities of
namespace replication-clusters".

Here is the pull request for PIP-321:
https://github.com/apache/pulsar/pull/21648

And the discussion thread:
https://lists.apache.org/thread/87qfp8ht5s0fvw2y4t3j9yzgfmdzmcnz

Highlight:
This proposal introduces a new feature for topics, allowing a topic to be
loaded across different clusters without data replication between these
clusters. It also introduces more granular control over `allowed_clusters`
at the namespace level.

Please review the PIP document and cast your vote!

Thank you,

Xiangying

[VERIFY] Pulsar Release 3.2.0 Candidate 2

[guo jiwei]

This is the second release candidate for Apache Pulsar version 3.2.0.

It fixes the following issues:
https://github.com/apache/pulsar/milestone/36?closed=1

*** Please download, test and verify on this release. This release
candidate verification will stay open until Jan 15 ***

Note that we are verifying upon the source (tag), binaries are provided for
convenience.

Source and binary files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.2.0-candidate-2/

SHA-512 checksums:

57af4de0531baada79ff3eb5e51659ae3d2b6732840a27861636d3538d8cca2b3aeb77d3f5cecf37dc5d8a0de11a05d0775ae2d2ca9398f9747fbe662e1cdeae

apache-pulsar-3.2.0-bin.tar.gz

7ddd8df261f4ffeed2e4f029aa475f523bb9505869870db681a57b7df25af01d5670ba00bc7e062ddae0b962eaed9ee828a4cd7f4744a965afd77e9ae1239d6a

apache-pulsar-3.2.0-src.tar.gz

Maven staging repo:
https://repository.apache.org/content/repositories/orgapachepulsar-1262/

The tag to verify:
v3.2.0-candidate-2 (5348e1b9124052a454f66769ae3e9f54ee0a75d4)
https://github.com/apache/pulsar/commits/v3.2.0-candidate-2/

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/technoboy8/pulsar/3.2.0-5348e1b/images/sha256-cf02a08e588ca493d10dbe472b72f5e64e4f90b8b5ae01e91321f336776a5a4e?context=repo

pulsar-all images:
https://hub.docker.com/layers/technoboy8/pulsar-all/3.2.0-5348e1b/images/sha256-801e395fc26257e2beb5ea0574fe27f5a4ff956c85cbcd6b362432d6dda28b95?context=repo

Please download the source package, and follow the README to build
and run the Pulsar standalone service.

Note that this RC doesn't require a formal vote, but we would also
appreciate your feedback with +1/-1. And please provide specific
comments if your feedback is not +1.


Regards
Jiwei Guo (Tboy)