Adjust high-water mark on final valid partition and drop other partitions when DELETE removes rows from the end of a table in key order.

There is a possible edgecase where the end of a ColumnStore table is deleted... ie,

/* "customer" Table loaded in "custkey" order */

DELETE FROM customer

WHERE custkey > 1000;

Which may leave the end of the table with a series of rows marked as deleted. There could also be partitions at the end of the table that contain only rows marked for deletion.

Could ColumnStore recover this space automatically in the case of deletes in key order as described?