-
Notifications
You must be signed in to change notification settings - Fork 15.1k
STORE_DAG_CODE not displaying correct code for zipped dag files #14412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Could you please test this on Airflow 2.0 and let us know if the problem persists there? |
This issue has been automatically marked as stale because it has been open for 30 days with no response from the author. It will be closed in next 7 days if no further activity occurs from the issue author. |
Any luck with testing @prithvisathiya with Airflow >= 2? |
hey, sorry for late reply. Recent changes have made de-prioritize this issue for the last couple months. If I remember correctly, it was affecting Airflow >= 2 as well, but I will double check and update here shortly |
This was fixed by #13984 and was released in 2.1.0, let us know if it is still the issue and we can reopen it |
Apache Airflow version:
1.10.14
Kubernetes version (if you are using kubernetes) (use
kubectl version
):1.19.4
Environment:
uname -a
):What happened:
I recently upgraded from 1.10.9 -> 1.10.14, and enabled both
STORE_SERIALIZED_DAGS
andSTORE_DAG_CODE
to True. Everything seems to work as expected, and the scheduler is able to execute the DAG and the tasks within. However, the "Code View" in the UI displays a very long hex string instead of the actual code.I have narrowed it down to be an issue, only when dag file is stored within zip files. For example,
my_dag.py
andmy_other_dag.py
would show in the UI incorrectly in the following case:but this is fine:
A quick look at the database also reflects the incorrectly parsed DAG code within the
source_code
column of thepublic.dag_code
table. But the fact that the scheduler can execute the dag, and that thedata
column of thepublic.serialized_dag
table contains the correct code, suggests that this issue is isolated only when storing within thedag_code
table.What you expected to happen:
I should expect the actual python code to show in UI
How to reproduce it:
Create 2 similar dags (1 within zip and 1 unzipped) and place into root dags folder. The UI will display the
dag2.py
incorrectly, but work fine fordag1.py
The text was updated successfully, but these errors were encountered: