[
https://issues.apache.org/jira/browse/SPARK-8105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639083#comment-14639083
]
Cheolsoo Park commented on SPARK-8105:
--------------------------------------
[~yhuai], what's the plan for this? SPARK-8107 seems to suggest adding a new
function to SqlContext {{table("dbName", "tblName")}}, but the patch isn't
committed while the jira is closed.
Why can we simply support HiveContext {{table("dbName.tblName")}} since it is
backward compatible I believe? Any concern with this approach?
> sqlContext.table("databaseName.tableName") broke with SPARK-6908
> ----------------------------------------------------------------
>
> Key: SPARK-8105
> URL: https://issues.apache.org/jira/browse/SPARK-8105
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 1.4.0
> Environment: Spark with Hive
> Reporter: Doug Balog
> Priority: Critical
>
> Since the introduction of Dataframes in Spark 1.3.0 and prior to SPARK-6908
> landing into master, a user could get a DataFrame to a Hive table using
> `sqlContext.table("databaseName.tableName")`
> Since SPARK-6908, the user now receives a NoSuchTableException.
> This amounts to a change in non experimental sqlContext.table() api and will
> require user code to be modified to work properly with 1.4.0.
> The only viable work around I could find is
> `sqlContext.sql("select * from databseName.tableName")`
> which seems like a hack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
