-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blocker: compatibility break in joins #6406
Comments
Needs this AK fix: https://issues.apache.org/jira/browse/KAFKA-10494 |
Adding needs-triage so that we will assign it in our weekly meeting. |
Removed needs triage label as I'm already working on it :p |
@big-andy-coates is this on track to be fixed in the coming week. cc @vpapavas |
also cc @mjsax who may have context. |
The AK ticket linked above is already merged: #6406 (comment) -- not sure if there is any ksql follow up work to do or if this can be closed. |
fixes: confluentinc#6406 The upstream fix is now available, so these tests can be re-enabled.
fixes: #6406 The upstream fix is now available, so these tests can be re-enabled. Co-authored-by: Andy Coates <[email protected]>
Description
AK commit apache/kafka#9156 introduced a compatibility breaking change: it's causing table source nodes to be materialized into a state store, even through the later mapValues node is already materialized. This MUST be fixed before we release off of master.
The following historic tests have been disabled:
ksqldb-functional-tests/src/test/resources/historical_plans/joins_-table_table_join_with_where_clause/6.0.0_1594233291874
ksqldb-functional-tests/src/test/resources/historical_plans/joins-_table_table_join_with_where_clause/6.1.0_1594164287151
The topology has changed due to the Apache Kafka change:
old topology
new topology:
Note how the
KSTREAM-SOURCE
nodes have state stores now.The text was updated successfully, but these errors were encountered: