This section explains how to export data from Ultipa Graph via Ultipa Manager and Ultipa Transporter-Exporter.
Export data via Manager
Manager can export multiple node or edge files at one time.
Files exported via Manager contain schema information, for instance: when exporting node schema
movie, its file name would be movie_nodes.csv；exported file would be csv format, with comma
, as column separator and
<property name> as table header:
- Export single node file:
To export node schema
name, we need to click "File" on the right menu, then click the "Export Nodes" in the poppup window, choose node schema
movie and properties
name, click submit：
Setting limit value to -1 means to export all nodes or edges, we can also set an interger to limit the number of nodes or edges to export. Properties not selected will not be exported, i.e., Manager does not export node/edge's system properties automatically.
- Export multiple node files:
For instance, export all properties of node schema
When exporting several files (schema) simultaneously, Manager does not support to select properties for each schema, but automatically exporting all property data for each schema. There might be popup windows asking users "Do you allow Manager to download multiple files at the same time?" in a few browsers and users will need to allow before download starts.
The approach to exporting edge files is similar to exporting node files: we will need to select "Export Edges", and we will often need to export the starting node
_fromand terminal node
_to_uuid) for edge files to make them meaningful.
Export data via Transporter
Differnt from Manager, Transporter can export both nodes and edges at the same time instead of exporting them separately.
Files exported via Transporter are slightly different from Manager, for example, if to export node schema
movie then its file name would be movie.node.csv; the column names in its header (if applicable) would be
<PropertyName>:<DataType>, for instance:
When exporting data via Ultipa Transporter's Exporter, we will need a Yaml comfiguration file which contains server's connection information, target graphset's name, schema and properties to be exported, and if to export table headers, etc.
Yaml configuration file are divided into 4 sections：
- Section 1 Server Information
server: host: "192.168.1.85:64001" username: "root" password: "root" graphset: "miniCircle" crt: ""
Server connection information
password should be provided by the server administrator;
graphset can be a graphset to be created;
crt can be skipped if IFS is not used for communication.
- Section 2 Node Information
nodeConfig: - schema: "movie" properties: - name: name - name: year - schema: "country" properties: - name: name
To export node/edge only requires users to state custom properties; their system propertes
_to_uuid will be automatically exported without statement.
- Section 3 Edge Information
edgeConfig: - schema: "filmedIn"
To only export system properties but not any custom properties, users do not have to state
properties; when exporting all schema for edge, we can state schema as
"*", which is same for exporting Node as well. See Transporter for more.
- Section 4 Global Information
settings: writeHeader: true
writeHeaderto true, all exported files will include table headers.
Save sections above in configuration file export_miniCircle.yml, place it with Transporter's import tool: ultipa-importer Transporter under a same directory, open the command line tool under the directory (e.g. right-click Powershell) and execute commands below:
./ultipa-exporter --config ./export_miniCircle.yml
When operating the command, if notice
bash: ./ultipa-importer: Permission deniedappears, it suggests that relevant execution privileges are not obtained; users can execute
chmod +x ultipa-exporterto obtain privileges required before executing