[
https://issues.apache.org/jira/browse/FLINK-36114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875816#comment-17875816
]
Leonard Xu edited comment on FLINK-36114 at 8/27/24 4:58 PM:
-------------------------------------------------------------
Fixed in master: ee843e2f246c300ecfeaf5cfd529693fadf2625f
release-3.2: 6dd1c11fe13f29fcaf202c35234040f44383e3bf
was (Author: leonard xu):
Fixed in master: ee843e2f246c300ecfeaf5cfd529693fadf2625f
> Schema registry should block when handling existing requests
> ------------------------------------------------------------
>
> Key: FLINK-36114
> URL: https://issues.apache.org/jira/browse/FLINK-36114
> Project: Flink
> Issue Type: Bug
> Components: Flink CDC
> Affects Versions: cdc-3.1.1
> Reporter: yux
> Assignee: yux
> Priority: Blocker
> Labels: pull-request-available
> Fix For: cdc-3.2.0
>
>
> Currently, SchemaRegistry asynchronously receives schema change requests from
> SchemaOperator, and results of multiple requests might got mixed up together,
> causing incorrect logic flow in multiple parallelism cases.
> Changing SchemaRegistry's behavior to accept requests in serial should
> resolve this problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
