gRPC 11 OUT_OF_RANGE vs 12 UNIMPLEMENTED
Both gRPC 11 (OUT_OF_RANGE) and 12 (UNIMPLEMENTED) belong to the gRPC Status Codes category. 11 indicates that the operation was attempted past the valid range. For example, seeking or reading past the end of a file. Meanwhile, 12 means that the operation is not implemented or is not supported/enabled in this service.
คำอธิบาย
The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
เมื่อคุณพบเห็น
A pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
วิธีแก้ไข
Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page.
คำอธิบาย
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 11: The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
gRPC 12: The operation is not implemented or is not supported/enabled in this service.
You encounter 11 when a pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
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 11 (OUT_OF_RANGE): Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page. 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.