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 wrote:
>
Not clear what exactly the concern is (i.e., what "other rates" will become
invalid) on a resource group when a new rate is set.
Among the rates in each direction (dispatch/publish), the semantics are
that throttling will kick in whenever any of the *RateInMsgs and,
*RateInBytes is hit during an ev
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 `
