Github user tigerquoll commented on the issue: https://github.com/apache/spark/pull/21308 @rdblue when you say "you don't think the API proposed here needs to support a first-class partition concept", are you referring to the "DeleteSupport" Interface, or to DataSourceV2 in general? If you are referring to DeleteSupport, then do you have the same objections to a separate "DropPartition"/"AddPartition" interface? If you mean that you don't think DataSourceV2 requires supporting partitions as a first-class concept, then how are users of spark supposed to perform operations like 1. adding, 2. altering, 3. removing, and 4. listing partitions on those data-sources that are represented by particular instances of DatasourceV2?
--- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org