[
https://issues.apache.org/jira/browse/PHOENIX-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827389#comment-16827389
]
Hudson commented on PHOENIX-5251:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-4.x-HBase-1.4 #129 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.4/129/])
PHOENIX-5251: Avoid taking explicit lock by using AtomicReference in (gjacoby:
rev f89c91989ac68f9a0e16f599da7239a9d5b6ca0c)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/PhoenixAccessController.java
> Avoid taking explicit lock by using AtomicReference in
> PhoenixAccessController class
> ------------------------------------------------------------------------------------
>
> Key: PHOENIX-5251
> URL: https://issues.apache.org/jira/browse/PHOENIX-5251
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Swaroopa Kadam
> Assignee: Swaroopa Kadam
> Priority: Minor
> Fix For: 4.15.0, 5.1
>
> Attachments: PHOENIX-5251.4.x-HBase-1.3.v1.patch,
> PHOENIX-5251.master.v1.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> By [~elserj] on PHOENIX-5070
> If we want to avoid taking an explicit lock, what about using AtomicReference
> instead? Can we spin out another Jira issue to fix that?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
