gRPC 5 NOT_FOUND vs 12 UNIMPLEMENTED
Both gRPC 5 (NOT_FOUND) and 12 (UNIMPLEMENTED) belong to the gRPC Status Codes category. 5 indicates that some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist. Meanwhile, 12 means that the operation is not implemented or is not supported/enabled in this service.
विवरण
Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
जब आप इसे देखें
The resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
कैसे ठीक करें
Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client.
विवरण
The operation is not implemented or is not supported/enabled in this service.
जब आप इसे देखें
The client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
कैसे ठीक करें
Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.
मुख्य अंतर
gRPC 5: Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
gRPC 12: The operation is not implemented or is not supported/enabled in this service.
You encounter 5 when the resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
You encounter 12 when the client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
कब किसका उपयोग करें
For 5 (NOT_FOUND): Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client. For 12 (UNIMPLEMENTED): Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.