You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vihang Karajgaonkar (JIRA)" <ji...@apache.org> on 2018/08/24 19:36:00 UTC
[jira] [Updated] (HIVE-20258) Should Syncronize getInstance in
ReplChangeManager
[ https://issues.apache.org/jira/browse/HIVE-20258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vihang Karajgaonkar updated HIVE-20258:
---------------------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
4.0.0
Status: Resolved (was: Patch Available)
Patch merged in master and branch-3. Thanks for your contribution [~belugabehr]
> Should Syncronize getInstance in ReplChangeManager
> --------------------------------------------------
>
> Key: HIVE-20258
> URL: https://issues.apache.org/jira/browse/HIVE-20258
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 3.0.0, 4.0.0
> Reporter: BELUGA BEHR
> Assignee: BELUGA BEHR
> Priority: Minor
> Fix For: 4.0.0, 3.2.0
>
> Attachments: HIVE-20258.1.patch
>
>
> {code:java}
> public static ReplChangeManager getInstance(Configuration conf) throws MetaException {
> if (instance == null) {
> instance = new ReplChangeManager(conf);
> }
> return instance;
> }
> {code}
> This method needs to be synchronized or two different threads may see a 'null' value and each create their own manager.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)