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

Correctly calculate the window end timestamp after read from state stores

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0
    • Component/s: streams
    • Labels:

      Description

      When storing the WindowedStore on the persistent KV store, we only use the start timestamp of the window as part of the combo-key as (start-timestamp, key). The reason that we do not add the end-timestamp as well is that we can always calculate it from the start timestamp + window_length, and hence we can save 8 bytes per key on the persistent KV store.

      However, after read it (via WindowedDeserializer) we do not set its end timestamp correctly but just read it as an UnlimitedWindow. We should fix this by calculating its end timestamp as mentioned above.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Yohan123 Richard Yu
                Reporter:
                guozhang Guozhang Wang
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: