You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/09/04 14:02:00 UTC
[jira] [Assigned] (KUDU-3192) Leverage cluster ID when playing HMS
notifications
[ https://issues.apache.org/jira/browse/KUDU-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke reassigned KUDU-3192:
---------------------------------
Assignee: Grant Henke
> 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)