sundapeng opened a new pull request, #9119: URL: https://github.com/apache/paimon/pull/9119
### Purpose `TRUNCATE TABLE`, `TRUNCATE TABLE PARTITION` and `ALTER TABLE ... RENAME TO PARTITION` all refuse a format table with catalog-managed partitions. These tests pin that they refuse *without moving anything*: a registration pointing at a directory that is gone, or data under a spec nobody registered, would both be worse than the refusal. The one behaviour change is an error message. `Only FileStoreTable supports partitions` is reached by a table that has partitions and lists them through this very trait, which sends the reader looking for the wrong problem. It now names the operations that do manage those partitions. The remaining probes cover `ADD`/`DROP PARTITION` idempotence, prefix `DROP`, partial specs in `SHOW PARTITIONS`, case-insensitive partition column names, null partition values and empty string partition values — all of which already behaved this way and are now held in place. ### Tests New: `CatalogManagedPartitionEdgeParityTest`, `CatalogManagedPartitionDdlParityTest`. The probes are mapped from Spark's own `TruncateTableSuiteBase`, `AlterTableRenamePartitionSuiteBase`, `AlterTableAddPartitionSuiteBase`, `AlterTableDropPartitionSuiteBase` and `ShowPartitionsSuiteBase`, so the reference for "what should happen" is Spark's rather than ours. One finding recorded rather than worked around: `SHOW PARTITIONS` prints a null partition value as `dt=null` rather than the default partition name. That is Spark's own `ShowPartitionsExec` with a v2 table, and a native Paimon partitioned table prints the same thing — so a test pins where the behaviour comes from instead of special-casing it here. ### API and Format No public API change. No format change. ### Documentation None needed; the only user-visible change is an error message. -- 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]
