Leah Thomas created KAFKA-10366:
-----------------------------------
Summary: TimeWindowedDeserializer doesn't allow users to set a
custom window size
Key: KAFKA-10366
URL: https://issues.apache.org/jira/browse/KAFKA-10366
Project: Kafka
Issue Type: Bug
Reporter: Leah Thomas
Assignee: Leah Thomas
Related to [KAFKA-4468|https://issues.apache.org/jira/browse/KAFKA-4468], in
timeWindowedDeserializer Long.MAX_VALUE is used as _windowSize_ for any
deserializer that uses the default constructor. While streams apps can pass in
a window size in serdes or while creating a timeWindowedDeserializer, the
deserializer that is actually used in processing the messages is created by the
Kafka consumer, without passing in the set windowSize. The deserializer the
consumer creates uses the configs, but as there is no config for windowSize,
the window size is always default.
See _KStreamAggregationIntegrationTest #ShouldReduceWindowed()_ as an example
of this issue. Despite passing in the windowSize to both the serdes and the
timeWindowedDeserializer, the window size is set to Long.MAX_VALUE.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
