fix(mysql): Update default mysql collation to utf8mb4_bin #3459
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the collation we were using for permitting unicode and emoji style characters was case insensitive. This was causing conflicts among URNs that had the same characters but different casing. This PR updates the default to use a case sensitive collation.
Existing deployments can be updated to use the new collation by executing the following command against your SQL store (verified against MySQL):
ALTER TABLE metadata_aspect_v2 CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;
Verified this works on demo.datahubproject.io, which previously was erroring out on URNs that were same exception for casing.
Checklist