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

[GitBox <gi...@apache.org>]

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

   >> 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.
   
   > True, good point. Maybe "dataset-history" then?
   
   Not to be mr stick in the mud or anything.... _but_....
   
   Mabye help me understand the concern a little better?  
   
   What's wrong with sticking with the standard convention?  We have a model, DatasetEvent, to represent "dataset events", so why not stick it in a `dataset_event` table -- like you would put "dags" in a `dag` table, "serialized dags" in a `serialized_dag` table, "XComs" in an `xcom` table, or for that matter "orders" in an `order` table etc?
   
   I like dataset_event.  Seems to be as plain and clear as possible -- it stores dataset events.
   


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