[jira] [Work logged] (HIVE-20967) Handle alter events when replicate to cluster with hive.strict.managed.tables enabled.

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-20967?focusedWorklogId=442798&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-442798 ]

ASF GitHub Bot logged work on HIVE-20967:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Jun/20 15:59
            Start Date: 09/Jun/20 15:59
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #613:
URL: https://github.com/apache/hive/pull/613#issuecomment-641143553


   This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
   Feel free to reach out on the dev@hive.apache.org list if the patch is in need of reviews.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 442798)
    Time Spent: 1h 50m  (was: 1h 40m)

> Handle alter events when replicate to cluster with hive.strict.managed.tables enabled.
> --------------------------------------------------------------------------------------
>
>                 Key: HIVE-20967
>                 URL: https://issues.apache.org/jira/browse/HIVE-20967
>             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-20967.04.patch, HIVE-20967.05.patch
>
>          Time Spent: 1h 50m
>  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 test).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)