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
It shouldn't throw excpetion in the second put although the first deletion delete nothing
Anything else?
In the first put with batch sequence, it delete a non-exist key, no binlog is generated which will cause skipping to append to log, so the currently sequene id is still -1;
In the second put with batch sequence 1, it'll then append to the log, which cause sequene not continuous. So the exception is thrown
No response
Are you willing to submit a PR?
I'm willing to submit a PR!
The text was updated successfully, but these errors were encountered:
First row is going to be merged in #240, first_row is expected to encounter this exception easily and thus this issue comes to a higher priority. Please remember to add some tests to reproduce the exception for first_row in the pull request. @swuferhong
Search before asking
Fluss version
0.5.0
Minimal reproduce step
Add a test in FlussTableITCase
What doesn't meet your expectations?
It shouldn't throw excpetion in the second put although the first deletion delete nothing
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: