hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Bapat (JIRA)" <>
Subject [jira] [Updated] (HIVE-20967) Handle alter events when replicate to cluster with hive.strict.managed.tables enabled.
Date Mon, 06 May 2019 10:14:00 GMT


Ashutosh Bapat updated HIVE-20967:
    Attachment: HIVE-20967.03.patch
        Status: Patch Available  (was: In Progress)

Patch with fixes for ptest failures in the previous run.

> Handle alter events when replicate to cluster with hive.strict.managed.tables enabled.
> --------------------------------------------------------------------------------------
>                 Key: HIVE-20967
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>    Affects Versions: 4.0.0
>            Reporter: mahesh kumar behera
>            Assignee: Ashutosh Bapat
>            Priority: Minor
>              Labels: DR, pull-request-available
>         Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, HIVE-20967.03.patch, HIVE-21678.02.patch
>          Time Spent: 20m
>  Remaining Estimate: 0h
> Some of the events from Hive2 may cause conflicts in Hive3 (hive.strict.managed.tables=true)
when applied. So, need to handle them properly.
>  1. Alter table to convert non-acid to acid.
>  - Do not allow this conversion on source of replication if strict.managed is false.
> 2. Alter table or partition that changes the location.
>  - For managed tables at source, the table location shouldn't be changed for the given
non-partitioned table and partition location shouldn't be changed for partitioned table as
alter event doesn't capture the new files list. So, it may cause data inconsistsency. So,
if database is enabled for replication at source, then alter location on managed tables should
be blocked.
>  - For external partitioned tables, if location is changed at source, the the location
should be changed for the table and any partitions which reside within the table location,
but not for the partitions which are not within the table location. (may be we just need the

This message was sent by Atlassian JIRA

View raw message