You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Leonard Xu (Jira)" <ji...@apache.org> on 2024/11/15 13:25:00 UTC

[jira] [Assigned] (FLINK-36697) Quickly evolving schema change in Doris fails

     [ https://issues.apache.org/jira/browse/FLINK-36697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonard Xu reassigned FLINK-36697:
----------------------------------

    Assignee: yux

> Quickly evolving schema change in Doris fails
> ---------------------------------------------
>
>                 Key: FLINK-36697
>                 URL: https://issues.apache.org/jira/browse/FLINK-36697
>             Project: Flink
>          Issue Type: Bug
>          Components: Flink CDC
>    Affects Versions: cdc-3.2.0
>            Reporter: yux
>            Assignee: yux
>            Priority: Major
>
> Unlike StarRocks, Doris metadata applier doesn't check if state is finished. So if we're executing schema changes consecutively, Doris connector will complain with:
>  * <TABLE>'s state(SCHEMA_CHANGE) is not NORMAL. Do not allow doing ALTER ops
> this exception. Adding loopcheck and ensures table state to be NORMAL before returning should help.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)