[
https://issues.apache.org/jira/browse/KUDU-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205873#comment-17205873
]
ASF subversion and git services commented on KUDU-3192:
-------------------------------------------------------
Commit e5579c9b7465f9d9a164d42709f1a9a07acdff59 in kudu's branch
refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=e5579c9 ]
KUDU-3192: [hms] Leverage the cluster ID in HMS sync
This patch propagates the cluster ID to the HMS entries for
Kudu tables and leverages the cluster ID to ignore irrelevant
notifications from the HMS.
Additionally the `kudu hms` tool is updated to identify
and repair tables that do not have the cluster ID set.
Change-Id: I865b418a3cc4e11c889cc4757cd940831c43af17
Reviewed-on: http://gerrit.cloudera.org:8080/16494
Reviewed-by: Andrew Wong <aw...@cloudera.com>
Tested-by: Grant Henke <granthe...@apache.org>
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
> Leverage cluster ID when playing HMS notifications
> --------------------------------------------------
>
> Key: KUDU-3192
> URL: https://issues.apache.org/jira/browse/KUDU-3192
> Project: Kudu
> Issue Type: Task
> Components: hms
> Reporter: Andrew Wong
> Assignee: Grant Henke
> Priority: Major
>
> KUDU-2574 added a unique cluster ID to the master system catalog table. We
> should leverage this with the HMS integration by 1) synchronizing the cluster
> ID to the HMS, storing it as a part of the table JSON, and 2) filtering the
> HMS notifications received by the HMS log listener based on cluster ID.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
