Change Password

Please enter the password.
Please enter the password. Between 8-64 characters. Not identical to your email address. Contain at least 3 of: uppercase, lowercase, numbers, and special characters.
Please enter the password.

Change Nickname

Current Nickname:

Apply New License

License Detail

Please complete this required field.

  • Ultipa Graph V4


Please complete this required field.

Please complete this required field.

The MAC address of the server you want to deploy.

Please complete this required field.

Please complete this required field.

Applied Validity Period(days)
Effective Date
Excpired Date
Mac Address
Apply Comment
Review Comment
  • Full Name:
  • Phone:
  • Company:
  • Company Email:
  • Country:
  • Language:
Change Password

You have no license application record.

Certificate Issued at Valid until Serial No. File
Serial No. Valid until File

Not having one? Apply now! >>>

Product Created On ID Amount (USD) Invoice
Product Created On ID Amount (USD) Invoice

No Invoice


      Data Import

      This page shows how to use Ultipa Manager and Ultipa Transporter-Importer to import data files into a GraphSet.

      Graph data used in this article comply to the graph model as introduced in Prepare Graph

      Data File

      Prepare a CSV file for each schema in the graph model, which are CUSTOMER.csv, MERCHANT.csv and TRANSACTION.csv. (click to download)

      • Columns led by headers cust_no in node file CUSTOMER.csv and merchant_no in node file MERCHANT.csv are system property _id of node
      • The rest of columns are custom properties
      • Columns led by headers cust_no and merchant_no in edge file TRANSACTION.csv are system properties _from and _to of edge
      • The rest of columns are custom properties

      Import via Manager

      • Import nodes before importing edges

      Step Breakdown (for node)

      Take importing node file CUSTOMER.csv as an example, the operation includes 5 steps:

      1. Create Loader
      Chart1: Create a loader to import data into graphset retail_test
      1. Create Task
      Chart2: Create a task of CSV type to import node file CUSTOMER.csv
      1. Configure Settings
      Chart3: Configure basic settings for the task

      Details of configuration items in Settings can be found in documentation of Loader.

      1. Configure File
      Chart4: Upload CSV file, configure file format and map data fields with properties

      Tips when mappting data fields with properties:

      • A red triangle for a Property indicates the header does not match with any property under the selected schema, in which case the respective property will be automatically created if the data of this header are to be imported (square box at the left most end checked)
      • Configuration item 'Headless' should be checked if the CSV file is headless, in which case the first row of data indicated by the Property should be modified into property names as they each represent

      Details of configuration items in Files can be found in documentation of Loader.

      Data files in this example use comma ',' as column delimiter and contain headers; header cust_no is system property _id.

      1. Import
      Chart5: Import current task

      Repeat from step-2 to step-5 to import node file MERCHANT.csv. Make sure in step-3 select merchant as schema and in step-4 select _id as Type of merchant_no.

      Complete Demo (for edge)

      Repeat from step-2 to step-5 to import edge file TRASACTION.csv. Make sure in step-3 switch to 'Edge', in step-3 select transfer as schema and in step-4 select _from and _to as Type of cust_no and merchant_no.

      Chart6: A complete demonstration of importing edge file TRASACTION.csv


      Chart7: a complete graph model with correct number of nodes and edges after a successful import

      Import via Transporter

      Comparing with Manager, the import operation via Transporter-Importer supports recognition of property types from file headers, such as:

      The import operation via Transporter-Importer includes 2 steps:

      1. Prepare YML file

      Declare information about Ultipa server and data files in a YML file. Below is part of the YML file:

        - schema: "customer"
          file: "./CUSTOMER2.csv"
        - schema: "merchant"
          file: "./MERCHANT2.csv"
        - schema: "transfer"
          file: "./TRANSACTION2.csv"
      • Download the file package YML_CSV that contains the complete YML file and the data files with updated headers
      • Extract this package and keep all the files in one folder
      • Make sure you update the server information in the YML file with the one you deployed

      See annotations about parameters in the YML file, or read more about the YML file in Import Config.

      1. Run Ultipa Importer in a command line tool

      Place the Importer tool 'ultipa-importer' in the same folder with the extracted YML file and data files, run a command line tool under the same folder and execute command below:

      ./ultipa-importer --config ./import_retail.yml

      Start a command line tool compatible with your system, e.g., right-click the blank space in the folder and click 'Open in Terminal' in an Ubantu system, or shift-right-click and 'Show More' and 'Open in Powershell' in a Windows system.

      If message is received as bash: ./ultipa-importer: Permission denied when running the above command, it suggests that relevant execution privileges are not granted; run chmod +x ultipa-importer to grant privileges required and run the command again.

      Please complete the following information to download this book