Skip to content
This repository has been archived by the owner on Nov 24, 2023. It is now read-only.

meaningless auto resume for "Error 1273: Unsupported collation when new collation is enabled: 'utf8_unicode_ci'" #709

Closed
csuzhangxc opened this issue Jun 3, 2020 · 1 comment
Assignees
Labels
severity/major type/bug This issue is a bug report
Milestone

Comments

@csuzhangxc
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do? If possible, provide a recipe for reproducing the error.

    run a data migration task.

  2. What did you expect to see?

    the task keeps running and data are migrated.

  3. What did you see instead?

    the task keeps running but no data are migrated.

    in the log of DM, got

    "Error 1273: Unsupported collation when new collation is enabled: 'utf8_unicode_ci'"
    
  4. Versions of the cluster

    • DM version (run dmctl -V or dm-worker -V or dm-master -V):

      v2.0.0-beta.1
      
@csuzhangxc csuzhangxc added the type/bug This issue is a bug report label Jun 3, 2020
@csuzhangxc csuzhangxc added this to the v2.0.0 beta.2 milestone Jun 3, 2020
@djshow832
Copy link

TiDB doesn't support utf8_unicode_ci and will support it later, pingcap/tidb#17596
For now, you can either do one of these:

  1. Turn off new collation. That is, to use utf8_bin collation.
  2. Keep the config untouched, change the collation of upstream to utf8_general_ci, it's similar to utf8_unicode_ci

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity/major type/bug This issue is a bug report
Projects
None yet
Development

No branches or pull requests

4 participants