Mensagens de erro e códigos do mecanismo gráfico - Amazon Neptune
Formato de erroErros de consultaErros de IAM

As traduções são geradas por tradução automática. Em caso de conflito entre o conteúdo da tradução e da versão original em inglês, a versão em inglês prevalecerá.

Mensagens de erro e códigos do mecanismo gráfico

Os endpoints do Amazon Neptune geram os erros padrão para Gremlin e SPARQL quando encontrados.

Os erros específicos do Neptune também podem ser gerados pelos mesmos endpoints. Esta seção documenta as mensagens de erro, os códigos e as ações recomendadas do Neptune.

nota

Esses erros são relativos somente aos endpoints do cluster de banco de dados do Neptune. As APIs para criar e modificar recursos do Neptune com o AWS SDK e a AWS CLI têm um conjunto diferente de erros comuns. Para obter mais informações sobre esses erros, consulte Códigos e mensagens de erro da API de gerenciamento do cluster de banco de dados.

Formato de erro do mecanismo de gráfico

As mensagens de erro do Neptune geram um código de erro HTTP relevante e uma resposta em formato JSON.

HTTP/1.1 400 Bad Request
x-amzn-RequestId: LDM6CJP8RMQ1FHKSC1RBVJFPNVV4KQNSO5AEMF66Q9ASUAAJG
Content-Type: application/x-amz-json-1.0
Content-Length: 465
Date: Thu, 15 Mar 2017 23:56:23 GMT

{
    "requestId": "0dbcded3-a9a1-4a25-b419-828c46342e47",
    "code": "ReadOnlyViolationException",
    "detailedMessage": "The request is rejected because it violates some read-only restriction, such as a designation of a replica as read-only."
}

Erros de consulta do mecanismo de gráfico

A tabela a seguir contém o código de erro, a mensagem e o status HTTP.

Ela também indica se é aceitável repetir a solicitação. No geral, é aceitável repetir a solicitação se ela puder ser bem-sucedida em uma nova tentativa.

Neptune Service Error Code HTTP status Ok to Retry? Message
AccessDeniedException 403 No Authentication or authorization failure.
BadRequestException 400 No The request could not be completed.
BadRequestException 400 No Request size exceeds max allowed value of 157286400 bytes.
CancelledByUserException 500 Yes The request processing was cancelled by an authorized client.
ConcurrentModificationException 500 Yes The request processing did not succeed due to a modification conflict. The client should retry the request.
ConstraintViolationException 400 Yes The query engine discovered, during the execution of the request, that the completion of some operation is impossible without violating some data integrity constraints, such as persistence of in- and out-vertices while adding an edge. Such conditions are typically observed if there are concurrent modifications to the graph, and are transient. The client should retry the request.
FailureByQueryException 500 Yes Calling fail() caused request processing to fail.
InternalFailureException 500 Yes The request processing has failed.
InvalidNumericDataException 400 No Invalid use of numeric data which cannot be represented in 64-bit storage size.
InvalidParameterException 400 No An invalid or out-of-range value was supplied for some input parameter or invalid syntax in a supplied RDF file.
MalformedQueryException 400 No The request is rejected because it contains a query that is syntactically incorrect or does not pass additional validation.
MemoryLimitExceededException 500 Yes The request processing did not succeed due to lack of memory, but can be retried when the server is less busy.
MethodNotAllowedException 405 No The request is rejected because the chosen HTTP method is not supported by the used endpoint.
MissingParameterException 400 No A required parameter for the specified action is not supplied.
QueryLimitExceededException 500 Yes The request processing did not succeed due to the lack of a limited resource, but can be retried when the server is less busy.
QueryLimitException 400 No Size of query exceeds system limit.
QueryTooLargeException 400 No The request was rejected because its body is too large.
ReadOnlyViolationException 400 No The request is rejected because it violates some read-only restriction, such as a designation of a replica as read-only.
ThrottlingException 500 Yes Rate of requests exceeds the maximum throughput. OK to retry.
TimeLimitExceededException 500 Yes The request processing timed out.
TooManyRequestsException 429 Yes The rate of requests exceeds the maximum throughput. OK to retry.
UnsupportedOperationException 400 No The request uses a currently unsupported feature or construct.

Erros de autenticação do IAM

Esses erros são específicos de cluster que possui autenticação do IAM habilitada.

A tabela a seguir contém o código de erro, a mensagem e o status HTTP.

Neptune Service Error Code HTTP status Message
Incorrect IAM User/Policy 403 You do not have sufficient access to perform this action.
Incorrect or Missing Region 403 Credential should be scoped to a valid Region, not 'região'.
Incorrect or Missing Service Name 403 Credential should be scoped to correct service: 'neptune-db'.
Incorrect or Missing Host Header / Invalid Signature 403 The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. Host header is missing or hostname is incorrect.
Missing X-Amz-Security-Token 403 'x-amz-security-token' is named as a SignedHeader, but it does not exist in the HTTP request
Missing Authorization Header 403 The request did not include the required authorization header, or it was malformed.
Missing Authentication Token 403 Missing Authentication Token.
Old Date 403 Signature expired: 20181011T213907Z is now earlier than 20181011T213915Z (20181011T214415Z - Cinco min..)
Future Date 403 Signature not yet current: 20500224T213559Z is still later than 20181108T225925Z (20181108T225425Z + Cinco min..)
Incorrect Date Format 403 Date must be in ISO-8601 'basic format'. Got 'data'. See https://en.wikipedia.org/wiki/ISO_8601.
Unknown/Missing Access Key or Session Token 403 The security token included in the request is invalid.
Unknown/Missing Secret Key 403 The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. Host header is missing or hostname is incorrect.
TooManyRequestsException 429 The rate of requests exceeds the maximum throughput. OK to retry.