We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
s we discussed in the thread on Spec thread for our new API, the idea came up of making conn_id unique in Airflow
https://lists.apache.org/thread.html/rfb6f7d95b2754fda9dd09b08444214dfad12d10f143d32de0fcf4104%40%3Cdev.airflow.apache.org%3E
The people in that thread seemed to be in favour of it:
Given the downsides/work arounds, and the confusion this causes we should remove this (mis)feature from Airflow 2.0.
We should take some care in the migration that does this to capture the unique constraint error and report it a a meaninful way to the user.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
s we discussed in the thread on Spec thread for our new API, the idea
came up of making conn_id unique in Airflow
https://lists.apache.org/thread.html/rfb6f7d95b2754fda9dd09b08444214dfad12d10f143d32de0fcf4104%40%3Cdev.airflow.apache.org%3E
The people in that thread seemed to be in favour of it:
Given the downsides/work arounds, and the confusion this causes we should remove this (mis)feature from Airflow 2.0.
We should take some care in the migration that does this to capture the unique constraint error and report it a a meaninful way to the user.
The text was updated successfully, but these errors were encountered: