You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2017/03/20 04:33:42 UTC

[jira] [Commented] (SPARK-20024) SessionCatalog API setCurrentDatabase need to set the current database of ExternalCatalog

    [ https://issues.apache.org/jira/browse/SPARK-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932152#comment-15932152 ] 

Apache Spark commented on SPARK-20024:
--------------------------------------

User 'gatorsmile' has created a pull request for this issue:
https://github.com/apache/spark/pull/17354

> SessionCatalog API setCurrentDatabase need to set the current database of ExternalCatalog
> -----------------------------------------------------------------------------------------
>
>                 Key: SPARK-20024
>                 URL: https://issues.apache.org/jira/browse/SPARK-20024
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.0.2, 2.1.0, 2.2.0
>            Reporter: Xiao Li
>            Assignee: Xiao Li
>
> SessionCatalog API setCurrentDatabase does not set the current database of the underlying ExternalCatalog. Thus, weird errors could come in the test suites. We need to fix it.
> So far, have not found the direct impact in the other code paths because we expect all the SessionCatalog APIs should use the current database value we managed, unless some of code paths skip it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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