Improve error handling / parsing #301
Description
Search before asking
- I searched in the issues and found nothing similar.
Motivation
Server side errors are returned as FlussAPIError with numeric error code to the users on rust side. We can perform the translation to cliend-side error e.g. PartitionNotExist.
Additionally, we can also consider tightening the C++ and Python side to go beyond stringification and provide ways for users to progammtically distinguish errors e.g. typed error.
On second thought, maybe APIError is the best way to bubble server error, user can check against error code constants if they want to response to error differently.
We can surface api error code on python/cpp side for the same benefit.
Solution
No response
Anything else?
No response
Willingness to contribute
- I'm willing to submit a PR! , Feel free to pick it up as well if you have bandwidth
Metadata
Metadata
Assignees
Labels
No labels