Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14690
> If a user queries such a table with predicates which prune that table's
partitions, we would like to be able to answer that query without consulting
partition metadata which are not involved in the query.
When we read a partitioned hive table, we will retrieve all partition
metadata from hive metastore and load them to driver memory. Yes, it's not so
efficient and may blow up the dirver.
However, it only happens at first read, then these data will be cached. If
you don't load all partition metadata at first read, how are you going to deal
with the cache?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
