[
https://issues.apache.org/jira/browse/KUDU-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204294#comment-17204294
]
ASF subversion and git services commented on KUDU-3192:
-------------------------------------------------------
Commit cc1e091904ceb6b6c527498d8ff849bb42412115 in kudu's branch
refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=cc1e091 ]
KUDU-3192: [client] Expose the cluster ID in the client KuduTable
This patch adds a cluster ID field to the C++ and Java Kudu
clients. This field will be used in a follow on change to better
enable the HMS integration to use the cluster ID.
Change-Id: Ia1f5a451aaa44834534d2387ee1c9aa9cf95dd37
Reviewed-on: http://gerrit.cloudera.org:8080/16493
Reviewed-by: Andrew Wong <aw...@cloudera.com>
Tested-by: Grant Henke <granthe...@apache.org>
> 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)
