S3 / CSV Incremental strategy

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Memory / Disk: 4gb
  • Deployment: Elastic Beanstalk /w Docker
  • Airbyte Version: 40.1
  • Source name/version: S3/latest
  • Destination name/version: Postgres/latest
  • Step: Sync

I’m using the S3 connector with CSV files. This works perfectly when using the full refresh | overwrite strategy with the one problem that it wipes out any views I might have created (I assume because the refresh drops the table that the view is dependent on).

However, if I want to use one of the incremental strategies, it seems I’m unable to select the cursor field (it defaults to _ab_source_file_last_modified).

I have a created_at field which I think would be more suitable for the cursor but I’m also aware that might be misunderstanding something about the way the S3/CSV system works.

When I’ve used the incremental strategy with the _ab_source_file_last_modified I get a lot of duplicates, I suspect that this is due to me replacing the CSV on a periodic basis. Should I instead be saving increments of the dump and relying on the wildcard selector to pick these up?

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

Thanks, looking forward to some feedback about how best to implement the S3/CSV pattern as it’s not clear from the documentation about how you are supposed to structure the files.

Bumping this. Some high level guidance around how we should be architecting the S3 / CSV connector would be welcome. Should we be thinking about incremental data dumps? How do others handle the need to retroactively change data without getting duplicates entries? Can we use a primary key in the CSV file?