Hi, dev:
This thread is to start a vote for PIP-386: Add resetIncludeHead
in CommandSubscribe for startMessageIdInclusive implementation
Discussion thread:
https://lists.apache.org/thread/tvk9nl47gqtbx2nrdzknm4v8sm67ywp9
PIP-PR: https://github.com/apache/pulsar/pull/23427
Sincerely
I'll start a vote on this pip.
This is intended to fix issue，and if we want to implement
startMessageIdInclusive() in broker side，
this pip will not affect the logic, we can do it in other pip later.
On 2024/10/15 16:47:49 Jiawen Wang wrote:
> Thanks for your reply !
>
> In my previous thoug
Now there's the first case where Jetty 9.4.x isn't getting a security upgrade:
https://github.com/jetty/jetty.project/pull/12012#issuecomment-2416450253
It's about a low priority 3.7/10 CVE-2024-6763:
https://nvd.nist.gov/vuln/detail/CVE-2024-6763
https://avd.aquasec.com/nvd/2024/cve-2024-6763/
Fo
+1 (non-binding)
- Built from source
- Checked the signatures of the source and binary release artifacts
- Ran pulsar standalone
- Checked producer and consumer
- Verified the Cassandra connector
- Verified the Stateful function
+1 (binding)
Validated source artifacts
- checked sha512 checksum
- checked signature
Validated binaries
- ran sample app
-Lari
On 2024/10/16 17:25:28 Chris Bono wrote:
> Following PIP-205: Reactive Java client for Apache Pulsar (
> https://github.com/apache/pulsar/issues/17335), this is releas
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.8.
*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours
+1 (binding)
- Verified checksum and signatures
- Built from source
- Ran the standalone locally
- Ran a simple e2e test
- Ran a customized function job
- Ran pulsar-shell to check some policies and topic info
Thanks,
Yunze
On Tue, Oct 15, 2024 at 3:58 PM 潘舒新 wrote:
>
> +1 (non-binding)
>
> - B
Hi all,
I recently encountered an issue with the Pulsar client used in the broker
interceptor, which broke the broker’s response command. To address this, I
submitted a PR[1], which has now been cherry-picked to the branch-3.0.
Since this change affects core functionality, it may introduce regres
Hi Lari,
*
There's a plan to decouple the Pulsar client from the protobuf-java version so
that client applications could choose to use a protobuf-java version that is
compatible with their own protoc-generated stub classes. The issue to track
this is https://github.com/apache/pulsar/issues/2
Regarding Pulsar performance tuning, it's crucial to tune the Pulsar broker
cache since the defaults in Pulsar are not optimal.
Besides poor performance for Pulsar use cases, this leads to wasted CPU and
unnecessary network transfer costs in cloud environments.
Tuning the Pulsar broker cache impr
10 matches
Mail list logo
