[jira] [Commented] (IMPALA-11335) WriteId must be requested before taking locks during inserts

["Csaba Ringhofer (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-11335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552836#comment-17552836 ] 

Csaba Ringhofer commented on IMPALA-11335:
------------------------------------------

https://gerrit.cloudera.org/#/c/18583/

> WriteId must be requested before taking locks during inserts
> ------------------------------------------------------------
>
>                 Key: IMPALA-11335
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11335
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog, Frontend
>            Reporter: Csaba Ringhofer
>            Priority: Major
>              Labels: ACID
>             Fix For: Impala 4.2.0
>
>
> It turned out that the writeId as saved to DB by HMS during lock creating for inserts, because this info is used to delete the folders created by aborted/time outed inserts. This seems a bit hacky but makes sense, as during lock creation we express the intention of the transaction for the given table ( https://github.infra.cloudera.com/CDH/hive/blob/4604ca6f1077dd808055539e95e9b9be97cdb312/standalone-metastore/src/main/thrift/hive_metastore.thrift#L1123 ), while this information is express in th other APIs (open_txns, allocate_table_write_ids).
> Currently Impala takes the lock first, which can cause issues during the cleanup of aborted/timeouted inserts. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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