diff options
author | Michael Armbrust <michael@databricks.com> | 2014-08-03 12:28:29 -0700 |
---|---|---|
committer | Michael Armbrust <michael@databricks.com> | 2014-08-03 12:29:05 -0700 |
commit | c5ed1deba6b3f3e597554a8d0f93f402ae62fab9 (patch) | |
tree | 101bf2d0e0a964901a2299378cf053a38b4095e5 /sbin | |
parent | eaa93555a7f935b00a2f94a7fa50a12e11578bd7 (diff) | |
download | spark-c5ed1deba6b3f3e597554a8d0f93f402ae62fab9.tar.gz spark-c5ed1deba6b3f3e597554a8d0f93f402ae62fab9.tar.bz2 spark-c5ed1deba6b3f3e597554a8d0f93f402ae62fab9.zip |
[SPARK-2784][SQL] Deprecate hql() method in favor of a config option, 'spark.sql.dialect'
Many users have reported being confused by the distinction between the `sql` and `hql` methods. Specifically, many users think that `sql(...)` cannot be used to read hive tables. In this PR I introduce a new configuration option `spark.sql.dialect` that picks which dialect with be used for parsing. For SQLContext this must be set to `sql`. In `HiveContext` it defaults to `hiveql` but can also be set to `sql`.
The `hql` and `hiveql` methods continue to act the same but are now marked as deprecated.
**This is a possibly breaking change for some users unless they set the dialect manually, though this is unlikely.**
For example: `hiveContex.sql("SELECT 1")` will now throw a parsing exception by default.
Author: Michael Armbrust <michael@databricks.com>
Closes #1746 from marmbrus/sqlLanguageConf and squashes the following commits:
ad375cc [Michael Armbrust] Merge remote-tracking branch 'apache/master' into sqlLanguageConf
20c43f8 [Michael Armbrust] override function instead of just setting the value
7e4ae93 [Michael Armbrust] Deprecate hql() method in favor of a config option, 'spark.sql.dialect'
(cherry picked from commit 236dfac6769016e433b2f6517cda2d308dea74bc)
Signed-off-by: Michael Armbrust <michael@databricks.com>
Diffstat (limited to 'sbin')
0 files changed, 0 insertions, 0 deletions