Can we set inter dependency between different jobs ? Like one job to be triggered based on run status of previous job ?

Now we dont need to go away from Coalesce. Otherwise we had to move all orchestration using Airflow

It works for streaming pipeline, but there are many aspects where we might not want to do this. For example, we will need to track all such tables to make them GDPR compliant. Another problem is storage, we may benefit from compute cost but we need to balance it with storage cost.

Excellent discussion. Being very fresh into the Snowflake ecosystem, let alone cloud data as a whole, I appreciate the built in data-ops capabilities in Coalesce. It's no mystery what the iterative and agile development workflow ought to look like with the integrated git and deployment implementation right in the GUI. However that only really covers sql objects created for the transformation portion of ELT. What should Snowflake's counterpart in DataOps look like for the rest of Snowflake with source tables, snowpipe objects, schema objects etc? How should one reconcile DataOps between Coalesce and non-Coalsce implementations? Is there a way both can be unified somehow? Also, with regards to setting up the data foundation/data strategy as a prerequisite to successful implementations built on it (analytics, machine learning, AI etc.), what are the components or considerations of said data foundation/strategy? Are there any recommended resources that one could use to read and learn more on this?

Luvvin' the format. Nice work, Armon & Satish ;)

『p』『r』『o』『m』『o』『s』『m』