Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
ghx-label-8
Description
Currently, when doing create/drop table/db from catalogD, catalogOpExecutor (via Impala Shell) and metastore server (via HS2) acquires lock on their own respective lock objects to prevent concurrent create/drop operations in HMS. But that does not prevent these concurrent operations across CatalogOpExecutor and Metastore server. For example currently a user can perform create/drop HMS operation from Impala shell and catalog metastore server concurrently which is not the desired behavior
Attachments
Issue Links
- is related to
-
IMPALA-10837 Add tests for IMPALA-10817
- Open