I've set up the MAC vectors connector and deployed it to Cloud Hub 2.0. While uploading the files, I noticed that the connector can only read files from a local file path. To do it, I needed to write my files to the /tmp folder in Cloud Hub and delete them after the upload. Example of the flow below:
It would be nice if the connector could offer to directly upload files from for example Azure/AWS bucket/Google Drive.
Since writing in the 'tmp 'folder has its limitations, and since you don't know how much free space there actually is and your files can sometimes be larger, you risk crashing the pod when it runs out of disk space
If the files are already in an S3 bucket the flow would look like this
which uses a lot of resources instead of loading the files directly
Hi everyone,
I've set up the MAC vectors connector and deployed it to Cloud Hub 2.0. While uploading the files, I noticed that the connector can only read files from a local file path. To do it, I needed to write my files to the
/tmp
folder in Cloud Hub and delete them after the upload. Example of the flow below:It would be nice if the connector could offer to directly upload files from for example Azure/AWS bucket/Google Drive. Since writing in the 'tmp 'folder has its limitations, and since you don't know how much free space there actually is and your files can sometimes be larger, you risk crashing the pod when it runs out of disk space
If the files are already in an S3 bucket the flow would look like this
which uses a lot of resources instead of loading the files directly