Skip to content
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 Kafka: connection reset doesn't reset data #10268

Open
akshay-github-acc opened this issue Feb 11, 2022 · 0 comments
Open

Destination Kafka: connection reset doesn't reset data #10268

akshay-github-acc opened this issue Feb 11, 2022 · 0 comments
Labels
area/databases autoteam community connectors/destination/kafka frozen Not being actively worked on help-welcome Accepting external contributions team/destinations Destinations team's backlog type/bug Something isn't working

Comments

@akshay-github-acc
Copy link

akshay-github-acc commented Feb 11, 2022

Environment

  • Airbyte version: 0.32.0-alpha
  • OS Version / Instance: Linux/UNIX
  • Deployment: Docker
  • Memory / Disk: 30GB SSD (c5a.2xlarge)
  • Source Connector and version: Kafka 0.1.2
  • Destination Connector and version: Trying on postgres. ( this is independent )
  • Severity: Medium
  • Step where error happened: During reset.

Following scenario is based on the assumption that Kafka is maintaining data (or some part of the data) and it is expected that data beyond retention period is not recoverable.

Current Behavior

  • When I was working with other source connector. On reset, source's cursor also reset and data starting coming from the beginning of the table. But when I was working with Kafka connector, this behaviour was not reflected here. If someone reset the connection then table from destination get drop and on re-sync no data comes, because kafka offset was not moved back to its initial position.

Expected Behavior

  • On reset, along with deletion of data from destination, Kafka offset should also get reset. Else reset will be a problem for user. User will never able to bring back old data.
    At-least this behaviour is aligned with the behaviour of the other connection.

Logs

Not required. No error is coming on logs.

How to replicate/ Steps to reproduce.

User can ingest data from kafka and after ingestion reset the connection. After complete reset, user can re-sync the connection. No data will be ingested. Unless new data has been loaded by Kafka producer. Also, if new data has been pushed by Kafka producer, then only new data will be ingested, no previous data will come.

Suggestion

Airbyte should able to reset offset using Airbyte's kafka consumer.

@akshay-github-acc akshay-github-acc added needs-triage type/bug Something isn't working labels Feb 11, 2022
@bleonard bleonard added autoteam team/tse Technical Support Engineers labels Apr 26, 2022
@marcosmarxm marcosmarxm changed the title Connection reset doesn't reset Kafka consumer's offset. Destination Kafka: connection reset doesn't reset data Nov 30, 2022
@marcosmarxm marcosmarxm added connectors/destination/kafka area/databases team/destinations Destinations team's backlog and removed needs-triage team/tse Technical Support Engineers labels Nov 30, 2022
@marcosmarxm marcosmarxm added the help-welcome Accepting external contributions label Jun 27, 2023
@bleonard bleonard added the frozen Not being actively worked on label Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/databases autoteam community connectors/destination/kafka frozen Not being actively worked on help-welcome Accepting external contributions team/destinations Destinations team's backlog type/bug Something isn't working
Projects
No open projects
Development

No branches or pull requests

4 participants