Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/248#issuecomment-39388592
You are right that this does not include the change for standardizing the
`sql` function for the Scala SQLContext (though for Java we should be doing the
right thing). I did not want to clutter this PR up with a bunch of spurious
changes to testing code. There is a JIRA tracking this so we don't forget, and
I do not anticipate any issues getting it in for 1.0
Regarding the naming, I had the same though as you after initially typing
out `hiveql`. We could provide both and just make one an alias for the other.
I don't feel too strongly here...
---
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.
---
