-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[destination-s3] No more sync_id in filenames #45084
Comments
Remark : we are using a |
Hello, |
Although destination is configured with S3 Filename pattern = |
@octavia-squidington-iii not sure what does the "community" label mean, but this happens in Airbyte Cloud as well |
can I get a link to the cloud connection where this is happening? #44933 seems pretty unlikely to affect the filename, and I don't see an obvious upstream code change that would cause this I also haven't been able to repro this in my own connection, which is a bit odd |
this should be fixed now - there was an unrelated platform update that got rolled out to a subset of users. We rolled back that update, can you try again? |
Thank you for your feedback. We will check starting tomorrow. We have already recreated most of our connections to avoid this condition so not sure if we can confirm it until few days |
Connector Name
S3 destination
Connector Version
1.0.4
What step the error happened?
During the sync
Relevant information
On airbyte cloud : The sync_id is not anymore present in the generated destination filename for a sync. Everything seems "as usual" but the file is created "without the sync_id", so we have just a file with the run nbr . For example
_58
instead of14235532_58
Our source is shopify
See also https://airbytehq.slack.com/archives/C021JANJ6TY/p1725177438711539
Relevant log output
No response
Contribute
The text was updated successfully, but these errors were encountered: