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

Denys Kuzmenko updated HIVE-30231:
----------------------------------
    Description: 
Since HIVE-29244, MetastoreLock puts the Iceberg catalog name on the HMS lock. 
Hive names the HiveCatalog of a table without 'iceberg.catalog' 
default_iceberg, while the table lives in theHMS default catalog (hive). So 
Hive's commit locks don't conflict with other writers of the table: Impala, 
Spark, and Hive's own external locks.                                           
 

Fix: that HiveCatalog takes the name of the HMS default catalog 
(metastore.catalog.default).

  was:  - MetastoreLock: the HMS lock and its lookup use the HMS catalog the 
table is read from, not the Iceberg catalog name, so a catalog named other than 
its HMS catalog (the default_iceberg fallback, 'iceberg.catalog'='foo') 
conflicts with every writer of the table


> Lock Iceberg tables in their HMS catalog
> ----------------------------------------
>
>                 Key: HIVE-30231
>                 URL: https://issues.apache.org/jira/browse/HIVE-30231
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Denys Kuzmenko
>            Priority: Major
>
> Since HIVE-29244, MetastoreLock puts the Iceberg catalog name on the HMS 
> lock. Hive names the HiveCatalog of a table without 'iceberg.catalog' 
> default_iceberg, while the table lives in theHMS default catalog (hive). So 
> Hive's commit locks don't conflict with other writers of the table: Impala, 
> Spark, and Hive's own external locks.                                         
>    
> Fix: that HiveCatalog takes the name of the HMS default catalog 
> (metastore.catalog.default).



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to