dev  

Messages by Thread

• • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2 PengHui Li
  • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2 Yunze Xu
  • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2 Yunze Xu
  • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2 PengHui Li
  • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2 mattison chao
  • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2 mattison chao
  • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2 Yunze Xu
  • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 2 Yunze Xu
• [DISSCUSS] Don't retain null-key messages during topic compaction Cong Zhao
  • Re: [DISSCUSS] Don't retain null-key messages during topic compaction mattison chao
  • Re: [DISSCUSS] Don't retain null-key messages during topic compaction Cong Zhao
  • Re: [DISSCUSS] Don't retain null-key messages during topic compaction Cong Zhao
  • Re: [DISSCUSS] Don't retain null-key messages during topic compaction Enrico Olivelli
  • Re: [DISSCUSS] Don't retain null-key messages during topic compaction Cong Zhao
• [DISSCUSS] PIP-317: Add `bookkeeperDeleted` field to show whether a ledger is deleted from the Bookie while using tiered storage 刘燊
  • Re: [DISSCUSS] PIP-317: Add `bookkeeperDeleted` field to show whether a ledger is deleted from the Bookie while using tiered storage Dezhi Liu
• [Discuss] Disable `Rebase and Merge` on Pulsar Repo Heesung Sohn
  • Re: [Discuss] Disable `Rebase and Merge` on Pulsar Repo Rajan Dhabalia
  • Re: [Discuss] Disable `Rebase and Merge` on Pulsar Repo Heesung Sohn
  • Re: [Discuss] Disable `Rebase and Merge` on Pulsar Repo tison
  • Re: [Discuss] Disable `Rebase and Merge` on Pulsar Repo Heesung Sohn
• Question about mismatch of ProducerStats/ConsumerStats interface description and implementation ywango
• [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 1 Yunze Xu
  • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 1 Baodi Shi
  • Re: [VOTE] Pulsar Client C++ Release 3.4.0 Candidate 1 Yunze Xu
• JVM's SIGSEGV crash bug JDK-8314024 possibly impacting Pulsar Lari Hotari
• [DISCUSS] PIP-315: Configurable max delay limit for delayed delivery Kevin Lu
  • Re: [DISCUSS] PIP-315: Configurable max delay limit for delayed delivery Cong Zhao
  • Re: [DISCUSS] PIP-315: Configurable max delay limit for delayed delivery Haiting Jiang
• Question about Pulsar gRPC client(s) Kiryl Valkovich
  • Re: Question about Pulsar gRPC client(s) Christophe Bornet
  • Re: Question about Pulsar gRPC client(s) Zike Yang
  • Re: Question about Pulsar gRPC client(s) Yunze Xu
  • Re: Question about Pulsar gRPC client(s) Dave Fisher
  • Re: Question about Pulsar gRPC client(s) Kiryl Valkovich
  • Re: Question about Pulsar gRPC client(s) Christophe Bornet
  • Re: Question about Pulsar gRPC client(s) Kiryl Valkovich
• Call for Presentations now open: Community over Code EU 2024 Ryan Skraba
• [CALL FOR CONTRIBUTE] The broker feature matrix page tison
• Reporting and tooling to detect thread leaks in Pulsar tests Lari Hotari
  • Re: Reporting and tooling to detect thread leaks in Pulsar tests Asaf Mesika
  • Re: Reporting and tooling to detect thread leaks in Pulsar tests Lari Hotari
  • Re: Reporting and tooling to detect thread leaks in Pulsar tests Enrico Olivelli
  • Re: Reporting and tooling to detect thread leaks in Pulsar tests Lari Hotari
  • Re: Reporting and tooling to detect thread leaks in Pulsar tests Asaf Mesika
• Pulsar CI broken due to Eclipse Temurin repository broken Lari Hotari
  • Re: Pulsar CI broken due to Eclipse Temurin repository broken Lari Hotari
  • Re: Pulsar CI broken due to Eclipse Temurin repository broken Lari Hotari
  • Re: Pulsar CI broken due to Eclipse Temurin repository broken Lari Hotari
  • Re: Pulsar CI broken due to Eclipse Temurin repository broken Lari Hotari
• [VOTE] Pulsar Release 3.0.2 Candidate 2 Yubiao Feng
  • Re: [VOTE] Pulsar Release 3.0.2 Candidate 2 Yubiao Feng
  • Re: [VOTE] Pulsar Release 3.0.2 Candidate 2 Lari Hotari
  • Re: [VOTE] Pulsar Release 3.0.2 Candidate 2 Yubiao Feng
  • Re: [VOTE] Pulsar Release 3.0.2 Candidate 2 Yubiao Feng
• [DISCUSS] PIP-313 Support force unsubscribe using consumer api Rajan Dhabalia
  • Re: [DISCUSS] PIP-313 Support force unsubscribe using consumer api PengHui Li
  • Re: [DISCUSS] PIP-313 Support force unsubscribe using consumer api Rajan Dhabalia
• [VOTE] PIP-271: Add broker health check status into prometheus metrics #20147 vineeth p
  • Re: [VOTE] PIP-271: Add broker health check status into prometheus metrics #20147 Rajan Dhabalia
  • Re: [VOTE] PIP-271: Add broker health check status into prometheus metrics #20147 太上玄元道君
• [DISCUSS] Expedited release of Pulsar 3.1.2 due to CVE-2023-44981 Lari Hotari
• [DISCUSS] Auto release Nuget artifacts for DotPulsar David Jensen
  • Re: [DISCUSS] Auto release Nuget artifacts for DotPulsar Zike Yang
  • Re: [DISCUSS] Auto release Nuget artifacts for DotPulsar Enrico Olivelli
  • Re: [DISCUSS] Auto release Nuget artifacts for DotPulsar tison
  • Re: [DISCUSS] Auto release Nuget artifacts for DotPulsar tison
  • RE: Re: [DISCUSS] Auto release Nuget artifacts for DotPulsar David Jensen
  • RE: Re: [DISCUSS] Auto release Nuget artifacts for DotPulsar David Jensen
• [ANNOUNCE] Apache Pulsar 3.1.1 released guo jiwei
• [DISCUSS] PIP-312 Use StateStoreProvider to manage state in Pulsar Functions endpoints Pengcheng Jiang
• Re: [DISCUSS] Roll up project status for pulsar-helm-chart Asaf Mesika
• [DISCUSS] PIP-311 Modify the signature of the `newMultiTransactionMessageAck` method Xiangying Meng
• [Discuss] Release Pulsar C++ Client 3.4.0 Yunze Xu
  • Re: [Discuss] Release Pulsar C++ Client 3.4.0 PengHui Li
  • Re: [Discuss] Release Pulsar C++ Client 3.4.0 Zike Yang
  • Re: [Discuss] Release Pulsar C++ Client 3.4.0 Baodi Shi
• [VOTE] PIP-304: Make PublishContext provide the message metadata kecona
  • Re: [VOTE] PIP-304: Make PublishContext provide the message metadata PengHui Li
  • Re: [VOTE] PIP-304: Make PublishContext provide the message metadata kecona
• [DISCUSS] PIP-309: Adding Pulsar Client Stats Reporter Ying
  • Re: [DISCUSS] PIP-309: Adding Pulsar Client Stats Reporter Asaf Mesika
• [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Asaf Mesika
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Asaf Mesika
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Rajan Dhabalia
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters 太上玄元道君
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Girish Sharma
  • Re: [DISCUSS] PIP-310: Support custom publish rate limiters Lari Hotari
• [VOTE] PIP-307: Support subscribing multi-topics for WebSocket guo jiwei
  • Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket mattison chao
  • Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket Yunze Xu
  • Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket PengHui Li
  • Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket Yubiao Feng
  • Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket Cong Zhao
  • Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket 太上玄元道君
  • Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket tison
  • Re: [VOTE] PIP-307: Support subscribing multi-topics for WebSocket guo jiwei
• [DISCUSS] PIP-308: Support share Retry and DLQ topic producers for MultiTopicConsumer instance lifepuzzlefun
• Upgrading Mockito to 5.6.0 in master branch for Java 21 compatibility Lari Hotari
• Pulsar CI partially blocked because "Broker Group 1" CI job times out frequently, adding new run group Lari Hotari
  • Re: Pulsar CI partially blocked because "Broker Group 1" CI job times out frequently, adding new run group Lari Hotari
• [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket guo jiwei
  • Re: [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket Yubiao Feng
  • Re: [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket mattison chao
  • Re: [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket Zixuan Liu
  • Re: [DISCUSS] PIP-307: Support subscribing multi-topics for WebSocket guo jiwei
• [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Lari Hotari
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime mattison chao
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Lari Hotari
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime mattison chao
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Enrico Olivelli
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime tison
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Lari Hotari
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Heesung Sohn
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Zixuan Liu
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime tison
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Lari Hotari
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Lari Hotari
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Christophe Bornet
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Lari Hotari
  • [OT] Evaluate Virtual thread [WAS][DISCUSS] Moving to Java 21 tison
  • Re: [OT] Evaluate Virtual thread [WAS][DISCUSS] Moving to Java 21 太上玄元道君
  • Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime Christophe Bornet
• [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client Diego Salvi
  • Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client Zili Chen
  • Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client Zixuan Liu
  • Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client guo jiwei
  • Re: [VOTE] PIP-305: Customize DNS servers to use for Pulsar Client PengHui Li
  • [RESULT][VOTE] PIP-305: Customize DNS servers to use for Pulsar Client Zili Chen
• [DISCUSS] Release Apache Pulsar 2.11.3 Baodi Shi
  • Re: [DISCUSS] Release Apache Pulsar 2.11.3 PengHui Li
  • Re: [DISCUSS] Release Apache Pulsar 2.11.3 mattison chao
  • Re: [DISCUSS] Release Apache Pulsar 2.11.3 Yubiao Feng
  • Re: [DISCUSS] Release Apache Pulsar 2.11.3 Zixuan Liu
  • Re: [DISCUSS] Release Apache Pulsar 2.11.3 Frank Kelly
• How do we generate new versioned docs now? tison
• Pulsar CI blocked because of disk space issue with docker image building Lari Hotari
  • Re: Pulsar CI blocked because of disk space issue with docker image building Lari Hotari
• [DISCUSS] PIP-305: Customize DNSes to use for Pulsar Client Diego Salvi
  • Re: [DISCUSS] PIP-305: Customize DNSes to use for Pulsar Client Dave Fisher
  • Re: [DISCUSS] PIP-305: Customize DNSes to use for Pulsar Client Zixuan Liu
  • Re: [DISCUSS] PIP-305: Customize DNSes to use for Pulsar Client Zili Chen
• [ANNOUNCE] Released Reactive client for Apache Pulsar, version 0.4.0 Christophe Bornet
• [DISCUSS] PIP-304: Make PublishContext provide the message metadata kecona
  • Re: [DISCUSS] PIP-304: Make PublishContext provide the message metadata Yubiao Feng
  • Re: [DISCUSS] PIP-304: Make PublishContext provide the message metadata kecona
  • Re: [DISCUSS] PIP-304: Make PublishContext provide the message metadata Yubiao Feng
  • Re: [DISCUSS] PIP-304: Make PublishContext provide the message metadata Zixuan Liu
• [VOTE] Pulsar Release 3.1.1 Candidate 1 guo jiwei
  • Re: [VOTE] Pulsar Release 3.1.1 Candidate 1 mattison chao
  • Re: [VOTE] Pulsar Release 3.1.1 Candidate 1 Yunze Xu
  • Re: [VOTE] Pulsar Release 3.1.1 Candidate 1 PengHui Li
  • Re: [VOTE] Pulsar Release 3.1.1 Candidate 1 guo jiwei
• Pulsar Flaky test report 2023-09-24 to 2023-10-01 for PR builds in CI Lari Hotari
• [GitHub] [pulsar-connectors] dependabot[bot] opened a new pull request, #7: Bump org.apache.avro:avro from 1.8.1 to 1.11.3 in /pulsar-io/flume via GitHub
• [VOTE] PIP-302 Introduce refreshAsync API for TableView Xiangying Meng
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView Zike Yang
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView PengHui Li
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView guo jiwei
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView Yubiao Feng
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView Baodi Shi
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView Dezhi Liu
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView 太上玄元道君
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView Yunze Xu
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView mattison chao
  • Re: [VOTE] PIP-302 Introduce refreshAsync API for TableView Xiangying Meng
• [VOTE] Reactive Java client for Apache Pulsar 0.4.0 Candidate 1 Christophe Bornet
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.4.0 Candidate 1 Lari Hotari
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.4.0 Candidate 1 Enrico Olivelli
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.4.0 Candidate 1 Enrico Olivelli

• Earlier messages
• Later messages