Batch Updating Vertex Properties
Function
This API is used to update vertex properties in batches.
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 |
actionId |
Yes |
String |
Operator. Possible values:
|
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
vertices |
Yes |
Json |
Vertex array to be updated For details about this array, see the vertices parameters. |
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
Update vertex properties in batches. The vertex names to be updated are 150 and 6.
POST http://{SERVER_URL}/ges/v1.0/{project_id}/graphs/{graph_name}/vertices/properties/action?action_id=batch-update { "vertices": [ { "vertex": "150", "label": "movie", "properties": { "movieid": [ "150" ], "title": [ "testmoive" ], "genres": [ "Comedy" ] } }, { "vertex": "6", "properties": { "title": [ "testmoive_exist_id" ], "genres": [ "Comedy" ] } } ], }
SERVER_URL: Address for accessing a graph. For details about its value, see Using Service Plane APIs.
Example Response
Status code: 200
Http Status Code: 200 { "result": "success" }
Status code: 400
Example response for a failed request
Http Status Code: 400 { "errorMessage":"vertex [Lily] does not exist", "errorCode":"GES.8220" }
Status Codes
Return Value |
Description |
---|---|
400 Bad Request |
Request error. |
401 Unauthorized |
Authorization 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 Codes
See Error Codes.
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