[ https://issues.apache.org/jira/browse/KAFKA-16382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831208#comment-17831208 ]
Matthias J. Sax commented on KAFKA-16382: ----------------------------------------- An application reset, does not touch the output topic. So it's expected that output from the first run of the app is still in the output topic after the reset. {quote}The issue is NOT reproduced if internal cache is disabled. {quote} That's also sounds like behavior as expected. Caching implies that the output might not contain all intermediate results. I think we can close this ticket as "not a bug" ? > Kafka Streams drop NULL values after reset > ------------------------------------------ > > Key: KAFKA-16382 > URL: https://issues.apache.org/jira/browse/KAFKA-16382 > Project: Kafka > Issue Type: Bug > Components: streams > Affects Versions: 3.6.1 > Reporter: Stanislav Spiridonov > Priority: Major > > Kafka Streams (KTable) drops null values after full reset. > See > [https://github.com/foal/Null-Issue/blob/main/src/main/java/NullProblemExample.java] > for sample topology > Step to reproduce (req NULL-IN, NULL-IN-AUX, NULL-OUT topics) > # Start example - 1st round > # Send to NULL-IN "A1:a" -> NULL-OUT "A1:anull" > # Send to NULL-IN-AUX "A1:b" -> NULL-OUT "A1:anull, A1:ab" > # Stop application > # Run kafka-streams-application-reset > {code:java} > call bin/windows/kafka-streams-application-reset --application-id > nullproblem-example^ > --input-topics "NULL-IN,NULL-IN-AUX"^ > --bootstrap-server "localhost:9092" > {code} > # Send to NULL-IN-AUX "A1:" -> NULL-OUT "A1:anull, A1:ab" - it is Ok (no app > running yet) > # Start example - 2nd round > # After initialization -> NULL-OUT *still contains* "A1:anull, A1:ab" > # Expected output "A1:anull, A1:ab, A1:" > The issue is NOT reproduced if application just restarted (skip step 5). > The issue is NOT reproduced if internal cache is disabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)