[
https://issues.apache.org/jira/browse/SPARK-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Li updated SPARK-20024:
----------------------------
Description:
SessionCatalog API setCurrentDatabase does not set the current database of the
underlying ExternalCatalog. Thus, weird errors could come in the test suites
after we call reset. 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 always use the current database value
we managed, unless some of code paths skip it. Thus, we fix it in the test-only
function reset().
was:
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.
> 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 after we call reset. 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 always use the current database
> value we managed, unless some of code paths skip it. Thus, we fix it in the
> test-only function reset().
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
