Alexey Serbin has posted comments on this change. ( http://gerrit.cloudera.org:8080/23649 )
Change subject: [docs] refresh `kudu master add` documentation ...................................................................... Patch Set 1: (2 comments) http://gerrit.cloudera.org:8080/#/c/23649/1/docs/administration.adoc File docs/administration.adoc: http://gerrit.cloudera.org:8080/#/c/23649/1/docs/administration.adoc@608 PS1, Line 608: the new Kudu master will be running after the procedure is complete > needed to run the new Kudu master after the procedure is complete. Done http://gerrit.cloudera.org:8080/#/c/23649/1/docs/administration.adoc@642 PS1, Line 642: if HMS integration is : enabled > As per my understanding, with or without HMS integration, we will have kudu Yes, that's indeed so, AFAIK. However, I don't see now this contradicts the described procedure or would require modifying it in any way. I wouldn't recommend messing up with the metadata that Impala manages on is own in the HMS in the latter case. I'm not even sure it's possible to update it directly in the database that backs the HMS without additional knowledge on the format of the data that Impala stores in the HMS for Kudu tables. -- To view, visit http://gerrit.cloudera.org:8080/23649 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I8d2ae84d596a0c3ffe840cc16d3ac0d0d28d05bc Gerrit-Change-Number: 23649 Gerrit-PatchSet: 1 Gerrit-Owner: Alexey Serbin <[email protected]> Gerrit-Reviewer: Abhishek Chennaka <[email protected]> Gerrit-Reviewer: Alexey Serbin <[email protected]> Gerrit-Reviewer: Ashwani Raina <[email protected]> Gerrit-Reviewer: Kudu Jenkins (120) Gerrit-Comment-Date: Fri, 07 Nov 2025 23:51:50 +0000 Gerrit-HasComments: Yes
