MM-Lehmann opened a new issue #19011: URL: https://github.com/apache/airflow/issues/19011
### Description In our use case, we often import data which contains some noise which cannot be handled correctly. However, we don't want an entire task or job to fail because of it (simply because it is not critical). A warning shall be logged to the corresponding data point and the job shall carry on as usual. **The problem**: a mere `logging.warning()` stays in the hiding when nobody looks at the logs (why should they when everything succeeded?). Also, having a separate task/job which checks for those kind of errors is adding too much complexity to the logic and makes it hard to sync to the origin. **The proposal**: Add a new task return status `Success with warning` or simply `Warning` which shows at high level, what's going on in the tasks. Users can see that there is some action needed, but not immediately, without having to read each of the logs or having to setup additional monitoring levels. If someone points me toward the relevant parts in the application logic that should be modified, I would be happy to have a shot at it myself. ### Use case/motivation Warnings in tasks should be made visible in the UI at job level (through a status flag). ### Related issues _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
