Almog Gavra
Almog Gavra
Just to update this ticket, we have the feature code complete (#9234) but it's causing some tests to fail and dramatically increasing the time it takes to run our tests....
@patrickstuedi will time box some investigation here, otherwise we'll pull it into the HA rewrite that we're planning on doing in a bit. 0.24 is improved because of @AlanConfluent's work...
@anupsdtiwari are you hitting the deadlock? if so do you mind posting thread dumps from your three node clusters here? that will help debug it
Can you share the sql statements you used to get to that? You shouldn't need to materialize a stream at all.
@suhas-satish this looks related to the value schema id work and I've actually seen this error pretty frequently in our cloud now, we should triage it with high priority.
@dberardo-com can you give us more information on your setup/configurations?
@colinhicks can you help me understand the priority of this?
@vcrfxia - I think the one thing that's interesting is that this isn't technically a self-join since there is no loop (though the limitation in KS probably still applies here):...
@SamiShaikh protobuf doesn't support nulls, so this is somewhat expected behavior. Perhaps we can make the error message more instructive though!
Hello @Perdjesk thanks for reporting this! I'm afraid this might not be a simple change (see https://github.com/confluentinc/ksql/pull/4965#pullrequestreview-385955315). Is this blocking you for something or is it just a nice-to-have?