Remote Filesystem Connection
A remote connection is a connection to an usually cloud-based remote repository, where flows or datasets can be stored.
You will find more information on how to set remote connections in the Establishing Remote Connections page.
Rulex's technical documentation does not and cannot provide comprehensive guidelines on the use of third-party software, beyond how Rulex integrates with this software. Please consult the technical documentation of the third-party software itself for up to date information.
The remote connection can be used to perform the following operations:
Flow operations | Dataset operations |
|---|---|
Focus on the Remote Filesystem in the cloud version
Using a Remote Filesystem as a data source in the cloud version implies the following:
In Import tasks, if the underlying source dataset is modified, then it gets updated at the first following computation.
In Export tasks, if the resulting dataset has already been exported from Rulex Platform and after the export further operations on data have been performed, the exported dataset gets updated at the first following computation.
Focus on the Remote Filesystem in the standalone version
Once the remote connection is set, you can import the files in it. When working in the standalone version, as the connection to the filesystem is set temporarily, you need to re-establish the connection to the filesystem and to import the file again, otherwise you won’t be able to see the changes occurred to the datasets.
Working with remote connections in the standalone version can be useful if you are not using datasets which get updated regularly by you or by other users, and they are stored remotely for other reasons.
The reason is that the file is imported in a machine-based software, so any change to the file made after the import operation won’t be applied to the imported version of the file.
When exporting datasets in the standalone version, if you perform further operations on the outcoming datasets after having exported them, you need to re-establish the connection to the remote repository.