dev  

Messages by Thread

• • 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
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Lari Hotari
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Yubiao Feng
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Lari Hotari
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Yubiao Feng
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Lari Hotari
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Yubiao Feng
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Lari Hotari
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Lin Lin
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Yubiao Feng
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Lin Lin
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Yubiao Feng
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar Lari Hotari
  • Re: [Discussion] PR #24423 Handling Overloaded Netty Channels in Apache Pulsar yubiao
• [ANNOUNCE] New Committer: Mingze Han Haiting Jiang
  • Re: [ANNOUNCE] New Committer: Mingze Han lushiji(apache)
  • Re: [ANNOUNCE] New Committer: Mingze Han houxiaoyu
  • Re: [ANNOUNCE] New Committer: Mingze Han Zixuan Liu
  • Re: [ANNOUNCE] New Committer: Mingze Han Wenbing Shen
  • Re: [ANNOUNCE] New Committer: Mingze Han Aloys Zhang
  • Re: [ANNOUNCE] New Committer: Mingze Han Gavin gao
  • Re: [ANNOUNCE] New Committer: Mingze Han Rafael Sousa
• [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service ran leon
  • Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service Yunze Xu
  • Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service Yubiao Feng
  • Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service Tao Jiuming
  • Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service Zixuan Liu
  • Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service Dezhi Liu
  • [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service Ran Gao
  • Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service Yunze Xu
  • Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service Zike Yang
  • Re: [VOTE] PIP-420: Provide ability for Pulsar clients to integrate with third-party schema registry service Yunze Xu
• [VOTE] PIP-429: Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing Yunze Xu
  • Re: [VOTE] PIP-429: Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing Yubiao Feng
  • Re: [VOTE] PIP-429: Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing guo jiwei
  • Re: [VOTE] PIP-429: Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing Tao Jiuming
  • Re: [VOTE] PIP-429: Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing Zike Yang
  • Re: [VOTE] PIP-429: Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing PengHui Li
  • Re: [VOTE] PIP-429: Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing Yunze Xu
• [DISCUSS] PIP-433: Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas Yubiao Feng
• [DISCUSS] PIP-432: Add isEncrypted field to EncryptionContext PengHui Li
• [ANNOUNCE] Apache Pulsar Node.js client 1.14.0 released Baodi Shi
• [VOTE] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats PengHui Li
  • Re: [VOTE] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats Zike Yang
  • Re: [VOTE] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats guo jiwei
  • Re: [VOTE] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats Yubiao Feng
  • Re: [VOTE] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats Jia Zhai
  • Re: [VOTE] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats Haiting Jiang
  • Re: [VOTE] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats PengHui Li
  • Re: [VOTE] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats Yike Xiao
• [VOTE] Pulsar Node.js Client Release 1.14.0 Candidate 2 Baodi Shi
  • Re: [VOTE] Pulsar Node.js Client Release 1.14.0 Candidate 2 Zike Yang
  • Re: [VOTE] Pulsar Node.js Client Release 1.14.0 Candidate 2 Yunze Xu
  • Re: [VOTE] Pulsar Node.js Client Release 1.14.0 Candidate 2 Baodi Shi
  • Re: [VOTE] Pulsar Node.js Client Release 1.14.0 Candidate 2 Baodi Shi
• [DISCUSS] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats PengHui Li
  • Re: [DISCUSS] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats Haiting Jiang
  • Re: [DISCUSS] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats Enrico Olivelli
  • Re: [DISCUSS] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats PengHui Li
  • Re: [DISCUSS] PIP-431: Add Creation and Last Publish Timestamps to Topic Stats Yike Xiao
• [VOTE] Pulsar Client C++ Release 3.7.2 Candidate 1 Yunze Xu
  • Re: [VOTE] Pulsar Client C++ Release 3.7.2 Candidate 1 Zike Yang
  • Re: [VOTE] Pulsar Client C++ Release 3.7.2 Candidate 1 Baodi Shi
  • Re: [VOTE] Pulsar Client C++ Release 3.7.2 Candidate 1 Yunze Xu
• [VOTE]PIP-425: Support connecting with next available endpoint for multi-endpoint serviceUrls Aurora Twinkle
  • Re: [VOTE]PIP-425: Support connecting with next available endpoint for multi-endpoint serviceUrls xiangying meng
  • Re: [VOTE]PIP-425: Support connecting with next available endpoint for multi-endpoint serviceUrls lushiji(apache)
  • Re: [VOTE]PIP-425: Support connecting with next available endpoint for multi-endpoint serviceUrls guo jiwei
  • Re: [VOTE]PIP-425: Support connecting with next available endpoint for multi-endpoint serviceUrls Zixuan Liu
  • Re: [VOTE]PIP-425: Support connecting with next available endpoint for multi-endpoint serviceUrls Aurora Twinkle
• [DISCUSS] Release Pulsar Node.js client v1.14.0 Baodi Shi
• [DISCUSS] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Lari Hotari
  • Re: [DISCUSS] PIP-430: Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count Tao Jiuming
• [DISCUSS] Release C++ Client 3.7.2 for RPM/DEB packages regression since 3.6.0 Yunze Xu
• [VOTE] PIP-428: Change TopicPoliciesService interface to fix consistency issues Lari Hotari
  • Re: [VOTE] PIP-428: Change TopicPoliciesService interface to fix consistency issues Yunze Xu
  • Re: [VOTE] PIP-428: Change TopicPoliciesService interface to fix consistency issues Tao Jiuming
  • Re: [VOTE] PIP-428: Change TopicPoliciesService interface to fix consistency issues Lari Hotari
  • Re: [VOTE] PIP-428: Change TopicPoliciesService interface to fix consistency issues Lari Hotari
• PIP-429: Client-Side Computation of Last Compacted Message ID Yunze Xu
  • Re: PIP-429: Client-Side Computation of Last Compacted Message ID Yunze Xu
  • Re: PIP-429: Client-Side Computation of Last Compacted Message ID Zike Yang
• [VOTE] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config PengHui Li
  • Re: [VOTE] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config Lari Hotari
  • Re: [VOTE] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config Tao Jiuming
  • Re: [VOTE] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config guo jiwei
  • Re: [VOTE] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config Yubiao Feng
  • Re: [VOTE] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config PengHui Li
• ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3. Lari Hotari
  • Re: ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3. Zixuan Liu
  • Re: ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3. Zixuan Liu
  • Re: ExtensibleLoadManager tests are broken in branch-3.0 and branch-3.3. Lari Hotari
• [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Matteo Merli
  • Re: [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Lari Hotari
  • Re: [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Zixuan Liu
  • Re: [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Tao Jiuming
  • Re: [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Yunze Xu
  • Re: [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK PengHui Li
  • Re: [VOTE] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Yubiao Feng
• [DISCUSS] Urgent: Proposed Revert of PR #23611 PengHui Li
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 Matteo Merli
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 WenZhi Feng
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 WenZhi Feng
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 PengHui Li
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 WenZhi Feng
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 Matteo Merli
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 PengHui Li
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 WenZhi Feng
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 PengHui Li
  • Re: [DISCUSS] Urgent: Proposed Revert of PR #23611 PengHui Li
• [DISCUSS] PIP-428: Change TopicPoliciesService interface to fix consistency issues Lari Hotari
  • Re: [DISCUSS] PIP-428: Change TopicPoliciesService interface to fix consistency issues Lari Hotari
• [DISCUSS] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config PengHui Li
  • Re: [DISCUSS] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config guo jiwei
  • Re: [DISCUSS] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config Yubiao Feng
  • Re: [DISCUSS] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config Haiting Jiang
  • Re: [DISCUSS] PIP-427: Align 'set-persistence' default for mark-delete rate with broker config Lari Hotari
• End of Windows Server 2019 runner support Andrew Wetmore
• [DISCUSS]PIP-425: Support connecting with next available endpoint for multi-endpoint serviceUrls Aurora Twinkle
• [ANNOUNCE] Released Reactive client for Apache Pulsar, version 0.7.0 Chris Bono
• [VOTE] Reactive Java client for Apache Pulsar 0.7.0 Candidate 1 Chris Bono
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.7.0 Candidate 1 Chris Bono
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.7.0 Candidate 1 Lari Hotari
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.7.0 Candidate 1 xiangying meng
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.7.0 Candidate 1 Chris Bono
• [ANNOUNCE] Apache Pulsar C# Client DotPulsar 4.3.0 released David Jensen
• [DISCUSS]PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking for Exclusive and Failover Subscriptions 蔡敏健
  • Re: [DISCUSS]PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking for Exclusive and Failover Subscriptions PengHui Li
  • Re: [DISCUSS]PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking for Exclusive and Failover Subscriptions 蔡敏健
  • Re: [DISCUSS]PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking for Exclusive and Failover Subscriptions Zixuan Liu
  • Re: [DISCUSS]PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking for Exclusive and Failover Subscriptions PengHui Li
  • Re: [DISCUSS]PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking for Exclusive and Failover Subscriptions 蔡敏健
  • Re: [DISCUSS]PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking for Exclusive and Failover Subscriptions PengHui Li
• [RESULT][VOTE] Apache Pulsar DotPulsar 4.3.0 released David Jensen
• [VOTE] PIP-418: Determine the behaviors for components that rely on BookKeeper when BookKeeper is not used Yunze Xu
  • Re: [VOTE] PIP-418: Determine the behaviors for components that rely on BookKeeper when BookKeeper is not used Yunze Xu
  • Re: [VOTE] PIP-418: Determine the behaviors for components that rely on BookKeeper when BookKeeper is not used PengHui Li
• [VOTE] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies Yubiao Feng
  • Re: [VOTE] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies PengHui Li
  • Re: [VOTE] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies Baodi Shi
  • Re: [VOTE] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies Yubiao Feng
• New PMC Member: Chris Bono Lari Hotari
  • Re: New PMC Member: Chris Bono Max Xu
  • Re: New PMC Member: Chris Bono Zhangjian He
  • Re: New PMC Member: Chris Bono Haiting Jiang
  • Re: New PMC Member: Chris Bono Yike Xiao
  • Re: New PMC Member: Chris Bono Zixuan Liu
• New PMC member: Xiangying Meng Lari Hotari
  • Re: New PMC member: Xiangying Meng lushiji(apache)
  • Re: New PMC member: Xiangying Meng SiNan Liu
  • Re: New PMC member: Xiangying Meng Tao Jiuming
  • Re: New PMC member: Xiangying Meng Zhangjian He
  • Re: New PMC member: Xiangying Meng Jie crossover
  • Re: New PMC member: Xiangying Meng Max Xu
  • Re: New PMC member: Xiangying Meng Haiting Jiang
  • Re: New PMC member: Xiangying Meng Yike Xiao
  • Re: New PMC member: Xiangying Meng Zixuan Liu
• [VOTE] DotPulsar Release 4.3.0-rc.1 David Jensen
  • Re: [VOTE] DotPulsar Release 4.3.0-rc.1 Lari Hotari
  • Re: [VOTE] DotPulsar Release 4.3.0-rc.1 Daniel Blankensteiner
  • Re: [VOTE] DotPulsar Release 4.3.0-rc.1 David Jensen
• [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages SiNan Liu
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages Lari Hotari
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages SiNan Liu
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages Lari Hotari
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages SiNan Liu
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages Lari Hotari
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages SiNan Liu
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages xiangying meng
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages SiNan Liu
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages SiNan Liu
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages xiangying meng
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages SiNan Liu
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages PengHui Li
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages SiNan Liu
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages PengHui Li
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages SiNan Liu
  • Re: [DISCUSS] PIP-423: Add Support for Cancelling Individual Delayed Messages PengHui Li
• [DISCUSS] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies Yubiao Feng
  • Re: [DISCUSS] PIP-422 Support global topic-level policy: replicated clusters and new API to delete topic-level policies Zixuan Liu
• [ANNOUNCE] Apache Pulsar Node.js client 1.13.2 released Baodi Shi
• Broker entry cache refactoring - PR #24363 review requested Lari Hotari
• [DISCUSS] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Matteo Merli
  • Re: [DISCUSS] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Lari Hotari
  • Re: [DISCUSS] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Tao Jiuming
  • Re: [DISCUSS] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK PengHui Li
  • Re: [DISCUSS] PIP-421: Require Java 17 as the minimum for Pulsar Java client SDK Haiting Jiang

• Earlier messages
• Later messages