You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Lian (JIRA)" <ji...@apache.org> on 2015/08/20 12:44:45 UTC

[jira] [Resolved] (SPARK-10092) Multi-DB support follow up

     [ https://issues.apache.org/jira/browse/SPARK-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cheng Lian resolved SPARK-10092.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0

Issue resolved by pull request 8336
[https://github.com/apache/spark/pull/8336]

> Multi-DB support follow up
> --------------------------
>
>                 Key: SPARK-10092
>                 URL: https://issues.apache.org/jira/browse/SPARK-10092
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Yin Huai
>            Assignee: Yin Huai
>            Priority: Blocker
>             Fix For: 1.5.0
>
>
> Seems we need a follow-up work for our multi-db support. Here are issues we need to address.
> 1. saveAsTable always save the table in the folder of the current database
> 2. HiveContext's refrshTable and analyze do not dbName.tableName.
> 3. It will be good to use TableIdentifier in CreateTableUsing, CreateTableUsingAsSelect, CreateTempTableUsing, CreateTempTableUsingAsSelect, CreateMetastoreDataSource, and CreateMetastoreDataSourceAsSelect, instead of using string representation (actually, in several places we have already parsed the string and get the TableIdentifier). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org