potiuk commented on issue #19058: URL: https://github.com/apache/airflow/issues/19058#issuecomment-946699275
Great analysis @uranusjr chapeau-bas ! I think there is another option for custom logs. I believe we could simply ban using `ts` in the names of the logs. That would mean some additional analysis of the custom logging specification and failing airflow if we detect it - possibly with a very descriptive explanation on how to convert the old logging spec and maybe even a tool to help with it. Yes it means breaking (somewhat) backwards compatibility, but I think this is the kind of change that we can claim is a fix to behaviour that was previously coincidentally working fine. I think - when it comes to 'custom' logging we do not have an API specifying clearly what is and what is not breaking compatibility. -- 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]
