[ https://issues.apache.org/jira/browse/HIVE-20890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125893#comment-17125893 ]
Hive QA commented on HIVE-20890: -------------------------------- Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/13004804/HIVE-20890.3.patch {color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified. {color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 17100 tests executed *Failed tests:* {noformat} TestStatsReplicationScenariosACID - did not produce a TEST-*.xml file (likely timed out) (batchId=185) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[explain_locks] (batchId=74) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[stats_part2] (batchId=49) {noformat} Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/22743/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/22743/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-22743/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Executing org.apache.hive.ptest.execution.PrepPhase Executing org.apache.hive.ptest.execution.YetusPhase Executing org.apache.hive.ptest.execution.ExecutionPhase Executing org.apache.hive.ptest.execution.ReportingPhase Tests exited with: TestsFailedException: 3 tests failed {noformat} This message is automatically generated. ATTACHMENT ID: 13004804 - PreCommit-HIVE-Build > ACID: Allow whole table ReadLocks to skip all partition locks > ------------------------------------------------------------- > > Key: HIVE-20890 > URL: https://issues.apache.org/jira/browse/HIVE-20890 > Project: Hive > Issue Type: Improvement > Components: Transactions > Reporter: Gopal Vijayaraghavan > Assignee: Denys Kuzmenko > Priority: Major > Attachments: HIVE-20890.1.patch, HIVE-20890.2.patch, > HIVE-20890.3.patch > > > HIVE-19369 proposes adding a EXCL_WRITE lock which does not wait for any > SHARED_READ locks for read operations - in the presence of that lock, the > insert overwrite no longer takes an exclusive lock. > The only exclusive operation will be a schema change or drop table, which > should take an exclusive lock on the entire table directly. > {code} > explain locks select * from tpcds_bin_partitioned_orc_1000.store_sales where > ss_sold_date_sk=2452626 > +----------------------------------------------------+ > | Explain | > +----------------------------------------------------+ > | LOCK INFORMATION: | > | tpcds_bin_partitioned_orc_1000.store_sales -> SHARED_READ | > | tpcds_bin_partitioned_orc_1000.store_sales.ss_sold_date_sk=2452626 -> > SHARED_READ | > +----------------------------------------------------+ > {code} > So the per-partition SHARED_READ locks are no longer necessary, if the lock > builder already includes the table-wide SHARED_READ locks. > The removal of entire partitions is the only part which needs to be taken > care of within this semantics as row-removal instead of directory removal > (i.e "drop partition" -> "truncate partition" and have the truncation trigger > a whole directory cleaner, so that the partition disappears when there are 0 > rows left). -- This message was sent by Atlassian Jira (v8.3.4#803005)