1. i understand SELECTs scan mode Row or Columnar (makes sense). And how about DML? Can for example a MERGE be executed by either row engine vs native micro partition engine? Same for all sorts of DML (INSERTs, UPDATEs and DELETEs) ? or regarding DML there's only one engine to execute? i have an old feeling on hybrid tables that would first write row based first, and that background process would then copy row based data into micro partitions (yo support typical analytic queries), but while SERVING an analytic query snowflake would merge data from both row based + micro partitions as micro partitions may be lagging till background process row based into micro partitions ? Thanks 🙏
Interesting video - any news on Azure availability?
1. i understand SELECTs scan mode Row or Columnar (makes sense). And how about DML? Can for example a MERGE be executed by either row engine vs native micro partition engine? Same for all sorts of DML (INSERTs, UPDATEs and DELETEs) ? or regarding DML there's only one engine to execute? i have an old feeling on hybrid tables that would first write row based first, and that background process would then copy row based data into micro partitions (yo support typical analytic queries), but while SERVING an analytic query snowflake would merge data from both row based + micro partitions as micro partitions may be lagging till background process row based into micro partitions ?
Thanks 🙏