[
https://issues.apache.org/jira/browse/HIVE-17420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
anishek updated HIVE-17420:
---------------------------
Description:
when we do the bootstrap dump, the idea is that we take note of the replication
id of a object (table in case of this bug) and then request the table metadata
from the rdbms which is then serialized to _metadata file for the table
containing lastReplicationId + table metadata.
This is to make sure that we only apply events after the event id in _metadata
on the table, which implies that its best to order the call to get
currentReplicationId and tablemetadata retrieval in the event of multiple
concurrent operations happening on the same table along with bootstrap.
> bootstrap - get replid before object dump
> -----------------------------------------
>
> Key: HIVE-17420
> URL: https://issues.apache.org/jira/browse/HIVE-17420
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 3.0.0
> Reporter: anishek
> Assignee: anishek
> Fix For: 3.0.0
>
>
> when we do the bootstrap dump, the idea is that we take note of the
> replication id of a object (table in case of this bug) and then request the
> table metadata from the rdbms which is then serialized to _metadata file for
> the table containing lastReplicationId + table metadata.
> This is to make sure that we only apply events after the event id in
> _metadata on the table, which implies that its best to order the call to get
> currentReplicationId and tablemetadata retrieval in the event of multiple
> concurrent operations happening on the same table along with bootstrap.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
