luoyuxia commented on issue #1260: URL: https://github.com/apache/fluss/issues/1260#issuecomment-3034775576
@Baibaiwuguo Thanks for reporting. But I'm still not sure what's the right behavior for lake table in `create table if not exists` statement. Actually, currently it's by design to always throw table exists in lake explicitly to tell users to drop table in lake before create a new table. The reason is that 1. user create a lake table, one in fluss, one in lake 2. write some data into the tables, and the data also is tiered into lake 3. user drop the table, table drop in fluss, but not drop in lake 4. user fire `create table if not exists` statement. It'll try to create the table in lake. If we don't throw table already in lake exception, it'll skip create the table in lake and create the new table in fluss. While the table in empty in fluss, the table in lake is not, which looks weird. So, it throws the exception explicitly instead of skip the exception. About the reason why table not drop in lake in step 3, please see [here](https://github.com/asf-transfer/fluss/issues/846#issuecomment-2889388255). -- 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]
