kosteev commented on PR #42410: URL: https://github.com/apache/airflow/pull/42410#issuecomment-2462495473
I agree that changing datatype doesn't solve issue radically. I haven't read all the comments here, but my vote is to have validation/safeguard for this (e.g. validation during DAG parsing and throwing import error for such a DAG, that customer could see it). In general the fact that Airflow scheduler (or DAG processor) can break because of user code doesn't look right, IMHO. -- 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]
