We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
用户使用一些online ddl操作,大致步骤: 第一步:mytable 复制成 _mytable_new 第二部:mytable 改名 _mytable_old 第三部:_mytable_new 改名 mytable 第四部:删除 _mytable_old
同步映射关系配置中,目前只定义了mytable,因为canal进行表匹配,是将rename的源和目标表,只要其中一个满足映射规则条件,就会返回. 所以在第一步时,otter就会收到rename mytable to _mytable_new的sql,而为了保证表结构的正确性,otter会根据rename的目标库清空对应的表结构cache. 因为映射规则没配置_mytable_new,所以就出现了该问题
The text was updated successfully, but these errors were encountered:
解决办法:otter在清空表结构时,检查下对应tablename是否存在映射关系中,如果不存在则忽略之.
针对以上online ddl的同步,几点建议:
Sorry, something went wrong.
fixed issue #57, 特殊处理下rename
9d366a9
agapple
No branches or pull requests
用户使用一些online ddl操作,大致步骤:
第一步:mytable 复制成 _mytable_new
第二部:mytable 改名 _mytable_old
第三部:_mytable_new 改名 mytable
第四部:删除 _mytable_old
同步映射关系配置中,目前只定义了mytable,因为canal进行表匹配,是将rename的源和目标表,只要其中一个满足映射规则条件,就会返回. 所以在第一步时,otter就会收到rename mytable to _mytable_new的sql,而为了保证表结构的正确性,otter会根据rename的目标库清空对应的表结构cache. 因为映射规则没配置_mytable_new,所以就出现了该问题
The text was updated successfully, but these errors were encountered: