[
https://issues.apache.org/jira/browse/HIVE-17022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075030#comment-16075030
]
Mohit Sabharwal commented on HIVE-17022:
----------------------------------------
For a table will large number of partitions, it will indeed print lot of log
statements. But only
applicable under debug mode, when you are debugging and could use this info.
For a complex query involving many write entities, it is hard to tell what lock
is being
taken for what entity otherwise.
Earlier, we had these statements as INFO, which we changed to DEBUG in
HIVE-12966
to avoid noise.
We already have the debug statement for ZooKeeperHiveLockManager, but did not
print the actual lock mode in that statement, so I added that to this patch.
For EmbeddedLockManager, which is useful when debugging locally, we had no
debug statements
whatsoever, so I added that to this patch.
> 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)
