[GitHub] [airflow] sterling-jackson commented on issue #26497: Upgrading to airflow 2.4.0 from 2.3.4 causes NotNullViolation error

[GitBox <gi...@apache.org>]

sterling-jackson commented on issue #26497:
URL: https://github.com/apache/airflow/issues/26497#issuecomment-1259688770

   We saw the same problem this past week with in an attempted upgrade to 2.4. Initially tried the database upgrade path and also tried resetting the database with `airflow db reset`. Same problem appeared both ways. DAGs would show up in the CLI and in the UI, but an error would be thrown when trying to view details and the scheduler was logging errors that they weren't in the serialized DAG table. Attempting to run `airflow dags reserialize` would throw a mess of null constraint errors.
   
   We ended up reaching into the metadata database (Postgres) and making the id column in the four permissions tables an IDENTITY column. It seems to have stabilized and is now running, but I'm concerned about potential ramifications and am not planning to promote this change into our production environment at this point in time. The id column _looks_ like a row ID, but there may very well be relations I'm not aware of that depend on it being set in a particular way versus using an identity / auto increment column.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org