[GitHub] [spark] rdblue commented on pull request #31475: [SPARK-34360][SQL] Support table truncation by v2 Table Catalogs

rdblue commented on pull request #31475: URL: https://github.com/apache/spark/pull/31475#issuecomment-776119870 @MaxGekk, thanks. Then let's work on updating this to fit more cleanly with the design of v2 catalogs and tables. This should be a `Table` interface, not an extension to

[GitHub] [spark] rdblue commented on pull request #31475: [SPARK-34360][SQL] Support table truncation by v2 Table Catalogs

rdblue commented on pull request #31475: URL: https://github.com/apache/spark/pull/31475#issuecomment-775490751 @MaxGekk, can you share the use case that you have for this? You mentioned truncation-specific optimizations. I think working with concrete use cases is usually a good idea. If

[GitHub] [spark] rdblue commented on pull request #31475: [SPARK-34360][SQL] Support table truncation by v2 Table Catalogs

rdblue commented on pull request #31475: URL: https://github.com/apache/spark/pull/31475#issuecomment-775318833 @MaxGekk, why is this necessary instead of deleting from the table or overwriting everything with no new records? I don't see a good reason to do this, especially at the catalog