Re: Inquiry about Possible Deadlock Problem in Hive 4.1.0 with Insert overwrite Query on Iceberg Table

Hi, I have submitted the bug-fix PR we discussed. It seems that the GitHub workflow needs approval. Is there anything else I need to do? Regards, Owen 2025년 3월 27일 (목) 오후 6:11, Denys Kuzmenko 님이 작성: > Great, thank you! >

Re: Inquiry about Possible Deadlock Problem in Hive 4.1.0 with Insert overwrite Query on Iceberg Table

Yes, I'd like to submit a bug-fix PR. Thank you for your proposal. 2025년 3월 27일 목요일, Denys Kuzmenko 님이 작성: > Sure, go ahead. > > To confirm, you'd like to submit a bug-fix PR as well, right? I started > looking into it, and I think a quick fix might look like: > > private HiveLock lockObject(or

Re: Inquiry about Possible Deadlock Problem in Hive 4.1.0 with Insert overwrite Query on Iceberg Table

Dear Denys, Thank you for your confirmation. Im considering reporting a bug on JIRA and creating a PR. Please advise. Regards, Owen 2025년 3월 27일 (목) 오후 4:52, Denys Kuzmenko 님이 작성: > Note: HiveIcebergMetaHook acquires an HMS lock regardless of > `iceberg.engine.hive.lock-enabled` config - needs

Re: Inquiry about Possible Deadlock Problem in Hive 4.1.0 with Insert overwrite Query on Iceberg Table

Thank you for your response. I understand that even if Hive and Trino use the same Hive Metastore as a Catalog, additional implementation in TrinoCatalog is necessary to ensure data correctness. To clarify, the deadlock issue I am referring to is not a situation where the IOW lock cannot be obtain

Re: Inquiry about Possible Deadlock Problem in Hive 4.1.0 with Insert overwrite Query on Iceberg Table

id table, not for Iceberg table. > The lock mechanism in Iceberg table is controlled by HMS Catalog or other > Iceberg Catalog(JDBC catalog, etc). So > 'org.apache.hadoop.hive.ql.lockmgr.DbTxnManager' should not be used in your > case(insert overwrite iceberg table). > >

Inquiry about Possible Deadlock Problem in Hive 4.1.0 with Insert overwrite Query on Iceberg Table

I am experiencing a possible deadlock issue while working with Hive version 4.1.0. The issue occurs when an 'insert overwrite' query is executed on an Iceberg table. Specifically, I have found that if the 'hive.txn.manager' setting is 'org.apache.hadoop.hive.ql.lockmgr.DbTxnManager', a deadlock see