Databricks, every mention

11 scenes (2022), the whole family · ← back to Databricks

mentionsepisodesper episode tap a year for its mentions

Verbatim, from the transcripts: the passages where Databricks comes up

loading…

▶ 18:44 Jack Berkowitz Uh, but, but on top of that, we, we build layers, so we use some of the Amazon data systems, we also use Databricks, we use Snowflake, and we use a few other vendors in terms of data lineage and security on top of those. 3 times in the scene

▶ 6:07 Alex Dean So we support Snowflake and Databricks and Redshift and BigQuery.
▶ 12:13 Alex Dean Uh, individual package to, um, to basically being Snowflake or Databricks or BigQuery. 3 times in the scene

▶ 15:39 Matt Turck And even if they want to be all those things, they're, they're going to be competing, uh, for like different features with different people, like the Firebolt, uh, for interactive queries, and, uh, Databricks, and, you know, a bunch of…
▶ 17:29 Benn Stancil You want to centralize it into your central warehouse, be it Snowflake or Databricks or BigQuery or whatever. 2 times in the scene
▶ 39:42 unnamed speaker In other words, Snowflake, you know, acquires upstream, Databricks, you know, acquires upstream, et cetera, et cetera.

▶ 2:20 Viraj Parekh Um, one thing I just want to point out about this, right, is architectures like this really have only become possible with the rise of folks like Snowflake, Databricks, Redshift, BigQuery, and this idea that as a data practitioner, I can…

▶ 20:17 Gleb Mezhanskiy The way we do this is by performing, doing log analysis, so we would, let's say, if using Snowflake or Databricks, we would connect to Snowflake, we would download the logs of all the SQL statements that were executed, and then we are… 2 times in the scene

▶ 14:22 Felix Van de Maele If you're purely technical metadata within BigQuery or Snowflake or Databricks and so on.

Turn any episode into a week of clips.