I see from the doc above that new parameters are to be added to the my.cnf file.
The default charset changes to utf8mb4 for the MySql instance; but the database of Jira is currently still in utf8 (because it was created this way). Do I need to do anything to switch it to utf8mb4
?
character_set_server=utf8mb4
Hi @Schups ,
I believe utf8mb4 is only to support emojis - if you don't plan on using them, you can keep the current charset and Jira will work fine with these settings.
Let me know if this helps,
--Alexis
Hi @Schups ,
there is actually an Atlassian documentation page that explains in detail how to do this: https://confluence.atlassian.com/kb/how-to-fix-the-collation-and-character-set-of-a-mysql-database-744326173.html
Keep in mind that this is quite complex and should be done by your database administrator if possible.
--Alexis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Alexis, I didn't find this KB before. I based myself on a similar one: https://confluence.atlassian.com/jirakb/emojis-and-special-characters-for-jira-with-mysql-952604493.html
For changing charsets and collations, I proceeded like this:
Before emojis and other special chars were supported, I had also to update the dbconfig.xml via the config.sh utility. Via diff I find that it removed the characterEncoding parameter from the mysql connection string. I assume it takes advantage of the character_set_server parameter added to the my.cnf file (ref. Jira 8 upgrade procedure).
Emojis are now supported (expect for the activity feeds, which is a known issue reported on the KB I linked above).
Judging from the KB you posted, what I did seems to be equivalent. Do you agree?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Alexis, I didn't find this KB before. I based myself on a similar one: https://confluence.atlassian.com/jirakb/emojis-and-special-characters-for-jira-with-mysql-952604493.html
For changing charsets and collations, I proceeded like this:
Before emojis and other special chars were supported, I had also to update the dbconfig.xml via the config.sh utility. Via diff I find that it removed the characterEncoding parameter from the mysql connection string. I assume it takes advantage of the character_set_server parameter added to the my.cnf file (ref. Jira 8 upgrade procedure).
Emojis are now supported (expect for the activity feeds, which is a known issue reported on the KB I linked above).
Judging from the KB you posted, what I did seems to be equivalent. Do you agree?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Schups ,
it's pretty much the same, the only difference is that the KB explains how to do this directly in MySQL with ALTER statements, where you went for a more manual approach with the find/replace in the dumps.
But in the end, pretty much the same yeah.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.