Resizing a Graph

This API is used to resize a graph instance.

POST /v1.0/{project_id}/graphs/{graph_id}/resize

**Table 1** URI parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID, which is used for resource isolation. For details, see Obtaining a Project ID.
graph_id	Yes	String	Graph ID

**Table 2** Parameters in the request header
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	User token. The token can be obtained by calling the IAM API. (The token is the value of X-Subject-Token in the response header.)

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
resize	Yes	GraphSizeTypeIndexReq object	Resize is an object.

**Table 4** GraphSizeTypeIndexReq
Parameter	Mandatory	Type	Description
graphSizeTypeIndex	Yes	String	Graph flavor type. Currently, the value can be 2, 3, 4, or 5, indicating that a graph can be scaled out to support 10 million, 100 million, 1 billion, or 10 billion edges, respectively.

Status code: 200

**Table 5** Response body parameters
Parameter	Type	Description
errorMessage	String	System prompt. If execution succeeds, this parameter may be left blank. If execution fails, this parameter is used to display the error message.
errorCode	String	System prompt. If execution succeeds, this parameter may be left blank. If execution fails, this parameter is used to display the error code.
jobId	String	Indicates the ID of the resize job. This parameter is left blank when the request fails. NOTE: You can view the job execution status and obtain the return result by querying the job ID. For details, see Job Management APIs.

POST http://Endpoint/v1.0/{project_id}/graphs/{graph_id}/resize

{
  "resize" : {
    "graphSizeTypeIndex" : "2"
  }
}

Status code: 200

{ }

Status code: 400

Bad Request

{
  "errorCode" : "GES.7001",
  "errorMessage" : "The graph is not running."
}

Status Code	Description
200	OK
400	Bad Request

Parent topic: Graph Management APIs

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.