dev  

Messages by Thread

• • Re: [DISCUSS] Stop using Netty Recycler in new code Zixuan Liu
  • Re: [DISCUSS] Stop using Netty Recycler in new code Yunze Xu
• [VOTE] DotPulsar Release 4.3.2-rc.1 David Jensen
  • Re: [VOTE] DotPulsar Release 4.3.2-rc.1 Daniel Blankensteiner
  • Re: [VOTE] DotPulsar Release 4.3.2-rc.1 David Jensen
  • Re: [VOTE] DotPulsar Release 4.3.2-rc.1 Lari Hotari
• [DISCUSS] PIP-442: Add Flow Control for CommandGetTopicsOfNamespace and CommandWatchTopicList Lari Hotari
  • Re: [DISCUSS] PIP-442: Add Flow Control for CommandGetTopicsOfNamespace and CommandWatchTopicList Lari Hotari
  • Re: [DISCUSS] PIP-442: Add memory limits for CommandGetTopicsOfNamespace and CommandWatchTopicList on Broker and Proxy Lari Hotari
• [VOTE] PIP-441: Add Broker-Level Metrics for Skipped Non-Recoverable Data PengHui Li
  • Re: [VOTE] PIP-441: Add Broker-Level Metrics for Skipped Non-Recoverable Data Lari Hotari
  • RE: [VOTE] PIP-441: Add Broker-Level Metrics for Skipped Non-Recoverable Data Yike Xiao
  • Re: [VOTE] PIP-441: Add Broker-Level Metrics for Skipped Non-Recoverable Data guo jiwei
• [DISCUSS] PIP-441: Add Broker-Level Metrics for Skipped Non-Recoverable Data PengHui Li
  • Re: [DISCUSS] PIP-441: Add Broker-Level Metrics for Skipped Non-Recoverable Data Lari Hotari
• [VOTE] PIP-439: Adding Transaction Support to Pulsar Functions Through Managed Transaction Wrapping Ramzan MAGOMADOW
  • Re: [VOTE] PIP-439: Adding Transaction Support to Pulsar Functions Through Managed Transaction Wrapping Lari Hotari
  • Re: [VOTE] PIP-439: Adding Transaction Support to Pulsar Functions Through Managed Transaction Wrapping guo jiwei
  • Re: [VOTE] PIP-439: Adding Transaction Support to Pulsar Functions Through Managed Transaction Wrapping Yunze Xu
  • Re: [VOTE] PIP-439: Adding Transaction Support to Pulsar Functions Through Managed Transaction Wrapping Pengcheng Jiang
  • Re: [VOTE] PIP-439: Adding Transaction Support to Pulsar Functions Through Managed Transaction Wrapping Neng Lu
  • RE: [VOTE] PIP-439: Adding Transaction Support to Pulsar Functions Through Managed Transaction Wrapping Ramzan MAGOMADOW
  • RE: [VOTE] PIP-439: Adding Transaction Support to Pulsar Functions Through Managed Transaction Wrapping Lari Hotari
• [ANNOUNCE] Apache Pulsar 4.1.0 released Cong Zhao
• [DISCUSS] PIP-440: WaitForExclusive priority queueing Joshua
  • Re: [DISCUSS] PIP-440: WaitForExclusive priority queueing Matteo Merli
• [DISCUSS] PIP-439: Adding Transaction Support to Pulsar Functions Through Auto-Transaction Wrapping Ramzan MAGOMADOW
  • Re: [DISCUSS] PIP-439: Adding Transaction Support to Pulsar Functions Through Auto-Transaction Wrapping Lari Hotari
  • RE: Re: [DISCUSS] PIP-439: Adding Transaction Support to Pulsar Functions Through Auto-Transaction Wrapping Ramzan MAGOMADOW
  • RE: Re: [DISCUSS] PIP-439: Adding Transaction Support to Pulsar Functions Through Auto-Transaction Wrapping Lari Hotari
  • RE: RE: Re: [DISCUSS] PIP-439: Adding Transaction Support to Pulsar Functions Through Auto-Transaction Wrapping Ramzan MAGOMADOW
  • RE: RE: Re: [DISCUSS] PIP-439: Adding Transaction Support to Pulsar Functions Through Auto-Transaction Wrapping Lari Hotari
• [VOTE] Release Apache Pulsar 4.1.0 based on 4.1.0-candidate-1 Cong Zhao
  • Re: [VOTE] Release Apache Pulsar 4.1.0 based on 4.1.0-candidate-1 Philipp Dolif
  • Re: [VOTE] Release Apache Pulsar 4.1.0 based on 4.1.0-candidate-1 guo jiwei
  • Re: [VOTE] Release Apache Pulsar 4.1.0 based on 4.1.0-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 4.1.0 based on 4.1.0-candidate-1 xiangying meng
  • Re: [VOTE] Release Apache Pulsar 4.1.0 based on 4.1.0-candidate-1 Cong Zhao
• Adding Wolfi OS base docker image support to Pulsar build in addition to Alpine Lari Hotari
• [DISCUSS] Cherry-pick PR #24647 (OpenTelemetry client memory buffer metrics) to LTS branches PengHui Li
• [DISCUSS] PIP-438: add namespace topics limit metric Alexandre Burgoni
• [VOTE] PIP-437: Granular and Fixed-Delay Policies for Message Delivery Christina
  • Re: [VOTE] PIP-437: Granular and Fixed-Delay Policies for Message Delivery Lari Hotari
  • Re: [VOTE] PIP-437: Granular and Fixed-Delay Policies for Message Delivery SiNan Liu
  • Re: [VOTE] PIP-437: Granular and Fixed-Delay Policies for Message Delivery Lari Hotari
• [DISCUSS] Cherry-pick "PIP-428: Change TopicPoliciesService interface to fix consistency issues" to branch-4.0 Lari Hotari
  • Re: [DISCUSS] Cherry-pick "PIP-428: Change TopicPoliciesService interface to fix consistency issues" to branch-4.0 Lari Hotari
• AI generated docs for Pulsar in deepwiki Lari Hotari
  • Re: AI generated docs for Pulsar in deepwiki SiNan Liu
• [DISCUSS] Stop using reflection to access private fields in tests Yunze Xu
  • Re: [DISCUSS] Stop using reflection to access private fields in tests Lari Hotari
  • Re: [DISCUSS] Stop using reflection to access private fields in tests Zhangjian He
  • Re: [DISCUSS] Stop using reflection to access private fields in tests Jie crossover
  • Re: [DISCUSS] Stop using reflection to access private fields in tests Ruimin MA
  • Re: [DISCUSS] Stop using reflection to access private fields in tests xiangying meng
  • Re: [DISCUSS] Stop using reflection to access private fields in tests Tao Jiuming
• [REQUEST] Please cleanup non-current releases from svn dist that appear on downloads.apache.org Dave Fisher
• [DISCUSS] Apache Pulsar 4.1.0 release Cong Zhao
  • Re: [DISCUSS] Apache Pulsar 4.1.0 release Lari Hotari
  • Re: [DISCUSS] Apache Pulsar 4.1.0 release Yunze Xu
  • Re: [DISCUSS] Apache Pulsar 4.1.0 release Cong Zhao
• Join the Data Streaming Summit SF — 50% off for Pulsar & BookKeeper users Sijie Guo
• [DISCUSS] PIP-437: Granular Control for Message Delivery Delays Christina
  • Re: [DISCUSS] PIP-437: Granular Control for Message Delivery Delays Lari Hotari
• [DISCUSS]Cherry-pick PIP-422 into branch-40. yubiao
  • Re: [DISCUSS]Cherry-pick PIP-422 into branch-40. yubiao
• [ANNOUNCE] Apache Pulsar Helm Chart version 4.2.0 Released Lari Hotari
• [ANNOUNCE] Apache Pulsar Go Client 0.16.0 released Zike Yang
• Test code coverage reports finally available for apache/pulsar master branch Lari Hotari
• [VOTE] Release Apache Pulsar Helm Chart 4.2.0 based on 4.2.0-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar Helm Chart 4.2.0 based on 4.2.0-candidate-1 xiangying meng
  • Re: [VOTE] Release Apache Pulsar Helm Chart 4.2.0 based on 4.2.0-candidate-1 Zixuan Liu
  • Re: [VOTE] Release Apache Pulsar Helm Chart 4.2.0 based on 4.2.0-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar Helm Chart 4.2.0 based on 4.2.0-candidate-1 Lari Hotari
• [VOTE]PIP-436:add decryptFailListener to Consumer Ruimin MA
  • Re: [VOTE]PIP-436:add decryptFailListener to Consumer Ruimin MA
  • Re: [VOTE]PIP-436:add decryptFailListener to Consumer Tao Jiuming
  • Re: [VOTE]PIP-436:add decryptFailListener to Consumer PengHui Li
  • Re: [VOTE]PIP-436:add decryptFailListener to Consumer Zike Yang
  • Re: [VOTE]PIP-436:add decryptFailListener to Consumer Ruimin MA
  • Re:[VOTE]PIP-436:add decryptFailListener to Consumer yubiao
• [ANNOUNCE] Apache Pulsar 4.0.6 released Lari Hotari
• [ANNOUNCE] Apache Pulsar 3.3.8 released Lari Hotari
• [ANNOUNCE] Apache Pulsar 3.0.13 released Lari Hotari
• [DISCUSSION] Adding Transactional Support to Pulsar Functions - PIP Proposal Ramzan MAGOMADOW
  • Re: [DISCUSSION] Adding Transactional Support to Pulsar Functions - PIP Proposal Lari Hotari
  • Re: [DISCUSSION] Adding Transactional Support to Pulsar Functions - PIP Proposal Pengcheng Jiang
• [VOTE] Release Apache Pulsar 4.0.6 based on 4.0.6-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 4.0.6 based on 4.0.6-candidate-1 Yunze Xu
  • Re: [VOTE] Release Apache Pulsar 4.0.6 based on 4.0.6-candidate-1 Yunze Xu
  • Re: [VOTE] Release Apache Pulsar 4.0.6 based on 4.0.6-candidate-1 PengHui Li
  • Re: [VOTE] Release Apache Pulsar 4.0.6 based on 4.0.6-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 4.0.6 based on 4.0.6-candidate-1 xiangying meng
  • Re: [VOTE] Release Apache Pulsar 4.0.6 based on 4.0.6-candidate-1 PengHui Li
  • Re: [VOTE] Release Apache Pulsar 4.0.6 based on 4.0.6-candidate-1 David Jensen
  • Re: [VOTE] Release Apache Pulsar 4.0.6 based on 4.0.6-candidate-1 Lari Hotari
• [VOTE] Release Apache Pulsar 3.3.8 based on 3.3.8-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 3.3.8 based on 3.3.8-candidate-1 David Jensen
  • Re: [VOTE] Release Apache Pulsar 3.3.8 based on 3.3.8-candidate-1 xiangying meng
  • Re: [VOTE] Release Apache Pulsar 3.3.8 based on 3.3.8-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 3.3.8 based on 3.3.8-candidate-1 Lari Hotari
• [VOTE] Release Apache Pulsar 3.0.13 based on 3.0.13-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 3.0.13 based on 3.0.13-candidate-1 David Jensen
  • Re: [VOTE] Release Apache Pulsar 3.0.13 based on 3.0.13-candidate-1 xiangying meng
  • Re: [VOTE] Release Apache Pulsar 3.0.13 based on 3.0.13-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 3.0.13 based on 3.0.13-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 3.0.13 based on 3.0.13-candidate-1 Lari Hotari
• [VOTE] Pulsar Client Go Release 0.16.0 Candidate 1 Zike Yang
  • Re: [VOTE] Pulsar Client Go Release 0.16.0 Candidate 1 Jie crossover
  • Re: [VOTE] Pulsar Client Go Release 0.16.0 Candidate 1 Yunze Xu
  • Re: [VOTE] Pulsar Client Go Release 0.16.0 Candidate 1 Baodi Shi
  • Re: [VOTE] Pulsar Client Go Release 0.16.0 Candidate 1 Zike Yang
  • Re: [VOTE] Pulsar Client Go Release 0.16.0 Candidate 1 Zike Yang
• [DISCUSS]PIP-436:add decryptFailListener to Consumer Ruimin MA
  • Re: [DISCUSS]PIP-436:add decryptFailListener to Consumer PengHui Li
• [DISCUSS] Release Pulsar Go Client 0.16.0 Zike Yang
• [VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable yubiao
  • Re: [VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable Lari Hotari
  • Re: [VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable Tao Jiuming
  • Re: [VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable PengHui Li
  • Re: [VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable yubiao
  • Re: [VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable Aloys Zhang
  • Re: [VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable Gavin gao
  • Re: [VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable PengHui Li
  • Re: [VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable guo jiwei
  • Re:[VOTE] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable yubiao
• [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Lari Hotari
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Yunze Xu
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Matteo Merli
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count PengHui Li
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Lari Hotari
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Lari Hotari
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Lari Hotari
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count PengHui Li
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Lari Hotari
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count PengHui Li
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Lari Hotari
  • Re: [VOTE] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count PengHui Li
• [DISCUSS] Cherry-pick 24524 to branch-4.0 guo jiwei
• [ANNOUNCE] Apache Pulsar Client Python 3.8.0 released Yunze Xu
• [VOTE] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli guo jiwei
  • Re: [VOTE] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli Yunze Xu
  • Re:[VOTE] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli yubiao
  • Re: [VOTE] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli xiangying meng
  • Re: [VOTE] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli Tao Jiuming
  • Re: [VOTE] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli Zixuan Liu
  • Re: [VOTE] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli Jie crossover
  • Re: [VOTE] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli guo jiwei
• [DISCUSS] Pulsar releases 3.0.13, 3.3.8 and 4.0.6 Lari Hotari
  • Re: [DISCUSS] Pulsar releases 3.0.13, 3.3.8 and 4.0.6 PengHui Li
  • Re: [DISCUSS] Pulsar releases 3.0.13, 3.3.8 and 4.0.6 Tao Jiuming
  • Re: [DISCUSS] Pulsar releases 3.0.13, 3.3.8 and 4.0.6 Lari Hotari
  • Re: [DISCUSS] Pulsar releases 3.0.13, 3.3.8 and 4.0.6 Lari Hotari
  • Re: [DISCUSS] Pulsar releases 3.0.13, 3.3.8 and 4.0.6 Lari Hotari
  • Re: [DISCUSS] Pulsar releases 3.0.13, 3.3.8 and 4.0.6 Lari Hotari
  • Re: [DISCUSS] Pulsar releases 3.0.13, 3.3.8 and 4.0.6 Lari Hotari
  • Re: [DISCUSS] Pulsar releases 3.0.13, 3.3.8 and 4.0.6 Lari Hotari
• Pulsar Manager 0.5.0 release rac pqab
• [DISCUSS] Whether to recycle failed recyclable objects Yunze Xu
  • Re: [DISCUSS] Whether to recycle failed recyclable objects Lari Hotari
  • Re: [DISCUSS] Whether to recycle failed recyclable objects Ran Gao
  • Re: [DISCUSS] Whether to recycle failed recyclable objects PengHui Li
  • Re: [DISCUSS] Whether to recycle failed recyclable objects Yunze Xu
  • Re: [DISCUSS] Whether to recycle failed recyclable objects Yunze Xu
  • Re: [DISCUSS] Whether to recycle failed recyclable objects Lari Hotari
  • Re: [DISCUSS] Whether to recycle failed recyclable objects Tao Jiuming
• [DISCUSS] PIP-435: Add startTimestamp and endTimestamp for consuming message in client cli guo jiwei
• [ANNOUNCE] Apache Pulsar C# Client DotPulsar 4.3.1 released David Jensen
• [RESULT][VOTE] Apache Pulsar DotPulsar 4.3.1 released David Jensen
• [DISCUSS] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable yubiao
  • Re: [DISCUSS] PIP-434: Expose Netty channel configuration WRITE_BUFFER_WATER_MARK to pulsar conf and pause receive requests when channel is unwritable Lari Hotari
• [VOTE] Pulsar Client Python Release 3.8.0 Candidate 1 Yunze Xu
  • Re: [VOTE] Pulsar Client Python Release 3.8.0 Candidate 1 Baodi Shi
  • Re: [VOTE] Pulsar Client Python Release 3.8.0 Candidate 1 Zike Yang
  • Re: [VOTE] Pulsar Client Python Release 3.8.0 Candidate 1 Yunze Xu
• [ANNOUNCE] Apache Pulsar Client C++ 3.7.2 released Yunze Xu
• [VOTE] DotPulsar Release 4.3.1-rc.1 David Jensen
  • Re: [VOTE] DotPulsar Release 4.3.1-rc.1 Daniel Blankensteiner
  • Re: [VOTE] DotPulsar Release 4.3.1-rc.1 Lari Hotari
  • Re: [VOTE] DotPulsar Release 4.3.1-rc.1 David Jensen
• Please rebase to master because checkstyle for tests is applied now Yunze Xu
• [VOTE] PIP-432: Add isEncrypted field to EncryptionContext PengHui Li
  • Re: [VOTE] PIP-432: Add isEncrypted field to EncryptionContext Yubiao Feng
  • Re: [VOTE] PIP-432: Add isEncrypted field to EncryptionContext Tao Jiuming
  • Re: [VOTE] PIP-432: Add isEncrypted field to EncryptionContext xiangying meng
  • Re: [VOTE] PIP-432: Add isEncrypted field to EncryptionContext Zike Yang
  • Re: [VOTE] PIP-432: Add isEncrypted field to EncryptionContext Zixuan Liu
  • Re: [VOTE] PIP-432: Add isEncrypted field to EncryptionContext PengHui Li
• [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas Yubiao Feng
  • Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas PengHui Li
  • Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas Baodi Shi
  • Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas guo jiwei
  • Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas Zixuan Liu
  • Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas yubiao
  • Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas yubiao
  • Re:Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas yubiao
  • Re: Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas Zixuan Liu
  • Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas yubiao
  • Re: [Vote] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas yubiao
• [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Yubiao Feng

• Earlier messages
• Later messages