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

StreamResetter shall be invoked to cleanup what was stored in Apache Kafka Streams #61

Closed
masesdevelopers opened this issue Sep 7, 2023 · 0 comments · Fixed by #63
Closed
Assignees
Labels
bug Something isn't working

Comments

@masesdevelopers
Copy link
Collaborator

Describe the bug
When the application is restarted, using the same ApplicationId, previously stored data in Apache Kafka Streams can impact the behavior of the application.

To Reproduce
Steps to reproduce the behavior:

  1. Change the test program adding/removing some values at the end of the current queries (e.g. add 100 items)
  2. Execute the test program
  3. Execute again the test program
  4. The following trace does not report the current values (expected 1000), but reports something like KafkaEnumerator - ApproximateNumEntries 1100 which means the stream application had stored the latest test done

Expected behavior
The stream application shall be resetted before

context.Database.EnsureDeleted();
is invoked.
This can be done manually from command-line or KNet shall be enhanced to do that programmatically.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • Latest KEFCore version

Additional context
N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment