Rolling Back a Transaction
Function
This API is used to roll back a transaction.
URI
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For how to obtain the project ID, see Obtaining a Project ID. |
graph_name |
Yes |
String |
Graph name |
commit |
Yes |
String |
Transaction ID, which is obtained by calling the transaction creation API. |
Request Parameters
None
Response Parameters
Parameter |
Type |
Description |
---|---|---|
errorMessage |
String |
System prompt
|
errorCode |
String |
System prompt
|
result |
String |
Transaction creation result. The value is success for a successful request and failed for a failed request. |
Example Request
Delete a transaction.
DELETE http://{SERVER_URL}/ges/v1.0/{project_id}/graphs/{graph_name}/transaction/{commit}
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
{ "result": "success" }
Status code: 400
{ "errorMessage": "Graph [11-moie] does not exist, please check projectId and graphName.", "errorCode": "GES.8000", "result": "failed" }
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
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