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
I searched in the issues and found nothing similar.
Fluss version
main (development)
Please describe the bug 🐞
When MemoryLogRecordsArrowBuilder try to resetWriterState in case the produceLog request failed and the batch is re-enqueue to send with different write state, we will reset the bytesView to null, this is very dangerous. Because once we set bytesView to null, we won't be able to retrieve the data from arrowWriter while next build, which means data in this batch will be lost. The correct approach is to simply reset the batch header instead of reset the whole batch.
Solution
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:
swuferhong
changed the title
MemoryLogRecordsArrowBuilder resetWriterState will cause can cause batch data loss
MemoryLogRecordsArrowBuilder resetWriterState can cause batch data loss
Feb 7, 2025
Search before asking
Fluss version
main (development)
Please describe the bug 🐞
When MemoryLogRecordsArrowBuilder try to
resetWriterState
in case the produceLog request failed and the batch is re-enqueue to send with different write state, we will reset thebytesView
tonull
, this is very dangerous. Because once we setbytesView
tonull
, we won't be able to retrieve the data fromarrowWriter
while next build, which means data in this batch will be lost. The correct approach is to simply reset the batch header instead of reset the whole batch.Solution
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: