milvus
milvus copied to clipboard
[Enhancement]: Unify error usage by wrapping error and make `errors.Is` available
Is there an existing issue for this?
- [X] I have searched the existing issues
What would you like to be added?
Unify error usage by wrapping error and make errors.Is
available
Why is this needed?
Some former error usage say ErrorList
may conceal leaf error type so user cannot determine the root cause
Anything else?
No response
/assign /assign @yah01
- [x] RootCoord #22689
- [ ] DataCoord
- [x] QueryCoord #22672 #22745 #22761 #23068
- [x] DataNode #22852
- [ ] QueryNode
- [ ] Proxy
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
/reopen still wip
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
keep it
/reopen
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
keep it
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
keep it
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.