[
https://issues.apache.org/jira/browse/KAFKA-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035043#comment-17035043
]
ASF GitHub Bot commented on KAFKA-9500:
---------------------------------------
vvcephei commented on pull request #8015: KAFKA-9500: Fix topology bug in
foreign key joins
URL: https://github.com/apache/kafka/pull/8015
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Foreign-Key Join creates an invalid topology
> --------------------------------------------
>
> Key: KAFKA-9500
> URL: https://issues.apache.org/jira/browse/KAFKA-9500
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.4.0
> Reporter: John Roesler
> Assignee: John Roesler
> Priority: Blocker
> Fix For: 2.5.0, 2.4.1
>
>
> Foreign-Key Join results are not required to be materialized by default, but
> they might be needed if downstream operators need to perform lookups on the
> result (such as when the join result participates in an equi-join).
> Currently, if the result is explicitly materialized (via Materialized), this
> works correctly, but if the result is _not_ materialized explicitly, but _is_
> needed, the topology builder throws an exception that the result store isn't
> added to the topology. This was an oversight in testing and review and needs
> to be fixed ASAP.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
