CloudSoda Integration - Storage Path Configuration

How to connect DataIntell storage to Soda storage

From the Soda Integration section in the Data Settings page, you can create a new Storage Path Configuration by clicking on the “+” sign in the designated section. From there, you can fill out the required information.

1. DataIntell Storage: A selection of all the DataIntell storage that can be used within the Soda application. These would be both the On-Premises and Cloud storage.
2. Soda Storage: A selection of all the Soda storage that are available right now through the Soda application. These would be the storage that you have already set up in the Soda application.
3. Rule: A rule that allows you to map your DataIntell Storage path to your Soda Storage path if there is a need to do so. More details in the next section.

Setting up a rule for a configuration

A rule is set up in a Storage Path Configuration to map the DataIntell Storage path to the Soda Storage path if there is a difference between both of them that can affect the transfer job.

None: No rule is applied here. An example would be:

• DataIntell Storage path: /mnt/NAS/data
• Soda Storage path: /mnt/NAS/data
• Value of rule: None

Append: Append would append the specified path to the Soda Storage path. An example would be:

• DataIntell Storage path: /mnt/NAS/data
• Soda Storage path: /mnt/NAS
• Value of rule: Append /data
• Result of applied rule: We append /data to Soda Storage path, resulting in /mnt/NAS/data

Ignore: Ignore would ignore the specified path from the end of the Soda Storage path. An example would be:

• DataIntell Storage path: /mnt/NAS
• Soda Storage path: /mnt/NAS/data
• Value of rule: Ignore /data
• Result of applied rule: We ignore /data from the end of the Soda Storage path, resulting in /mnt/NAS

Troubleshoot

There are two scenarios that can lead to unexpected behaviours that should be kept in mind when creating a Storage Path Configuration.

1. If the path in the source files or folders are out of the scope of the applied rule, the files or folders will not be found, which will lead to an error in the Soda jobs.
2. If the path in the target folder is out of the scope of the applied rule, there will be a new folder created with the wrong path and the source files or folders will be transferred into this new folder.