[rocketmq-apis] branch main updated: Remove Publishing#compress_body_threshold (#53)

[li...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

lizhanhui pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/rocketmq-apis.git


The following commit(s) were added to refs/heads/main by this push:
     new 9ca8c91  Remove Publishing#compress_body_threshold (#53)
9ca8c91 is described below

commit 9ca8c91aa7e16b224a75eb972e0ee4a96f008bb9
Author: Aaron Ai <ya...@alibaba-inc.com>
AuthorDate: Mon Jul 11 10:56:46 2022 +0800

    Remove Publishing#compress_body_threshold (#53)
---
 apache/rocketmq/v2/service.proto | 11 ++---------
 1 file changed, 2 insertions(+), 9 deletions(-)

diff --git a/apache/rocketmq/v2/service.proto b/apache/rocketmq/v2/service.proto
index 7a81355..9aac010 100644
--- a/apache/rocketmq/v2/service.proto
+++ b/apache/rocketmq/v2/service.proto
@@ -195,21 +195,14 @@ message Publishing {
   // List of topics to which messages will publish to.
   repeated Resource topics = 1;
 
-  // Publishing settings below here are from server, it is essential for
-  // server to push.
-  //
-  // Body of message will be deflated if its size in bytes exceeds the
-  // threshold.
-  int32 compress_body_threshold = 2;
-
   // If the message body size exceeds `max_body_size`, broker servers would
   // reject the request. As a result, it is advisable that Producer performs
   // client-side check validation.
-  int32 max_body_size = 3;
+  int32 max_body_size = 2;
 
   // When `validate_message_type` flag set `false`, no need to validate message's type
   // with messageQueue's `accept_message_types` before publising.
-  bool validate_message_type = 4;
+  bool validate_message_type = 3;
 }
 
 message Subscription {