OpenSearch:Error codes

Error code

Description

1000

A timeout error occurs. Try again and check whether the error persists. If the error persists, submit a ticket.

2112

The field referenced in a feature function, such as text_relevance(field) or fieldterm_proximity(field), in a sort expression is not a source index field of a query. This error does not affect search results.

3007

The frequency at which API operations are called to push data exceeds the limit. We recommend that you call API operations at an appropriate frequency.

4003

Use the sample document to check whether the same signature result is returned. This method can be used to check whether the error is caused by the signature algorithm. If the error is not caused by the signature algorithm, check whether the common parameters in uppercase rank before the request parameters in lowercase after all these parameters are sorted in alphabetical order. In addition, check whether encoding rules such as rules about spaces are followed. For more information, see the authorization documentation.

4007

Failed to parse the format because JSON fields contain double quotation marks (") or non-printable characters. In this case, escape the characters or specify a filter condition and try again.

4010

Invalid timestamp. A timestamp has a validity period. Set the TimeStamp parameter based on the current time in the valid format.

5001

The user does not exist. Generally, this error occurs because the AccessKey pair or API endpoint is invalid. Make sure that the AccessKey pair and API endpoint are valid and try again. To view the API endpoint, perform the following operations: Log on to the OpenSearch console. In the left-side navigation pane, click Instance Management. Find the application that you want to manage and click Manage in the Actions column. In the API Endpoint section of the Instance Details page, view the API endpoint.

5008

OpenSearch verifies your identity by using the AccessKey pair. Make sure that your AccessKey pair is enabled. You can create or delete an AccessKey pair on the AccessKey Pair page of the Resource Access Management (RAM) console.

6013

The sum of the values of the start and hit parameters exceeds 5000 and no result is returned. For requests in which the sum of the values of the start and hit parameters exceeds 5000, use the SCROLL operation. For more information, see the API reference.

6015

The request is discarded because the number of logical computing units (LCUs) consumed per second exceeds the purchased quota. To increase the quota, log on to the OpenSearch console, find the application that you want to manage on the Instance Management page. Choose More > Scale Up in the Actions column. On the page that appears, increase the computing resource quota.

6127

The fields referenced in clauses other than query clauses are not configured as attribute fields for use. Modify the application schema and try again. You can configure the attribute fields by performing offline changes.

7500

An internal error occurs. Submit a ticket.

Error code

Description

1000

An internal error occurs.

1001

The template is not found.

1003

Invalid index type.

1004

The service is unavailable. Try again later.

Error code

Description

2001

The specified application is not found.

2002

The specified application already exists.

2003

The number of applications exceeds the upper limit.

2004

Invalid application name. The application name can be up to 30 characters in length, and can contain digits, letters, and underscores (_).

2005

The application name is required.

2006

The new application name is required.

2007

The description exceeds the upper limit in length. The description can be up to 300 characters in length.

2008

Invalid summary parameter.

2009

Failed to update the status of the application.

2010

The application is paused.

2011

The application is frozen.

2012

The application is not started.

2013

Failed to delete the application because the application does not exist.

2014

Failed to upload the file.

2016

The region is required.

2017

The application does not reside in the current region.

2099

This operation is unavailable.

2101

The expression does not exist.

2102

The expression name already exists.

2103

The number of expressions in the application exceeds the upper limit.

2104

Invalid expression name. The expression name can be up to 30 characters in length, and can contain digits, letters, and underscores (_).

2105

The expression name is required.

2106

The new expression name is required.

2107

The length of the expression description exceeds the upper limit. The description can be up to 300 characters in length.

2108

Invalid format of the expression description.

2109

Invalid expression format.

2110

The expression exceeds the upper limit in length.

2111

The expression ID is required.

2112

Invalid expression.

2113

The expression is required.

2114

An operation error occurs.

2201

The name of the rough sort expression is required.

2202

The name of the rough sort expression already exists.

2203

The number of rough sort expressions exceeds the upper limit.

2204

Invalid name of the rough sort expression. The name can contain only digits, letters, and underscores (_).

2205

The name of the rough sort expression exceeds the upper limit in length.

2206

The fields used for rough sort are not of numeric types.

2207

The rough sort expression does not exist.

2208

Invalid rough sort expression. Make sure that fields are specified in the rough sort expression.

2209

Invalid weight configuration in the rough sort expression. Make sure that a weight value is a non-zero numeric value that ranges from -100000 to 100000. A numeric value of the FLOAT type can be precise to six decimal places.

2210

The name is used by the default rough sort expression in the system.

2211

The parameter value in the timeliness() function is not of the INT type.

2112

Invalid sort expression.

2551

The drop-down suggestion rule specified in the query does not exist.

Error code

Description

3001

The document is required.

3002

The document size exceeds the upper limit.

3003

The number of documents exceeds the upper limit.

3004

Failed to save the document.

3005

Invalid document format.

3006

The command that is used to process the document is invalid.

3007

Excessive requests are submitted in a short period of time.

3008

The document size is excessively large.

3009

The document ID is required.

3011

After an ApsaraDB RDS for MySQL or MySQL data source is configured, operations are called to push documents, which is not supported.

3012

The specified resource is not found.

3013

The rate at which documents are pushed exceeds the maximum threshold specified in the application.

3014

The rate at which documents are pushed exceeds the system limit.

3015

The number of documents that are pushed each time exceeds the upper limit.

3016

The total number of documents in the application exceeds the upper limit.

Error code

Description

4001

Failed to authenticate the request.

4002

The signature is required.

4003

Failed to verify the signature.

4004

The SignatureNonce parameter is required.

4005

The value of the SignatureNonce parameter is not unique.

4006

The SignatureNonce verification fails.

4007

Failed to parse the JSON format.

4008

The username is required. Check whether the domain name is correct.

4009

The user ID is required.

4010

Invalid timestamp.

4011

This operation is not allowed for a demo account.

4012

The specified table does not exist.

4013

Invalid timestamp format.

4014

The Timestamp parameter is required.

4020

Failed to authenticate the RAM user.

Error code

Description

5001

The user is not found.

5002

Invalid username.

5003

You have not logged on.

5008

The AccessKey pair is disabled.

5100

You are not authorized to perform operations in this region.

5004

You have overdue payments.

5005

OpenSearch is not activated. Go to the Alibaba Cloud official website to activate the service.

5006

The specified application is frozen due to overdue payments.

5008

The AccessKey pair is disabled.

5009

The user is deleted.

5010

The AccessKey pair is disabled.

5011

Multiple users are registered by using the same email address.

5012

CODE_USER_ALIYUN_USER_ID_INVALID. No error message is returned.

5013

CODE_USER_ALIYUN_BID_INVALID. No error message is returned.

5014

CODE_USER_CLIENT_ID_INVALID. No error message is returned.

5015

CODE_USER_ID_INVALID. No error message is returned.

5100

You are not authorized to perform operations in this region.

Error code

Description

6001

Search queries are required.

6002

The keyword used to search for a key is invalid.

6003

The keyword used to search for a field is invalid.

6004

Complex queries are required.

6005

Invalid field.

6006

Excessive application names are contained in the request.

6007

The total number of indexes in each template for a multi-index query exceeds the upper limit.

6008

Failed to parse the request due to a syntax error.

6009

The query clause is too long.

6010

Invalid rerank size.

6011

Invalid SignatureNonce format.

6013

The sum of the values of the start and hit parameters exceeds the upper limit.

6014

The request is discarded because the system is busy.

6015

The request is discarded because the LCUs of computing resources exceed the purchased quota.

6016

The number of query hits exceeds the upper limit.

6017

The scroll parameter is specified, but the search_type parameter is not set to scan.

6018

The scroll parameter is specified, but the search_type parameter is not specified.

6019

Failed to parse the scroll_id parameter.

6020

Invalid value of the scroll parameter.

6021

The aggregate, sort, or distinct clause is not supported by scroll requests.

6022

The value of the scroll_id parameter has expired.

6024

Invalid value of the hit parameter in the drop-down suggestion.

6031

Invalid value of the abtest parameter.

6033

Invalid value of the re_search parameter.

6034

Invalid value of the biz parameter.

6100

The search query is required.

6101

The index field of the query does not exist.

6102

Invalid numeric value range in the query clause.

6103

The return value of the expression in the filter clause is not of the BOOLEAN type.

6104

The return value of the expression in the sort clause is of the BOOLEAN type.

6105

Same expressions are contained in the sort clause.

6106

Invalid query.

6107

The return value of the statistical function is of the BOOLEAN or STRING type.

6108

The range specified in the statistical function is not in ascending order.

6109

The data type of the value returned by the range expression in the statistical function is invalid.

6110

The statistical function does not exist.

6111

Invalid statistical function.

6112

Invalid query clause.

6113

Invalid filter clause.

6114

Invalid aggregate clause.

6115

Invalid sort clause.

6116

Invalid distinct clause.

6117

The query contains unknown clauses.

6118

A syntax error occurs.

6119

Invalid value of the dist_count parameter in the distinct clause. The value must be an integer greater than 0.

6120

Invalid value of the dist_times parameter in the distinct clause. The value must be an integer greater than 0.

6121

Invalid value of the reserved parameter in the distinct clause. The parameter must be set to true or false.

6122

The distinct_key parameter is not specified in the distinct clause.

6123

Invalid value of the grade parameter in the distinct clause. For example, this parameter is left empty or set to a non-numeric value.

6124

Invalid value of the distinct parameter in the distinct clause. The value must be within the range of (0,2].

6125

Invalid value of the max_item_count parameter in the distinct clause. The value must be an integer greater than 0.

6126

Invalid value of the update_total_hit parameter in the distinct clause. The parameter must be set to true or false.

6127

The request contains undefined attribute fields. Modify the application schema and try again. You can configure the attribute fields by performing offline changes.

6128

The data types of the operands that surround the binary operator in the expression are different.

6129

The operands that surround the binary operator in the expression are constants at the same time.

6130

Invalid value type of the binary logic operation expression. The value must be of the BOOLEAN type.

6131

The values in the binary expression are of the STRING type, which is not supported.

6132

The values in the binary expression are of the ARRAY type, which is not supported.

6133

Invalid value type of the bit manipulation.

6134

Invalid data type of the value returned by the constant expression.

6135

Invalid value type of the constant expression.

6140

Aggregate clause syntax error.

The field type is LITERAL, and the SUM function is not supported.

6300

The values in the constant expression are not integers or floating-point numbers.

6301

The operands on which you want to perform bitwise negation are not integers.

6302

The operands on which you want to perform negation are not numbers.

6303

The operands on which you want to perform logical NOT operations are not numbers.

6304

Invalid data type of the operand on which the binary operation is performed.

6305

Invalid binary operator.

6306

Invalid parameter type of the function.

6307

The function is undefined.

6308

Invalid number of parameters in the function.

6309

Invalid array function.

6310

No field can be filtered.

6311

An array field is used as a single-value field.

6312

A single-value field is used as an array field.

6313

Invalid subscript value of the array field. Make sure that the subscript value is not less than 0.

6314

Invalid field type.

6315

The parameter that specifies an index field does not exist.

6316

The index is required in the query.

6317

A formula is used more than once in the filter clause. Make sure that each formula is used only once in a filter clause.

6318

Failed to parse the formula syntax.

6400

The sort script does not exist.

6450

An error occurs when the script is being used.

6500

The search syntax contains fields that do not exist.

6501

No index data is contained in the online system.

6502

Invalid query syntax.

6503

The default operator OR is not supported.

6504

Accurate statistics are not supported.

6505

Invalid rank size.

6506

An excessive number of terms are obtained after query analysis.

6601

An index field is contained in more than one rule. Make sure that each index field is contained only in one rule.

6602

No search query is specified. For example, default:" is specified.

6603

The index field in the query is not specified in the query analysis rule.

6604

The keyword is not enclosed in single quotation marks ('). For example, default:xxx is specified. The valid form is default:'xxx'.

6605

The keyword is enclosed in double quotation marks ("). In this case, query analysis rules cannot be configured.

6606

The search query does not contain the index that needs to be analyzed.

6607

Invalid format of the disable parameter.

6608

The index field to be disabled based on the disable parameter does not exist.

6609

A list of features to be disabled based on the disable parameter does not exist.

6610

The query obtained after query analysis is empty. This may be caused because the original query is empty or the original query contains only stop words.

6611

The index field is required in the query.

6612

term_weight makeup data fail. The intervention data does not take effect.

6613

The number of terms in the query clause exceeds the upper limit. The maximum number of terms in a query clause is 256.

Error code

Description

7202

Invalid command. Only UPDATE, ADD, and DELETE commands are supported.

7301

The primary key field of the document is not found. Failed to push the data because the primary key value of the document is not found.

7302

The data type does not match. Failed to push the data because the primary key value of the document is invalid.

7303

The document contains multiple primary key values. Failed to push the data because multiple primary key values are contained in the document.

7304

The primary key value of the document is required. Failed to push the data because the primary key value of the document is empty.

7305

Table data that does not belong to the application is pushed. Failed to push the data because the table name does not exist in the current application.

7500

An internal error occurs. Submit a ticket.

7520

Failed to push the data because the size of a single document exceeds 1 MB, which is the upper limit specified by the system.

7503

Failed to push the data because the field value that is obtained by using the JSON plug-in is not in the JSON format. Check and try again.

7504

Failed to push data because the key corresponding to the field value that is obtained by using the JSON plug-in does not exist.

7505

A configuration error occurs in content conversion by using the TairLDBExtractor plug-in. As a result, the connection to Tair fails. Check whether the configuration ID or namespace is valid.

7510

Failed to push data because an error occurs in field processing by using the KeyValueExtractor plug-in.

7515

An error occurs when the filter condition is being executed.

7523

Failed to push data because an error occurs in data processing by using the StringConnector plug-in.

7524

The value of the geo field is outside the value range. The longitude or latitude value of the range field is outside the value range. The longitude value must be greater than 180, and the latitude value must be greater than 90.

7525

The formats of the geo and range fields are invalid.

7601

An error occurs when the task is running. Submit a ticket.

7602

No data is contained in the MaxCompute table. Make sure that data can be generated in the MaxCompute table partitions and try again.

7607

You have no permissions on the MaxCompute table.

7603

An error occurs when an ApsaraDB RDS for MySQL or PolarDB for MySQL data source is being configured.

7605

A configuration error occurs in Taobao Distributed Data Layer (TDDL).

7608

A source field does not exist in the MySQL data source.

7803

Failed to push data because the document to be updated does not exist.

7805

Failed to push data because an error occurs in data processing by using the HTML plug-in.

7807

The field type and value do not match. As a result, the field type fails to be converted. The missing value is to imputed with a default value.

73106

The number of data push operations exceeds the upper limit. Increase the quota.

7620

An execution timeout error occurs when the data source is being queried.

Error code

Description

8001

Failed to save the error message.

8002

The required parameters are missing.

8003

The application does not exist.

8004

One or more parameters are invalid.

Error code

Description

9001

The username is required.

9002

The application name is required.

9003

Invalid template name. The template name can contain only digits, letters, and underscores (_).

9004

The template name cannot exceed 30 characters in length.

9005

An error occurs when you query the template information.

9006

The template name already exists.

9007

An error occurs when you insert data into the template.

9008

Invalid data.

9009

The number of fields that can be defined exceeds the upper limit specified in the system.

9010

The name of this field is reserved.

9011

The field name already exists.

9012

The index name does not meet the requirements. An index name can be up to 30 characters in length. It can contain digits, letters, and underscores (_), and must start with a letter. The multi-value field cannot be of the SWS_TEXT or TEXT type.

9013

Arrays are not supported.

9014

Primary keys are not supported.

9015

The primary key is required.

9016

The primary key is not unique.

9017

Failed to update the information.

9018

Failed to delete the information.

9019

The number of search fields exceeds the upper limit. The maximum number of search fields that contain multiple index fields is four.

9020

An index field of the STRING or TEXT type is used in multiple single-field search fields.

9021

The index name does not meet the requirements. An index name can be up to 30 characters in length. It can contain digits, letters, and underscores (_), and must start with a letter.

9022

An association is established with this table.

9023

The index name contains different types of fields, which is not allowed.

9100

An internal error occurs.

9101

The quantity of the field exceeds the upper limit.

9102

This data source is not used.

9103

Invalid connection to a secondary table.

9104

The number of association levels exceeds the upper limit. The maximum number of association levels is two.

9105

The template to be checked does not exist.

9501

The username is required.

9502

The application name is required.

9519

The template is required.

9600

An internal error occurs.

9902

Invalid field type of the plug-in.

9999

This service is unavailable for this domain name.

Error code

Description

10001

Failed to obtain the TDDL information because the TDDL group key is not specified.

10002

Failed to obtain the field or the table does not exist.

10011

Failed to connect to Aggregator.

10012

The application contains documents.

10013

The application schema is not a custom one.

10110

The task is complete.

10010

Specific data sources contain invalid data. The invalid data is ignored.

10014

Invalid data source type.

10100

Failed to create the task. Specific tasks are in process.

10101

The application ID is required.

10106

The application ID is required.

10107

The application ID is required.

10102

Invalid action.

10112

The number of documents exceeds the upper limit.

10201

Failed to obtain the quota list.

10202

Failed to update the quota.

10301

One or more required parameters are not specified or their formats are invalid.

10302

Invalid time parameter.

10303

The data source is required.

10304

The quota for this table exceeds the upper limit.

10305

Invalid Object Storage Service (OSS) parameter.

10306

Invalid name of the OSS bucket.

10307

Invalid OSS record type.

10308

The log feature of the OSS bucket is disabled.

10309

Specific tasks are in process.

10310

The application is not running. Tasks cannot be created.

10311

Invalid time range.

10312

The application description exceeds the upper limit in length. The application description can be up to 600 characters in length.

10313

Invalid OSS content format.

10314

Failed to access the access control list (ACL) in the region in which the OSS bucket resides.

10315

Invalid endpoint of the OSS bucket.

10330

Data source parameters are invalid.

10350

Failed to connect to the MaxCompute data source.

10351

An error occurs in the MaxCompute data source.

10400

Invalid prefix of the OSS bucket name.

10450

The field does not exist.

4007

Failed to parse the JSON format.