You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I send messages I always get 0 in batchIndex component of MessageID in the result of sendAsync method. Here is a unit test that reproduce the issue:
…in a batch
*Motivation*
Fixesapache#1455.
Pulsar uses a callback chain for completing the list of callbacks for a batch. However the callback chain doesn't reference the message instance for completing the callback.
so when callback chain is triggered, it always uses the first message id to complete the chain of callbacks.
*Changes*
Introduce a field to keep message instance in the callback chain. So when the chain is invoked, each callback can use the right message instance to complete the callback.
Added an integration test to ensure it works correctly.
…in a batch (#2099)
*Motivation*
Fixes#1455.
Pulsar uses a callback chain for completing the list of callbacks for a batch. However the callback chain doesn't reference the message instance for completing the callback.
so when callback chain is triggered, it always uses the first message id to complete the chain of callbacks.
*Changes*
Introduce a field to keep message instance in the callback chain. So when the chain is invoked, each callback can use the right message instance to complete the callback.
Added an integration test to ensure it works correctly.
When I send messages I always get 0 in batchIndex component of MessageID in the result of sendAsync method. Here is a unit test that reproduce the issue:
Actual output is
Expected output is
version: 1.22.0-incubating
The text was updated successfully, but these errors were encountered: