[jira] [Created] (KAFKA-16585) No way to forward message from punctuation method in the FixedKeyProcessor

[Stanislav Spiridonov (Jira)]

Stanislav Spiridonov created KAFKA-16585:


 Summary: No way to forward message from punctuation method in the 
FixedKeyProcessor
 Key: KAFKA-16585
 URL: https://issues.apache.org/jira/browse/KAFKA-16585
 Project: Kafka
  Issue Type: Bug
  Components: streams
Affects Versions: 3.6.2
Reporter: Stanislav Spiridonov


The FixedKeyProcessorContext can forward only FixedKeyRecord. This class 
doesn't have a public constructor and can be created based on existing records. 
But such record usually is absent in the punctuation method.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-16382) Kafka Streams drop NULL values after reset

[Stanislav Spiridonov (Jira)]

Stanislav Spiridonov created KAFKA-16382:


 Summary: 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


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)