KAFKA-4880 (a dupe of this ticket), @Michael Noll writes:
> FWIW, I wonder how much interest there actually is for this functionality. Users have been requesting stream-globalTable joins, but personally I have yet to run into a person that wants table-globalTable joins. Just saying.
I hadn't noticed that GlobalKTables were severely limited and assumed they had all the functionality of regular tables. I had been really excited to use them for "hydration"/denormalization. I have two models which will be present in my application in different quantities. Instances of one model will be very few in quantity compared to instances of the second model. I want to "hydrate" instances of the high-quantity model with instances of the low-quantity model, which can be available in its entirety on all streams app instances. KTable/KTable joins are great for denormalization because you can drive the update from both sides of the relationship. KTable/GlobalKTable joins would facilitates such updates while removing the need to repartition the left table.