hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-19815) Repl dump should not propagate the checkpoint and repl source properties
Date Wed, 06 Jun 2018 13:19:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-19815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503275#comment-16503275
] 

ASF GitHub Bot commented on HIVE-19815:
---------------------------------------

GitHub user sankarh opened a pull request:

    https://github.com/apache/hive/pull/367

    HIVE-19815: Repl dump should not propagate the checkpoint and repl source properties.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sankarh/hive HIVE-19815

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hive/pull/367.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #367
    
----
commit 39711256350121104a771c4aaea3ed7519308346
Author: Sankar Hariappan <mailtosankarh@...>
Date:   2018-06-06T09:20:42Z

    HIVE-19815: Repl dump should not propagate the checkpoint and repl source properties.

----


> Repl dump should not propagate the checkpoint and repl source properties
> ------------------------------------------------------------------------
>
>                 Key: HIVE-19815
>                 URL: https://issues.apache.org/jira/browse/HIVE-19815
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2, repl
>    Affects Versions: 3.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.1.0, 4.0.0
>
>
> For replication scenarios of A-> B -> C the repl dump on B should not include the
checkpoint property when dumping out table information. 
> Alter tables/partitions during incremental should not propagate this as well.
> Also should not propagate the the db level parameters set by replication internally.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message