[
https://issues.apache.org/jira/browse/HIVE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793190#comment-13793190
]
Jason Dere commented on HIVE-5474:
----------------------------------
Still disagree here, since the set is not actually helping here - you could
insert both [EXCLUSIVE, default/test_exec_thrift] and [SHARED,
default/test_exec_thrift] into the set because the two locks wouldn't be
considere equivalent to each other. And we'd have to implement equals() and
hashCode(), for something that isn't actually helping.
Also I think that having a Set here gives the sense that users do not have to
worry about handling duplicates themselves, when in fact they do.
> drop table hangs when concurrency=true
> --------------------------------------
>
> Key: HIVE-5474
> URL: https://issues.apache.org/jira/browse/HIVE-5474
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, Locking
> Reporter: Thejas M Nair
> Assignee: Jason Dere
> Attachments: HIVE-5474.1.patch, HIVE-5474.2.patch
>
>
> This is seen in hive 0.12 branch sequential test run.
> TestThriftHttpCLIService.testExecuteStatement
> https://builds.apache.org/job/Hive-branch-0.12-hadoop1/13/testReport/org.apache.hive.service.cli.thrift/TestThriftHttpCLIService/testExecuteStatement/
> stderr has "FAILED: Error in acquiring locks: Locks on the underlying
> objects cannot be acquired. retry after some time"
--
This message was sent by Atlassian JIRA
(v6.1#6144)
