Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/5247#issuecomment-92551194
You are correct, thanks for clarifying. Query planning was not the right
phrase, but really my point was that ideally the logic in DataFrame would
handle only ensuring commands are executed eagerly. Hopefully this can be as
simple as matching on `Command` and making sure `executedCommand` is evaluated.
(However this would require refactoring to make sure that every operation
implements the `Command` trait)
I like your second point, but I'd make one change. Lets not put it in the
optimizer since that feels a little weird to me (its not really an
optimization). Instead, in the query planner lets go directly from
`RunnableCommand` to `LocalTableScan` What do you think?
---
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]
