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

Rollback change which requires join key to be non null on KStream->GlobalKTable

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.7.0
    • Fix Version/s: None
    • Component/s: streams
    • Labels:
      None

      Description

      As part of KAFKA-10277 the behavior for KStream->GlobalKtable joins was changed to require non null join keys.

      But it seems reasonable that not every record will have an existing relationship (and hence a key) with the join globalktable. Think about a User>Car for instance, or PageView>Product. An empty/zero key could be returned by the KeyMapper but that will make a totally unnecessary search into the store.

      I do not think that makes sense for any GlobalKtable join (inner or left) but for left join it sounds even more strange.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                pedrong Pedro Gontijo
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: