Querying General Information About a Graph
Function
This API is used to query the general information about a graph, such as the numbers of vertices and edges.
URI
GET /ges/v1.0/{project_id}/graphs/{graph_name}/summary?label_details={labelDetails}
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 |
labelDetails |
No |
Boolean |
Whether to return the number of vertices and edges under each label. The default value is false. If this parameter is set to true, the numbers of vertices and edges under each label are returned. |
Example Request
Query general information about a graph, such as the numbers of vertices and edges. The value true indicates that the numbers of vertices and edges of different labels are returned.
GET http://{SERVER_URL}/ges/v1.0/{project_id}/graphs/{graph_name}/summary?label_details=true
SERVER_URL: Address for accessing a graph. For details about its value, see Using Service Plane APIs.
Response Parameters
Parameter |
Type |
Description |
---|---|---|
errorMessage |
String |
System prompt.
|
errorCode |
String |
System prompt.
|
jobId |
String |
ID of an asynchronous job You can view the job execution status and obtain the return result by querying the job ID. For details, see Querying Job Status on the Service Plane. |
Example Response
Status code: 200
Http Status Code: 200 { "jobId": "f99f60f1-bba6-4cde-bd1a-ff4bdd1fd500000168232" }
Status code: 400
Http Status Code: 400 { "errorMessage": "graph [demo] is not found", "errorCode": "GES.8001" }
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.