potiuk opened a new pull request #17729:
URL: https://github.com/apache/airflow/pull/17729


   The index size is too big in case utf8mb4 is used as encoding
   for MySQL database. We already had `sql_engine_collation_for_ids`
   configuration to allow the id fields to use different collation,
   but the user had to set it up manually in case of a failure to
   create a db and it was not obvious, not discoverable and rather
   clumsy.
   
   Since this is really only a problem with MySQL the easy solution
   is to force this parameter to utf8mb3_general_ci for all mysql
   databases. It has no negative consequences, really as all
   relevant IDs are ASCII anyway.
   
   Related: #17603
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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]


Reply via email to