You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/09/16 19:07:33 UTC

[GitHub] [airflow] Jorricks commented on issue #16790: Support manual task annotation.

Jorricks commented on issue #16790:
URL: https://github.com/apache/airflow/issues/16790#issuecomment-1249711431

   > The features are implemented when someone implements it.. There has to be someone who would like to take on the feature and work on it. It does  not depend on 'committers' as a whole but on the willingness of someone to do it. And it absolutely does not have to be commiter - if you for example want this feature badly you could take on the task and implement it. If your company has a need they could let it be done by someone who they employ or who they pay for.
   > 
   > That's how it works for open source project. If you really need it and have no skills to implement it, convince someone to do it :). 
   
   I was wondering, what would be the best DB schema change? Should it be a separate table or would it make more sense to add an extra field to the DagRun and TaskInstance tables? 


-- 
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-unsubscribe@airflow.apache.org

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