Specification Description
As a new graph database product, the database edition provides graph management, graph data addition, deletion, modification, query, and analysis capabilities, supports Cypher, and provides graph data persistence to flush data written by users to disks. In this way, multiple copies and hardware redundancy are used to achieve high availability and fast fault recovery. Currently, the database edition has completed storage and query of hundreds of billions and trillions of graphs.
The following sections describe the APIs supported by database graphs.
Data Types
Type |
Description |
---|---|
char |
Character |
float |
Float type (32-bit float) |
double |
Double type (64-bit float) |
bool |
Boolean type. Available values are 0/1 and true/false. |
long |
Long integer (value range: -2^63 to 2^63–1) |
int |
Integer (value range: -2^31 to 2^31–1) |
date |
Date. Currently, the following formats are supported:
NOTE:
The value of MM or DD must consist of two digits. If the value contains only one digit, add 0 before it, for example, 05-01. |
string |
Variable-length string |
Restrictions on Composite Types
Only the single type is supported. List/set is not supported.
Data Import Restrictions
There are some restrictions when you import data to a database edition graph:
- Importing data concurrently
Multiple data files can be imported at the same time. To accelerate the import, split a large file into multiple OBS files that each does not exceed 5 GB.
- Uploading import logs to OBS
Set the logDir parameter to save import logs where you can find the error cause.
- Importing edge data
If you import only edges of a database edition graph, DLI cannot automatically generate vertices for the graph. If only edges are imported, you cannot query vertices or access the graph from vertices. You are advised to import vertex data too.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.