Skip to main content
Archived

S3Connector needs to be further improved

Related products:Transformers
  • March 28, 2019
  • 1 reply
  • 24 views

Forum|alt.badge.img

The S3Connector would be useful if there could be a Writer that intigrates and uses the connection to an S3 bucket (i.e., treat it like a virtual drive. So anywhere you define a file path, an S3 bucket connection/path can be specified making S3 storage as transparent as possible.

Also, within the S3Connector parameters that there are only two options for "If file exists": Reject or Overwrite. It would also be very useful to add an Append option so that the same zip file can be used for scenarios where batches of workspace runs can be captured in a single zip file...

I'm hoping this gets into 2019 sooner than later.

Thanks for all you do...


Also, suggest adding a s3connector topic.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

Forum|alt.badge.img+3
  • August 13, 2019

"Destination " needs an option to "Suffix Path Last Folder" in the "Download to Folder:". ie.

 

1. option = Yes: this is how the S3Connector currently works, it suffixes the last folder in the Path to the "Download as:" folder, then the contents

 

"Download Options - Path: folder1/sub1/sub2/sub3/"

 

"Destination - Download as: Folder"

 

"Destination - Suffix Path Last Folder: Yes"

 

"Destination - Download to Folder: folder2/sub4/sub5/sub6/"

 

-sub3 and it's contents will be downloaded to folder2/sub4/sub5/sub6/sub3/<contents>

 

-this is frustrating when you are trying to maintain the same structure under folder1 and folder2

 

2. option = No: in this case the Path Last Folder is left off and only the contents is downloaded

 

"Download Options - Path: folder1/sub1/sub2/sub3/"

 

"Destination - Download as: Folder"

 

"Destination - Suffix Path Last Folder: No"

 

"Destination - Download to Folder: folder2/sub4/sub5/sub6/"

 

-sub3 contents will be downloaded to folder2/sub4/sub5/sub6/<contents>

 

For even more flexibility the Suffix Path Last Folder could be an integer to suffix the last N folders, with default 1, ie.

 

"Download Options - Path: folder1/sub1/sub2/sub3/"

 

"Destination - Download as: Folder"

 

"Destination - Suffix Path Last Folders: 2"

 

"Destination - Download to Folder: folder2/sub4/sub5/sub6/"

 

-sub3 contents will be downloaded to folder2/sub4/sub5/sub6/sub2/sub3/<contents>

 

"Download Options - Path: folder1/sub1/sub2/sub3/"

 

"Destination - Download as: Folder"

 

"Destination - Suffix Path Last Folders: 0"

 

"Destination - Download to Folder: folder2/sub4/sub5/sub6/"

 

-sub3 contents will be downloaded to folder2/sub4/sub5/sub6/<contents>