hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohit Sabharwal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-16016) Use same PersistenceManager for metadata and notification
Date Fri, 24 Feb 2017 17:13:44 GMT

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

Mohit Sabharwal updated HIVE-16016:
-----------------------------------
    Resolution: Duplicate
        Status: Resolved  (was: Patch Available)

Marking this as duplicate of HIVE-15766. 

[~vgumashta], it'd be great to commit that patch, because it's a critical fix.  Fixed the
failing tests in this patch and moved those over to HIVE-15305., appreciate if you could take
a look at it as well. Thank you!

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

Mime
View raw message