[
https://issues.apache.org/jira/browse/HIVE-17022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075017#comment-16075017
]
Naveen Gangam commented on HIVE-17022:
--------------------------------------
[~mohitsabharwal] I am a bit worried that the following code generates a lot of
noise in the logs, given the frequency at which lock() method is called and the
number of locks that can be held at any particular point in time. Have you seen
otherwise?
{code}
for (HiveLockObj obj : objs) {
LOG.debug("Acquiring lock for {} with mode {}", obj.getObj().getName(),
obj.getMode());
}
{code}
Thanks
> Add mode in lock debug statements
> ---------------------------------
>
> Key: HIVE-17022
> URL: https://issues.apache.org/jira/browse/HIVE-17022
> Project: Hive
> Issue Type: Improvement
> Components: Locking
> Reporter: Mohit Sabharwal
> Assignee: Mohit Sabharwal
> Priority: Trivial
> Attachments: HIVE-17022.patch
>
>
> Currently, lock debug statements print IMPLICIT/EXPLICIT as lock mode,
> whereas SHARED/EXCLUSIVE/SEMI_SHARED are more useful
> when debugging.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
