Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/10541#issuecomment-168384367
@liancheng this looks cool!
I was wondering why we are bound to SQL? Is this because of Hive? I was
thinking of the following, we could also store the logical plan's json
representation. This should alot easier to (de)serialize. Could we store that
in the Hive metadata store?
Another idea I was having. If a view is defined in HQL, we could also store
that in some way with the query execution. This saves us a
serialization/deserialization trip, and allows the user to recognize his own
query.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
