Gabriella Lotz has posted comments on this change. ( http://gerrit.cloudera.org:8080/23655 )
Change subject: Add Introducing REST API blog post ...................................................................... Patch Set 2: (15 comments) http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md File _posts/2025-11-10-introducing-the-rest-api.md: PS2: > For regular text content, could you break long lines so a single line would Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@7 PS2, Line 7: tools > Consider adding which version of Kudu this feature is supported from. Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@13 PS2, Line 13: full client application > client application that depends on the Kudu client library and uses KRPC to Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@13 PS2, Line 13: catalog > system catalog Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@13 PS2, Line 13: table-metadata > table metadata ? Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@20 PS2, Line 20: Integrates with Kudu's existing authentication mechanisms > nit: Since most of the clusters use security, consider adding extending the Thanks for the suggestion. I've added a brief note about authentication for secure clusters after the example. Since this is an introductory article rather than complete documentation, I kept it concise. http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@24 PS2, Line 24: table metadata management > Here and elsewhere in appropriate context: being 'table metadata' from the Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@89 PS2, Line 89: OpenAPI > Consider adding an extra Reference section to provide hyperlinks to OpenAPI Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@89 PS2, Line 89: master's web UI > Does it make sense to provide path the the API doc page from the root of th Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@89 PS2, Line 89: interactive > nit: iirc it is not interactive as that was pulled out because of Knox righ Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@96 PS2, Line 96: will return errors > Maybe, be more specific as for what particular HTTP status code non-leader Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@96 PS2, Line 96: only the leader master will respond to REST API requests > Non-leader masters respond as well, but they respond with errors, IIUC. Pl Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@96 PS2, Line 96: configurations > Kudu clusters Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@96 PS2, Line 96: connect to the correct master > Since it's not quite evident for people without Kudu or other distributed s Done http://gerrit.cloudera.org:8080/#/c/23655/2/_posts/2025-11-10-introducing-the-rest-api.md@99 PS2, Line 99: for optimal performance > nit: drop this part? Done -- To view, visit http://gerrit.cloudera.org:8080/23655 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: gh-pages Gerrit-MessageType: comment Gerrit-Change-Id: I1435431857a9f493e6492fae002c70f7af4cdd6c Gerrit-Change-Number: 23655 Gerrit-PatchSet: 2 Gerrit-Owner: Gabriella Lotz <[email protected]> Gerrit-Reviewer: Abhishek Chennaka <[email protected]> Gerrit-Reviewer: Alexey Serbin <[email protected]> Gerrit-Reviewer: Gabriella Lotz <[email protected]> Gerrit-Reviewer: Marton Greber <[email protected]> Gerrit-Comment-Date: Thu, 27 Nov 2025 10:14:25 +0000 Gerrit-HasComments: Yes
