potiuk commented on issue #24526: URL: https://github.com/apache/airflow/issues/24526#issuecomment-1190539682
> question Am I doing the right thing with the character set and collation? Yes. But you should also do it for all colums that use different collation (the different CHARACTER seet for thos should be `uf8mb3`). I just looked through all the tables columns and here is a complete list (most of the new ones should have it correctly set - simply not sure which ones were already in 2.2.5): * slamiss: dag_id * taskmap: dag_id, task_id, run_id * taskreschedule: dag_id, task_id, run_id * xcom: dag_id, task_id, run_id, key * dagrun: dag_id, run_id * dagwarning: dag_id * log: dag_id, task_id * renderedtifields: dag_id, task_id, run_id * taskfail: dag_id, task_id, run_id * taskinstance: dag_id, task_id, run_id, external_executor_id Also I think the above comment sets another trap on you using utf8 and utf8_bin is very bad idea. MySQL 8 set a trap on you here, because if you migrate to the next version, the index will likely not increase but utf8 will become an alias to utf8mb4 (in MySQL 8 it is utf8mb3): https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8.html CHARSET/COLLATION for the "id" fields should be explicitly `utf8mb3' and collation 'utf8mb3_bin' NOT 'utf8', 'utf8_bin' The trap is a bit deeper, because is (as they warn) they remove utf8mb3 in the future then you will be locked witth MySQL8. My recommendation is as usual here: Switch to Postgres. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
