Destination Improvement: S3 as destination currently pushed the connector name into the prefix-name within S3 as-well, can this be configuration driven
AnsweredWhen we use the S3 destination today, the name of the connector is been pushed as the prefix construct with database-name from source following the connector-name. Currently we don't want to push the name of the connector to the S3 prefix, but we don't have a choice or flexibility to do that. Is this something than can be changed in fivetran side to make it more configuration driven?Â
-
Official comment
Hi Mohan,
Thank you for taking the time to submit this feature request and share your thoughts about the S3 destination prefix configuration. At this time, this feature is not on our current product roadmap. However, we rely heavily on user feedback and upvotes to gauge demand and prioritize future improvements—every upvote this request receives helps strengthen the case for us to consider it.
Thanks again for your input!
Best regards,
Casey Karst
Please sign in to leave a comment.
Comments
1 comment