Skip to main content

Features

FeatureSupportedNotes
Set pipeline frequencyYesFor more details, see the guide.
Full load synchronizationYes
Incremental - Append synchronizationNo
Select collected tablesYes
VPN connectionYesConnections are only possible through a VPN.

Quick Start

To create a pipeline, open the Collect module, go to "Pipelines", and click "New Pipeline".

Choose the Data Source​

Use an existing source or register a new one​

Connection Parameters (Source Registration)​

Field nameDescriptionExample
EndpointPublic address for connecting to your database, in a valid IPv4 or DNS format32.142.63.4
Port numberDatabase port27017
Connection typeOnly VPN connections are supported, to access private databases
UserDatabase useradmin
PasswordDatabase user's password
Authentication databaseDatabase where the user is definedmy-db

Pipeline Information​

Assign a name and a brief description to your pipeline.​

Pipeline Configuration Parameters​

Field nameDescriptionExample
DatabaseDatabase where the databases will be synchronizedmy-db
Enable SSL (optional)Enable SSL for encrypted collection

Specify Tables​

Enter the names of the database tables to collect.

📘

A separate dataset is created in the catalog for each imported table.

Scheduling​

  • Finally, configure how often your pipeline should run. Choose one of the available options or enter a custom frequency using a cron expression. For more information, see the guide.

📘

  • The default time zone for scheduling is UTC.

  • All frequency methods define when extractions begin. They do not control how long replication runs or when the data actually reaches its destination.

Done! Wait for collection to run on the scheduled day and time.

To run the pipeline immediately, you can start it manually within 30 seconds after creating it. Go to "Pipelines", "List", and "Synchronize Pipeline".

After a few minutes, your pipeline will be cataloged as a Data Asset in the Explore tab.

You can also open "View pipeline" in the pipeline list to review the summary, collected entities and columns, execution history, and micro-transformation history.