[
https://issues.apache.org/jira/browse/FLINK-36076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874940#comment-17874940
]
Leonard Xu edited comment on FLINK-36076 at 8/27/24 5:01 PM:
-------------------------------------------------------------
master: d3473de4db92229eb09e1e4c698a2db5448c8805
3.2: 9f358ab1d7c2693d475560dd02d62a75ebe659ef
was (Author: leonard xu):
master: d3473de4db92229eb09e1e4c698a2db5448c8805
3.2: TODO
> Hotfix: Set isSchemaChangeApplying as volatile for thread safe.
> ---------------------------------------------------------------
>
> Key: FLINK-36076
> URL: https://issues.apache.org/jira/browse/FLINK-36076
> Project: Flink
> Issue Type: Technical Debt
> Components: Flink CDC
> Affects Versions: cdc-3.1.1
> Reporter: Hongshun Wang
> Assignee: Hongshun Wang
> Priority: Blocker
> Labels: pull-request-available
> Fix For: cdc-3.2.0
>
>
> Current, we apply schema change asynchronous.
> SchemaChangeThreadPool will set isSchemaChangeApplying as true when apply
> schema change event. And the main thread which handle operater event will
> check isSchemaChangeApplying.
>
> For thread safe, this should be volatile.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
