Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/17240
@nsyca Thanks. I know there could be such cases when size is also useful.
However, usually big tables (fact table) have more columns than small tables,
so cardinality and size is positively correlated, i.e. relation with larger
cardinality also has larger size.
Again, I agree with you in some cases this could be violated. But we also
need to consider from implementation aspect. Do column pruning after reordering
makes more sense and makes the code much conciser.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
