You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the error information in HoraeDB is unclear (for example, In many cases, users will see the error table not found.). When an error occurs, it confuses users and increases the difficulty of troubleshooting and locating problems.
Proposal
Make error messages clearer, classify error messages, and even consider designing error codes to classify error messages in the form of error codes.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
## Rationale
Refer to this issue
#1386, currently, if
the status of the shard is abnormal, we cannot get any valid exception
information from the error message `table not found`.
## Detailed Changes
* Add `TableStatus` in `cluster`, you can use it to get the status of
the table in the current cluster..
* Add `SchemaWithCluster`, It wraps the schema inside the cluster,
through which the state of the cluster and schema can be combined.
## Test Plan
Pass CI.
Describe This Problem
Currently, the error information in HoraeDB is unclear (for example, In many cases, users will see the error
table not found
.). When an error occurs, it confuses users and increases the difficulty of troubleshooting and locating problems.Proposal
Make error messages clearer, classify error messages, and even consider designing error codes to classify error messages in the form of error codes.
Additional Context
No response
The text was updated successfully, but these errors were encountered: