apache / gravitino

World's most powerful open data catalog for building a high-performance, geo-distributed and federated metadata lake.
https://gravitino.apache.org
Apache License 2.0
1.1k stars 345 forks source link

[Subtask] Replace mock data with real data from API in Metalakes page #793

Closed ch3yne closed 1 year ago

ch3yne commented 1 year ago

Describe the subtask

Metalakes list is generated from mock data, this issue is develop to replace the mock data with real data obtained from API.

# get metalakes
curl -X GET 'http://localhost:8090/api/metalakes'

# get metalake from name
curl -X GET 'http://localhost:8090/api/metalakes/{matalake_name}'

# create metalake
curl -X POST 'http://localhost:8090/api/metalakes' \
-H 'Content-Type: application/json' \
-d '{"name": <metalake_name>, "comment": <comment_text>, "properties": <key_value_object>}' 

# replace `{matalake_name}, <metalake_name>, <comment_text>, <key_value_object>` with your own data

Parent issue

605

justinmclean commented 1 year ago

BTW, curl uses GET by default, so there is no need for the -x GET. Also, depending on the type of metalake, you may need some other parameters when it comes to creating catalogs.

ch3yne commented 1 year ago

BTW, curl uses GET by default, so there is no need for the -x GET. Also, depending on the type of metalake, you may need some other parameters when it comes to creating catalogs.

Thank you for your suggestions. I added GET for better differentiation during front-end reading and debugging. Currently, on the front-end home page (metalakes), only the metalakes list, create metalake, and metalake details APIs are used. The development of functionalities related to creating catalogs and others on different front-end pages will be addressed in separate issues.