Sighery commented on issue #32657:
URL: https://github.com/apache/airflow/issues/32657#issuecomment-1648206389

   @jens-scheffler-bosch @potiuk So, tried it today [in my 
fork](https://github.com/Sighery/airflow/pull/1). I think I managed to set up 
the required CI checks correctly. I couldn't get Breeze to work locally (using 
NixOS which is a fair bit different to most other Linux distros), so I had to 
settle for the CI runs.
   
   [MySQL is indeed failing with the 
migrations](https://github.com/Sighery/airflow/actions/runs/5644920445/job/15290684879?pr=1#step:5:1735).
 But it's strange, it actually fails when downgrading. And it fails on 
downgrading [migration 
0079](https://github.com/apache/airflow/blob/d05e42e5d2081909c9c33de4bd4dfb759ac860c1/airflow/migrations/versions/0079_2_0_2_increase_size_of_connection_extra_field_.py#L4).
 This was the `extra` field in connection that used to be a `5000` characters 
`VARCHAR`. Migration 79 converted it to `TEXT`. The downgrade then tries to 
convert it back into `VARCHAR(5000)` and fails.
   
   Not quite sure why this happens only after applying `VARCHAR(5000)` change 
to `login`. The downgrade of the `login` migration should also bring it back 
down to `VARCHAR(500)`, unless I messed up somewhere. If I didn't mess up the 
downgrade code, I'm guessing perhaps downgrading length afterwards doesn't 
decrease/release the page size, at least not in MySQL.


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