You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Michael Smith (Jira)" <ji...@apache.org> on 2025/07/18 00:04:00 UTC

[jira] [Work started] (IMPALA-14073) test_local_catalog_ddls_with_invalidate_metadata_sync_ddl is flaky after IMPALA-13631

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

Work on IMPALA-14073 started by Michael Smith.
----------------------------------------------
> test_local_catalog_ddls_with_invalidate_metadata_sync_ddl is flaky after IMPALA-13631
> -------------------------------------------------------------------------------------
>
>                 Key: IMPALA-14073
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14073
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog, Test
>    Affects Versions: Impala 5.0.0
>            Reporter: Riza Suminto
>            Assignee: Michael Smith
>            Priority: Major
>              Labels: broken-build
>
> IMPALA-13631 change alterTableOrViewRename to not hold catalog version lock while making HMS RPC.
> It adds back-and-forth ALTER TABLE RENAME testcase into test_local_catalog_ddls_with_invalidate_metadata_sync_ddl, which make it flaky for causing DDL occasionally not finding the target table after concurrent RENAME-INVALIDATE-REFRESH.
> We need to understand what happen and how to make the test deterministic.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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