Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/4506#issuecomment-73997207
The deferred resolving table should be harmless, and since most of the DF
API are yielding the unresolved logical plans(can I say that?), I think we'd
better keep it the same for `def table(name)`, .
Ideally, eagerly resolving the table should produce the the result in unit
test, but seems not, probably something wrong somewhere, I will keep
investigating that.
---
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]
