Hi Ruguo, When we were doing this feature it was decided that we will keep it clean and assume that the user will do a read, modify, write. This will ensure that the user can preserve the current values if the intent is to do so.
Thanks. Ravi. > On Jan 6, 2022, at 5:03 AM, Ruguo Yu <jiang7chengz...@163.com> wrote: > > [ External sender. Exercise caution. ] > > Hi Pulsar Community, > Currently, the resource group has four rates, including publishRateInMsgs, > publishRateInBytes, dispatchRateInMsgs and dispatchRateInBytes, but other > rates if previously set or updated will be invalid when we update part rates, > which does not conform to the semantics of the `update` and makes it easy for > users to generate confuse. > > > The purposr of PR[0] is to truly implement the semantics of the `update` to > ensure that the other rates remain the original value during an update > operation. > > > > Obviously, this is a behavior change and it is necessary to let everyone > know, please point out if you have other questions. > > > > Thanks, > > Ruguo Yu > > > > [0] https://github.com/apache/pulsar/pull/13543 >
