Batch Deleting Vertices (2.1.9)
Function
This API is used to delete vertices in batches based on the vertex IDs.
URI
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For details about how to obtain the project ID, see Obtaining a Project ID. |
graph_name |
Yes |
String |
Graph name |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
vertices |
Yes |
String |
IDs of the vertices to delete |
ignoreError (2.2.28) |
No |
Boolean |
Whether to ignore errors, for example, the vertices you want to delete does not exist. The value can be true or false. The default value is false, indicating that errors will not be ignored. Note that JSON format errors will not be ignored. |
Response Parameters
Parameter |
Type |
Description |
---|---|---|
errorMessage |
String |
System prompt.
|
errorCode |
String |
System prompt.
|
result |
String |
Request result. If the request is successful, the value is success. If the request fails, the value is failed. |
Example Request
Delete vertices in batches by vertex ID. The IDs of the vertices to delete are Vivian and 46.
POST http://{SERVER_URL}/ges/v1.0/{project_id}/graphs/{graph_name}/vertices/action?action_id=batch-delete { "vertices": [ "Vivian", "46" ], "ignoreError": true }
SERVER_URL: Address for accessing a graph. For details about its value, see Using Service Plane APIs.
Example Response
Status code: 200
Example response for a successful request
Http Status Code: 200 { "result": "success" }
Status code: 400
Http Status Code: 400 { "errorMessage": " Bad Request, parameter vertices cannot be null", "errorCode": "GES.8214" }
Status Codes
Return Value |
Description |
---|---|
400 Bad Request |
Request error. |
401 Unauthorized |
Authentication failed. |
403 Forbidden |
No operation permissions. |
404 Not Found |
No resources found. |
500 Internal Server Error |
Internal server error. |
503 Service Unavailable |
Service unavailable. |
Error Code
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot