hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (HIVE-14770) too many locks acquired?
Date Wed, 28 Jul 2021 14:14:03 GMT

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

Eugene Koifman reassigned HIVE-14770:
-------------------------------------

    Assignee:     (was: Eugene Koifman)

> too many locks acquired?
> ------------------------
>
>                 Key: HIVE-14770
>                 URL: https://issues.apache.org/jira/browse/HIVE-14770
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>            Reporter: Eugene Koifman
>            Priority: Major
>
> need to verify
> UpdateDeleteSemanticAnalyzer.reparseAndSuperAnalyze() has
> {noformat}
>     if (inputIsPartitioned(inputs)) {
>       // In order to avoid locking the entire write table we need to replace the single
WriteEntity
>       // with a WriteEntity for each partition
>       outputs.clear();
>       for (ReadEntity input : inputs) {
>         if (input.getTyp() == Entity.Type.PARTITION) {
>           WriteEntity.WriteType writeType = deleting() ? WriteEntity.WriteType.DELETE
:
>               WriteEntity.WriteType.UPDATE;
>           outputs.add(new WriteEntity(input.getPartition(), writeType));
>         }
>       }
>     } else {
> {noformat}
> but this seems to assume that each partition read is also written
> shouldn't this check isWritten()?  see HIVE-11848



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message