Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-10366

TimeWindowedDeserializer doesn't allow users to set a custom window size

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.8.0
    • None

    Description

      Related to 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. 

      Attachments

        Issue Links

          Activity

            People

              lthomas Leah Thomas
              lthomas Leah Thomas
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: