[
https://issues.apache.org/jira/browse/SPARK-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kuldeep updated SPARK-9333:
---------------------------
Description: `Right now there is `registerTempTable` which registers table
in sql/hive context. Then there is `save` which registers it to hivestore but
materializes the df. Would it make sense to have a mid-path like
`registerTable` which registers to hivestore and points to table in sql context
without materializing it? (was: Right now there is `registerTempTable` which
registers table in sql/hive context. Then there is `save` which registers it to
hivestore but materializes the df. Would it make sense to have a mid-path like
`registerTable` which registers to hivestore and points to table in sql context
without materializing it?)
> JDBC connection to hivethrift server broken on 1.4.1
> ----------------------------------------------------
>
> Key: SPARK-9333
> URL: https://issues.apache.org/jira/browse/SPARK-9333
> Project: Spark
> Issue Type: New Feature
> Components: SQL
> Affects Versions: 1.4.1
> Reporter: Kuldeep
>
> `Right now there is `registerTempTable` which registers table in sql/hive
> context. Then there is `save` which registers it to hivestore but
> materializes the df. Would it make sense to have a mid-path like
> `registerTable` which registers to hivestore and points to table in sql
> context without materializing it?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
