gRPC 3 INVALID_ARGUMENT vs 6 ALREADY_EXISTS
Both gRPC 3 (INVALID_ARGUMENT) and 6 (ALREADY_EXISTS) belong to the gRPC Status Codes category. 3 indicates that the client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system. Meanwhile, 6 means that the entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists.
描述
The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
何时出现
A request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
如何修复
Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.
描述
The entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists.
何时出现
A create operation failed because a resource with the same unique identifier or name already exists in the system.
如何修复
Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating.
主要区别
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
gRPC 6: The entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists.
You encounter 3 when a request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
You encounter 6 when a create operation failed because a resource with the same unique identifier or name already exists in the system.
何时使用哪个
For 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints. For 6 (ALREADY_EXISTS): Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating.