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

Posted to issues@hive.apache.org by "Mohit Sabharwal (JIRA)" <ji...@apache.org> on 2017/02/23 02:02:44 UTC

[jira] [Updated] (HIVE-16016) Use same PersistenceManager for metadata and notification

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

Mohit Sabharwal updated HIVE-16016:
-----------------------------------
    Status: Patch Available  (was: Open)

> Use same PersistenceManager for metadata and notification
> ---------------------------------------------------------
>
>                 Key: HIVE-16016
>                 URL: https://issues.apache.org/jira/browse/HIVE-16016
>             Project: Hive
>          Issue Type: Bug
>          Components: repl
>            Reporter: Mohit Sabharwal
>            Assignee: Mohit Sabharwal
>         Attachments: HIVE-16016.patch
>
>
> HIVE-13966 added to support for persisting notification in the same JDO transaction as the metadata event. However, the notification is currently added using a different ObjectStore object from the one used to persist the metadata event.  
> The notification is added using the ObjectStore constructed in DbNotificationListener, whereas the metadata event is added via the thread local ObjectStore (i.e. threadLocalMS in HiveMetaStore.HMSHandler).
> As a result, different PersistenceManagers (different transactions) are used to persist notification and metadata events.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)