Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-49386103
@yhuai I agree with you we should make a clear boundary between
`HiveTableScan` and `TableReader`, but I am not sure if it's a good idea to
create multiple `HiveTableScan` classes instead of one. Routing to different
table scan operators may requires exposing more details in the `SparkPlanner`,
which sits inside of the `HiveTableScan` currently.
Perhaps making multiple `TableReader` is more reasonable, for example,
`TableReader`, `PartitionReader`, `MemoryTableReader` etc.
---
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.
---
