Andrew Wong has posted comments on this change. ( http://gerrit.cloudera.org:8080/16493 )
Change subject: KUDU-3192: [client] Expose the cluster ID in the client KuduTable ...................................................................... Patch Set 2: (1 comment) http://gerrit.cloudera.org:8080/#/c/16493/2//COMMIT_MSG Commit Message: http://gerrit.cloudera.org:8080/#/c/16493/2//COMMIT_MSG@9 PS2, Line 9: This patch adds a cluster ID field to the KuduTable object in the > It is convenient to have it on the KuduTable object so that the user can ch I agree it's convenient to know the cluster ID, but every table will hit the same masters and get the same cluster ID. It seems like if we have a KuduTable, we should also have a Kudu client, in which case we could get the cluster ID directly from the client for such validation. I'd be onboard with the ConnectToMaster approach. -- To view, visit http://gerrit.cloudera.org:8080/16493 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ia1f5a451aaa44834534d2387ee1c9aa9cf95dd37 Gerrit-Change-Number: 16493 Gerrit-PatchSet: 2 Gerrit-Owner: Grant Henke <granthe...@apache.org> Gerrit-Reviewer: Andrew Wong <aw...@cloudera.com> Gerrit-Reviewer: Grant Henke <granthe...@apache.org> Gerrit-Reviewer: Hao Hao <hao....@cloudera.com> Gerrit-Reviewer: Kudu Jenkins (120) Gerrit-Comment-Date: Wed, 23 Sep 2020 18:13:57 +0000 Gerrit-HasComments: Yes
