Connector Improvement: Custom prefix for webhook data to be sent in case of S3 destination
Completed
When we setup events to be sent from WEBHOOKS to S3 we are not able to configure custom location(prefix) to send events to.
Right now, the events are written into root of the bucket.
something like this
<bucket_name>/<company_name>/<connector_name>/<schema>.<table>/2023/NOVEMBER/1/1698863229_1698863262_1698864881793.json.gz
we would appreciate we can get data to below prefix
<bucket_name>/<custom_prefix>/<company_name>/<connector_name>/<schema>.<table>/2023/NOVEMBER/1/1698863229_1698863262_1698864881793.json.gz
-
Official comment
Hi everyone,
We’re excited to announce that the “Custom prefix for webhook data to be sent in case of S3 destination” feature is now live available in our Managed Data Lake Service. During destination creation, Fivetran Managed Data Lake Service destinations have an optional Prefix_path parameter https://fivetran.com/docs/destinations/managed-data-lake-service#storagedirectory.
Thank you all for your valuable feedback and patience as we worked to deliver this improvement.
— Casey Karst
Please sign in to leave a comment.
Comments
1 comment