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
Although we record the pkid (as offset) of each message, we cannot subscribe to the topic from spec offset.
And we cannot do the manual ACK on our side, because the message's ACK is tied to client. We cannot do ack from a different client (in WaitCheckpointTask).
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
This issue has been open for 60 days with no activity.
If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.
You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄
Describe the bug
Although we record the
pkid
(as offset) of each message, we cannot subscribe to the topic from spec offset.And we cannot do the manual ACK on our side, because the message's ACK is tied to client. We cannot do ack from a different client (in
WaitCheckpointTask
).Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: