Ultipa Transporter supports cross platform operations of importing data from file, database, data warehouse, distributed stream, etc. as well as exporting data as CSV files. It has two components Importer and Exporter:

• ultipa-importer:

  • Support creating graphset, schema and property in the Ultipa database
  • Support importing into multiple schemas
  • Support prefix processing for data IDs

• ultipa-export:

  • Supports exporting to CSV (separated by comma)
  • Supports exporting into multiple schemas

Prerequisites

• data files, or the link of data source
• a command line terminal, such as:
  • Linux: bash, zsh, tcsh
  • MacOS X Terminal, iTerm
  • Windows: PowerShell
• a version of Ultipa Importer/Exporter compatible with your operating system

Change Log

V4.3.22

• Added support of neo4j by mode
• Supports importing CSV files from folder

V4.3.18

• Supports configuration of SFTP for importing and exporting files

V4.3.17

• Added support of json and jsonl by mode

V4.3.16

• Obsolete types and keep using properties to configure data fields for all data sources
• Added head to declare whether the CSV file has header

V4.3.15

• Added support of kafka by mode
• Added prefix to append string before data of _id, _from and _to
• Modify timezone to timeZone

V4.3.12

• Added support of sqlserver by mode

V4.3.10

• Supports CSV field separators: ^A，^B，^C，^D
• Supports data formats of point type:
  • {latitude:value,longitude:value} i.e.: {latitude:48.5, longitude:22.2}
  • [latitude, longitude] i.e.: [48.5, 22.2]
  • latitude, longitude i.e.: 48.5, 22.2

V4.3.8

• Supports value of mode: csv/bigQuery/postgreSQL/mysql
• Added sqlDatabase to configure database informationof MySQL and ostgresSQL
• Added quotes to configure the meaning of double quotation in the data field

V4.3.6

• Added mode to declare source type
• Added bigQuery to configure BigQuery project information
• Added sql to acquire data fields from BigQuery project (in replace of file)

V4.3.5

• Added new_name for modifying field name (under types)
• Modified logic when setting field type: yml > headers > default string
• Supports list, point type
• Parses null for no data between two delimiters