platinumhamburg opened a new issue, #1256: URL: https://github.com/apache/fluss/issues/1256
### Search before asking - [x] I searched in the [issues](https://github.com/alibaba/fluss/issues) and found nothing similar. ### Fluss version 0.7.0 (latest release) ### Please describe the bug 🐞 While we have implemented several latch mechanisms (e.g., Java locks) to protect atomicity in short critical sections, we still lack a proper database lock system to ensure ACID properties (specifically atomicity, consistency, and isolation) for DDL transactions. This allows concurrent operations to access intermediate states of DDL 'transactions', violating meta integrity. For example: - RemoteLogDownloader may throw "No such file or directory" exceptions during partition removal - ReplicaManager may throw LogOffsetOutOfRangeException during concurrent reads on deleted partitions Though full ACID support for DDL transactions may be considered in future, we should initially: 1. Fix the exception types thrown in these scenarios 2. Make user code clearly identify and handle such errors ### Solution _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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: issues-unsubscr...@fluss.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
