# NebulaGraph Database Developer Edition documentation

Documentation version: v5.3.2

## Pages

- [Adamic-Adar](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/adamic_adar.md): Adamic-Adar uses common neighbors to determine how likely two nodes are to connect. The score is higher when the nodes share more common neighbors, especially when those neighbors  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/adamic_adar/))
- [All-Pairs Shortest Path](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/all_pairs_shortest_path.md): All-pairs shortest path computes shortest distances between every pair of nodes in the graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/all_pairs_shortest_path/))
- [A* Shortest Path](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/astar_shortest_path.md): A* shortest path uses a best-first strategy with a heuristic score to find an efficient route from source to target. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/astar_shortest_path/))
- [Betweenness Centrality](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/betweenness_centrality.md): Betweenness centrality quantifies how often a node lies on shortest paths between other node pairs. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/betweenness_centrality/))
- [Breadth-First Search (BFS)](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/bfs.md): Breadth-First Search explores a graph level by level from a given source node. In an unweighted graph, BFS computes the shortest-path distance (in number of hops) from the source t ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/bfs/))
- [Closeness Centrality](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/closeness_centrality.md): Closeness centrality evaluates how near a node is to all other reachable nodes via shortest path distances. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/closeness_centrality/))
- [Clustering Coefficient](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/clustering_coefficient.md): Clustering coefficient measures how tightly a node's neighbors are connected with each other. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/clustering_coefficient/))
- [Common Neighbors](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/common_neighbors.md): Common neighbors predicts potential links by counting shared neighbors between node pairs. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/common_neighbors/))
- [Cosine Similarity](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/cosine_similarity.md): Cosine similarity computes pairwise similarity scores from vector directions in embedding space. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/cosine_similarity/))
- [Cycle Detection](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/cycle_detection.md): Cycle detection finds closed paths in a directed graph, where each path starts and ends at the same node and follows edge directions. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/cycle_detection/))
- [Degree Centrality](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/degree_centrality.md): Degree centrality measures node importance by counting incident edges. Nodes with higher degree are considered more influential, as they have more direct connections to other nodes ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/degree_centrality/))
- [Depth-First Search](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/depth_first_search.md): Depth-first search explores graph paths by expanding one branch deeply before backtracking. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/depth_first_search/))
- [Dijkstra Shortest Path](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/dijkstra_shortest_path.md): Dijkstra shortest path computes the minimum path cost from a source node to all reachable nodes on non-negative weighted graphs. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/dijkstra_shortest_path/))
- [FastRP](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/fastrp.md): FastRP (Fast Random Projection) is a scalable graph embedding algorithm. It maps each node to a dense vector, and structurally similar nodes tend to have similar vectors. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/fastrp/))
- [GraphSAGE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/graphsage.md): GraphSAGE generates node embeddings by aggregating neighborhood features layer by layer. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/graphsage/))
- [HANP](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/hanp.md): HANP performs weighted label propagation with neighborhood influence to detect communities. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/hanp/))
- [HITS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/hits.md): HITS jointly computes hub and authority scores based on mutually reinforcing link structures. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/hits/))
- [Algorithms overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/index.md): The following algorithms are grouped by the problem they solve. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/))
- [Infomap](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/infomap.md): Infomap optimizes flow-based code length and partitions nodes into communities with efficient random-walk encoding. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/infomap/))
- [Jaccard Similarity](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/jaccard.md): The Jaccard similarity algorithm is a measure of similarity coefficient between two sets. The Jaccard similarity coefficient, also known as the Jaccard index, is a statistical meas ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/jaccard/))
- [K-Core](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/k_core.md): K-Core peels nodes iteratively and keeps the maximal subgraph in which each node has degree at least K. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/k_core/))
- [K-Hop Traversal](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/k_hop.md): K-hop traversal enumerates nodes reachable within at most K edges from a source node. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/k_hop/))
- [K-Means](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/k_means.md): K-Means groups nodes into K clusters by iteratively assigning nodes and updating centroids in embedding space. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/k_means/))
- [Louvain Community Detection](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/louvain.md): Louvain is a community detection algorithm for weighted graphs. Its goal is to partition a graph into communities by maximizing modularity, where internal connections are dense and ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/louvain/))
- [Label Propagation Algorithm (LPA)](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/lpa.md): The Label Propagation Algorithm (LPA) is a community detection algorithm for graphs. It operates by propagating labels and forming communities through the network based on the labe ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/lpa/))
- [Maximum Flow](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/maximum_flow.md): Maximum flow computes the largest feasible flow value from source to sink under edge capacity constraints. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/maximum_flow/))
- [Minimum Spanning Tree](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/minimum_spanning_tree.md): Minimum spanning tree finds a tree that connects all nodes with the minimum total edge weight. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/minimum_spanning_tree/))
- [PageRank](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/pagerank.md): The PageRank algorithm is developed by Google to rank web pages in their search engine results. It works by counting the number of links to a page to determine a rough estimate of  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/pagerank/))
- [Personalized PageRank (PPR)](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/ppr.md): The PPR algorithm is a variant of the PageRank algorithm that computes the importance of pages based on personalized preferences. Unlike the traditional PageRank, which treats all  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/ppr/))
- [Prepare algorithm sample data](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/prepare-data.md): Prepare algorithm sample files for a Docker Compose deployment, check CSV locations and directory mounts, and find the output files. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/prepare-data/))
- [Random Walk](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/random_walk.md): Random walk simulates probabilistic traversal paths and summarizes visit distribution across graph nodes. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/random_walk/))
- [Single-Pair Shortest Path](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/single_pair_shortest_path.md): Single-pair shortest path computes the minimum-cost route between one source node and one target node. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/single_pair_shortest_path/))
- [Single-Source Shortest Paths (SSSP)](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/sssp.md): Single-Source Shortest Paths computes the minimum path distances from a given source node to all other nodes in a weighted graph. When all edge weights are non-negative, classical  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/sssp/))
- [Strongly Connected Components](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/strong_connected_component.md): Strongly connected component identifies maximal subgraphs where every node is reachable from every other node. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/strong_connected_component/))
- [Triangle Count](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/triangle_count.md): Triangle count computes the number of closed triplets in the graph and can be used to estimate clustering strength. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/triangle_count/))
- [Weakly Connected Components (WCC)](https://dev-docs.nebula-graph.io/v5.3.2/markdown/analytic/algorithms/wcc.md): Weakly Connected Components identify groups of nodes in a directed graph where each pair of nodes within a group is connected via some path if edge directions are ignored. In other ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/analytic/algorithms/wcc/))
- [REST API](https://dev-docs.nebula-graph.io/v5.3.2/markdown/apis/index.md): Caution ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/apis/))
- [Overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/app-development/index.md): Build a movie cast service with the Python SDK or REST API, connect to NebulaGraph Database Developer Edition, and return JSON. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/app-development/))
- [Python SDK: movie cast service](https://dev-docs.nebula-graph.io/v5.3.2/markdown/app-development/python-sdk.md): Build a movie cast service with the Python SDK and FastAPI, configure database access, execute GQL, process result sets, and verify the HTTP endpoint. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/app-development/python-sdk/))
- [REST API: movie cast service](https://dev-docs.nebula-graph.io/v5.3.2/markdown/app-development/rest-api.md): Build a movie cast service with the REST API and FastAPI, including JWT authentication, GQL queries, response handling, and endpoint verification. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/app-development/rest-api/))
- [Configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/flink-connector/flink-options.md): Configure the NebulaGraph Flink connector with these classes: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/flink-connector/flink-options/))
- [Flink connector guide](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/flink-connector/index.md): The Flink connector enables data transfer between NebulaGraph Database Developer Edition and Apache Flink. This topic introduces how to set up the Flink connector to read and write ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/flink-connector/))
- [Go SDK](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/go-client.md): This topic introduces how to set up the Go SDK to connect to NebulaGraph Database Developer Edition and perform simple queries. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/go-client/))
- [SDKs and connectors](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/index.md): NebulaGraph Database Developer Edition provides SDKs in multiple programming languages to make it easy to develop applications that interact with NebulaGraph Database Developer Edi ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/))
- [Java SDK](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/java-client.md): This topic introduces how to set up the Java SDK to connect to NebulaGraph Database Developer Edition and perform simple queries. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/java-client/))
- [Kafka connector guide](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/kafka-connector/index.md): The Kafka connector is a sink connector that pulls data from Kafka topics and streams it to NebulaGraph Database Developer Edition. This topic introduces how to set up the Kafka co ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/kafka-connector/))
- [Configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/kafka-connector/kafka-options.md): Configure the NebulaGraph Database Developer Edition Kafka connector with the options below. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/kafka-connector/kafka-options/))
- [Python SDK](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/python-client.md): Set up the Python SDK to connect to NebulaGraph Database Developer Edition and run basic queries. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/python-client/))
- [Configurations overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/spark-connector/config/index.md): The Spark connector provides a collection of options that you can use to configure read and write operations for NebulaGraph Database Developer Edition. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/spark-connector/config/))
- [Reader options](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/spark-connector/config/reader-options.md): The following table lists the options that you can use to configure the reader. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/spark-connector/config/reader-options/))
- [Configuration classes](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/spark-connector/config/spark-options.md): Use these classes to configure Spark read and write operations for NebulaGraph Database Developer Edition: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/spark-connector/config/spark-options/))
- [Writer options](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/spark-connector/config/writer-options.md): The following table lists the options that you can use to configure the writer. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/spark-connector/config/writer-options/))
- [Spark connector guide](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/spark-connector/index.md): The Spark connector is a library that enables data transfer between NebulaGraph Database Developer Edition and Apache Spark. This topic introduces how to set up the Spark connector ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/spark-connector/))
- [Reading from NebulaGraph](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/spark-connector/read.md): The Spark connector allows you to read data from nodes, edges, or the result of a GQL query and then load it into a Spark DataFrame. The examples below use reader options and confi ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/spark-connector/read/))
- [Writing to NebulaGraph](https://dev-docs.nebula-graph.io/v5.3.2/markdown/clients/spark-connector/write.md): The Spark connector allows you to write data from a Spark DataFrame to nodes and edges in NebulaGraph Database Developer Edition. The examples below use writer options and configur ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/clients/spark-connector/write/))
- [Control flow](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/control-flow.md): The control flow statements control the execution order of statements in a procedure. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/control-flow/))
- [ALTER USER](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/alter-user.md): The ALTER USER command is used to set the home schema and home graph for the current user in the catalog, or modify a user's password. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/alter-user/))
- [CLEAR ALL WARNINGS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/clear/clear-all-warnings.md): The CLEAR ALL WARNINGS command clears all warnings occurred during the execution of GQL queries in the service group. When memory usage of the Graph service is high, you can execut ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/clear/clear-all-warnings/))
- [CLEAR WARNINGS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/clear/clear-warnings.md): The CLEAR WARNINGS command clears specific warnings occurred during the execution of GQL queries in the service group. When memory usage of the Graph service is high, you can execu ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/clear/clear-warnings/))
- [DESCRIBE EDGE TYPE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/describe/describe-edge-type.md): The DESCRIBE EDGE TYPE command returns detailed information about an edge type in a table that consists of the following columns: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/describe/describe-edge-type/))
- [DESCRIBE GRAPH TYPE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/describe/describe-graph-type.md): The DESCRIBE GRAPH TYPE command returns detailed information about a graph type in a table that consists of the following columns: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/describe/describe-graph-type/))
- [DESCRIBE GRAPH](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/describe/describe-graph.md): The DESCRIBE GRAPH command returns the name of the graph type based on which the graph or temporary graph was created. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/describe/describe-graph/))
- [DESCRIBE NODE TYPE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/describe/describe-node-type.md): The DESCRIBE NODE TYPE command returns detailed information about a node type in a table that consists of the following columns: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/describe/describe-node-type/))
- [DESCRIBE PROCEDURE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/describe/describe-proc.md): The DESCRIBE PROCEDURE command returns details about a specific named procedure. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/describe/describe-proc/))
- [Database administration overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/index.md): Database administration involves the activities required to manage and maintain a database system. You can execute database administration commands to efficiently manage user confi ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/))
- [INVITE USER](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/invite-user.md): The INVITE USER command invites a user to a service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/invite-user/))
- [KILL QUERY](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/kill/kill-query.md): The KILL QUERY command terminates a query that is running in the current Graph service and then returns the ID of the terminated query. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/kill/kill-query/))
- [KILL SESSION](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/kill/kill-session.md): The KILL SESSION command terminates a session that is running in the Graph service and then returns the ID of the terminated session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/kill/kill-session/))
- [REMOVE USER](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/remove-user.md): The REMOVE USER command removes a user from a service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/remove-user/))
- [SET USER GRAPH](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/set-user-graph.md): Deprecated ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/set-user-graph/))
- [SET USER SCHEMA](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/set-user-schema.md): Deprecated ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/set-user-schema/))
- [EXPORT SCHEMA](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/export-schemas.md): The EXPORT SCHEMA command returns the resource objects and the statements used to create those resource objects across all schemas within the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/export-schemas/))
- [SHOW ALL ROLES](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-all-roles.md): The SHOW ALL ROLES command returns information about all roles in the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-all-roles/))
- [SHOW ALL WARNINGS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-all-warnings.md): The SHOW ALL WARNINGS command shows all the warnings that are generated from previous query executions in the service group. Warnings alert users to non-critical issues without rai ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-all-warnings/))
- [SHOW CONFIGS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-configs.md): The SHOW CONFIGS command lists all runtime configuration options for the connected Graph service or a specified Storage service within the current session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-configs/))
- [SHOW CREATE GRAPH TYPE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-create-graph-type.md): The SHOW CREATE GRAPH TYPE command returns the CREATE GRAPH TYPE statement that creates the specified graph type. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-create-graph-type/))
- [SHOW CREATE GRAPH](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-create-graph.md): The SHOW CREATE GRAPH command returns the CREATE GRAPH statement that creates the specified graph or the CREATE TEMPORARY GRAPH statement that creates the specified temporary graph ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-create-graph/))
- [SHOW CREATE PROCEDURE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-create-proc.md): The SHOW CREATE PROCEDURE command returns the CREATE PROCEDURE statement that creates the specified user-defined procedure (UDP). ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-create-proc/))
- [SHOW CURRENT_GRAPH](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-current-graph.md): The SHOW CURRENT_GRAPH command returns information about the graph or the temporary graph in the current session. The graph or temporary graph in the current session acts as the wo ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-current-graph/))
- [SHOW CURRENT_SCHEMA](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-current-schema.md): The SHOW CURRENT_SCHEMA command returns information about the schema in the current session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-current-schema/))
- [SHOW CURRENT_SESSION TIME FORMATS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-current-session-time-formats.md): The SHOW CURRENT_SESSION TIME FORMATS command returns information about the date and time formats in the current session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-current-session-time-formats/))
- [SHOW CURRENT_SESSION](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-current-session.md): The SHOW CURRENT_SESSION command returns information about the session that is created by the current user. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-current-session/))
- [SHOW CURRENT_USER](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-current-user.md): The SHOW CURRENT_USER command returns information about the currently logged-in user in the current session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-current-user/))
- [SHOW FUNCTIONS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-functions.md): The SHOW FUNCTIONS command displays all the functions in the current schema. The SHOW FUNCTION <function_name> command displays the functions that match the specified function name ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-functions/))
- [SHOW GLOBAL CONFIGS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-global-configs.md): The SHOW GLOBAL CONFIGS command lists the configuration options set using GLOBAL SET or GLOBAL RESET for all Graph services or all Storage services in a service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-global-configs/))
- [SHOW GRAPH TYPES](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-graph-types.md): The SHOW GRAPH TYPES command returns information about all the graph types in the current schema. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-graph-types/))
- [SHOW GRAPHS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-graphs.md): The SHOW GRAPHS command returns information about all graphs in the schema of the current session and all temporary graphs in the catalog. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-graphs/))
- [SHOW (ALL) INDEXES](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-indexes.md): The SHOW ALL INDEXES command returns information about all indexes in the schema that is set in the current session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-indexes/))
- [SHOW JOBS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-jobs.md): The SHOW JOBS command returns information about all the unexpired jobs in the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-jobs/))
- [SHOW LEADERS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-leaders.md): The SHOW LEADERS command shows the information about the leader replicas in the Storage services of the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-leaders/))
- [SHOW OBJECTS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-objects.md): The SHOW OBJECTS command returns information about the resource objects that are owned by the current user or a specific user. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-objects/))
- [SHOW PARAMETERS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-parameters.md): The SHOW PARAMETERS command lists all the parameters in the current session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-parameters/))
- [SHOW PARTITIONS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-partitions.md): The SHOW PARTITIONS command returns information about all partitions in the Storage services of the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-partitions/))
- [SHOW PEERS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-peers.md): The SHOW PEERS command returns the information of all replicas of partitions in the Storage services of the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-peers/))
- [SHOW PLUGINS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-plugins.md): The SHOW PLUGINS command lists information and status for all loaded plugins, including manually loaded plugins and automatically loaded built-in plugins. The built-in plugins disp ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-plugins/))
- [SHOW PRIVILEGES](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-privileges.md): The SHOW PRIVILEGES command returns information about the privileges that are contained in a specific role or the privileges that are granted to the current user or a specific user ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-privileges/))
- [SHOW PROCEDURES](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-procedures.md): The SHOW PROCEDURES command displays information about named procedures, including all built-in procedures in the catalog and all user-defined procedures in the used schema. To vie ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-procedures/))
- [SHOW QUERIES](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-queries.md): The SHOW QUERIES command lists all queries that are currently running or being canceled by the user in the current Graph service. This is useful for identifying resource-intensive  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-queries/))
- [SHOW ROLES](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-roles.md): The SHOW ROLES command returns information about the roles that are granted to the current user or a specific user. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-roles/))
- [SHOW SCHEMAS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-schemas.md): The SHOW SCHEMAS command returns information about the schemas in the current catalog that the current user can access. Schemas on which the user does not have USAGE are omitted. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-schemas/))
- [SHOW SERVICE CONFIGS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-service-configs.md): The SHOW SERVICE CONFIGS command lists the configuration options set for the currently connected Graph service or a specified Storage service, including: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-service-configs/))
- [SHOW SERVICE GROUP](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-service-group.md): The SHOW SERVICE GROUP command returns information about the service group to which the currently connected Graph service belongs.pl}}. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-service-group/))
- [SHOW SERVICES](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-services.md): The SHOW SERVICES command returns information about all the Graph and Storage services in the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-services/))
- [SHOW SESSION CONFIGS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-session-configs.md): The SHOW SESSION CONFIGS command lists the configuration options set using either SESSION SET or SESSION RESET for the current session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-session-configs/))
- [SHOW SESSIONS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-sessions.md): The SHOW SESSIONS command returns information about all sessions that are active for the user in the current Graph service. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-sessions/))
- [SHOW STATS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-stats.md): The SHOW STATS command shows the statistics about a specific graph or a temporary graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-stats/))
- [SHOW TTLS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-ttls.md): The SHOW TTLS command returns information about the time-to-live (TTL) settings of a specific graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-ttls/))
- [SHOW USER DEFINED FUNCTIONS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-user-defined-functions.md): The SHOW USER DEFINED FUNCTIONS command displays all user-defined functions (UDFs) in the current schema. The SHOW USER DEFINED FUNCTION <function_name> command displays the UDFs t ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-user-defined-functions/))
- [SHOW USERS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-users.md): The SHOW USERS command returns all users that are invited to the current service group. For more information, see INVITE USER. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-users/))
- [SHOW VERSION](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-version.md): The SHOW VERSION command displays the currently installed version information for NebulaGraph Database Developer Edition. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-version/))
- [SHOW WARNINGS](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/show/show-warnings.md): The SHOW WARNINGS command shows the warning resulted from the previous GQL query execution in the current session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/show/show-warnings/))
- [EXPLAIN](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/tuning/explain.md): The EXPLAIN command displays the execution plan of a query. Unlike actually executing a query, the EXPLAIN command outlines the steps taken during query execution, which is useful  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/tuning/explain/))
- [Performance tuning](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/tuning/index.md): GQL generates an execution plan for each query to determine how to execute the query efficiently. You can view the execution plan to understand how the query is executed and optimi ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/tuning/))
- [PROFILE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-admin/tuning/profile.md): The PROFILE command executes a query, produces output, and collects runtime information for each operator in the execution plan. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-admin/tuning/profile/))
- [Boolean types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/boolean-type.md): The boolean type is declared with the BOOL or BOOLEAN keyword and can be set to the following values: TRUE, FALSE, and UNKNOWN (equals NULL, indicating the unknown truth value). ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/boolean-type/))
- [Character string types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/c-string-type.md): The string type is declared with the keyword STRING and is used to store a sequence of characters. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/c-string-type/))
- [Spatial types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/geo-type.md): Spatial types are composite data types that consist of longitude and latitude coordinates to represent spatial data. GQL supports three spatial types: point, linestring, and polygo ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/geo-type/))
- [Graph element reference types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/graph-element-reference-type.md): Graph element reference types represent references to nodes or edges in a graph: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/graph-element-reference-type/))
- [Data types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/index.md): A data type, also called a value type, describes the values that an expression, variable, parameter, query result, or property can contain. When you create a graph type, you must s ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/))
- [List types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/list-type.md): The list type is a constructed data type that can be declared using the keyword LIST<E> or ARRAY<E>, where E represents the data type of the list elements, which can be any predefi ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/list-type/))
- [Map types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/map-type.md): A map is a constructed data type used to store an unordered collection of key-value pairs. Each key in a map is unique and associated with a specific value. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/map-type/))
- [NULL type](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/null-type.md): The null value represents the absence of a value. It is different from an empty string, the number 0, or an empty container. NebulaGraph Database Developer Edition uses the NULL ty ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/null-type/))
- [Numeric types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/numeric-type.md): GQL supports integers, floating-point numbers, and arbitrary-precision numbers. Integers can be signed or unsigned, while floating-point numbers and arbitrary-precision numbers are ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/numeric-type/))
- [Path types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/path-type.md): The path type is a constructed data type that can be defined by using path patterns. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/path-type/))
- [Record types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/record-type.md): The record type is a constructed data type that can be defined by using construct expressions. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/record-type/))
- [Set types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/set-type.md): A set is a constructed data type used to store an unordered collection of unique elements. Unlike lists, elements in a set are not indexed and are automatically deduplicated. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/set-type/))
- [Table types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/table-type.md): A table type describes tabular data composed of named fields and rows. Each field has a value type. For example, TABLE {id INT64, name STRING} describes a table with an id field of ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/table-type/))
- [Temporal types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/temporal-type.md): Temporal values are used for the storage, manipulation, and retrieval of date and time information. GQL comes with built-in support for temporal values that can be stored as proper ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/temporal-type/))
- [Vector types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/data-types/vector-type.md): The vector type is a data type used to describe vector data, which is defined by a fixed number of dimensions and a specific data type of the coordinates. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/data-types/vector-type/))
- [CREATE TEMPORARY GRAPH](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/graph-projection/create.md): The CREATE TEMPORARY GRAPH statement creates a temporary graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/graph-projection/create/))
- [ALTER GRAPH TYPE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/graph-type/alter-graph-type.md): The ALTER GRAPH TYPE statement modifies a graph type in the schema of the current session or a specified schema, including the node types and edge types defined by the graph type. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/graph-type/alter-graph-type/))
- [CREATE GRAPH TYPE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/graph-type/create.md): The CREATE GRAPH TYPE statement creates a graph type in the schema of the current session or a specified schema. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/graph-type/create/))
- [DROP GRAPH TYPE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/graph-type/drop.md): The DROP GRAPH TYPE statement destroys a graph type in the schema of the current session or a specified schema. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/graph-type/drop/))
- [RENAME GRAPH TYPE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/graph-type/rename.md): The RENAME GRAPH TYPE statement renames a graph type in the schema of the current session or a specified schema. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/graph-type/rename/))
- [CREATE GRAPH](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/graph/create.md): The CREATE GRAPH statement creates a persistent graph (also known as a graph) in the schema of the current session or a specified schema. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/graph/create/))
- [DROP GRAPH](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/graph/drop.md): The DROP GRAPH statement destroys a graph or temporary graph. You can destroy a graph in the schema of the current session or a specified schema. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/graph/drop/))
- [RENAME GRAPH](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/graph/rename.md): The RENAME GRAPH statement renames a graph in the schema of the current session or a specified schema. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/graph/rename/))
- [Data definitions overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/index.md): Data definitions refer to the structure of your data in the database. Use data definition language (DDL) statements in GQL to manage that structure. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/))
- [CREATE FULLTEXT INDEX](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/index/create-fulltext.md): The CREATE FULLTEXT INDEX statement creates a full-text index on a specific graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/index/create-fulltext/))
- [CREATE SPATIAL INDEX](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/index/create-geo.md): The CREATE SPATIAL INDEX statement creates a spatial index on a specific graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/index/create-geo/))
- [CREATE VECTOR INDEX](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/index/create-vector.md): The CREATE VECTOR INDEX statement creates a vector index on a specific graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/index/create-vector/))
- [CREATE NORMAL INDEX](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/index/create.md): The CREATE NORMAL INDEX statement creates a normal index on a specific graph or temporary graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/index/create/))
- [DROP INDEX](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/index/drop.md): The DROP INDEX statement deletes an index from a specific graph or temporary graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/index/drop/))
- [Indexes overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/index/index.md): An index is a data structure that speeds up queries by providing quick access to specific data. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/index/))
- [CREATE SCHEMA](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/schema/create.md): The CREATE SCHEMA statement creates a schema in the current catalog. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/schema/create/))
- [DROP SCHEMA](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/schema/drop.md): The DROP SCHEMA statement destroys a schema in the current catalog. Once destroyed, all the objects in the schema are also destroyed. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/schema/drop/))
- [ALTER TTL](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/ttl/alter.md): The ALTER TTL statement modifies the time-to-live (TTL) duration set on edges of a specific graph by edge type. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/ttl/alter/))
- [CREATE TTL](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/ttl/create.md): The CREATE TTL statement sets a time-to-live (TTL) duration on graph elements by element type. Currently, TTL durations can be set on only edges in a graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/ttl/create/))
- [DROP TTL](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/ddl/ttl/drop.md): The DROP TTL statement deletes the time-to-live (TTL) duration set on edges of a specific graph by edge type. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/ddl/ttl/drop/))
- [DELETE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dml/delete.md): The DELETE statement removes one or more elements from a graph or temporary graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dml/delete/))
- [Data manipulations overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dml/index.md): Data manipulation language (DML) is used to modify the data in the database, such as inserting, updating, or deleting data. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dml/))
- [INSERT](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dml/insert.md): The INSERT statement creates nodes and edges in a graph or temporary graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dml/insert/))
- [SET](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dml/set.md): The SET statement modifies the properties of elements in a graph or temporary graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dml/set/))
- [CALL inline procedures](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/call/call-inline-procedure.md): To perform more complex queries and result processing in GQL, you can use the CALL statement to encapsulate a set of statements into a statement block. You can then further operate ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/call/call-inline-procedure/))
- [CALL named procedures](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/call/call-procedure.md): Use the CALL statement to run a named procedure. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/call/call-procedure/))
- [GROUP BY](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/clauses/group-by.md): The GROUP BY clause groups rows based on the specified columns. Rows with the same values in those columns are placed into the same group, and aggregate calculations are then perfo ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/clauses/group-by/))
- [LIMIT](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/clauses/limit.md): The LIMIT clause specifies the maximum number of rows to return. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/clauses/limit/))
- [OFFSET](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/clauses/offset.md): The OFFSET clause skips a number of rows before returning the remaining rows. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/clauses/offset/))
- [ORDER BY](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/clauses/order-by.md): The ORDER BY clause sorts rows by one or more columns either in ascending or descending order. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/clauses/order-by/))
- [SAMPLE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/clauses/sample.md): The SAMPLE clause samples a subset of edges during traversal. It is useful for analyzing superlarge datasets by working with a smaller, manageable sample. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/clauses/sample/))
- [USE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/clauses/use-graph.md): The USE clause declares a working graph in a query. A working graph is the graph or temporary graph where the query is executed. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/clauses/use-graph/))
- [WHERE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/clauses/where.md): The WHERE clause declares one or more filter conditions in the form of boolean value expressions. It usually references one or more properties of a node or edge and filters the res ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/clauses/where/))
- [YIELD](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/clauses/yield.md): The YIELD clause selects columns to be used by subsequent statements, or renames those columns. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/clauses/yield/))
- [Composite query](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/composite-query.md): The composite query statement combines the result sets of multiple linear query statements. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/composite-query/))
- [FILTER](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/filter.md): The FILTER statement selects a subset of the data produced by the preceding statement. The argument of the FILTER statement is a boolean expression that determines whether the data ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/filter/))
- [FOR](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/for.md): The FOR statement unnest a list or a table by iterating over its elements, allowing subsequent statements to process these elements one by one. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/for/))
- [Data queries overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/index.md): Data query language (DQL) is used to fetch information from a database. You can use query statements to read persistent data and perform filtering, aggregating, and projecting oper ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/))
- [LET](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/let.md): The LET statement declares variables that can be used in subsequent statements. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/let/))
- [Linear query](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/linear-query.md): The linear query statement consists of a linear composition of simple query statements, which are executed sequentially to produce a single result set. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/linear-query/))
- [MATCH](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/match.md): The MATCH statement retrieves data from a graph or temporary graph by pattern matching. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/match/))
- [Nearest neighbor query](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/nearest-neighbor.md): The nearest neighbor query statements search for the nearest neighbors of a query vector in a graph. The statements support two types of searches: k-nearest neighbor (KNN) search a ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/nearest-neighbor/))
- [Paging](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/order-by-page.md): ORDER BY, OFFSET and LIMIT clauses can be used together to divide the result dataset into discrete subsets or pages. Such processes are often known as paging. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/order-by-page/))
- [Primitive result](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/primitive-result.md): The primitive result statement defines the final output behavior of a linear query: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/primitive-result/))
- [RETURN](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/dql/return.md): The RETURN statement selects output columns or performs aggregation before output. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/dql/return/))
- [Configure hints](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/executions/hints.md): Hints are special comments that you can add to a query to advise the query optimizer on how to execute the query. Hints use the /*+ ... */ syntax. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/executions/hints/))
- [Query configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/executions/index.md): GQL provides the following configurations to control how queries are parsed and executed: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/executions/))
- [Configure limits](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/executions/limits.md): Add a SET_VAR hint at the start of a GQL query to set options such as its memory limit and execution parallelism. The hint uses /*+ ... */ syntax and applies only to the current qu ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/executions/limits/))
- [Configure parameters](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/executions/parameters.md): Each parameter consists of a name and a value. The name must start with a dollar sign ($), and the value must be a literal of one of the following data types: Numeric, String, Bool ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/executions/parameters/))
- [Aggregate value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/aggregate.md): The aggregate value expression holds an aggregate function instance and returns the execution result of the aggregate function. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/aggregate/))
- [Variable value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/binding-variable.md): The variable value expression references the field of the record or the fields of the records in the current working dataset. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/binding-variable/))
- [Case value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/case.md): The case value expression returns a value based on the evaluation of one or more search conditions. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/case/))
- [Cast value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/cast.md): The cast value expression converts the data type of an expression to a specified target data type. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/cast/))
- [Constant value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/constant.md): The constant value expression holds a constant literal that refers to a fixed value that is used directly in a query and does not change during operations. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/constant/))
- [Construct value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/construct.md): The construct value expression is an expression used to create constructed data types, such as LIST and RECORD. For information about the list type and record type, see Data types. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/construct/))
- [Function value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/function.md): The function value expression holds a function instance and returns the execution result of the function. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/function/))
- [Label expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/label.md): The label expression references one or more labels of a graph element. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/label/))
- [Lambda value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/lambda.md): Lambda value expressions, also known as lambda expressions, are used to define an operation to be applied to each element in a list. Lambda value expressions take the form x -> exp ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/lambda/))
- [Logical value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/logical.md): The logical value expression performs logical operations and returns a result of the boolean type. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/logical/))
- [Property value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/property.md): The property value expression references a property of a graph element or a field of a record. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/property/))
- [Subquery value expression](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/expressions/subquery.md): A subquery value expression returns a single value or a boolean value derived from a query. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/expressions/subquery/))
- [Aggregate functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/aggregate.md): Aggregate functions in GQL perform calculations over a group of values and return a single value. To view the supported data types of each aggregate function, use SHOW FUNCTION. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/aggregate/))
- [Full-text index functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/fulltext.md): Use the following GQL functions with full-text indexes. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/fulltext/))
- [Spatial functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/geo.md): Returns a point with the specified longitude and latitude. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/geo/))
- [Graph element functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/graph.md): The following GQL functions operate on graph elements. Examples use the example dataset. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/graph/))
- [Lambda functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/lambda.md): Lambda functions in NebulaGraph Database Developer Edition apply operations to collection elements in persistent graphs and temporary graphs. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/lambda/))
- [List functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/list.md): Returns the number of elements in a list. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/list/))
- [Map functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/map.md): Map functions are used to construct and modify data from map-based data structures (collections of key-value pairs). ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/map/))
- [Math functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/math.md): GQL supports these categories of mathematical functions: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/math/))
- [Set functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/set.md): Set functions are used to construct and modify data from set-based data structures (collections that do not contain duplicate elements). ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/set/))
- [String functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/string.md): Returns a substring of a string. The substring is of length len and starts from position idx. Positions start from 1. len must be positive. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/string/))
- [System information functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/system.md): System information functions return details about NebulaGraph Database Developer Edition in persistent graphs and temporary graphs. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/system/))
- [Table functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/table.md): The following functions operate on tables. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/table/))
- [Temporal functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/temporal.md): Temporal functions in NebulaGraph Database Developer Edition work with date, time, and duration values in persistent graphs and temporary graphs. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/temporal/))
- [User-defined functions (UDF)](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/user-defined.md): Create and call user-defined functions (UDFs) written in GQL to reuse query logic in NebulaGraph Database Developer Edition. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/user-defined/))
- [Vector functions](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/functions/vector.md): The following reference covers vector arithmetic and vector functions supported by GQL, with examples. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/functions/vector/))
- [Expressions overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/index.md): An expression is, in general, a declaration of constants, variables, operators, function calls and many others that evaluate to a specific value. In GQL, there are many forms of ex ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/))
- [Literals](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/literals.md): Literals are fixed values used directly in GQL queries. These values can be numbers, strings, dates, booleans, etc., and are written directly in the query rather than referencing c ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/literals/))
- [Operators](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/operators.md): The following table lists the operators supported by GQL. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/operators/))
- [ALL_DIFFERENT predicate](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/predicates/all_different.md): The ALL_DIFFERENT predicate checks if all graph elements in a list are pairwise different from one another. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/predicates/all_different/))
- [Comparison predicate](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/predicates/comparison.md): The comparison predicate compares two values and returns true if the comparison is true, false if the comparison is false, and null if any of the values is null. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/predicates/comparison/))
- [EXISTS predicate](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/predicates/exists.md): The EXISTS predicate checks if a graph pattern exists or a query returns a non-empty result. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/predicates/exists/))
- [Labeled predicate](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/predicates/labeled.md): The labeled predicate checks if a graph element has specific labels. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/predicates/labeled/))
- [NULL predicate](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/predicates/null.md): The null predicate checks if a value is null or not. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/predicates/null/))
- [SAME predicate](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/fe/predicates/same.md): The SAME predicate checks if all graph elements in a list are the same. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/fe/predicates/same/))
- [EXPORT](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/in-out/export.md): The EXPORT statement exports query results to a table, a file, or a persistent graph in NebulaGraph Database Developer Edition. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/in-out/export/))
- [IMPORT](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/in-out/import.md): The IMPORT statement imports data into a temporary graph. It is typically used together with the USE clause, which specifies the target temporary graph. Data can come from files, N ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/in-out/import/))
- [Remote execution (nebula_exec)](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/in-out/nebula-exec.md): The nebula_exec procedure executes a GQL query on a remote NebulaGraph Database Developer Edition cluster. You can use this procedure to import data into a graph in NebulaGraph Dat ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/in-out/nebula-exec/))
- [Logging](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/log.md): The logging statement prints information during procedure execution for debugging or monitoring purposes. You can specify the log level, location, and content based on the context  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/log/))
- [Match compute](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/match-compute.md): The match compute statement performs iterative computations on temporary graphs. It lets you match specific graph patterns and then execute computations or updates on the matched s ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/match-compute/))
- [GQL cheat sheet](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/overview/cheat-sheet.md): This topic catalogs the most commonly used statements and commands in GQL for quick reference. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/overview/cheat-sheet/))
- [Comments](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/overview/comment.md): Comments are used to add explanatory notes or remarks to statements within a GQL query. They are ignored by the interpreter and do not affect query execution. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/overview/comment/))
- [Example dataset](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/overview/example-dataset.md): The example dataset used throughout these docs contains movie data. Load it to try the queries and explore the graph. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/overview/example-dataset/))
- [FAQ](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/overview/faq.md): Find answers to common questions about using GQL in NebulaGraph Database Developer Edition. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/overview/faq/))
- [Get started with GQL](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/overview/first-steps.md): Create a practice graph in NebulaGraph Database Developer Edition and learn GQL statements for defining graph types, inserting nodes and edges, querying relationships, updating properties, and deleting data. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/overview/first-steps/))
- [What is GQL](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/overview/index.md): Graph Query Language (GQL) is a declarative language for property graphs. Use it to define graph structures, write data, and query relationships between nodes and edges. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/overview/))
- [Keywords and identifiers](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/overview/keywords-identifiers.md): Identifiers and keywords are two fundamental components in GQL statements. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/overview/keywords-identifiers/))
- [Syntax notation](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/overview/syntax-conventions.md): The syntax notation used in the documentation is an Extended Backus–Naur Form (EBNF), which defines the syntax of the GQL language with a set of production rules. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/overview/syntax-conventions/))
- [Graph vs Temporary Graph](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/overview/versus.md): Developer Edition supports persistent graphs and temporary graphs. Persistent graph data is stored on disk. Temporary graph data resides in the memory of the current Graph service  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/overview/versus/))
- [Edge pattern](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/patterns/edge-patterns.md): An edge pattern is a pattern used to match edges in a property graph. There are two types of edge patterns: full edge patterns and abbreviated edge patterns. A full edge pattern co ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/patterns/edge-patterns/))
- [Graph patterns](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/patterns/index.md): Graph pattern matching is the process of matching a list of regular expressions, which are specifically defined by the GQL standard, against a property graph to get a set of reduce ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/patterns/))
- [Node pattern](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/patterns/node-patterns.md): A node pattern is a common pattern used to match nodes in a property graph. Each node pattern consists of one node pattern filler enclosed in parentheses (()). The node pattern fil ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/patterns/node-patterns/))
- [Path pattern](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/patterns/path-patterns.md): Path patterns match paths from graphs. A path pattern consists of the following parts: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/patterns/path-patterns/))
- [ALTER PROCEDURE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/procedures/alter.md): The ALTER PROCEDURE statement modifies a user-defined procedure (UDP) in the used schema, including its name and comment. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/procedures/alter/))
- [Built-in named procedures](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/procedures/built-in/index.md): Built-in named procedures are predefined by NebulaGraph Database Developer Edition. Some are provided through official plugins and become available only after the corresponding plu ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/procedures/built-in/))
- [CREATE PROCEDURE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/procedures/create.md): The CREATE PROCEDURE statement creates a user-defined procedure (UDP) in the used schema. All UDPs must be named procedures. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/procedures/create/))
- [DROP PROCEDURE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/procedures/drop.md): The DROP PROCEDURE statement deletes a user-defined procedure (UDP) in the used schema. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/procedures/drop/))
- [Procedures overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/procedures/index.md): Procedures in GQL package computation for reuse. The following sections cover their categories and usage. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/procedures/))
- [Subgraph procedure (algo.subgraph)](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/procedures/subgraph.md): algo.subgraph is a built-in named procedure provided by the official algo plugin. It extracts a subgraph from a persistent graph with multi-source BFS traversal. You can control so ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/procedures/subgraph/))
- [Server-side programming overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/server-prog/index.md): GQL supports server-side programming through user-defined procedures (UDPs). This allows developers to extend the capabilities of GQL by writing custom logic that can be executed d ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/server-prog/))
- [SESSION CLOSE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/sessions/close.md): The SESSION CLOSE command closes the current session and returns the ID of the closed session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/sessions/close/))
- [Sessions overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/sessions/index.md): A session is a consecutive series of interactions between a client and the NebulaGraph Database Developer Edition server-side. Sessions maintain the context between queries, which  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/sessions/))
- [SESSION RESET](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/sessions/reset.md): The SESSION RESET command resets the schema, graph, or temporary graph in the current session, and deletes all parameters set in the session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/sessions/reset/))
- [SESSION SET](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/sessions/set.md): The SESSION SET command sets the schema, graph, temporary graph, or parameters for the current session. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/sessions/set/))
- [SESSION UNSET command](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/sessions/unset.md): The SESSION UNSET command unsets the value of a configuration option set using SESSION SET or SESSION RESET for the current session. The configuration options unset by SESSION UNSE ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/sessions/unset/))
- [Variable manipulation](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/set.md): You can use the SET statement to perform assignments, aggregations, and function calls on variables. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/set/))
- [Statement block](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/statement-block.md): A statement block in GQL is a collection of one or more statements that are executed sequentially. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/statement-block/))
- [Active set variables](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/active-set-variable.md): An active set variable is used to store the set of nodes to be processed during procedure execution. The active set variable can be updated so that subsequent operations are perfor ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/active-set-variable/))
- [AndAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/and_agg.md): An AndAgg aggregator value variable (AndAgg) maintains the result of logical AND operation on all inputs of the boolean type. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/and_agg/))
- [AvgAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/avg_agg.md): An AvgAgg aggregator value variable (AvgAgg<T>) maintains the average of all inputs, where T represents the data type of the input values. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/avg_agg/))
- [Aggregator value variables](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/index.md): Aggregator value variables are used to define aggregation operations on nested values. When referenced in subsequent statements, aggregator value variables must be prefixed with th ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/))
- [ListAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/list_agg.md): A ListAgg aggregator value variable (ListAgg<T>) aggregates all inputs into a list in insertion order, where T represents the data type of the input values. To aggregate a set of u ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/list_agg/))
- [MapAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/map_agg.md): A MapAgg aggregator value variable (MapAgg<K, V>) maintains a map of key-value pairs where each key maps to an aggregated value. K represents the data type of the key, and V repres ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/map_agg/))
- [MaxAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/max_agg.md): A MaxAgg aggregator value variable (MaxAgg<T>) maintains the maximum value among all inputs, where T represents the data type of the input values. To maintain the minimum value, se ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/max_agg/))
- [MinAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/min_agg.md): A MinAgg aggregator value variable (MinAgg<T>) maintains the minimum value among all inputs, where T represents the data type of the input values. To maintain the maximum value, se ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/min_agg/))
- [OrAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/or_agg.md): An OrAgg aggregator value variable (OrAgg) maintains the result of logical OR operation on all inputs of the boolean type. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/or_agg/))
- [SetAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/set_agg.md): A SetAgg aggregator value variable (SetAgg<T>) aggregates all inputs into a set that contains only unique values, where T represents the data type of the input values. To aggregate ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/set_agg/))
- [SumAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/sum_agg.md): A SumAgg aggregator value variable (SumAgg<T>) maintains the aggregated result of all inputs, where T represents the data type of the input values. The aggregation behavior depends ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/sum_agg/))
- [TopKAgg](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/agg/topk_agg.md): A TopKAgg aggregate value variable (TopKAgg<K, SortFields>) maintains the top K records based on specified sort fields (SortFields). This variable automatically retains the top K r ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/agg/topk_agg/))
- [File variables](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/file-variable.md): File variables define file-based data sources and destinations. They are primarily used for importing or exporting data, and support multiple file formats including CSV, Parquet, a ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/file-variable/))
- [Graph variables](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/graph-variable.md): Graph variables are used to store subgraphs for querying and computation. The keyword GRAPH is used to define graph variables. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/graph-variable/))
- [Variables](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/index.md): In GQL, a variable is an identifier assigned to a collection of values of a specific data type. Variables can be used to hold values for data retrieval and manipulation within proc ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/))
- [Table variables](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/table-variable.md): Table variables store data in tabular form. In NebulaGraph Database Developer Edition, they are mainly used to store query results, intermediate traversal results, and to drive bat ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/table-variable/))
- [Primitive value variables](https://dev-docs.nebula-graph.io/v5.3.2/markdown/database-gql-reference/variable-definition/value-variable.md): Primitive value variables are used to hold values in procedures or to pass values during procedure execution. Primitive value variables are declared with the keyword VALUE. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/database-gql-reference/variable-definition/value-variable/))
- [Example data](https://dev-docs.nebula-graph.io/v5.3.2/markdown/get-started/dataset.md): The built-in movie sample dataset contains movies, actors, directors, users, genres, and their relationships. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/get-started/dataset/))
- [Deploy with Docker Compose](https://dev-docs.nebula-graph.io/v5.3.2/markdown/get-started/deploy.md): Download compose.yaml, set a login password, start NebulaGraph Database Developer Edition and Studio on your development machine, and check service status. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/get-started/deploy/))
- [Connect and run your first query](https://dev-docs.nebula-graph.io/v5.3.2/markdown/get-started/first-query.md): Connect to NebulaGraph Database Developer Edition with NebulaGraph Studio, load the movie sample dataset, and find a movie and its actors. Complete the four steps below in your bro ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/get-started/first-query/))
- [Home](https://dev-docs.nebula-graph.io/v5.3.2/markdown/index.md): Documentation for NebulaGraph Database Developer Edition, covering deployment, your first query, application development, GQL syntax, APIs, and tools. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/))
- [Graph data concepts](https://dev-docs.nebula-graph.io/v5.3.2/markdown/intro/concepts.md): Understand nodes, edges, properties, types, labels, graph types, graphs, Schemas, and working graphs through movie examples. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/intro/concepts/))
- [Introduction](https://dev-docs.nebula-graph.io/v5.3.2/markdown/intro/introduction.md): Use cases, limits, Docker Compose deployment, and getting started with NebulaGraph Database Developer Edition. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/intro/introduction/))
- [Capabilities and limits](https://dev-docs.nebula-graph.io/v5.3.2/markdown/intro/limitations.md): Understand NebulaGraph Database Developer Edition deployment requirements, service count limits, a 1 GB data-size limit, and availability constraints. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/intro/limitations/))
- [Documentation for AI tools](https://dev-docs.nebula-graph.io/v5.3.2/markdown/llms.md): Use llms.txt and Markdown content to provide version-specific NebulaGraph Database Developer Edition documentation to an AI tool. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/llms/))
- [Authentication](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authentication/index.md): NebulaGraph Database Developer Edition uses authentication to verify a user's identity. For password authentication, the user must exist, be enabled, and not be locked. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authentication/))
- [User management](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authentication/manage-users.md): Use ngctl to create users, change passwords, enable, disable, unlock, and delete users in NebulaGraph Database Developer Edition. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authentication/manage-users/))
- [Sessionless mode](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authentication/sessionless.md): Sessionless mode lets SDK clients connect to NebulaGraph Database Developer Edition with an empty username and password. The Graph service checks request privileges using the ident ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authentication/sessionless/))
- [ALTER OWNER](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/alter-owner.md): ALTER OWNER transfers ownership of a resource in the current service group to another user. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/alter-owner/))
- [ALTER ROLE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/alter-role.md): ALTER ROLE changes a role's description in the current service group. It does not change the privileges in the role. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/alter-role/))
- [Configure user access](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/configure-user-access.md): Add the user to a service group, then grant connection, schema access, and resource privileges. This guide walks through allowing user1 to query /finance/transactions. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/configure-user-access/))
- [CREATE ROLE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/create-role.md): CREATE ROLE creates a custom role in the current service group. A new role has no privileges until you add them with GRANT. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/create-role/))
- [DROP ROLE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/drop-role.md): DROP ROLE deletes one or more roles from the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/drop-role/))
- [GRANT](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/grant-privilege.md): GRANT adds privileges to a user or role in the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/grant-privilege/))
- [GRANT ROLE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/grant-role.md): GRANT ROLE assigns one or more custom roles to a user in the current service group. A user can have up to 16 custom roles. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/grant-role/))
- [Authorization overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/index.md): Authorization determines whether a user can connect to a service group and which operations the user can perform on its resources. After creating the user, follow Configure user ac ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/))
- [Manage roles and privileges](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/manage-roles.md): Use roles to assign the same privileges to multiple users. This guide covers inspecting grants, creating and assigning roles, and changing or revoking access. To give a user access ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/manage-roles/))
- [Privilege reference](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/privilege-reference.md): This reference lists actions that can be granted for each resource type. To give a user access for the first time, follow Configure user access. For direct grants, roles, and owner ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/privilege-reference/))
- [REVOKE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/revoke-privilege.md): REVOKE removes privileges granted to a user or role in the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/revoke-privilege/))
- [REVOKE ROLE](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/revoke-role.md): REVOKE ROLE removes one or more role assignments from a user in the current service group. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/revoke-role/))
- [Schema access control](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/authorization/schema-access-control.md): To access a resource in a non-default schema, a regular user needs two privileges: USAGE on the schema and the privilege required to operate on the resource. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/authorization/schema-access-control/))
- [Docker Compose configuration](https://dev-docs.nebula-graph.io/v5.3.2/markdown/server-admin/configurations/docker-compose.md): This reference explains the services, ports, environment variables, and data directories in the compose.yaml supplied with NebulaGraph Database Developer Edition. For the first dep ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/server-admin/configurations/docker-compose/))
- [Encrypt passwords](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/encrypt.md): NebulaGraph Exchange supports using encrypted passwords in NebulaGraph Database Developer Edition configurations for enhanced security during data import. This topic introduces how ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/encrypt/))
- [Data import configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/index.md): This topic introduces the configuration file for data import in NebulaGraph Exchange. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/))
- [HDFS configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/hdfs.md): This topic introduces the configuration options for importing data from an HDFS data source. For information about the complete configuration file and options, see Data import conf ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/hdfs/))
- [Hive configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/hive.md): This topic introduces the configuration options for importing data from a Hive data source. For information about the complete configuration file and options, see Data import confi ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/hive/))
- [Source configuration](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/index.md): Source configuration covers: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/))
- [JDBC configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/jdbc.md): This topic introduces the configuration options for importing data from a JDBC data source. For information about the complete configuration file and options, see Data import confi ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/jdbc/))
- [Kafka configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/kafka.md): This topic introduces the configuration options for importing data from a Kafka data source. For information about the complete configuration file and options, see Data import conf ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/kafka/))
- [Local source configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/local.md): This topic introduces the configuration options for importing data from a local data source. For information about the complete configuration file and options, see Data import conf ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/local/))
- [Mapping configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/mapping.md): This topic describes the mapping configurations when importing data into NebulaGraph Database Developer Edition, which include node mapping configurations and edge mapping configur ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/mapping/))
- [MaxCompute configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/maxcompute.md): This topic introduces the configuration options for importing data from a MaxCompute data source. For information about the complete configuration file and options, see Data import ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/maxcompute/))
- [NebulaGraph 3.x configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/nebula3.md): This topic introduces the configuration options for importing data from a NebulaGraph 3.x data source. For information about the complete configuration file and options, see Data i ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/nebula3/))
- [Neo4j configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/neo4j.md): This topic introduces the configuration options for importing data from a Neo4j data source. For information about the complete configuration file and options, see Data import conf ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/neo4j/))
- [Preprocessing configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/preprocess.md): This topic describes the optional preprocessing configurations when importing data into NebulaGraph Database Developer Edition. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/preprocess/))
- [Amazon S3 configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/s3.md): This topic introduces the configuration options for importing data from an Amazon S3 data source. For information about the complete configuration file and options, see Data import ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/s3/))
- [Tencent Cloud configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/config/sources/tencent.md): This topic introduces the configuration options for importing data from a Tencent Cloud data source. For information about the complete configuration file and options, see Data imp ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/config/sources/tencent/))
- [Deploy Exchange](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/deploy-exchange.md): Download the NebulaGraph Exchange package and deploy its Spark environment. Run the commands below on the Linux machine that will run NebulaGraph Exchange. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/deploy-exchange/))
- [Export data](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/export-data.md): Use NebulaGraph Exchange to export a graph to files or to another graph. The source and destination graphs may be in the same NebulaGraph Database Developer Edition cluster or in d ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/export-data/))
- [Import data with NebulaGraph Exchange](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/import-data/index.md): This topic describes how to import data into NebulaGraph Database Developer Edition using NebulaGraph Exchange. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/import-data/))
- [Import data with GQL templates](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/import-data/template-import.md): NebulaGraph Exchange supports importing data into NebulaGraph Database Developer Edition by using custom GQL templates. Unlike the standard workflow in Import data, this mode lets  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/import-data/template-import/))
- [What is NebulaGraph Exchange?](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/exchange/index.md): NebulaGraph Exchange is an Apache Spark tool for importing data from multiple sources into NebulaGraph Database Developer Edition and exporting data from NebulaGraph Database Devel ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/exchange/))
- [NebulaGraph tools overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/index.md): NebulaGraph provides the following command-line and data tools: ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/))
- [What is ngctl](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/ngctl/index.md): ngctl is a command-line tool for managing the Meta service of NebulaGraph Database Developer Edition. Use it to sign in to the Meta service, sign out, change your password, and man ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/ngctl/))
- [Meta service commands](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/ngctl/meta-commands.md): This page covers ngctl commands for signing in to the Meta service, changing passwords, managing users, and checking the client version. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/ngctl/meta-commands/))
- [What is ngql](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/ngql/index.md): ngql is a command-line client for the Graph service in NebulaGraph Database Developer Edition. Use it to run GQL statements and scripts, load built-in sample data, and change resul ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/ngql/))
- [ngql usage guide](https://dev-docs.nebula-graph.io/v5.3.2/markdown/utilities/ngql/usage.md): ngql is a command-line tool that allows you to interact with the Graph service in a NebulaGraph Database Developer Edition service group. Use the commands below to connect and run  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/utilities/ngql/usage/))
- [Canvas operations and shortcuts](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/explorer/canvas-operations.md): Use the following canvas operations and keyboard shortcuts in NebulaGraph Studio. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/explorer/canvas-operations/))
- [Edit graph data](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/explorer/data-exploration/edit-graph-data.md): Edit mode in graph exploration lets you add nodes and edges, edit properties, and delete nodes and edges. Use edit mode on the canvas to modify graph data in NebulaGraph Database D ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/explorer/data-exploration/edit-graph-data/))
- [Explore subgraphs](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/explorer/data-exploration/explore-subgraphs.md): Explore subgraphs in NebulaGraph Studio by querying nodes, relationships, and paths. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/explorer/data-exploration/explore-subgraphs/))
- [Data exploration overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/explorer/data-exploration/index.md): Use the following NebulaGraph Studio tools to explore and visualize graph data. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/explorer/data-exploration/))
- [Exploration settings](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/explorer/data-exploration/manage-custom-settings.md): Adjust query and visualization behavior with the following exploration settings. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/explorer/data-exploration/manage-custom-settings/))
- [Manage explorations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/explorer/data-exploration/manage-explore.md): An exploration in NebulaGraph Studio is a canvas where you can query and visualize data from graphs in NebulaGraph Database Developer Edition . You can create, delete, and rename e ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/explorer/data-exploration/manage-explore/))
- [Manage canvas data](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/explorer/data-exploration/modify-results.md): After querying and displaying graph data (nodes and edges) on the canvas, you can manage the data. Filter, inspect, save, export, or zoom the results displayed on the canvas. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/explorer/data-exploration/modify-results/))
- [Studio configurations](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/configs.md): Configure NebulaGraph Studio with the settings below. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/configs/))
- [Connect to NebulaGraph](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/connect.md): Connect NebulaGraph Studio to NebulaGraph Database Developer Edition by following the steps below. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/connect/))
- [Console settings](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/console/console-settings.md): In the NebulaGraph Studio console, you can configure the query and visualization settings. Additionally, the display style for nodes and edges can be adjusted. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/console/console-settings/))
- [Console overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/console/console-usage.md): Use the NebulaGraph Studio console to run queries in the browser. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/console/console-usage/))
- [Viewing execution plans](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/console/execution-plans.md): NebulaGraph Studio supports the PROFILE and EXPLAIN commands to generate execution plans for GQL queries. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/console/execution-plans/))
- [Graph exploration](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/graph-exploration/index.md): Graph exploration is a visualization feature in NebulaGraph Studio for exploring relationships in data hosted with NebulaGraph Database Developer Edition. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/graph-exploration/))
- [What is NebulaGraph Studio](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/index.md): NebulaGraph Studio (Studio for short) is a browser-based visualization tool for NebulaGraph Database Developer Edition 5.x versions. It provides a graphical user interface (GUI) fo ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/))
- [Install Studio](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/install.md): Download a package for your operating system and CPU architecture from GitHub Releases, or deploy the container image with Docker Compose. You do not need to download the source co ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/install/))
- [Schema design overview](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/schema-design/index.md): A schema in NebulaGraph Database Developer Edition is a system object that serves as a container for graph types and graphs. NebulaGraph Studio provides a visual interface for you  ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/schema-design/))
- [Manage graph types](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/schema-design/manage-graph-type.md): Create, inspect, modify, or delete graph types in NebulaGraph Studio. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/schema-design/manage-graph-type/))
- [Manage graphs](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/schema-design/manage-graph.md): Create or delete graphs, manage indexes, and inspect graph statistics in NebulaGraph Studio. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/schema-design/manage-graph/))
- [Manage schemas](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/schema-design/manage-schema.md): Create and manage Schemas in NebulaGraph Studio. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/schema-design/manage-schema/))
- [System settings](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/system-settings.md): Use the NebulaGraph Studio system menu to inspect settings, change the theme or language, and log out. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/system-settings/))
- [Uninstall Studio](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/uninstall.md): Follow the steps for your installation method. Back up any configuration and data you need before uninstalling. ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/uninstall/))
- [Upgrade Studio](https://dev-docs.nebula-graph.io/v5.3.2/markdown/visualization/studio/upgrade.md): Upgrade NebulaGraph Studio with the method used for its current installation. Use the same method as your current installation, and back up the configuration and data first. The v5 ([HTML](https://dev-docs.nebula-graph.io/v5.3.2/visualization/studio/upgrade/))