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
Current implementation losses messages, because SolaceTask#commit() method in reality doesn't have guarantee that all messages from the previous poll() call committed. This is explicitly highlighted in kafka-connect-api 3.6.1
"This method is invoked periodically when offsets are committed for this source task. Note that the offsets being committed won't necessarily correspond to the latest offsets returned by this source task via poll()."
Expected Behavior
Ack only really committed messages
Steps to Reproduce
Problem scenario:
Connect calls poll() which returns, let's say 100 record
Connect calls commit(), after partial message publishing 30
a. Current implementation acks all 100
Restart connect and 70 msgs will be lost
Solace Broker version
No response
Solace API
No response
Solace API version
No response
The text was updated successfully, but these errors were encountered:
Bug Description
Current implementation losses messages, because
SolaceTask#commit()
method in reality doesn't have guarantee that all messages from the previouspoll()
call committed. This is explicitly highlighted in kafka-connect-api 3.6.1"This method is invoked periodically when offsets are committed for this source task. Note that the offsets being committed won't necessarily correspond to the latest offsets returned by this source task via poll()."
Expected Behavior
Ack only really committed messages
Steps to Reproduce
Problem scenario:
poll()
which returns, let's say 100 recordcommit()
, after partial message publishing 30a. Current implementation acks all 100
Solace Broker version
No response
Solace API
No response
Solace API version
No response
The text was updated successfully, but these errors were encountered: