dev  

Messages by Thread

• • 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
• Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system Heesung Sohn
  • Re: [DISCUSS] PIP-264: Enhanced OTel-based metric system Dave Fisher
• 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
  • Re: [VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout Apurva Telang
  • Re: [VOTE] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout xiangying meng
• Release Pulsar C++ Client 3.6.0 Baodi Shi
  • Re: Release Pulsar C++ Client 3.6.0 Zike Yang
• [DISCUSS] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout Yubiao Feng
  • Re: [DISCUSS] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout xiangying meng
  • Re: [DISCUSS] PIP-375 Expose the Admin client configs: readTimeout, requestTimeout, and connectionTimeout Lari Hotari
• [DISCUSS] Cherry-pick PIP-359 Support custom message listener executor for specific subscription xiangying meng
  • Re: [DISCUSS] Cherry-pick PIP-359 Support custom message listener executor for specific subscription Yubiao Feng
  • Re: [DISCUSS] Cherry-pick PIP-359 Support custom message listener executor for specific subscription xiangying meng
  • Re: [DISCUSS] Cherry-pick PIP-359 Support custom message listener executor for specific subscription xiangying meng
• [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication Yubiao Feng
  • Re: [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication Lari Hotari
  • Re: [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication Yubiao Feng
  • Re: [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication Lari Hotari
  • Re: [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication Yubiao Feng
  • Re: [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication Lari Hotari
  • Re: [DISCUSS] Cherry-pick PIP-370 configurable remote topic creation in geo-replication Yubiao Feng
• [DISCUSS] Replace default NONE_KEY in Key_Shared implementation with producer name and producer sequence number Philipp D
  • Re: [DISCUSS] Replace default NONE_KEY in Key_Shared implementation with producer name and producer sequence number Lari Hotari
  • RE: Re: [DISCUSS] Replace default NONE_KEY in Key_Shared implementation with producer name and producer sequence number Philipp Dolif
• [VOTE] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before Yubiao Feng
  • Re: [VOTE] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before Tao Jiuming
  • Re: [VOTE] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before Baodi Shi
  • Re: [VOTE] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before guo jiwei
  • Re: [VOTE] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before 丛搏
• Apache Pulsar Release Policy and Supported Release Versions Lari Hotari
• Ldap integration Haydar Urdoğan
  • Re: Ldap integration Lari Hotari
• [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before Yubiao Feng
  • Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before Tao Jiuming
  • Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before Ran Gao
  • Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before xiangying meng
  • Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before Yubiao Feng
  • Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before xiangying meng
  • Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before Yubiao Feng
  • Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before xiangying meng
  • Re: [DISCUSS] PIP-373: Add a topic's system prop that indicates whether users have published TXN messages in before xiangying meng
• Important Reminders to Apache Pulsar committers for PR Merging and Release Management Lari Hotari
  • Re: Important Reminders to Apache Pulsar committers for PR Merging and Release Management Lari Hotari
• [PR] [WIP] Initial Setup: Apache Pulsar Contributor Repository Structure [pulsar-java-contrib] via GitHub
  • Re: [PR] [WIP] Initial Setup: Apache Pulsar Contributor Repository Structure [pulsar-java-contrib] via GitHub
  • [PR] [WIP] Initial Setup: Apache Pulsar Contributor Repository Structure [pulsar-java-contrib] via GitHub
  • Re: [PR] [WIP] Initial Setup: Apache Pulsar Contributor Repository Structure [pulsar-java-contrib] via GitHub
  • Re: [PR] [WIP] Initial Setup: Apache Pulsar Contributor Repository Structure [pulsar-java-contrib] via GitHub
• [DISCUSS] Delete unused util class ConcurrentSortedLongPairSet. thetumbled
• [ANNOUNCE] Released Reactive client for Apache Pulsar, version 0.5.7 Chris Bono
• [VOTE] Reactive Java client for Apache Pulsar 0.5.7 Candidate 1 Chris Bono
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.7 Candidate 1 Lari Hotari
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.7 Candidate 1 PengHui Li
  • Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.7 Candidate 1 guo jiwei
• [DISCUSS] PIP-371 Support to specify message listeners in TableView constructor Heesung Sohn
• Re: [PR] [fix] [meta] Oxia metadta store: Convert error to MetadataStoreException if operation failed [pulsar] Dave Fisher
  • Re: [PR] [fix] [meta] Oxia metadta store: Convert error to MetadataStoreException if operation failed [pulsar] Lari Hotari
  • Re: [PR] [fix] [meta] Oxia metadta store: Convert error to MetadataStoreException if operation failed [pulsar] Yunze Xu
• [VOTE] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation Yubiao Feng
  • Re: [VOTE] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation Hang Chen
  • Re: [VOTE] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation PengHui Li
  • Re: [VOTE] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation guo jiwei
  • Re: [VOTE] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation Lari Hotari
  • Re: [VOTE] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation Yubiao Feng
  • Re: [VOTE] PIP-370: An optional flag: disable the replicators to automatically trigger topic creation PengHui Li
• [VOTE] PIP-369: Flag based selective unload on changing ns-isolation-policy Anshul Singh
  • Re: [VOTE] PIP-369: Flag based selective unload on changing ns-isolation-policy Lari Hotari
  • Re: [VOTE] PIP-369: Flag based selective unload on changing ns-isolation-policy Zike Yang
  • Re: [VOTE] PIP-369: Flag based selective unload on changing ns-isolation-policy guo jiwei
  • Re: [VOTE] PIP-369: Flag based selective unload on changing ns-isolation-policy Anshul Singh
• [ANNOUNCE] Apache Pulsar Go Client 0.13.1 released Zike Yang
• Pulsar 4.0 LTS release timeline Lari Hotari
  • Re: Pulsar 4.0 LTS release timeline Lari Hotari
  • Re: Pulsar 4.0 LTS release timeline Lari Hotari
  • Re: Pulsar 4.0 LTS release timeline Lari Hotari
  • Re: Pulsar 4.0 LTS release timeline Yike Xiao
• [DISCUSS] PIP-371 Support for request-reply model that implements RPC calls SiNan Liu
  • Re: [DISCUSS] PIP-371 Support for request-reply model that implements RPC calls Lari Hotari
  • Re: [DISCUSS] PIP-371 Support for request-reply model that implements RPC calls SiNan Liu
  • Re: [DISCUSS] PIP-371 Support for request-reply model that implements RPC calls SiNan Liu
  • Re: [DISCUSS] PIP-371 Support for request-reply model that implements RPC calls naresh

• Earlier messages
• Later messages