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 Thu, 02 May 2019 18:07:00 GMT

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

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

[~elserj] This one doesn't use volatile keyword. It was an improvement on top of the previous
fix. 

> 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.0
>
>         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)

Mime
View raw message