[GitHub] [pulsar-dotpulsar] sijie commented on issue #61: Single batched message metadata is not read correctly

2020-10-13 Thread GitBox
sijie commented on issue #61: URL: https://github.com/apache/pulsar-dotpulsar/issues/61#issuecomment-707871069 @blankensteiner Correct. You should check if that field is set or not. This is an automated message from the Apach

[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #61: Single batched message metadata is not read correctly

2020-10-13 Thread GitBox
blankensteiner commented on issue #61: URL: https://github.com/apache/pulsar-dotpulsar/issues/61#issuecomment-707869166 @sijie Using proto2. The generator gives me a "bool ShouldSerializeNumMessagesInBatch()" which returns false if the field is null. Guess I can use that. ---

[GitHub] [pulsar-dotpulsar] sijie commented on issue #61: Single batched message metadata is not read correctly

2020-10-13 Thread GitBox
sijie commented on issue #61: URL: https://github.com/apache/pulsar-dotpulsar/issues/61#issuecomment-707855292 @blankensteiner Are you generating the code using proto2 or proto3? The proto file is written in proto2 syntax. So the generated code should have a method to check if a field is s

Pulsar Community Weekly Update] 2020-09-26 ~ 2020-10-09

2020-10-13 Thread Huanli Meng
Dear Pulsar enthusiast, This is the Pulsar community weekly update for 2020-09-26 ~ 2020-10-09, with updates on Pulsar client, broker, Pulsar Admin, Pulsar Functions, Pulsar schema, and so on. This Pulsar community weekly update is also available at https://streamnative.io/weekly/2020/2020-10/202

[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #61: Single batched message metadata is not read correctly

2020-10-13 Thread GitBox
blankensteiner commented on issue #61: URL: https://github.com/apache/pulsar-dotpulsar/issues/61#issuecomment-707784365 @dionjansen Since they have added a default value of '1' in the proto-file, we will never see num_messages_in_batch as being null. @sijie can the default value of '1' b

[GitHub] [pulsar-dotpulsar] dionjansen commented on issue #61: Single batched message metadata is not read correctly

2020-10-13 Thread GitBox
dionjansen commented on issue #61: URL: https://github.com/apache/pulsar-dotpulsar/issues/61#issuecomment-707765720 @blankensteiner I verified with @sijie and he confirmed my assumption, so the following should apply: * `num_messages_in_batch` is set (to any number) the payload is a

[GitHub] [pulsar-manager] Red-Night-Aria opened a new issue #344: Tenant disappered in dashborad if a namespace under this tenant is failed to getTopicsList

2020-10-13 Thread GitBox
Red-Night-Aria opened a new issue #344: URL: https://github.com/apache/pulsar-manager/issues/344 **To Reproduce** 1. There is a pulsar instance contains two cluster c1 and c2, a tenant t1 with allowed_cluster=[c1, c2]. Create namespace t1/ns1 in cluster c1, t1/ns2 in cluster c2. 2. C

Slack digest for #dev - 2020-10-13

2020-10-13 Thread Apache Pulsar Slack
2020-10-13 04:17:57 UTC - Sijie Guo: You should use `num_messages_in_batch` in the metadata 2020-10-13 06:52:19 UTC - dionjansen: @Sijie Guo so is the following correct? The metadata property `num_messages_in_batch` is optional so if  `num_messages_in_batch` is set (whether to 1 or a number