Hi there, I have an airflow conflict issue. It's o...
# troubleshooting
a
Hi there, I have an airflow conflict issue. It's only appeared in the last few week, when we rebuilt a docker image. The simplest way to recreate the issue is using a new container based on the
meltano/meltano:latest
docker image, run meltano init and cd into the project directory. The command
meltano add utility airflow
fails. The logs say this relates to "The user requested (constraint) typing-extensions==4.3.0" and says "pydantic 2.0 depending on typing-extensions>=4.6.1". This worked for me a few weeks back, can anyone offer guidance to install airflow from the meltano command line? Thanks
UPDATE: looks like the issue is caused by airflow commit on 22 Nov where they dropped support for Pydantic v1. The airflow plugin on meltano hub needs to be bumped up to fix. Is someone able to guide on where to post this issue? It looks like it's the manifests in meltano/meltano that need updating, as these are fixed at
apache-airflow==2.3.3
e
Hi Alex 👋 Support for Pydantic 2 was added to the airflow extension via a bump to the EDK library here: https://github.com/meltano/airflow-ext/pull/52. The pinned version can be updated by making a PR in https://github.com/meltano/hub/blob/6d73d176f5d99de96476eff67bdc49eda6ad5e23/_data/meltano/utilities/airflow/apache.yml#L54-L55.
a
Thanks @edgar_ramirez_mondragon. I have not done a pull request before, but keen to give it a go. Is it best practice to commit the bump in a new branch of my forked repo? Or just commit in the main branch, before creating pull request. Thx
e
Hi @alex_c. It's always best to do it in a new branch on your fork.