[
https://issues.apache.org/jira/browse/HIVE-15774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849072#comment-15849072
]
Hive QA commented on HIVE-15774:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12850496/HIVE-15774.2.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), 11022 tests
executed
*Failed tests:*
{noformat}
TestDerbyConnector - did not produce a TEST-*.xml file (likely timed out)
(batchId=235)
org.apache.hadoop.hive.cli.TestEncryptedHDFSCliDriver.testCliDriver[encryption_join_with_different_encryption_keys]
(batchId=159)
org.apache.hadoop.hive.cli.TestPerfCliDriver.testCliDriver[query14]
(batchId=223)
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/3310/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/3310/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-3310/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
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: 12850496 - PreCommit-HIVE-Build
> Ensure DbLockManager backward compatibility for non-ACID resources
> ------------------------------------------------------------------
>
> Key: HIVE-15774
> URL: https://issues.apache.org/jira/browse/HIVE-15774
> Project: Hive
> Issue Type: Improvement
> Components: Hive, Transactions
> Reporter: Wei Zheng
> Assignee: Wei Zheng
> Attachments: HIVE-15774.1.patch, HIVE-15774.2.patch
>
>
> In pre-ACID days, users perform operations such as INSERT with either
> ZooKeeperHiveLockManager or no lock manager at all. If their workflow is
> designed to take advantage of no locking and they take care of the control of
> concurrency, this works well with good performance.
> With ACID, if users enable transactions (i.e. using DbTxnManager &
> DbLockManager), then for all the operations, different types of locks will be
> acquired accordingly by DbLockManager, even for non-ACID resources. This may
> impact the performance of some workflows designed for pre-ACID use cases.
> A viable solution would be to differentiate the locking mode for ACID and
> non-ACID resources, so that DbLockManager will continue its current behavior
> for ACID tables, but will be able to acquire a less strict lock type for
> non-ACID resources, thus avoiding the performance loss for those workflows.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
