eladkal commented on PR #35745: URL: https://github.com/apache/airflow/pull/35745#issuecomment-1826371098
> @eladkal Yes, I had thought about that, but speaking honestly I don't have experience with really big deployments of Airflow. What is your experience of using the DAG Import Error UI in that situation? I would imagine that once there are a certain amount of broken DAGs the user would start to use the Find tool in their browser, rather than scroll through all the DAGs. You can create such case in your breeze and see how your experience with it is. If people are comfortable with the suggested UX I am happy to accept it. My comment here is to avoid case where we accept it and then someone else will raise PR to undo it. -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
