potiuk commented on PR #56044: URL: https://github.com/apache/airflow/pull/56044#issuecomment-3427103587
> The reason I'm asking is that our current verification might become invalid later and could potentially lead to new bugs. If this DB usage pattern is not absolute, then the uniform but absolute prevention approaches mentioned by @tirkarthi (NullPool, change driver, recreate engine) could be better long-term solutions. Yes - that's the current design philosophy, If it changes - it will go further into isolation - i.e. both Triggerer and Dag processor eventually should not access DB at all - all the communication should go through the api-server. Currently it's a bit balance between performance and security but in the future, complete isolation will become more important. -- 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]
