[
https://issues.apache.org/jira/browse/KAFKA-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953398#comment-16953398
]
ASF GitHub Bot commented on KAFKA-9058:
---------------------------------------
vvcephei commented on pull request #7541: KAFKA-9058: Lift queriable and
materialized restrictions on FK Join
URL: https://github.com/apache/kafka/pull/7541
Update foreign key joins not to require materialization or queriability to
function.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
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:
[email protected]
> Foreign Key Join should not require a queriable store
> -----------------------------------------------------
>
> Key: KAFKA-9058
> URL: https://issues.apache.org/jira/browse/KAFKA-9058
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 2.4.0
> Reporter: John Roesler
> Assignee: John Roesler
> Priority: Blocker
> Labels: streams
>
> While resolving KAFKA-9000, I uncovered a significant flaw in the
> implementation of foreign key joins. The join only works if supplied with a
> queriable store. I think this was simply an oversight during implementation
> and review.
> It would be better to fix this now before the release, since the restriction
> it places on users could represent a significant burden. If they don't
> otherwise need the store to be queriable, then they shouldn't be forced to
> allocate enough storage for a full copy of the join result, or add the
> changelog topic for it either.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
