https://community.databricks.com/t5/get-started-discussions/dlt-to-push-data-instead-of-a-pull/m-p/68685#M7234 <P>I am relatively new to Databricks, and from my recent experience it appears that every step in a DLT Pipeline, we define each LIVE TABLES (be it streaming or not) to pull data upstream.</P><P>I have yet to see an implementation where data from upstream would push its data downstream, say, I could create a bronze table and configure in its definition the silver tables it can push its data into.</P><P>This would be especially useful, I think, when ingesting data from Kafka where different topics contain differing&nbsp; payload(message) schema and would like to segregate these messages by topic, that is, to put each topic to its own table.</P><P>&nbsp;</P> Fri, 10 May 2024 02:20:15 GMT _databreaks 2024-05-10T02:20:15Z https://community.databricks.com/t5/get-started-discussions/dlt-to-push-data-instead-of-a-pull/m-p/68685#M7234 <P>I am relatively new to Databricks, and from my recent experience it appears that every step in a DLT Pipeline, we define each LIVE TABLES (be it streaming or not) to pull data upstream.</P><P>I have yet to see an implementation where data from upstream would push its data downstream, say, I could create a bronze table and configure in its definition the silver tables it can push its data into.</P><P>This would be especially useful, I think, when ingesting data from Kafka where different topics contain differing&nbsp; payload(message) schema and would like to segregate these messages by topic, that is, to put each topic to its own table.</P><P>&nbsp;</P> Fri, 10 May 2024 02:20:15 GMT https://community.databricks.com/t5/get-started-discussions/dlt-to-push-data-instead-of-a-pull/m-p/68685#M7234 _databreaks 2024-05-10T02:20:15Z