-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Improvement] Improve the thrown exception in EntityStore #3976
Labels
Comments
@yuqi1129 Would you work on this issue? |
Yeah, I would like to do it. |
@xloya, as I may start this next week, please let me know if you plan to work on it. Thanks. |
@yuqi1129 Sure, I'd like to do this today. |
jerryshao
pushed a commit
that referenced
this issue
Jun 28, 2024
…tore (#3979) ### What changes were proposed in this pull request? Improve the throwing behavior of some SQL exceptions in EntityStore. ### Why are the changes needed? Fix: #3976 ### How was this patch tested? Through the existing tests. Co-authored-by: xiaojiebao <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be improved?
Currently, there're several misuse of exception in entity store.
In
put
method, we useEntityAlreadyExistsException
but inupdate
we useAlreadyExistsException
, we should unify to useEntityAlreadyExistsException
.in relation storage backend.
AlreadyExistsException
, this should be changed toEntityAlreadyExistsException
, otherwise this exception will be leaked.GravitinoRuntimeException
, we should useIOException
instead to avoid exception leakage and conform to the interface definition.How should we improve?
No response
The text was updated successfully, but these errors were encountered: