Understanding why Airbyte thinks records are invalid

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Ubuntu EC2 t3.xlarge
  • Memory / Disk: 16Gb/ 100Gb (gp3)
  • Deployment: Docker on EC2 instance
  • Airbyte Version: 0.40.18
  • Source name/version: source-postgres 1.0.22
  • Destination name/version: destination-redshift 0.3.51
  • Step: when i’m validating it worked as expected
  • Description:
    The job ends with message: Sync Succeeded 10,000,000 emitted records | 10,000,000 committed records
    But there are only 9,986,326 rows in the raw destination (I’m going to do manual normalisation)
    So I check the log and there’s a line saying
    A total of 13674 record(s) of data from stream AirbyteStreamNameNamespacePair{name='events_196', namespace='analytics_raw'} were invalid and were ignored.
    But I don’t know how to find out why airbyte thinks these are invalid, obviously I need them and they are valid in the source.
    The table i’m trying to load has nearly 2B rows so this was just a sample sub-set.
    I’m going direct Postgres to Redshift Serverless

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

Hello tonkas, it’s been a while without an update from us. Are you still having problems or did you find a solution?