Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/9399#issuecomment-153008498
@chenghao-intel Thanks for the comment. That's a good point and I didn't
consider this situation when writing this PR. However, fortunately we don't
even try to push down predicates that reference any partition columns (see
[here][1]). In general, when implementing a data source, developers shouldn't
worry about partitioning. A `HadoopFsRelation` data source is only responsible
for returning data within a single partition, the query planner does the rest
including partition pruning. So I think this is fine?
[1]:
https://github.com/apache/spark/blob/ea4a3e7d06dd4a0f669460513b27469c468214fb/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSourceStrategy.scala#L73
---
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]
