[
https://issues.apache.org/jira/browse/KUDU-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17938935#comment-17938935
]
ASF subversion and git services commented on KUDU-3608:
-------------------------------------------------------
Commit 500a7b778be9c032d24568f42e9b94da6b29ce5f in kudu's branch
refs/heads/master from gabriellalotz
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=500a7b778 ]
KUDU-3608: REST API for Metadata Management
This commit introduces a REST API integrated directly into the Kudu
master web server to simplify metadata access and management. The API
operates under the /api path and focuses exclusively on
metadata-related operations. The following endpoints have been added:
- GET /api/v1/tables - Lists all tables by name and ID.
- POST /api/v1/tables - Creates a new table.
- GET /api/v1/tables/<table_id> - Retrieves table details.
- PUT /api/v1/tables/<table_id> - Updates table metadata.
- DELETE /api/v1/tables/<table_id> - Deletes a table.
HTTP Status Codes: Introduced additional HTTP status codes like 201
Created and 204 No Content for operations such as creating and deleting
tables.
Enhanced the web server's content-length check to include the PUT
method, allowing it to handle errors similar to POST.
Limitations: Deleting, altering, or retrieving a table object requires
the table's ID. Operations using table names are not yet supported.
Testing: Two new test files called rest_catalog-test.cc and
spnego_rest_catalog-test.cc have been created to validate these
endpoints using an internal mini-cluster setup. Both tests are based on
the rest_catalog_test_base.h header file.
These test files have been tested for flakiness and evaluated under high
load to ensure stability.
Usage:
When running Kudu, the endpoints are accessible via the /api/v1/ path
on the master web server. For POST and PUT endpoints, appropriate
data must be provided with the HTTP request (e.g., via curl).
Follow-up patches:
- Support for multi-master setup
- Adding ranger itests
- Swagger/OpenAI documentation for the endpoint under /api/docs path
Change-Id: I67f964c4f950edfde31772cafd5c3ed5d6b87413
Reviewed-on: http://gerrit.cloudera.org:8080/21823
Tested-by: Kudu Jenkins
Reviewed-by: Marton Greber <greber...@gmail.com>
Reviewed-by: Zoltan Chovan <zcho...@cloudera.com>
Reviewed-by: Zoltan Martonka <zmarto...@cloudera.com>
> Implementing a metadata management interface for Kudu
> -----------------------------------------------------
>
> Key: KUDU-3608
> URL: https://issues.apache.org/jira/browse/KUDU-3608
> Project: Kudu
> Issue Type: New Feature
> Reporter: Gabriella Lotz
> Assignee: Gabriella Lotz
> Priority: Major
>
> Support REST Catalog API so that Kudu can serve metadata for Kudu tables.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
