0016-00000834

Updated at:

Problem description

The value of the MaxSkippedRecordsAllowed element in the XML request body of the SelectObject request is invalid.

Causes

This error occurs when a SelectObject request contains an invalid value for the MaxSkippedRecordsAllowed element in the XML request body.

Examples

In the following request, the value of the MaxSkippedRecordsAllowed element is abc, which is not a valid positive integer.

POST /oss-select/bigcsv_normal.csv?x-oss-process=csv%2Fselect HTTP/1.1
Date: Fri, 25 May 2018 22:11:39 GMT
Authorization: OSS qn6q**************:77Dv****************
Range: bytes=1024-2048
Host: host name
<?xml version="1.0"?>
<SelectRequest>
    <Expression>...</Expression>
    <InputSerialization>
        ......
    </InputSerialization>
    <OutputSerialization>
        ......
    </OutputSerialization>
    <Options>
    	<MaxSkippedRecordsAllowed>
      	abc
      </MaxSkippedRecordsAllowed>
    </Options>
</SelectRequest>

Solutions

Ensure that the value of the MaxSkippedRecordsAllowed element in the XML request body is an integer greater than or equal to 0. The default value is 0.

This parameter specifies the maximum number of rows that can be skipped. A row is skipped if it does not match the data type specified in the SQL statement, or if data is missing from one or more columns and SkipPartialDataRecord is set to True. If the number of skipped rows exceeds the value of this parameter, OSS stops processing and reports an error.

If a row is an invalid CSV row, for example, if a column contains an odd number of consecutive quote characters, OSS immediately stops processing and reports an error. This type of error can affect the parsing of the entire CSV file. You can use this parameter to adjust the tolerance for irregular data, but not for invalid CSV files.

References