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.