[
https://issues.apache.org/jira/browse/HIVE-18352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312651#comment-16312651
]
ASF GitHub Bot commented on HIVE-18352:
---------------------------------------
GitHub user anishek opened a pull request:
https://github.com/apache/hive/pull/286
HIVE-18352: introduce a METADATAONLY option while doing REPL DUMP to allow
integrations of other tools
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anishek/hive HIVE-18352
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/286.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 #286
----
commit c03814bd857cfd70a40aa7a5ec674e73cbfc63f9
Author: Anishek Agarwal <anishek@...>
Date: 2018-01-03T10:27:04Z
HIVE-18352: introduce a METADATAONLY option while doing REPL DUMP to allow
integrations of other tools
----
> introduce a METADATAONLY option while doing REPL DUMP to allow integrations
> of other tools
> -------------------------------------------------------------------------------------------
>
> Key: HIVE-18352
> URL: https://issues.apache.org/jira/browse/HIVE-18352
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: anishek
> Assignee: anishek
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: HIVE-18352.0.patch
>
>
> * Introduce a METADATAONLY option as part of the REPL DUMP command which will
> only try and dump out events for DDL changes, this will be faster as we wont
> need scan of files on HDFS for DML changes.
> * Additionally since we are only going to dump metadata operations, it might
> be useful to include acid tables as well via an option as well. This option
> can be removed when ACID support is complete via HIVE-18320
> it will be good to support the "WITH" clause as part of REPL DUMP command as
> well (repl dump already supports it viaHIVE-17757) to achieve the above as
> that will prevent less changes to the syntax of the statement and provide
> more flexibility in future to include additional options as well.
> {code}
> REPL DUMP [db_name] {FROM [event_id]} {TO [event_id]} {WITH
> (['key'='value'],.....)}
> {code}
> This will enable other tools like security / schema registry / metadata
> discovery to use replication related subsystem for their needs as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
