[jira] [Updated] (IMPALA-6900) Invalidate metadata operation is ignored at a coordinator if catalog is empty
[
https://issues.apache.org/jira/browse/IMPALA-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltán Borók-Nagy updated IMPALA-6900:
--
Target Version: Impala 3.2.0, Impala 2.13.0 (was: Impala 2.13.0, Impala
3.1.0)
> Invalidate metadata operation is ignored at a coordinator if catalog is empty
> -
>
> Key: IMPALA-6900
> URL: https://issues.apache.org/jira/browse/IMPALA-6900
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
>Affects Versions: Impala 3.0, Impala 2.12.0
>Reporter: Dimitris Tsirogiannis
>Assignee: Vuk Ercegovac
>Priority: Blocker
>
> The following workflow may cause an impalad that issued an invalidate
> metadata to falsely consider that the effect of that operation has taken
> effect, thus causing subsequent queries to fail due to unresolved references
> to tables or databases.
> Steps to reproduce:
> # Start an impala cluster connecting to an empty HMS (no databases).
> # Create a database "db" in HMS outside of Impala (e.g. using Hive).
> # Run INVALIDATE METADATA through Impala.
> # Run "use db" statement in Impala.
>
> The while condition in the code snippet below is cause the
> WaitForMinCatalogUpdate function to prematurely return even though INVALIDATE
> METADATA has not taken effect:
> {code:java}
> void ImpalaServer::WaitForMinCatalogUpdate(..) {
> ...
> VLOG_QUERY << "Waiting for minimum catalog object version: "
><< min_req_catalog_object_version << " current version: "
><< min_catalog_object_version;
> while (catalog_update_info_.min_catalog_object_version <
> min_req_catalog_object_version && catalog_update_info_.catalog_service_id ==
> catalog_service_id) {
>catalog_version_update_cv_.Wait(unique_lock);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-6900) Invalidate metadata operation is ignored at a coordinator if catalog is empty
[
https://issues.apache.org/jira/browse/IMPALA-6900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brown updated IMPALA-6900:
--
Priority: Blocker (was: Major)
> Invalidate metadata operation is ignored at a coordinator if catalog is empty
> -
>
> Key: IMPALA-6900
> URL: https://issues.apache.org/jira/browse/IMPALA-6900
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
>Affects Versions: Impala 3.0, Impala 2.12.0
>Reporter: Dimitris Tsirogiannis
>Assignee: Vuk Ercegovac
>Priority: Blocker
>
> The following workflow may cause an impalad that issued an invalidate
> metadata to falsely consider that the effect of that operation has taken
> effect, thus causing subsequent queries to fail due to unresolved references
> to tables or databases.
> Steps to reproduce:
> # Start an impala cluster connecting to an empty HMS (no databases).
> # Create a database "db" in HMS outside of Impala (e.g. using Hive).
> # Run INVALIDATE METADATA through Impala.
> # Run "use db" statement in Impala.
>
> The while condition in the code snippet below is cause the
> WaitForMinCatalogUpdate function to prematurely return even though INVALIDATE
> METADATA has not taken effect:
> {code:java}
> void ImpalaServer::WaitForMinCatalogUpdate(..) {
> ...
> VLOG_QUERY << "Waiting for minimum catalog object version: "
><< min_req_catalog_object_version << " current version: "
><< min_catalog_object_version;
> while (catalog_update_info_.min_catalog_object_version <
> min_req_catalog_object_version && catalog_update_info_.catalog_service_id ==
> catalog_service_id) {
>catalog_version_update_cv_.Wait(unique_lock);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
