dev  

Messages by Thread

• • RE: Re: [DISCUSS] PIP-386: Add resetIncludeHead in CommandSubscribe for startMessageIdInclusive implementation Jiawen Wang
  • RE: Re: [DISCUSS] PIP-386: Add resetIncludeHead in CommandSubscribe for startMessageIdInclusive implementation Jiawen Wang
  • RE: RE: Re: [DISCUSS] PIP-386: Add resetIncludeHead in CommandSubscribe for startMessageIdInclusive implementation Jiawen Wang
• [DISCUSS] PIP-380: Support setting up specific namespaces to skipping the load-shedding Kai Wang
• [DISCUSS] Revert the PR 23395, which broke the behavior of schemas Yubiao Feng
  • Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas Baodi Shi
  • Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas Yubiao Feng
  • Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas Lari Hotari
  • Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas Rajan Dhabalia
  • Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas Yubiao Feng
  • Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas Lari Hotari
  • Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas SiNan Liu
  • Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas Rajan Dhabalia
  • Re: [DISCUSS] Revert the PR 23395, which broke the behavior of schemas Yubiao Feng
• [DISCUSS] dropping pulsar-io hdfs2 support due to addressing CVE-2024-25638 Lari Hotari
• [VOTE] Release Apache Pulsar Helm Chart 3.6.0 based on 3.6.0-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar Helm Chart 3.6.0 based on 3.6.0-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar Helm Chart 3.6.0 based on 3.6.0-candidate-1 David Jensen
  • Re: [VOTE] Release Apache Pulsar Helm Chart 3.6.0 based on 3.6.0-candidate-1 Nicolò Boschi
  • Re: [VOTE] Release Apache Pulsar Helm Chart 3.6.0 based on 3.6.0-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar Helm Chart 3.6.0 based on 3.6.0-candidate-1 Lari Hotari
• [ANNOUNCE] Apache Pulsar 3.3.2 released with important security fix for CVE-2024-47561 Lari Hotari
• [ANNOUNCE] Apache Pulsar 3.0.7 released with important security fix for CVE-2024-47561 Lari Hotari
• [VOTE] Release Apache Pulsar 3.3.2 based on 3.3.2-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 3.3.2 based on 3.3.2-candidate-1 PengHui Li
  • Re: [VOTE] Release Apache Pulsar 3.3.2 based on 3.3.2-candidate-1 Matteo Merli
  • Re: [VOTE] Release Apache Pulsar 3.3.2 based on 3.3.2-candidate-1 Michael Marshall
  • Re: [VOTE] Release Apache Pulsar 3.3.2 based on 3.3.2-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 3.3.2 based on 3.3.2-candidate-1 Lari Hotari
• [VOTE] Release Apache Pulsar 3.0.7 based on 3.0.7-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 3.0.7 based on 3.0.7-candidate-1 PengHui Li
  • Re: [VOTE] Release Apache Pulsar 3.0.7 based on 3.0.7-candidate-1 Matteo Merli
  • Re: [VOTE] Release Apache Pulsar 3.0.7 based on 3.0.7-candidate-1 Michael Marshall
  • Re: [VOTE] Release Apache Pulsar 3.0.7 based on 3.0.7-candidate-1 Lari Hotari
  • Re: [VOTE] Release Apache Pulsar 3.0.7 based on 3.0.7-candidate-1 Lari Hotari
• [DISCUSS] PIP-385 Add rate limit semantics to pulsar protocol and Java client Girish Sharma
  • Re: [DISCUSS] PIP-385 Add rate limit semantics to pulsar protocol and Java client Lari Hotari
  • Re: [DISCUSS] PIP-385 Add rate limit semantics to pulsar protocol and Java client Rajan Dhabalia
  • Re: [DISCUSS] PIP-385 Add rate limit semantics to pulsar protocol and Java client Girish Sharma
  • Re: [DISCUSS] PIP-385 Add rate limit semantics to pulsar protocol and Java client Girish Sharma
  • Re: [DISCUSS] PIP-385 Add rate limit semantics to pulsar protocol and Java client Lari Hotari
  • Re: [DISCUSS] PIP-385 Add rate limit semantics to pulsar protocol and Java client Girish Sharma
  • Re: [DISCUSS] PIP-385 Add rate limit semantics to pulsar protocol and Java client Rajan Dhabalia
  • Re: [DISCUSS] PIP-385 Add rate limit semantics to pulsar protocol and Java client Girish Sharma
• [DISCUSS] Expediting Pulsar releases 3.0.7 and 3.3.2 due to critical RCE vulnerability in Avro Java SDK <1.11.4, CVE-2024-47561 Lari Hotari
  • Re: [DISCUSS] Expediting Pulsar releases 3.0.7 and 3.3.2 due to critical RCE vulnerability in Avro Java SDK <1.11.4, CVE-2024-47561 Lari Hotari
  • Re: [DISCUSS] Expediting Pulsar releases 3.0.7 and 3.3.2 due to critical RCE vulnerability in Avro Java SDK <1.11.4, CVE-2024-47561 Enrico Olivelli
  • Re: [DISCUSS] Expediting Pulsar releases 3.0.7 and 3.3.2 due to critical RCE vulnerability in Avro Java SDK <1.11.4, CVE-2024-47561 Lari Hotari
  • Re: [DISCUSS] Expediting Pulsar releases 3.0.7 and 3.3.2 due to critical RCE vulnerability in Avro Java SDK <1.11.4, CVE-2024-47561 Michael Marshall
• [DISCUSS] Core Implementation for PIP-379: Key_Shared Draining Hashes for Improved Message Ordering - Reviews Needed Lari Hotari
  • Re: [DISCUSS] Core Implementation for PIP-379: Key_Shared Draining Hashes for Improved Message Ordering - Reviews Needed Lari Hotari
  • Re: [DISCUSS] Core Implementation for PIP-379: Key_Shared Draining Hashes for Improved Message Ordering - Reviews Needed Rajan Dhabalia
  • Re: [DISCUSS] Core Implementation for PIP-379: Key_Shared Draining Hashes for Improved Message Ordering - Reviews Needed Lari Hotari
• [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Lari Hotari
  • Re: [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Matteo Merli
  • Re: [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Enrico Olivelli
  • Re: [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Apurva Telang
  • Re: [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Nicolò Boschi
  • Re: [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering ZhangJian He
  • Re: [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Yuri Mizushima
  • Re: [VOTE] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Lari Hotari
• [VOTE] PIP-384: ManagedLedger interface decoupling Lari Hotari
  • Re: [VOTE] PIP-384: ManagedLedger interface decoupling Rajan Dhabalia
  • Re: [VOTE] PIP-384: ManagedLedger interface decoupling Matteo Merli
  • Re: [VOTE] PIP-384: ManagedLedger interface decoupling Enrico Olivelli
  • Re: [VOTE] PIP-384: ManagedLedger interface decoupling PengHui Li
  • Re: [VOTE] PIP-384: ManagedLedger interface decoupling Lari Hotari
• [ANNOUNCE] Apache Pulsar Go Client 0.14.0 released Zike Yang
• [VOTE] PIP-383: Support granting/revoking permissions for multiple topics guo jiwei
  • Re: [VOTE] PIP-383: Support granting/revoking permissions for multiple topics Lari Hotari
  • Re: [VOTE] PIP-383: Support granting/revoking permissions for multiple topics Zike Yang
  • Re: [VOTE] PIP-383: Support granting/revoking permissions for multiple topics PengHui Li
  • Re: [VOTE] PIP-383: Support granting/revoking permissions for multiple topics guo jiwei
• [DISCUSS] Can pass the std tlsconfig to pulsar go client 匡增雄
  • Re: [DISCUSS] Can pass the std tlsconfig to pulsar go client ZhangJian He
  • Re: [DISCUSS] Can pass the std tlsconfig to pulsar go client Lari Hotari
• [DISCUSS] PIP-384: ManagedLedger interface decoupling Lari Hotari
  • Re: [DISCUSS] PIP-384: ManagedLedger interface decoupling Rajan Dhabalia
• Apache Pulsar 4.0.0-preview.1 available for testing - Feedback requested Lari Hotari
  • Re: Apache Pulsar 4.0.0-preview.1 available for testing - Feedback requested Yunze Xu
  • Re: Apache Pulsar 4.0.0-preview.1 available for testing - Feedback requested Lari Hotari
• [DISCUSS] PIP-383: Support granting/revoking permissions for multiple topics guo jiwei
  • Re: [DISCUSS] PIP-383: Support granting/revoking permissions for multiple topics Lari Hotari
  • Re: [DISCUSS] PIP-383: Support granting/revoking permissions for multiple topics Baodi Shi
  • Re: [DISCUSS] PIP-383: Support granting/revoking permissions for multiple topics Lari Hotari
  • Re: [DISCUSS] PIP-383: Support granting/revoking permissions for multiple topics guo jiwei
  • Re: [DISCUSS] PIP-383: Support granting/revoking permissions for multiple topics Yubiao Feng
• [DISCUSS] PIP-382: Add a label named reason for topic_load_failed_total Yubiao Feng
• Reverting some cherry-picks in branch-3.3 and branch-3.0 Lari Hotari
  • Re: Reverting some cherry-picks in branch-3.3 and branch-3.0 Yubiao Feng
  • Re: Reverting some cherry-picks in branch-3.3 and branch-3.0 Andrey Yegorov
  • Re: Reverting some cherry-picks in branch-3.3 and branch-3.0 Lari Hotari
• [VOTE] PIP-381: Handle large PositionInfo state Andrey Yegorov
  • Re: [VOTE] PIP-381: Handle large PositionInfo state Enrico Olivelli
  • Re: [VOTE] PIP-381: Handle large PositionInfo state Lari Hotari
  • Re: [VOTE] PIP-381: Handle large PositionInfo state Apurva Telang
  • Re: [VOTE] PIP-381: Handle large PositionInfo state Andrey Yegorov
  • Re: [VOTE] PIP-381: Handle large PositionInfo state Rajan Dhabalia
• [VOTE] Pulsar Client Go Release 0.14.0 Candidate 1 Zike Yang
  • Re: [VOTE] Pulsar Client Go Release 0.14.0 Candidate 1 Baodi Shi
  • Re: [VOTE] Pulsar Client Go Release 0.14.0 Candidate 1 Yunze Xu
  • Re: [VOTE] Pulsar Client Go Release 0.14.0 Candidate 1 PengHui Li
  • Re: [VOTE] Pulsar Client Go Release 0.14.0 Candidate 1 Zike Yang
• [DISCUSS] BookieRackAffinityMapping revert into sync way to avoid broker lost rack information issue Jianye Fan
• [DISCUSS] PIP-381: Handle large PositionInfo state Andrey Yegorov
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Rajan Dhabalia
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Enrico Olivelli
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Rajan Dhabalia
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Lari Hotari
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state PengHui Li
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Andrey Yegorov
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Heesung Sohn
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Heesung Sohn
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Rajan Dhabalia
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Lari Hotari
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Rajan Dhabalia
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Lari Hotari
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Rajan Dhabalia
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Heesung Sohn
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Lari Hotari
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Rajan Dhabalia
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Heesung Sohn
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Lari Hotari
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Andrey Yegorov
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Andrey Yegorov
  • Re: [DISCUSS] PIP-381: Handle large PositionInfo state Lari Hotari
• Pulsar CI is currently (Sep 19) broken; "CI - System - Pulsar IO" build job fails Lari Hotari
  • Re: Pulsar CI is currently (Sep 19) broken; "CI - System - Pulsar IO" build job fails Lari Hotari
• [VOTE] PIP-378 Add ServiceUnitStateTableView abstraction (ExtensibleLoadMangerImpl only) Heesung Sohn
  • Re: [VOTE] PIP-378 Add ServiceUnitStateTableView abstraction (ExtensibleLoadMangerImpl only) Lari Hotari
  • Re: [VOTE] PIP-378 Add ServiceUnitStateTableView abstraction (ExtensibleLoadMangerImpl only) Yunze Xu
  • Re: [VOTE] PIP-378 Add ServiceUnitStateTableView abstraction (ExtensibleLoadMangerImpl only) PengHui Li
  • Re: [VOTE] PIP-378 Add ServiceUnitStateTableView abstraction (ExtensibleLoadMangerImpl only) Lari Hotari
• [DISCUSS] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Lari Hotari
  • Re: [DISCUSS] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Enrico Olivelli
  • Re: [DISCUSS] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering PengHui Li
  • Re: [DISCUSS] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Lari Hotari
  • Re: [DISCUSS] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Girish Sharma
  • Re: [DISCUSS] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Lari Hotari
  • Re: [DISCUSS] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Apurva Telang
  • Re: [DISCUSS] PIP-379: Key_Shared Draining Hashes for Improved Message Ordering Lari Hotari
• [PR] renamed [pulsar-presto] via GitHub
  • Re: [PR] renamed [pulsar-presto] via GitHub
  • Re: [PR] renamed [pulsar-presto] via GitHub
  • Re: [PR] renamed [pulsar-presto] Dave Fisher
  • Re: [PR] renamed [pulsar-presto] Lari Hotari
  • Re: [PR] renamed [pulsar-presto] Dave Fisher
  • Re: [PR] renamed [pulsar-presto] Lari Hotari
• [ANNOUNCE] Apache Pulsar Node.js client 1.12.0 released Baodi Shi
• [DISCUSS] PIP-378 Add ServiceUnitStateTableView abstraction in ExtensibleLoadMangerImpl Heesung Sohn
  • Re: [DISCUSS] PIP-378 Add ServiceUnitStateTableView abstraction in ExtensibleLoadMangerImpl Heesung Sohn
  • Re: [DISCUSS] PIP-378 Add ServiceUnitStateTableView abstraction in ExtensibleLoadMangerImpl Lari Hotari
• [DISCUSS] Release Pulsar Go Client 0.14.0 Zike Yang
  • Re: [DISCUSS] Release Pulsar Go Client 0.14.0 Baodi Shi
• Re: [DISCUSS] PIP-377: Automatic retry for failed acknowledgements Lari Hotari
• Re: [VOTE] Pulsar Node.js Client Release 1.12.0 Candidate 1 Baodi Shi
  • Re: [VOTE] Pulsar Node.js Client Release 1.12.0 Candidate 1 Yunze Xu
  • Re: [VOTE] Pulsar Node.js Client Release 1.12.0 Candidate 1 Zike Yang
  • Re: [VOTE] Pulsar Node.js Client Release 1.12.0 Candidate 1 Baodi Shi
• [DISCUSS] Reduce PulsarClientException stacktrace to avoid heavy logging impact on broker and client Rajan Dhabalia
• Re: [VOTE] PIP-376 Make topic policies pluggable Lari Hotari
  • Re: [VOTE] PIP-376 Make topic policies pluggable PengHui Li
  • Re: [VOTE] PIP-376 Make topic policies pluggable Zike Yang
• Re: [VOTE] PIP-374: Visibility of messages in receiverQueue for the consumers Baodi Shi
  • Re: [VOTE] PIP-374: Visibility of messages in receiverQueue for the consumers PengHui Li
  • Re: [VOTE] PIP-374: Visibility of messages in receiverQueue for the consumers Cong Zhao
  • Re: [VOTE] PIP-374: Visibility of messages in receiverQueue for the consumers Aloys Zhang
  • Re: [VOTE] PIP-374: Visibility of messages in receiverQueue for the consumers Baodi Shi
• [VOTE] PIP-360 Add admin API to display Schema metadata Rajan Dhabalia
  • [DISCUSS] Revisit PIP voting max time Rajan Dhabalia
  • Re: [DISCUSS] Revisit PIP voting max time Yunze Xu
  • Re: [DISCUSS] Revisit PIP voting max time Dave Fisher
  • Re: [DISCUSS] Revisit PIP voting max time Enrico Olivelli
  • Re: [DISCUSS] Revisit PIP voting max time Rajan Dhabalia
  • Re: [DISCUSS] Revisit PIP voting max time Lari Hotari
  • Re: [DISCUSS] Revisit PIP voting max time Girish Sharma
  • Re: [DISCUSS] Revisit PIP voting max time Lari Hotari
• [DISCUSS] PIP-376 Make topic policies service pluggable Yunze Xu
  • Re: [DISCUSS] PIP-376 Make topic policies service pluggable Enrico Olivelli
  • Re: [DISCUSS] PIP-376 Make topic policies service pluggable PengHui Li
  • Re: [DISCUSS] PIP-376 Make topic policies service pluggable Lari Hotari
• {DISCUSS] PIP-374: Visibility of messages in receiverQueue for the consumers Bhat, Vinay
  • Re: {DISCUSS] PIP-374: Visibility of messages in receiverQueue for the consumers Cong Zhao
  • Re: {DISCUSS] PIP-374: Visibility of messages in receiverQueue for the consumers xiangying meng
• [VOTE] Pulsar Client C++ Release 3.6.0 Candidate 2 Baodi Shi
  • Re: [VOTE] Pulsar Client C++ Release 3.6.0 Candidate 2 Baodi Shi
  • Re: [VOTE] Pulsar Client C++ Release 3.6.0 Candidate 2 Yunze Xu
  • Re: [VOTE] Pulsar Client C++ Release 3.6.0 Candidate 2 Zike Yang
  • Re: [VOTE] Pulsar Client C++ Release 3.6.0 Candidate 2 Baodi Shi
• review needed for PIP-369 changes that are also planned for cherry-picking Lari Hotari
• [VOTE] Pulsar Client C++ Release 3.6.0 Candidate 1 Baodi Shi
  • Re: [VOTE] Pulsar Client C++ Release 3.6.0 Candidate 1 Baodi Shi
  • Re: [VOTE] Pulsar Client C++ Release 3.6.0 Candidate 1 Yunze Xu
  • Re: [VOTE] Pulsar Client C++ Release 3.6.0 Candidate 1 Baodi Shi
• [VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout Yubiao Feng
  • Re: [VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout Jie crossover
  • Re: [VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout ZhangJian He
  • Re: [VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout Baodi Shi
  • Re: [VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout Zixuan Liu
  • Re: [VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout Lari Hotari

• Earlier messages
• Later messages