Jackeyzhe commented on issue #3483: URL: https://github.com/apache/fluss/issues/3483#issuecomment-4762300421
@luoyuxia Thanks, I agree with your analysis. To avoid mixing the confirmed race with a still-unclear second path, I can scope this PR to case (1) only: reject `commitLakeTableSnapshot` when the target table id no longer exists in coordinator context or has already been queued for deletion. For case (2), I agree the ordinary commit path should be protected by the tableId check in `TieringCommitOperator.commitWriteResults`. The missing-snapshot recovery path you pointed out is the only possible path I can identify as well, but since it depends on the old lake snapshot still being visible after drop + recreate, I think it is better to leave that as a separate follow-up discussion / defensive validation rather than blocking this PR on it. @binary-signal How do you think about this ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
