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

A KStream/GlobalKTable join shouldn't reset the repartition flag

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.1
    • Fix Version/s: 1.1.2, 2.2.0, 2.1.1, 2.0.2
    • Component/s: streams
    • Labels:
      None

      Description

      Currently a KStream/GlobalKTable join resets the repartition required flag to false.

      I have a topology where I map a stream, join with a GlobalKTable, then groupByKey then aggregate.

      The aggregate wasn't behaving correctly because it didn't force a repartition as I expected. The KStream/GlobalKTable join had reset the flag and hence I was getting the same keys in different partitions.

      Since a KStream/GlobalKTable join does not itself force a repartition, it should simply propagate the flag down to the resultant KStream the same way most other operators work.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bbejeck Bill Bejeck
                Reporter:
                kiwiandy Andy Bryant
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: