Status 200 parse error

wrong status code when schema parse error #554

Comments

Environment

  • Elixir version : 1.6.4
  • Absinthe version : 1.4.2
  • Client Framework and version: Apollo-client (latest)

Expected behavior

should return a 200 status code with error filed contains parse error infos

Actual behavior

when i query with missing arg, the server return a 400 status code, which cause graphql-client treat this as Network-Error instead of GraphQL-Parse-Error

a 400 status code is returned

Relevant Schema/Middleware Code

The text was updated successfully, but these errors were encountered:

The 400 status code was definitely what the spec required at some point in the past, but I haven’t looked lately. Let me see if I can find the relevant bit.

thanks @benwilson512, but i don’t think there is relevant bit in the spec .

As far as I can tell from the GraphQL spec there is no discussion of http response codes at all. The status codes of HTTP are strongly tied to rest principles. It’s not clear to me whether GraphQL APIs should distinguish between 2XX and 4XX status codes.

Most notably, you can batch multiple mutations into the same request to the server. If one successfully creates a resource (201), one mutates a resource (200), one fails validation (400) and another the target object does not exists (404), what should the return value from the API be?

At the moment, GraphQL APIs seem to err on the side of 200 unless the server blows up, in which case 500.

I have created a PR to resolve that. but I am not 100% convinced what we should be doing here.

I am leaning towards returning 200 OK unless the server blows up, mostly because of good point above about batch mutations.

The other thing is that HTTP is just a transport layer, and as such transport layer should be invisible for the applications that use it. GraphQL specification seems to not to mention HTTP status codes at all.

But HTTP status code used here has a meaning on a transport layer: «request-response cycle was successful».

When we return 400 on wrong requests we are also giving it protocol-layer meaning.

Now if we keep doing that, swapping GraphQL transport layers from say HTTP to websocket or something else might not be as easy, becausue our application code relies on status codes from transport layer.. that might not be there at all in case of protocol different than HTTP.

Источник

jQuery Forum

jQuery calls error callback on successful ajax request (status 200)

Why, oh why does jquery think my header only response is an error?
I am using jQuery to submit a form via ajax in my ruby on rails application. The server responds with a header with status 200. (I don’t need to send anything else to the page, just an ‘ok’) But jquery seems to think this is erroneous.

jQuery 1.4
Ruby On Rails 2.3.8

Replies(11)

Re: jQuery calls error callback on successful ajax request (status 200)

can we see some code? just because the status was 200 doesn’t mean an error hasn’t happened somewhere else, such as when jquery parsed the return data. try using the error callback of the .ajax() method to get more information as to what the error is.

Re: Re: jQuery calls error callback on successful ajax request (status 200)

Ok, this is a bit involved.
Basically what I have is a Ruby on Rails entity called ‘Job’
Here is the Action that receives my Ajax POST request:

  1. def update
    @job = Job.find params[:id]
    if @job.update_attributes params[:job]
    respond_to do |format|
    format.html do
    flash[:notice] = «Job updated successfully. (ID: #<@job.id>)»
    smart_redirect @job
    end
    format.json
    end
    else
    respond_to do |format|
    format.html do
    flash.now[:warning] = AppConfig.messages[‘submission_invalid’]
    render :edit
    end
    format.json @job.errors, :status => :unprocessable_entity>
    end
    end
    end

So what this does is tries to update the job from the submitted data, if it can, it responds by either redirecting to the job detail page, or if the requested content-type is json (AKA my Ajax request), it sends a header with status 200. No response text. By sending http status code of 200, I am expecting jQuery to treat this as a successful request.

Here is my jquery:

  1. jtable = $(‘section.jobs.open-with-budget table’);
    jtable.find(‘td.target-completion-date’).each(function() <
    $(this).append(‘ edit ‘);
    >);
    jtable.find(‘button.edit’).click(function() <
    tr = $(this).closest(‘tr’);
    job_id = tr.attr(‘data-record-id’);
    form = $(»);
    form.append(‘
    1. \n\
      Target Completion Date \n\
      \n\
      mm/dd/yyyy

    \n\
    \n\
    ‘);
    form.appendTo(‘jtable’);
    form.dialog( <
    title: tr.find(‘td.address’).text(),
    modal: true,
    buttons: <
    Ok: function() <
    $.loadingBlocksUI = true;
    $.ajax( <
    type: ‘POST’,
    url: ‘ /’ + job_id ,
    dataType: ‘json’,
    data: form.serialize(),
    success: function(data) <
    spn = tr.find(‘span.value’);
    spn.text(form.find(‘input[name*=TargetCompletionDate]’).val());
    spn.siblings(‘span.error.flag’).remove();
    $(this).remove();
    >,
    error: function(xhr) <
    if(xhr.status == 422) <
    alertValidationErrors(parseErrors(xhr));
    > else <
    alert(‘An error occurred while processing the request.’);
    >
    $(this).remove();
    >
    >);
    $(this).dialog(‘close’);
    >,
    Cancel: function()<$(this).dialog('close');>
    >
    >);
    return false;
    >);

So to explain:

  • jtable is the table of data I am working with
  • I want to update one attribute called ‘TargetCompletionDate’
  • So, I find the cell, inject an edit button.
  • When the edit button is clicked, it opens a ui dialog box with a form inside.
  • This form only contains one field to update, (TargetCompletionDate)
  • — ANYWAY — All of this works as described.
  • When the user clicks the ‘Ok’ button, it serializes the form and sends it to the above action.
  • If their are validation errors, the action renders those to json, and returns http status 422 (unprocessable_entity)
  • if the post action is successful, it simply returns a header response with status 200.

So, what I am assuming is that jquery would call my success callback because of the status code of 200.
but it is not. It calls my error callback. The error callback checks for http code 422. If 422, it will render the validation errors. If anything else, it will alert »An error occurred while processing the request.»

With firebug i have inspected the xhr object inside the error callback and it reports status of 200, thus calling the alert.

Источник

Error Responses

This section provides reference information about Amazon S3 errors.

SOAP support over HTTP is deprecated, but it is still available over HTTPS. New Amazon S3 features will not be supported for SOAP. We recommend that you use either the REST API or the AWS SDKs.

Topics

REST Error Responses

When an error occurs, the header information contains the following:

An appropriate 3xx, 4xx, or 5xx HTTP status code

The body of the response also contains information about the error. The following sample error response shows the structure of response elements common to all REST error responses.

The following table explains the REST error response elements.

The error code is a string that uniquely identifies an error condition. It is meant to be read and understood by programs that detect and handle errors by type. For more information, see List of Error Codes.

Container for all error elements.

The error message contains a generic description of the error condition in English. It is intended for a human audience. Simple programs display the message directly to the end user if they encounter an error condition they don’t know how or don’t care to handle. Sophisticated programs with more exhaustive error handling and proper internationalization are more likely to ignore the error message.

ID of the request associated with the error.

The bucket or object that is involved in the error.

Many error responses contain additional structured data meant to be read and understood by a developer diagnosing programming errors. For example, if you send a Content-MD5 header with a REST PUT request that doesn’t match the digest calculated on the server, you receive a BadDigest error. The error response also includes as detail elements the digest that the server calculated, and the digest that you told the server to expect. During development, you can use this information to diagnose the error. In production, a well-behaved program might include this information in its error log.

For information about general response elements, go to Error Responses.

List of Error Codes

The following table lists Amazon S3 error codes.

Error Code Description HTTP Status Code SOAP Fault Code Prefix
AccessControlListNotSupported The bucket does not allow ACLs. 400 Bad Request Client
AccessDenied Access Denied 403 Forbidden Client
AccessPointAlreadyOwnedByYou An access point with an identical name already exists in your account. 409 Conflict Client
AccountProblem There is a problem with your AWS account that prevents the operation from completing successfully. For further assistance, see Contact Us . 403 Forbidden Client
AllAccessDisabled All access to this Amazon S3 resource has been disabled. For further assistance, see Contact Us . 403 Forbidden Client
AmbiguousGrantByEmailAddress The email address that you provided is associated with more than one account. 400 Bad Request Client
AuthorizationHeaderMalformed The authorization header that you provided is not valid. 400 Bad Request N/A
BadDigest The Content-MD5 or checksum value that you specified did not match what the server received. 400 Bad Request Client
BucketAlreadyExists The requested bucket name is not available. The bucket namespace is shared by all users of the system. Specify a different name and try again. 409 Conflict Client
BucketAlreadyOwnedByYou The bucket that you tried to create already exists, and you own it. Amazon S3 returns this error in all AWS Regions except in the US East (N. Virginia) Region (us-east-1). For legacy compatibility, if you re-create an existing bucket that you already own in us-east-1, Amazon S3 returns 200 OK and resets the bucket access control lists (ACLs).

For Amazon S3 on Outposts, the bucket that you tried to create already exists in your Outpost and you own it.

409 Conflict (in all Regions except us-east-1)

Client BucketNotEmpty The bucket that you tried to delete is not empty. 409 Conflict Client ClientTokenConflict Your Multi-Region Access Point idempotency token was already used for a different request. 409 Conflict Client CredentialsNotSupported This request does not support credentials. 400 Bad Request Client CrossLocationLoggingProhibited Cross-Region logging is not allowed. Buckets in one AWS Region cannot log information to a bucket in another Region. 403 Forbidden Client EntityTooSmall Your proposed upload is smaller than the minimum allowed object size. 400 Bad Request Client EntityTooLarge Your proposed upload exceeds the maximum allowed object size. For more information, see Amazon Simple Storage Service endpoints and quotas in the AWS General Reference. 400 Bad Request Client ExpiredToken The provided token has expired. 400 Bad Request Client IllegalLocationConstraintException You are trying to access a bucket from a different Region than where the bucket exists. To avoid this error, use the —region option. For example: aws s3 cp awsexample.txt s3:// DOC-EXAMPLE-BUCKET / —region ap-east-1 . 400 Bad Request Client IllegalVersioningConfigurationException The versioning configuration specified in the request is not valid. 400 Bad Request Client IncompleteBody You did not provide the number of bytes specified by the Content-Length HTTP header. 400 Bad Request Client IncorrectNumberOfFilesInPostRequest POST requires exactly one file upload per request. 400 Bad Request Client InlineDataTooLarge The inline data exceeds the maximum allowed size. 400 Bad Request Client InternalError An internal error occurred. Try again. 500 Internal Server Error Server InvalidAccessKeyId The AWS access key ID that you provided does not exist in our records. 403 Forbidden Client InvalidAccessPoint The specified access point name or account is not valid. 400 Bad Request Client InvalidAccessPointAliasError The specified access point alias name is not valid. 400 Bad Request Client InvalidAddressingHeader You must specify the Anonymous role. N/A Client InvalidArgument

This error might occur for the following reasons:

The specified argument was not valid.

The request was missing a required header.

The specified argument was incomplete or in the wrong format.

The specified argument must have a length greater than or equal to 3.

400 Bad Request Client InvalidBucketAclWithObjectOwnership Bucket cannot have ACLs set with ObjectOwnership’s BucketOwnerEnforced setting. 400 Bad Request Client InvalidBucketName The specified bucket is not valid. 400 Bad Request Client InvalidBucketState The request is not valid for the current state of the bucket. 409 Conflict Client InvalidDigest The Content-MD5 or checksum value that you specified is not valid. 400 Bad Request Client InvalidEncryptionAlgorithmError The encryption request that you specified is not valid. The valid value is AES256 . 400 Bad Request Client InvalidLocationConstraint The specified location (Region) constraint is not valid. For more information about selecting a Region for your buckets, see Buckets overview. 400 Bad Request Client InvalidObjectState The operation is not valid for the current state of the object. 403 Forbidden Client InvalidPart One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part’s entity tag. 400 Bad Request Client InvalidPartOrder The list of parts was not in ascending order. The parts list must be specified in order by part number. 400 Bad Request Client InvalidPayer All access to this object has been disabled. For further assistance, see Contact Us . 403 Forbidden Client InvalidPolicyDocument The content of the form does not meet the conditions specified in the policy document. 400 Bad Request Client InvalidRange The requested range is not valid for the request. Try another range. 416 Requested Range Not Satisfiable Client InvalidRequest

This error might occur for the following reasons:

The request is using the wrong signature version. Use AWS4-HMAC-SHA256 (Signature Version 4).

An access point can be created only for an existing bucket.

The access point is not in a state where it can be deleted.

An access point can be listed only for an existing bucket.

The next token is not valid.

At least one action must be specified in a lifecycle rule.

At least one lifecycle rule must be specified.

The number of lifecycle rules must not exceed the allowed limit of 1000 rules.

The range for the MaxResults parameter is not valid.

SOAP requests must be made over an HTTPS connection.

Amazon S3 Transfer Acceleration is not supported for buckets with non-DNS compliant names.

Amazon S3 Transfer Acceleration is not supported for buckets with periods (.) in their names.

The Amazon S3 Transfer Acceleration endpoint supports only virtual style requests.

Amazon S3 Transfer Acceleration is not configured on this bucket.

Amazon S3 Transfer Acceleration is disabled on this bucket.

Amazon S3 Transfer Acceleration is not supported on this bucket. For assistance, contact AWS Support .

Amazon S3 Transfer Acceleration cannot be enabled on this bucket. For assistance, contact AWS Support .

Conflicting values provided in HTTP headers and query parameters.

Conflicting values provided in HTTP headers and POST form fields.

400 Bad Request Client InvalidSecurity The provided security credentials are not valid. 403 Forbidden Client InvalidSOAPRequest The SOAP request body is not valid. 400 Bad Request Client InvalidStorageClass The storage class that you specified is not valid. 400 Bad Request Client InvalidTargetBucketForLogging The target bucket for logging either does not exist, is not owned by you, or does not have the appropriate grants for the log-delivery group. 400 Bad Request Client InvalidToken The provided token is malformed or otherwise not valid. 400 Bad Request Client InvalidURI The specified URI couldn’t be parsed. 400 Bad Request Client KeyTooLongError Your key is too long. 400 Bad Request Client MalformedACLError The ACL that you provided was not well formed or did not validate against our published schema. 400 Bad Request Client MalformedPOSTRequest The body of your POST request is not well-formed multipart/form-data. 400 Bad Request Client MalformedXML The XML that you provided was not well formed or did not validate against our published schema. 400 Bad Request Client MaxMessageLengthExceeded Your request was too large. 400 Bad Request Client MaxPostPreDataLengthExceededError Your POST request fields preceding the upload file were too large. 400 Bad Request Client MetadataTooLarge Your metadata headers exceed the maximum allowed metadata size. 400 Bad Request Client MethodNotAllowed The specified method is not allowed against this resource. 405 Method Not Allowed Client MissingAttachment A SOAP attachment was expected, but none was found. N/A Client MissingContentLength You must provide the Content-Length HTTP header. 411 Length Required Client MissingRequestBodyError You sent an empty XML document as a request. 400 Bad Request Client MissingSecurityElement The SOAP 1.1 request is missing a security element. 400 Bad Request Client MissingSecurityHeader Your request is missing a required header. 400 Bad Request Client NoLoggingStatusForKey There is no such thing as a logging status subresource for a key. 400 Bad Request Client NoSuchBucket The specified bucket does not exist. 404 Not Found Client NoSuchBucketPolicy The specified bucket does not have a bucket policy. 404 Not Found Client NoSuchCORSConfiguration The specified bucket does not have a CORS configuration. 404 Not Found Client NoSuchKey The specified key does not exist. 404 Not Found Client NoSuchLifecycleConfiguration The specified lifecycle configuration does not exist. 404 Not Found Client NoSuchMultiRegionAccessPoint The specified Multi-Region Access Point does not exist. 404 Not Found Client NoSuchWebsiteConfiguration The specified bucket does not have a website configuration. 404 Not Found Client NoSuchTagSet

The specified tag does not exist.

404 Not Found Client NoSuchUpload The specified multipart upload does not exist. The upload ID might not be valid, or the multipart upload might have been aborted or completed. 404 Not Found Client NoSuchVersion The version ID specified in the request does not match an existing version. 404 Not Found Client NotImplemented A header that you provided implies functionality that is not implemented. 501 Not Implemented Server NotModified The resource was not changed. 304 Not Modified Server NotSignedUp Your account is not signed up for the Amazon S3 service. You must sign up before you can use Amazon S3. You can sign up at the following URL: https://aws.amazon.com/s3 403 Forbidden Client OwnershipControlsNotFoundError The bucket ownership controls were not found. 404 Not Found Client OperationAborted A conflicting conditional operation is currently in progress against this resource. Try again. 409 Conflict Client PermanentRedirect The bucket that you are attempting to access must be addressed using the specified endpoint. Send all future requests to this endpoint. 301 Moved Permanently Client PreconditionFailed At least one of the preconditions that you specified did not hold. 412 Precondition Failed Client Redirect Temporary redirect. You are being redirected to the bucket while the Domain Name System (DNS) server is being updated. 307 Moved Temporarily Client RequestHeaderSectionTooLarge The request header and query parameters used to make the request exceed the maximum allowed size. 400 Bad Request Client RequestIsNotMultiPartContent A bucket POST request must be of the enclosure-type multipart/form-data. 400 Bad Request Client RequestTimeout Your socket connection to the server was not read from or written to within the timeout period. 400 Bad Request Client RequestTimeTooSkewed The difference between the request time and the server’s time is too large. 403 Forbidden Client RequestTorrentOfBucketError Requesting the torrent file of a bucket is not permitted. 400 Bad Request Client RestoreAlreadyInProgress The object restore is already in progress. 409 Conflict Client ServerSideEncryptionConfigurationNotFoundError The server-side encryption configuration was not found. 400 Bad Request Client ServiceUnavailable Service is unable to handle request. 503 Service Unavailable Server SignatureDoesNotMatch The request signature that the server calculated does not match the signature that you provided. Check your AWS secret access key and signing method. For more information, see REST Authentication and SOAP Authentication. 403 Forbidden Client SlowDown Reduce your request rate. 503 Slow Down Server TemporaryRedirect You are being redirected to the bucket while the Domain Name System (DNS) server is being updated. 307 Moved Temporarily Client TokenRefreshRequired The provided token must be refreshed. 400 Bad Request Client TooManyAccessPoints You have attempted to create more access points than are allowed for an account. For more information, see Amazon Simple Storage Service endpoints and quotas in the AWS General Reference. 400 Bad Request Client TooManyBuckets You have attempted to create more buckets than are allowed for an account. For more information, see Amazon Simple Storage Service endpoints and quotas in the AWS General Reference. 400 Bad Request Client TooManyMultiRegionAccessPointregionsError You have attempted to create a Multi-Region Access Point with more Regions than are allowed for an account. For more information, see Amazon Simple Storage Service endpoints and quotas in the AWS General Reference. 400 Bad Request Client TooManyMultiRegionAccessPoints You have attempted to create more Multi-Region Access Points than are allowed for an account. For more information, see Amazon Simple Storage Service endpoints and quotas in the AWS General Reference. 400 Bad Request Client UnexpectedContent This request contains unsupported content. 400 Bad Request Client UnresolvableGrantByEmailAddress The email address that you provided does not match any account on record. 400 Bad Request Client UserKeyMustBeSpecified The bucket POST request must contain the specified field name. If it is specified, check the order of the fields. 400 Bad Request Client NoSuchAccessPoint The specified access point does not exist. 404 Not Found Client InvalidTag Your request contains tag input that is not valid. For example, your request might contain duplicate keys, keys or values that are too long, or system tags. 400 Bad Request Client MalformedPolicy Your policy contains a principal that is not valid. 400 Bad Request Client

List of SELECT Object Content Error Codes

The following table contains special errors that SELECT Object Content might return. For general information about Amazon S3 errors and a list of error codes, see Error Responses.

Error Code Description HTTP Status Code SOAP Fault Code Prefix
Busy The service is unavailable. Try again later. 503 Client
CastFailed An attempt to convert from one data type to another using CAST failed in the SQL expression. 400 Client
ColumnTooLong The length of a column in the result is greater than maxCharsPerColumn of 1 MB. 400 Client
CSVEscapingRecordDelimiter A quoted record delimiter was found in the file. To allow quoted record delimiters, set AllowQuotedRecordDelimiter to ‘TRUE’ . 400 Client
CSVParsingError An error occurred while parsing the CSV file. Check the file and try again. 400 Client
CSVUnescapedQuote An unescaped quote was found while parsing the CSV file. To allow quoted record delimiters, set AllowQuotedRecordDelimiter to ‘TRUE’ . 400 Client
EmptyRequestBody The request body cannot be empty. 400 Client
ExpressionTooLong The SQL expression is too long. The maximum byte-length for an SQL expression is 256 KB. 400 Client
EvaluatorBindingDoesNotExist A column name or a path provided does not exist in the SQL expression. 400 Client
EvaluatorInvalidArguments There is an incorrect number of arguments in the function call in the SQL expression. 400 Client
EvaluatorInvalidTimestampFormatPattern The timestamp format string in the SQL expression is not valid. 400 Client
EvaluatorInvalidTimestampFormatPattern The timestamp format pattern requires additional fields in the SQL expression. 400 Client
EvaluatorTimestampFormatPatternDuplicateFields The timestamp format pattern contains multiple format specifiers representing the timestamp field in the SQL expression. 400 Client
EvaluatorTimestampFormatPatternHourClockAmPmMismatch The timestamp format pattern contains a 12-hour hour of day format symbol but doesn’t also contain an AM/PM field, or it contains a 24-hour hour of day format specifier and contains an AM/PM field in the SQL expression. 400 Client
EvaluatorInvalidTimestampFormatPatternSymbolForParsing The timestamp format pattern contains a valid format symbol that cannot be applied to timestamp parsing in the SQL expression. 400 Client
EvaluatorUnterminatedTimestampFormatPatternToken The timestamp format pattern contains an unterminated token in the SQL expression. 400 Client
EvaluatorInvalidTimestampFormatPatternToken The timestamp format pattern contains a token in the SQL expression that is not valid. 400 Client
EvaluatorInvalidTimestampFormatPatternSymbol The timestamp format pattern contains a symbol in the SQL expression that is not valid. 400 Client
IllegalSqlFunctionArgument An illegal argument was used in the SQL function. 400 Client
InternalError An internal error occurred. 500 Client
InvalidColumnIndex The column index in the SQL expression is not valid. 400 Client
InvalidCompressionFormat The file is not in a supported compression format. Only GZIP and BZIP2 are supported. 400 Client
InvalidExpressionType The ExpressionType value is not valid. Only SQL expressions are supported. 400 Client
InvalidFileHeaderInfo The FileHeaderInfo value is not valid. Only NONE , USE , and IGNORE are supported. 400 Client
InvalidKeyPath The key path in the SQL expression is not valid. 400 Client
InvalidJsonType The JsonType value is not valid. Only DOCUMENT and LINES are supported. 400 Client
InvalidQuoteFields The QuoteFields value is not valid. Only ALWAYS and ASNEEDED are supported. 400 Client
InvalidRequestParameter The value of a parameter in the SelectRequest element is not valid. Check the service API documentation and try again. 400 Client
OverMaxColumn The number of columns in the result is greater than the maximum allowable number of columns. 400 Client
OverMaxRecordSize The length of a record in the input or result is greater than the maxCharsPerRecord limit of 1 MB. 400 Client
TruncatedInput Object decompression failed. Check that the object is properly compressed using the format specified in the request. 400 Client
UnauthorizedAccess You are not authorized to perform this operation. 401 Client
ExternalEvalException The query cannot be evaluated. Check the file and try again. 400 Client
InvalidDataSource The data source type is not valid. Only CSV, JSON, and Parquet are supported. 400 Client
InvalidDataType The SQL expression contains a data type that is not valid. 400 Client
InvalidTableAlias The SQL expression contains a table alias that is not valid. 400 Client
InvalidTextEncoding The encoding type is not valid. Only UTF-8 encoding is supported. 400 Client
JSONParsingError An error occurred while parsing the JSON file. Check the file and try again. 400 Client
UnrecognizedFormatException We encountered a record type that is not valid. 400 Client
MalformedXML The XML provided was not well formed or did not validate against our published schema. Check the service documentation and try again. 400 Client
MissingRequiredParameter The SelectRequest entity is missing a required parameter. Check the service documentation and try again. 400 Client
MultipleDataSourcesUnsupported Multiple data sources are not supported. 400 Client
ObjectSerializationConflict InputSerialization specifies more than one format (CSV, JSON, or Parquet), or OutputSerialization specifies more than one format (CSV or JSON). For InputSerialization and OutputSerialization , you can specify only one format for each. 400 Client
UnsupportedFunction We encountered an unsupported SQL function. 400 Client
UnsupportedSqlOperation We encountered an unsupported SQL operation. 400 Client
UnsupportedSqlStructure We encountered an unsupported SQL structure. Check the SQL Reference. 400 Client
UnsupportedStorageClass We encountered a storage class that is not supported. Only STANDARD , STANDARD_IA , and ONEZONE_IA storage classes are supported. 400 Client
UnsupportedSyntax We encountered syntax that is not valid. 400 Client
UnsupportedRangeHeader A range header is not supported for this operation. 400 Client
LexerInvalidChar The SQL expression contains a character that is not valid. 400 Client
LexerInvalidOperator The SQL expression contains a literal that is not valid. 400 Client
LexerInvalidLiteral The SQL expression contains an operator that is not valid. 400 Client
LexerInvalidIONLiteral The SQL expression contains an operator that is not valid. 400 Client
ParseExpectedDatePart The expected date part in the SQL expression was not found. 400 Client
ParseExpectedKeyword The expected keyword in the SQL expression was not found. 400 Client
ParseExpectedTokenType The expected token in the SQL expression was not found. 400 Client
ParseExpected2TokenTypes The expected token in the SQL expression was not found. 400 Client
ParseExpectedNumber The expected number in the SQL expression was not found. 400 Client
ParseExpectedRightParenBuiltinFunctionCall The expected right parenthesis character in the SQL expression was not found. 400 Client
ParseExpectedTypeName The expected type name in the SQL expression was not found. 400 Client
ParseExpectedWhenClause The expected WHEN clause in the SQL expression was not found. CASE is not supported. 400 Client
ParseUnsupportedToken The SQL expression contains an unsupported token. 400 Client
ParseUnsupportedLiteralsGroupBy The SQL expression contains an unsupported use of GROUP BY . 400 Client
ParseExpectedMember The SQL expression contains an unsupported use of MEMBER . 400 Client
ParseUnsupportedSelect The SQL expression contains an unsupported use of SELECT . 400 Client
ParseUnsupportedCase The SQL expression contains an unsupported use of CASE . 400 Client
ParseUnsupportedCaseClause The SQL expression contains an unsupported use of CASE . 400 Client
ParseUnsupportedAlias The SQL expression contains an unsupported use of ALIAS . 400 Client
ParseUnsupportedSyntax The SQL expression contains unsupported syntax. 400 Client
ParseUnknownOperator The SQL expression contains an operator that is not valid. 400 Client
ParseInvalidPathComponent The SQL expression contains a path component that is not valid. 400 Client
ParseMissingIdentAfterAt The expected identifier after the @ symbol in the SQL expression was not found. 400 Client
ParseUnexpectedOperator The SQL expression contains an unexpected operator. 400 Client
ParseUnexpectedTerm The SQL expression contains an unexpected term. 400 Client
ParseUnexpectedToken The SQL expression contains an unexpected token. 400 Client
ParseUnExpectedKeyword The SQL expression contains an unexpected keyword. 400 Client
ParseExpectedExpression The expected SQL expression was not found. 400 Client
ParseExpectedLeftParenAfterCast The expected left parenthesis after CAST in the SQL expression was not found. 400 Client
ParseExpectedLeftParenValueConstructor The expected left parenthesis in the SQL expression was not found. 400 Client
ParseExpectedLeftParenBuiltinFunctionCall The expected left parenthesis in the SQL expression was not found. 400 Client
ParseExpectedArgumentDelimiter The expected argument delimiter in the SQL expression was not found. 400 Client
ParseCastArity The SQL expression CAST has incorrect arity. 400 Client
ParseInvalidTypeParam The SQL expression contains a parameter value that is not valid. 400 Client
ParseEmptySelect The SQL expression contains an empty SELECT clause. 400 Client
ParseSelectMissingFrom The SQL expression contains a missing FROM after the SELECT list. 400 Client
ParseExpectedIdentForGroupName GROUP is not supported in the SQL expression. 400 Client
ParseExpectedIdentForAlias The expected identifier for the alias in the SQL expression was not found. 400 Client
ParseUnsupportedCallWithStar Only COUNT with (*) as a parameter is supported in the SQL expression. 400 Client
ParseNonUnaryAgregateFunctionCall Only one argument is supported for aggregate functions in the SQL expression. 400 Client
ParseMalformedJoin JOIN is not supported in the SQL expression. 400 Client
ParseExpectedIdentForAt The expected identifier for AT name in the SQL expression was not found. 400 Client
ParseAsteriskIsNotAloneInSelectList Other expressions are not allowed in the SELECT list when * is used without dot notation in the SQL expression. 400 Client
ParseCannotMixSqbAndWildcardInSelectList Cannot mix [] and * in the same expression in a SELECT list in the SQL expression. 400 Client
ParseInvalidContextForWildcardInSelectList The use of * in the SELECT list in the SQL expression is not valid. 400 Client
ValueParseFailure A timestamp parse failure occurred in the SQL expression. 400 Client
IncorrectSqlFunctionArgumentType An incorrect argument type was specified in a function call in the SQL expression. 400 Client
AmbiguousFieldName The field name matches to multiple fields in the file. Check the SQL expression and the file, and try again. 400 Client
ValueParseFailure A timestamp parse failure occurred in the SQL expression. 400 Client
IntegerOverflow An integer overflow or underflow occurred in the SQL expression. 400 Client
LikeInvalidInputs The argument given to the LIKE clause in the SQL expression is not valid. 400 Client
InvalidCast An attempt to convert from one data type to another using CAST failed in the SQL expression. 400 Client
ParquetParsingError An error occurred while parsing the Parquet file. Check the file and try again. 400 Client
NumberFormatError An error occurred while parsing a number. This error can be caused by underflow or overflow of integers. 400 Client
EvaluatorLikePatternInvalidEscapeSequence An argument given to the LIKE expression was not valid. 400 Client
EvaluatorNegativeLimit LIMIT must not be negative. 400 Client
OverMaxParquetBlockSize The Parquet file is above the max row group size. 400 Client
UnsupportedParquetType The specified Parquet type is not supported. 400 Client
UnsupportedTypeForQuerying Your query contains an unsupported type for comparison (e.g. verifying that a Parquet INT96 column type is greater than 0). 400 Client
ParquetUnsupportedCompressionCodec The specified Parquet compression codec is not supported. 400 Client
UnsupportedScanRangeInput Scan range queries are not supported on this type of object. 400 Client
InvalidScanRange The provided scan range is not valid. 400 Client

The following table contains special errors that the Replication operation might return. For general information about Amazon S3 errors and a list of error codes, see Error Responses.

This error might occur for the following reasons:

Источник

Читайте также:  Error loading python dll loadlibrary не найден указанный модуль
Smartadm.ru
Adblock
detector
Error Code Description HTTP Status Code SOAP Fault Code Prefix
InvalidArgument