Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/21308
@tigerquoll, I'm not debating whether we should or shouldn't expose
partitions here. In general, I'm undecided. I don't think that the API proposed
here needs to support a first-class partition concept for tables, largely
because partitions aren't currently exposed in the v2 API.
The issue you linked to, SPARK-22389, exposes Spark's view of partitioning
-- as in `repartition(col)` -- which is to say data rows are grouped together.
That's not the same thing as partitions in a data source that can exist
independent of data rows.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
