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/07/08 21:01:48 UTC

[GitHub] [airflow] dstandish commented on pull request #24908: Dataset event log

dstandish commented on PR #24908:
URL: https://github.com/apache/airflow/pull/24908#issuecomment-1179357417

   > Might be worth tossing `log` in the name as well, `dataset_event_log`, to help distinguish it from `dataset_dag_run_queue` for those less familiar with this area.
   
   I thought about this too, and it I think it would be a reasonable way to go.  However, the reason I leaned towards not using the word "log" is because, logs tend to be things that are not needed for the operation of your app.  They are there to troubleshoot etc.  But I think this table is / will be more than that -- it's not merely a log, e.g. not just for auditing or troubleshooting.  It's going to be surfaced  in the UI, for one, and I suspect that these events ultimately I think will be accessible by TIs, sort of like XCom.  
   
   They are events, operational in nature, more akin to XCom than Log.  And I think omitting the "log" word signals that aspect better.
   
   BUT, if general consensus is in the other direction, I am happy to go along.


-- 
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