slfan1989 opened a new pull request, #1339:
URL: https://github.com/apache/paimon-rust/pull/1339

   <!--
   Thank you very much for contributing to Paimon Rust - we are happy that you 
want to help us improve it. To help the community review your contribution in 
the best possible way, please go through the checklist below, which will get 
the contribution into a shape in which it can be best reviewed.
   
   ## Contribution Checklist
   
     - Make sure that the pull request corresponds to a [GitHub 
issue](https://github.com/apache/paimon-rust/issues). Exceptions are made for 
typos in documentation or comments, which need no issue.
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
   
     - Make sure that the change passes the automated tests, i.e., `cargo test` 
passes.
   
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
   
   **(The sections below can be removed for hotfixes or typos)**
   -->
   
   ### Purpose
   
   Linked issue: close #1337 
   
   Fix `DROP TABLE` deleting the wrong table when a statement targets multiple 
Paimon catalogs. For example, `DROP TABLE cat1.default.a, cat2.default.b` could 
delete `cat1.default.b` and leave `cat2.default.b` intact.
   
   ### Brief change log
   
   - Resolve every target's catalog and table identifier before deleting any 
tables.
   - Execute each deletion against its own catalog. If a target references an 
unknown catalog, return an error before deleting any tables.
   
   ### Tests
   
   - Added a regression test that verifies both requested tables are dropped 
and the unrelated same-name table is preserved.
   
   ### API and Format
   
   No.
   
   ### Documentation
   
   No.
   


-- 
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]

Reply via email to