Incremental mode for notion to Amazon S3 [Parquet] format is replicating duplicating entries in 2nd sync

  • Is this your first time deploying Airbyte?:Yes
  • OS Version / Instance: Windows 10
  • Deployment: Kubernetes
  • Airbyte Version: 0.40.6
  • Source name/version: Notion
  • Destination name/version: Amazon s3 [Parquet File Format] /

Issue came while using source stream: database

I have 2 databases in my source notion
When i replicate data it adds to rows in the parquet file
Now i run 2nd sync with incremental mode, it replicates 1 record in a new file.
My concern is that it should not replicate any data since i have done no change in my source data stream “database”.
The cursor field is set to as source defined i.e “Last_edited_at”. Its value is same but still data is being replicated.

Sync 01 Logs
logs-931.txt (39.4 KB)
Output file after sync 01
sync01_Database.parquet.txt (52.2 KB)

Sync 02 Logs
logs-932.txt (53.0 KB)

Output file after sync 02
Uploading: Sync02_Database.parquet.txt…

This issue is reproducible for all source streams that support incremental mode i.e.

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.
The Community Assistance Team

Hey could you create a github issue around this so that team can get back to you