potiuk commented on PR #37778:
URL: https://github.com/apache/airflow/pull/37778#issuecomment-2016865953

   Agree with TP that if we were to merge this one, we will need quite a bit 
more:
   
   * documentation with some examples
   * general use cases where it would be available
   * some performance considerations (i.e. what those who create the custom 
deps should be aware of when writing their own deps
   * dos and don'ts 
   * possibly some way of detecting when someone is doing bad things there (not 
sure how it should look like).
   
   The big difference vs. what we have now with "built-in" deps, is that 
scheduler gives control to "user" code in a very, very "hot area" in the code. 
Unlike most of the other code we allow our users to configure in Airflow, this 
one wlll have a crucial and very serious impact on the scheduling performance.
   


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to