siddharthvp edited a comment on pull request #17891: URL: https://github.com/apache/airflow/pull/17891#issuecomment-908299380
Yes the logic is indeed hacky. @uranusjr Even with the two solutions you suggest, the problem doesn't really go away (unless I'm much mistaken) - if a DAG is moved from one file to another in the middle of a parsing run and Airflow processed the source file before the move occurred and the destination file after the move, we still have a false-positive error. So I think the only way to implement this feature would be via hacky heuristics. Maybe we should also change the exception text to clarify that it is a _possible_ duplication. When the next DAG parsing run occurs, the false-positive alert would disappear. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
