Syncs for Data Lake destinations are failing with table corruption error
Incident
Report for Fivetran
Subscribe to Updates
Update
Customers with bucket versioning enabled, please attach the below policy to the role ARN mentioned in the destination setup form, and then we will restore the files from our end:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:GetBucketVersioning",
"s3:ListBucketVersions"
],
"Resource": [
"arn:aws:s3:::your-bucket-name"
]
}
]
}
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:GetBucketVersioning",
"s3:ListBucketVersions"
],
"Resource": [
"arn:aws:s3:::your-bucket-name"
]
}
]
}
Update
Customers with bucket versioning enabled can proceed to restore all files for their bucket to allow the sync to complete successfully. For customers without bucket versioning enabled, our engineering team is actively working on determining the next steps and will provide further guidance shortly
Update
We have identified the root cause of the issue, which was related to orphan file cleanup deleting some active files. A hotfix has been deployed to prevent further impact. We are currently working on unlinking the deleted files to restore sync functionality. Our team continues to actively work on resolving this.
Update
We are continuing to work on a fix for this issue.
Identified
The issue has been identified and we are working to resolve it.
This incident affects: Systems (Destinations).