phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swaroopa Kadam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5251) Avoid taking explicit lock by using AtomicReference in PhoenixAccessController class
Date Fri, 26 Apr 2019 16:34:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827107#comment-16827107
] 

Swaroopa Kadam commented on PHOENIX-5251:
-----------------------------------------

[~gjacoby] has reviewed and approved the PR. Can one of you please help me commit it? [~ckulkarni]
[~abhishek.chouhan] Thank you. 

> 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
>         Attachments: PHOENIX-5251.4.x-HBase-1.3.v1.patch
>
>          Time Spent: 0.5h
>  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)

Mime
View raw message