@mchades @FANNG1 @yuqi1129 @diqiu50 let's discuss here.

if succ, return true, if not exists return false, otherwise, throw corresponding exception, the behavior seems clear.

I think we should revisit all the drop related APIs and implementations, and change the behavior if necessary, which includes:

1. Rest client and server implementations.
2. The drop implementations in each catalog.

I would love to revisit all the drop related APIs and implementations first, then write the results into a document.
What do you think about this? @mchades @FANNG1 @yuqi1129 @diqiu50 @jerryshao

Great, you can go ahead. Thanks a lot.

Is this a list of all Rest APIs?
https://github.com/datastrato/gravitino/tree/main/docs/open-api

Is this a list of all Rest APIs? https://github.com/datastrato/gravitino/tree/main/docs/open-api

Yep, you can also look into the codes in package com.datastrato.gravitino.server.web.rest

The web also FYI: https://datastrato.ai/docs/0.4.0/api/rest/gravitino-rest-api

@mchades @FANNG1 @yuqi1129 @diqiu50 @jerryshao
The result after revisiting the drop APIs is following. Please correct me if there are any omissions.
Drop Related APIs

@mchades
I didn't find the information about dropPartition in the open API. Has it not been made available yet?

Could you please also add the exception response? For example, the response when encountering a RuntimeException.

I didn't find the information about dropPartition in the open API. Has it not been made available yet?

yep, it's WIP #2492

BTW, it's better to make your doc commentable

Could you please also add the exception response? For example, the response when encountering a RuntimeException.

I didn't find the information about dropPartition in the open API. Has it not been made available yet?

yep, it's WIP #2492

BTW, it's better to make your doc commentable

The exception response has been updated, but it seems that the implementation is not aligned.

@charliecheng630 are you still working on this? I found that for most the JDBC catalogs, the current implementation is not aligned the definition, we should improve it.

@jerryshao I haven't started to work yet. I will work on this ASAP.

OK, thanks!

@mchades After tracing code, here are the areas that need to be improve：

com.datastrato.gravitino.catalog.xxx.xxxCatalogOperations#dropXXX
com.datastrato.gravitino.catalog.xxxOperationDispatcher#dropXXX
com.datastrato.gravitino.storage.relational.service.xxxService#deleteXXX

Please correct me if I am wrong.

I'm working on the core part to fix the current fix, you can check #3075 and the related PR. I think what you should check is:

1. all the specific catalog's dropXXX.
2. CatalogManger/MetalakeManager's dropXXX.
3. Rest server's dropXXX.
4. Client API's dropXXX.

I've check all the Operation Dispatcher's dropXXX in #3075.