Github user saucam commented on the pull request:
https://github.com/apache/spark/pull/2841#issuecomment-61052070
yes. In task side metadata strategy, the tasks are spawned first, and each
task will then read the metadata and drop the row groups. So if I am using
yarn, and data is huge (metadata is large) , the memory will be consumed on
the yarn side , but in case of client side metadata strategy, whole of the
metadata will be read before the tasks are spawned, on a single node.
---
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
