hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Vary (JIRA)" <>
Subject [jira] [Commented] (HIVE-20797) Print Number of Locks Acquired
Date Sat, 01 Dec 2018 07:07:00 GMT


Peter Vary commented on HIVE-20797:

[~belugabehr]: I had to look up {{MoreObjects}}, to find out what it does. In the current
situation it is basically used for null check. Maybe the owner of the code wrote unit tests,
maybe they really covered the situation above, but for a check this trivial in my opinion
it is better/less error prone if the code is readable at first glance, so I would vote for
the version where we do not use an extra class for this simple check.

> Print Number of Locks Acquired
> ------------------------------
>                 Key: HIVE-20797
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2, Locking
>    Affects Versions: 4.0.0
>            Reporter: BELUGA BEHR
>            Assignee: BELUGA BEHR
>            Priority: Minor
>              Labels: newbie, noob
>         Attachments: HIVE-20797.1.patch
> The number of locks acquired by a query can greatly influence the performance and stability
of the system, especially for ZK locks.  Please add INFO level logging with the number of
locks each query obtains.
> Log here:
> {quote}
> A list of acquired locks will be stored in the org.apache.hadoop.hive.ql.Context object
and can be retrieved via org.apache.hadoop.hive.ql.Context#getHiveLocks.
> {quote}

This message was sent by Atlassian JIRA

View raw message