You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Chinmay Kulkarni (Jira)" <ji...@apache.org> on 2019/12/21 00:57:05 UTC

[jira] [Closed] (PHOENIX-5251) Avoid taking explicit lock by using AtomicReference in PhoenixAccessController class

     [ https://issues.apache.org/jira/browse/PHOENIX-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chinmay Kulkarni closed PHOENIX-5251.
-------------------------------------

Bulk closing Jiras for the 4.15.0 release.

> 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
(v8.3.4#803005)