zhoulii opened a new issue, #9419: URL: https://github.com/apache/paimon/issues/9419
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Paimon version 2.0 ### Compute Engine flink ### Minimal reproduce step 1. Create a table with row tracking and data evolution enabled. 2. Insert data and create a Global Index on a column. 3. Drop the indexed column. 4. Call drop_global_index for the removed column. 5. The procedure fails because the column no longer exists, while the Global Index remains referenced by the index manifest. ### What doesn't meet your expectations? Dropping a column succeeds even when it is referenced by live Global Index files. Afterward, drop_global_index cannot resolve the removed column to its field ID, leaving the index impossible to remove through the public procedure. Schema changes that drop, rename, or change the type of an indexed column should be rejected and instruct the user to drop the complete Global Index first. This is consistent with the existing protection in `SchemaManager#assertNotUpdatingPrimaryKeyIndexColumn` . ### Anything else? _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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
