Github user concretevitamin commented on the pull request:
https://github.com/apache/spark/pull/948#issuecomment-45026360
Removing duplication is definitely a good thing. The other benefit is that
it seems more natural to me to push such DDL/command processing logic into
QueryExecution, instead of putting them into two thin entry methods (`sql` and
`hql`).
I am super new to Spark SQL so bear with me if this is silly -- what is the
reason we don't do this as well for `InsertIntoHiveTable` and
`InsertIntoParquetTable`?
---
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.
---
