Hi everyone. I'm trying to use Kafka topic as a source. Test passed with one warning

WARN c.n.s.JsonMetaSchema(newValidator):338 - Unknown keyword examples - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword

Topic contains fresh messages but sync returned "no records"

2022-10-26 06:24:14 WARN i.a.w.g.DefaultReplicationWorker(run):305 - State capture: No new state, falling back on input state: io.airbyte.config.State@2820a8af[state={}]
2022-10-26 06:24:14 INFO i.a.w.g.DefaultReplicationWorker(run):316 - sync summary: {
  "status" : "completed",
  "recordsSynced" : 0,
  "bytesSynced" : 0,
  "startTime" : 1666765438208,
  "endTime" : 1666765454843,
  "totalStats" : {
    "recordsEmitted" : 0,
    "bytesEmitted" : 0,
    "sourceStateMessagesEmitted" : 0,
    "destinationStateMessagesEmitted" : 0,
    "recordsCommitted" : 0,
    "meanSecondsBeforeSourceStateMessageEmitted" : 0,
    "maxSecondsBeforeSourceStateMessageEmitted" : 0,
    "maxSecondsBetweenStateMessageEmittedandCommitted" : 0,
    "meanSecondsBetweenStateMessageEmittedandCommitted" : 0,
    "replicationStartTime" : 1666765438208,
    "replicationEndTime" : 1666765454843,
    "sourceReadStartTime" : 1666765438243,
    "sourceReadEndTime" : 1666765452324,
    "destinationWriteStartTime" : 1666765438295,
    "destinationWriteEndTime" : 1666765454842
  },
  "streamStats" : [ ]
}

What should I do to detect the problem?

Hi! That issue does seem applicable. As Kafka is an alpha connector, issues like this are typically not prioritized at this stage. Have you tried this workaround form one of the users? https://github.com/airbytehq/airbyte/issues/8875#issuecomment-1181828864

Parameter

1000ms

helped to fill _airbyte_raw_<topic_name>, but target table <topic_name> is empty.

Auto Offset Reset

works in

earliest

and

latest

value.

Thanks for your patience, @Andriy Khomenko! At this point it looks like the best bet is to comment and upvote that GitHub issue, unfortunately. I apologize for the inconvenience and sorry to hear that the workaround isn't working for you. Would you be willing to look into contributing a PR?

Yes. I can look into this PR. @Nataly Merezhuk (Airbyte)

Wonderful, thank you!