Ultipa Transporter supports cross platform operations of importing data from files (i.e., CSV, JSON), MySQL, BigQuery, Neo4J, etc. as well as exporting data as files.
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 usingproperties
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
totimeZone
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
- {latitude:value,longitude:value} i.e.:
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 offile
)
V4.3.5
- Added
new_name
for modifying field name (undertypes
) - Modified logic when setting field type: yml > headers > default string
- Supports list, point type
- Parses null for no data between two delimiters