Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/5141#issuecomment-86507585
@marmbrus @saucam Confirmed that 1.2 actually works in this case. So this
is a regression. Merging to master and 1.3. Thanks for working on this and the
comments!
And @saucam, yes, reading from all Parquet data files isn't a scalable way.
The reason why this is necessary is that, while creating a `ParquetRelation2`,
we need to figure out the full schema of this relation before any queries are
executed. Thus there are no information about "referred partitions". But I
totally agree that this needs furthur optimization to make it more scalable.
(BTW, do you really have Parquet tables consist of *millions* of partitions?...)
---
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]
