WEBVTT Kind: captions Language: en 00:00:00.080 --> 00:00:01.829 align:start position:0% Hello<00:00:00.240> everybody.<00:00:00.560> I'm<00:00:00.719> Alexi<00:00:01.120> Kraov,<00:00:01.680> the 00:00:01.829 --> 00:00:01.839 align:start position:0% Hello everybody. I'm Alexi Kraov, the 00:00:01.839 --> 00:00:03.590 align:start position:0% Hello everybody. I'm Alexi Kraov, the organizer<00:00:02.159> of<00:00:02.320> Rust<00:00:02.720> AI<00:00:03.040> and<00:00:03.280> head<00:00:03.439> of 00:00:03.590 --> 00:00:03.600 align:start position:0% organizer of Rust AI and head of 00:00:03.600 --> 00:00:06.869 align:start position:0% organizer of Rust AI and head of ecosystems<00:00:04.240> at<00:00:04.400> Lake<00:00:05.120> Sale,<00:00:06.160> the<00:00:06.640> company 00:00:06.869 --> 00:00:06.879 align:start position:0% ecosystems at Lake Sale, the company 00:00:06.879 --> 00:00:09.830 align:start position:0% ecosystems at Lake Sale, the company which<00:00:07.200> wrote<00:00:07.839> Spark<00:00:08.160> and<00:00:08.400> Rust.<00:00:09.040> And<00:00:09.280> here<00:00:09.599> we 00:00:09.830 --> 00:00:09.840 align:start position:0% which wrote Spark and Rust. And here we 00:00:09.840 --> 00:00:11.910 align:start position:0% which wrote Spark and Rust. And here we are<00:00:10.000> with<00:00:10.240> us<00:00:10.480> we<00:00:10.639> have<00:00:10.880> Matt<00:00:11.280> toel, 00:00:11.910 --> 00:00:11.920 align:start position:0% are with us we have Matt toel, 00:00:11.920 --> 00:00:15.509 align:start position:0% are with us we have Matt toel, co-founder<00:00:12.400> of<00:00:12.639> Columnar,<00:00:14.000> uh<00:00:14.320> PMC<00:00:14.799> of<00:00:14.960> Apache 00:00:15.509 --> 00:00:15.519 align:start position:0% co-founder of Columnar, uh PMC of Apache 00:00:15.519 --> 00:00:16.390 align:start position:0% co-founder of Columnar, uh PMC of Apache iceberg 00:00:16.390 --> 00:00:16.400 align:start position:0% iceberg 00:00:16.400 --> 00:00:17.109 align:start position:0% iceberg and<00:00:16.560> arrow 00:00:17.109 --> 00:00:17.119 align:start position:0% and arrow 00:00:17.119 --> 00:00:20.310 align:start position:0% and arrow and<00:00:17.279> arrow<00:00:18.160> and<00:00:18.800> magpie<00:00:19.439> recently<00:00:19.920> right 00:00:20.310 --> 00:00:20.320 align:start position:0% and arrow and magpie recently right 00:00:20.320 --> 00:00:22.710 align:start position:0% and arrow and magpie recently right and<00:00:20.720> Apache<00:00:21.119> Macpie<00:00:21.840> Macpie<00:00:22.320> we're<00:00:22.480> going<00:00:22.640> to 00:00:22.710 --> 00:00:22.720 align:start position:0% and Apache Macpie Macpie we're going to 00:00:22.720 --> 00:00:25.990 align:start position:0% and Apache Macpie Macpie we're going to ask<00:00:22.880> about<00:00:23.039> that<00:00:23.600> and<00:00:23.760> so<00:00:24.080> Matt<00:00:24.640> is<00:00:25.359> uh<00:00:25.760> working 00:00:25.990 --> 00:00:26.000 align:start position:0% ask about that and so Matt is uh working 00:00:26.000 --> 00:00:29.589 align:start position:0% ask about that and so Matt is uh working on<00:00:26.400> ADBC.<00:00:27.039> He<00:00:27.199> gave<00:00:27.359> a<00:00:27.519> talk<00:00:28.000> on<00:00:28.320> ADBC<00:00:28.880> and<00:00:29.039> DDB 00:00:29.589 --> 00:00:29.599 align:start position:0% on ADBC. He gave a talk on ADBC and DDB 00:00:29.599 --> 00:00:32.709 align:start position:0% on ADBC. He gave a talk on ADBC and DDB here<00:00:30.080> at<00:00:30.400> PI<00:00:30.720> data<00:00:31.039> Amsterdam<00:00:32.000> where<00:00:32.239> we<00:00:32.480> are 00:00:32.709 --> 00:00:32.719 align:start position:0% here at PI data Amsterdam where we are 00:00:32.719 --> 00:00:34.870 align:start position:0% here at PI data Amsterdam where we are on<00:00:32.960> location.<00:00:34.000> So<00:00:34.239> it's<00:00:34.480> a<00:00:34.640> wonderful 00:00:34.870 --> 00:00:34.880 align:start position:0% on location. So it's a wonderful 00:00:34.880 --> 00:00:36.470 align:start position:0% on location. So it's a wonderful industrial<00:00:35.360> space.<00:00:35.520> You<00:00:35.680> hear<00:00:35.840> some<00:00:36.000> echoes 00:00:36.470 --> 00:00:36.480 align:start position:0% industrial space. You hear some echoes 00:00:36.480 --> 00:00:39.270 align:start position:0% industrial space. You hear some echoes of<00:00:36.800> Python<00:00:37.680> uh<00:00:38.480> echoing<00:00:38.960> through<00:00:39.120> the 00:00:39.270 --> 00:00:39.280 align:start position:0% of Python uh echoing through the 00:00:39.280 --> 00:00:43.110 align:start position:0% of Python uh echoing through the building<00:00:40.000> and<00:00:40.719> uh<00:00:41.360> uh<00:00:41.600> super<00:00:41.920> excited<00:00:42.640> uh<00:00:42.879> Matt 00:00:43.110 --> 00:00:43.120 align:start position:0% building and uh uh super excited uh Matt 00:00:43.120 --> 00:00:47.110 align:start position:0% building and uh uh super excited uh Matt told<00:00:43.360> us<00:00:44.239> uh<00:00:44.719> cool<00:00:45.040> things<00:00:45.280> about<00:00:45.600> ADBC 00:00:47.110 --> 00:00:47.120 align:start position:0% told us uh cool things about ADBC 00:00:47.120 --> 00:00:49.590 align:start position:0% told us uh cool things about ADBC uh<00:00:47.440> kind<00:00:47.600> of<00:00:47.760> becoming<00:00:48.239> the<00:00:48.559> backbone<00:00:49.039> of<00:00:49.440> uh 00:00:49.590 --> 00:00:49.600 align:start position:0% uh kind of becoming the backbone of uh 00:00:49.600 --> 00:00:52.229 align:start position:0% uh kind of becoming the backbone of uh what<00:00:49.840> I<00:00:49.920> call<00:00:50.079> AI<00:00:50.399> infra<00:00:50.800> 2.0.<00:00:51.520> So<00:00:51.760> tell<00:00:51.840> us<00:00:52.000> a 00:00:52.229 --> 00:00:52.239 align:start position:0% what I call AI infra 2.0. So tell us a 00:00:52.239 --> 00:00:54.869 align:start position:0% what I call AI infra 2.0. So tell us a little<00:00:52.399> bit<00:00:52.879> uh<00:00:53.760> uh<00:00:54.160> for<00:00:54.399> folks<00:00:54.640> who<00:00:54.800> don't 00:00:54.869 --> 00:00:54.879 align:start position:0% little bit uh uh for folks who don't 00:00:54.879 --> 00:00:57.670 align:start position:0% little bit uh uh for folks who don't know<00:00:55.039> what<00:00:55.199> is<00:00:55.360> ADBC,<00:00:56.399> why<00:00:56.640> is<00:00:56.719> it<00:00:56.960> cool,<00:00:57.520> why 00:00:57.670 --> 00:00:57.680 align:start position:0% know what is ADBC, why is it cool, why 00:00:57.680 --> 00:00:59.110 align:start position:0% know what is ADBC, why is it cool, why are<00:00:57.840> you<00:00:58.000> going<00:00:58.239> around<00:00:58.480> the<00:00:58.640> world? 00:00:59.110 --> 00:00:59.120 align:start position:0% are you going around the world? 00:00:59.120 --> 00:01:00.950 align:start position:0% are you going around the world? Easiest<00:00:59.520> easiest<00:01:00.000> way<00:01:00.160> of<00:01:00.320> pulling<00:01:00.559> it<00:01:00.640> out.<00:01:00.800> I 00:01:00.950 --> 00:01:00.960 align:start position:0% Easiest easiest way of pulling it out. I 00:01:00.960 --> 00:01:03.430 align:start position:0% Easiest easiest way of pulling it out. I mean<00:01:01.760> I'm<00:01:02.000> trying<00:01:02.160> to<00:01:02.239> kill<00:01:02.480> ODBC<00:01:03.039> is<00:01:03.199> the<00:01:03.280> best 00:01:03.430 --> 00:01:03.440 align:start position:0% mean I'm trying to kill ODBC is the best 00:01:03.440 --> 00:01:05.189 align:start position:0% mean I'm trying to kill ODBC is the best way<00:01:03.520> to<00:01:03.680> describe<00:01:03.920> it.<00:01:04.640> If<00:01:04.799> you're<00:01:04.960> familiar 00:01:05.189 --> 00:01:05.199 align:start position:0% way to describe it. If you're familiar 00:01:05.199 --> 00:01:07.910 align:start position:0% way to describe it. If you're familiar at<00:01:05.360> all<00:01:05.439> with<00:01:05.600> ODBC<00:01:06.080> or<00:01:06.240> JDBC,<00:01:07.280> you<00:01:07.360> know<00:01:07.600> data 00:01:07.910 --> 00:01:07.920 align:start position:0% at all with ODBC or JDBC, you know data 00:01:07.920 --> 00:01:09.030 align:start position:0% at all with ODBC or JDBC, you know data connect,<00:01:08.240> you<00:01:08.320> know,<00:01:08.400> how<00:01:08.560> you<00:01:08.720> connect<00:01:08.880> to 00:01:09.030 --> 00:01:09.040 align:start position:0% connect, you know, how you connect to 00:01:09.040 --> 00:01:11.990 align:start position:0% connect, you know, how you connect to your<00:01:09.200> database.<00:01:10.320> Uh<00:01:11.200> historically<00:01:11.840> and 00:01:11.990 --> 00:01:12.000 align:start position:0% your database. Uh historically and 00:01:12.000 --> 00:01:14.310 align:start position:0% your database. Uh historically and traditionally,<00:01:12.560> all<00:01:12.720> of<00:01:12.799> that<00:01:13.040> connection<00:01:13.760> is 00:01:14.310 --> 00:01:14.320 align:start position:0% traditionally, all of that connection is 00:01:14.320 --> 00:01:17.270 align:start position:0% traditionally, all of that connection is row<00:01:14.560> oriented.<00:01:15.920> uh<00:01:16.159> because<00:01:16.560> even<00:01:16.799> though<00:01:17.040> all 00:01:17.270 --> 00:01:17.280 align:start position:0% row oriented. uh because even though all 00:01:17.280 --> 00:01:19.429 align:start position:0% row oriented. uh because even though all of<00:01:17.360> our<00:01:18.400> almost<00:01:18.720> all<00:01:18.880> of<00:01:18.960> your<00:01:19.119> data 00:01:19.429 --> 00:01:19.439 align:start position:0% of our almost all of your data 00:01:19.439 --> 00:01:21.830 align:start position:0% of our almost all of your data analytical<00:01:20.159> systems<00:01:20.960> and<00:01:21.280> analytical 00:01:21.830 --> 00:01:21.840 align:start position:0% analytical systems and analytical 00:01:21.840 --> 00:01:24.310 align:start position:0% analytical systems and analytical databases<00:01:22.400> are<00:01:22.960> column<00:01:23.360> oriented. 00:01:24.310 --> 00:01:24.320 align:start position:0% databases are column oriented. 00:01:24.320 --> 00:01:26.870 align:start position:0% databases are column oriented. So<00:01:24.479> you're<00:01:24.720> paying<00:01:24.960> this<00:01:25.200> huge<00:01:25.920> transpose 00:01:26.870 --> 00:01:26.880 align:start position:0% So you're paying this huge transpose 00:01:26.880 --> 00:01:30.310 align:start position:0% So you're paying this huge transpose copy<00:01:27.280> cost<00:01:27.840> of<00:01:28.159> getting<00:01:28.320> your<00:01:28.479> data<00:01:28.799> from<00:01:29.600> your 00:01:30.310 --> 00:01:30.320 align:start position:0% copy cost of getting your data from your 00:01:30.320 --> 00:01:33.510 align:start position:0% copy cost of getting your data from your uh<00:01:31.040> from<00:01:31.280> your<00:01:31.439> data<00:01:31.759> your<00:01:31.920> analytical<00:01:32.400> system 00:01:33.510 --> 00:01:33.520 align:start position:0% uh from your data your analytical system 00:01:33.520 --> 00:01:35.030 align:start position:0% uh from your data your analytical system to 00:01:35.030 --> 00:01:35.040 align:start position:0% to 00:01:35.040 --> 00:01:38.950 align:start position:0% to uh<00:01:35.680> uh<00:01:35.920> uh<00:01:36.159> uh<00:01:36.320> to<00:01:36.560> your<00:01:36.799> local<00:01:37.119> system<00:01:37.840> to<00:01:38.159> then 00:01:38.950 --> 00:01:38.960 align:start position:0% uh uh uh uh to your local system to then 00:01:38.960 --> 00:01:41.030 align:start position:0% uh uh uh uh to your local system to then your<00:01:39.920> data<00:01:40.159> frame<00:01:40.320> libraries<00:01:40.720> of<00:01:40.880> your 00:01:41.030 --> 00:01:41.040 align:start position:0% your data frame libraries of your 00:01:41.040 --> 00:01:42.550 align:start position:0% your data frame libraries of your choice.<00:01:41.520> You<00:01:41.600> know<00:01:41.680> polars,<00:01:42.000> pandas<00:01:42.320> and<00:01:42.400> so 00:01:42.550 --> 00:01:42.560 align:start position:0% choice. You know polars, pandas and so 00:01:42.560 --> 00:01:44.069 align:start position:0% choice. You know polars, pandas and so on.<00:01:42.799> And<00:01:42.960> you<00:01:43.040> have<00:01:43.119> to<00:01:43.280> transpose<00:01:43.680> it<00:01:43.840> all 00:01:44.069 --> 00:01:44.079 align:start position:0% on. And you have to transpose it all 00:01:44.079 --> 00:01:46.069 align:start position:0% on. And you have to transpose it all from<00:01:44.320> columns<00:01:44.640> to<00:01:44.960> rows<00:01:45.119> for<00:01:45.280> the<00:01:45.439> compute<00:01:45.920> for 00:01:46.069 --> 00:01:46.079 align:start position:0% from columns to rows for the compute for 00:01:46.079 --> 00:01:48.069 align:start position:0% from columns to rows for the compute for ODBC<00:01:46.560> JDBC.<00:01:47.119> You<00:01:47.280> transpose<00:01:47.680> it<00:01:47.759> all<00:01:47.920> back 00:01:48.069 --> 00:01:48.079 align:start position:0% ODBC JDBC. You transpose it all back 00:01:48.079 --> 00:01:50.630 align:start position:0% ODBC JDBC. You transpose it all back into<00:01:48.399> columns<00:01:49.040> because<00:01:49.360> of<00:01:49.840> your<00:01:50.159> data<00:01:50.479> frame 00:01:50.630 --> 00:01:50.640 align:start position:0% into columns because of your data frame 00:01:50.640 --> 00:01:51.190 align:start position:0% into columns because of your data frame libraries, 00:01:51.190 --> 00:01:51.200 align:start position:0% libraries, 00:01:51.200 --> 00:01:51.429 align:start position:0% libraries, right? 00:01:51.429 --> 00:01:51.439 align:start position:0% right? 00:01:51.439 --> 00:01:53.990 align:start position:0% right? And<00:01:51.600> so<00:01:51.759> ADBC<00:01:52.399> is<00:01:52.560> a<00:01:52.720> similar<00:01:53.040> concept<00:01:53.360> to<00:01:53.600> ODBC 00:01:53.990 --> 00:01:54.000 align:start position:0% And so ADBC is a similar concept to ODBC 00:01:54.000 --> 00:01:57.109 align:start position:0% And so ADBC is a similar concept to ODBC and<00:01:54.079> JDBC.<00:01:54.560> It's<00:01:54.720> a<00:01:55.200> single<00:01:55.759> interface<00:01:56.799> client 00:01:57.109 --> 00:01:57.119 align:start position:0% and JDBC. It's a single interface client 00:01:57.119 --> 00:01:57.990 align:start position:0% and JDBC. It's a single interface client API 00:01:57.990 --> 00:01:58.000 align:start position:0% API 00:01:58.000 --> 00:01:59.590 align:start position:0% API and<00:01:58.159> you<00:01:58.320> have<00:01:58.479> drivers<00:01:58.880> that<00:01:59.119> implement<00:01:59.439> the 00:01:59.590 --> 00:01:59.600 align:start position:0% and you have drivers that implement the 00:01:59.600 --> 00:02:01.830 align:start position:0% and you have drivers that implement the API<00:02:00.640> and<00:02:00.880> the<00:02:01.040> big<00:02:01.200> difference<00:02:01.439> there<00:02:01.600> being 00:02:01.830 --> 00:02:01.840 align:start position:0% API and the big difference there being 00:02:01.840 --> 00:02:03.350 align:start position:0% API and the big difference there being that<00:02:02.079> it<00:02:02.320> the<00:02:02.560> data<00:02:02.799> goes<00:02:03.040> through<00:02:03.200> the 00:02:03.350 --> 00:02:03.360 align:start position:0% that it the data goes through the 00:02:03.360 --> 00:02:05.590 align:start position:0% that it the data goes through the interface<00:02:03.759> using<00:02:04.320> Apache<00:02:04.880> Arrow 00:02:05.590 --> 00:02:05.600 align:start position:0% interface using Apache Arrow 00:02:05.600 --> 00:02:07.510 align:start position:0% interface using Apache Arrow which<00:02:05.759> is<00:02:05.840> an<00:02:06.000> in-memory<00:02:06.479> column<00:02:06.799> oriented 00:02:07.510 --> 00:02:07.520 align:start position:0% which is an in-memory column oriented 00:02:07.520 --> 00:02:09.109 align:start position:0% which is an in-memory column oriented data<00:02:07.840> representation<00:02:08.399> format. 00:02:09.109 --> 00:02:09.119 align:start position:0% data representation format. 00:02:09.119 --> 00:02:11.270 align:start position:0% data representation format. Mh.<00:02:09.440> So<00:02:09.679> your<00:02:09.840> data<00:02:10.080> stays<00:02:10.399> column<00:02:10.800> oriented 00:02:11.270 --> 00:02:11.280 align:start position:0% Mh. So your data stays column oriented 00:02:11.280 --> 00:02:13.910 align:start position:0% Mh. So your data stays column oriented the<00:02:11.599> whole<00:02:11.760> way<00:02:11.920> through<00:02:12.239> end<00:02:12.480> to<00:02:12.640> end.<00:02:13.360> So<00:02:13.680> if 00:02:13.910 --> 00:02:13.920 align:start position:0% the whole way through end to end. So if 00:02:13.920 --> 00:02:16.309 align:start position:0% the whole way through end to end. So if your<00:02:14.160> data<00:02:14.400> system<00:02:14.640> returns<00:02:15.680> returns<00:02:16.000> column 00:02:16.309 --> 00:02:16.319 align:start position:0% your data system returns returns column 00:02:16.319 --> 00:02:18.229 align:start position:0% your data system returns returns column oriented<00:02:16.720> data,<00:02:17.200> it<00:02:17.360> gets<00:02:17.520> to<00:02:17.680> stay<00:02:17.840> column 00:02:18.229 --> 00:02:18.239 align:start position:0% oriented data, it gets to stay column 00:02:18.239 --> 00:02:20.309 align:start position:0% oriented data, it gets to stay column oriented.<00:02:18.879> If<00:02:19.120> your<00:02:19.280> data<00:02:19.520> system<00:02:19.840> is<00:02:20.080> say 00:02:20.309 --> 00:02:20.319 align:start position:0% oriented. If your data system is say 00:02:20.319 --> 00:02:21.430 align:start position:0% oriented. If your data system is say Postgress<00:02:20.720> or<00:02:20.959> something<00:02:21.040> that<00:02:21.280> doesn't 00:02:21.430 --> 00:02:21.440 align:start position:0% Postgress or something that doesn't 00:02:21.440 --> 00:02:23.830 align:start position:0% Postgress or something that doesn't return<00:02:22.080> column,<00:02:22.400> it<00:02:22.560> returns<00:02:22.879> rows<00:02:23.120> anyways. 00:02:23.830 --> 00:02:23.840 align:start position:0% return column, it returns rows anyways. 00:02:23.840 --> 00:02:25.510 align:start position:0% return column, it returns rows anyways. Well,<00:02:24.160> your<00:02:24.400> application<00:02:24.879> still<00:02:25.120> gets<00:02:25.360> to 00:02:25.510 --> 00:02:25.520 align:start position:0% Well, your application still gets to 00:02:25.520 --> 00:02:27.910 align:start position:0% Well, your application still gets to have<00:02:25.680> a<00:02:25.920> consistent<00:02:26.959> column<00:02:27.440> oriented 00:02:27.910 --> 00:02:27.920 align:start position:0% have a consistent column oriented 00:02:27.920 --> 00:02:29.910 align:start position:0% have a consistent column oriented representation.<00:02:29.040> You<00:02:29.280> don't<00:02:29.440> have<00:02:29.520> to<00:02:29.680> own 00:02:29.910 --> 00:02:29.920 align:start position:0% representation. You don't have to own 00:02:29.920 --> 00:02:32.470 align:start position:0% representation. You don't have to own the<00:02:30.080> type<00:02:30.319> mapping<00:02:30.879> and<00:02:31.599> all<00:02:31.840> the<00:02:32.000> logic<00:02:32.239> and 00:02:32.470 --> 00:02:32.480 align:start position:0% the type mapping and all the logic and 00:02:32.480 --> 00:02:33.910 align:start position:0% the type mapping and all the logic and build<00:02:32.720> all<00:02:32.800> the<00:02:32.959> logic<00:02:33.120> for<00:02:33.280> actually<00:02:33.680> doing 00:02:33.910 --> 00:02:33.920 align:start position:0% build all the logic for actually doing 00:02:33.920 --> 00:02:36.550 align:start position:0% build all the logic for actually doing that<00:02:34.080> conversion<00:02:34.800> back.<00:02:35.680> It<00:02:36.000> just<00:02:36.239> makes 00:02:36.550 --> 00:02:36.560 align:start position:0% that conversion back. It just makes 00:02:36.560 --> 00:02:37.830 align:start position:0% that conversion back. It just makes everything<00:02:36.879> simpler<00:02:37.280> while<00:02:37.599> still 00:02:37.830 --> 00:02:37.840 align:start position:0% everything simpler while still 00:02:37.840 --> 00:02:39.830 align:start position:0% everything simpler while still maintaining<00:02:38.480> a<00:02:38.800> significant<00:02:39.360> performance 00:02:39.830 --> 00:02:39.840 align:start position:0% maintaining a significant performance 00:02:39.840 --> 00:02:41.430 align:start position:0% maintaining a significant performance improvement. 00:02:41.430 --> 00:02:41.440 align:start position:0% improvement. 00:02:41.440 --> 00:02:44.229 align:start position:0% improvement. Yes.<00:02:42.000> And<00:02:42.319> you<00:02:42.560> mentioned<00:02:42.879> that<00:02:43.519> uh<00:02:43.680> it's<00:02:44.000> not 00:02:44.229 --> 00:02:44.239 align:start position:0% Yes. And you mentioned that uh it's not 00:02:44.239 --> 00:02:47.270 align:start position:0% Yes. And you mentioned that uh it's not just<00:02:44.720> like<00:02:45.440> yeah<00:02:46.160> building<00:02:47.040> uh 00:02:47.270 --> 00:02:47.280 align:start position:0% just like yeah building uh 00:02:47.280 --> 00:02:50.150 align:start position:0% just like yeah building uh self-contained<00:02:48.160> ADBC.<00:02:48.959> People<00:02:49.120> who<00:02:49.680> install 00:02:50.150 --> 00:02:50.160 align:start position:0% self-contained ADBC. People who install 00:02:50.160 --> 00:02:52.390 align:start position:0% self-contained ADBC. People who install OBBC<00:02:50.800> have<00:02:50.959> a<00:02:51.120> hard<00:02:51.360> time<00:02:51.920> finding 00:02:52.390 --> 00:02:52.400 align:start position:0% OBBC have a hard time finding 00:02:52.400 --> 00:02:54.390 align:start position:0% OBBC have a hard time finding configuring<00:02:52.959> and<00:02:53.200> doing<00:02:53.360> it<00:02:53.920> and<00:02:54.080> you<00:02:54.239> guys 00:02:54.390 --> 00:02:54.400 align:start position:0% configuring and doing it and you guys 00:02:54.400 --> 00:02:56.309 align:start position:0% configuring and doing it and you guys have<00:02:54.480> a<00:02:54.640> CLI<00:02:55.680> to<00:02:55.840> do<00:02:55.920> that. 00:02:56.309 --> 00:02:56.319 align:start position:0% have a CLI to do that. 00:02:56.319 --> 00:02:59.670 align:start position:0% have a CLI to do that. So<00:02:56.640> so<00:02:57.120> so<00:02:58.239> first<00:02:58.400> of<00:02:58.480> all<00:02:58.640> ADBC<00:02:59.120> itself<00:02:59.519> the 00:02:59.670 --> 00:02:59.680 align:start position:0% So so so first of all ADBC itself the 00:02:59.680 --> 00:03:01.270 align:start position:0% So so so first of all ADBC itself the interface<00:03:00.000> is<00:03:00.239> part<00:03:00.400> of<00:03:00.480> the<00:03:00.560> Apache<00:03:00.959> Arrow 00:03:01.270 --> 00:03:01.280 align:start position:0% interface is part of the Apache Arrow 00:03:01.280 --> 00:03:03.030 align:start position:0% interface is part of the Apache Arrow project<00:03:01.519> and<00:03:01.680> therefore<00:03:02.000> is<00:03:02.159> completely<00:03:02.800> open 00:03:03.030 --> 00:03:03.040 align:start position:0% project and therefore is completely open 00:03:03.040 --> 00:03:04.630 align:start position:0% project and therefore is completely open source<00:03:03.360> Apache<00:03:03.760> governed<00:03:04.080> and<00:03:04.239> so<00:03:04.319> on<00:03:04.480> so 00:03:04.630 --> 00:03:04.640 align:start position:0% source Apache governed and so on so 00:03:04.640 --> 00:03:05.350 align:start position:0% source Apache governed and so on so forth.<00:03:04.879> Mhm. 00:03:05.350 --> 00:03:05.360 align:start position:0% forth. Mhm. 00:03:05.360 --> 00:03:09.030 align:start position:0% forth. Mhm. Most<00:03:05.599> of<00:03:05.680> our<00:03:05.920> drivers<00:03:06.319> are<00:03:06.640> themselves<00:03:07.840> also 00:03:09.030 --> 00:03:09.040 align:start position:0% Most of our drivers are themselves also 00:03:09.040 --> 00:03:09.910 align:start position:0% Most of our drivers are themselves also as<00:03:09.200> good<00:03:09.360> as<00:03:09.519> what<00:03:09.599> it<00:03:09.680> is. 00:03:09.910 --> 00:03:09.920 align:start position:0% as good as what it is. 00:03:09.920 --> 00:03:13.589 align:start position:0% as good as what it is. Also,<00:03:10.319> you<00:03:10.480> know,<00:03:10.720> open<00:03:10.959> source.<00:03:11.920> And<00:03:13.120> so<00:03:13.360> if 00:03:13.589 --> 00:03:13.599 align:start position:0% Also, you know, open source. And so if 00:03:13.599 --> 00:03:16.390 align:start position:0% Also, you know, open source. And so if you've<00:03:13.840> ever<00:03:14.080> had<00:03:14.319> to<00:03:15.040> figure<00:03:15.280> out<00:03:15.840> how<00:03:16.080> to 00:03:16.390 --> 00:03:16.400 align:start position:0% you've ever had to figure out how to 00:03:16.400 --> 00:03:18.630 align:start position:0% you've ever had to figure out how to find,<00:03:17.200> install,<00:03:17.519> and<00:03:17.760> configure<00:03:18.000> an<00:03:18.080> OBBC 00:03:18.630 --> 00:03:18.640 align:start position:0% find, install, and configure an OBBC 00:03:18.640 --> 00:03:21.110 align:start position:0% find, install, and configure an OBBC driver,<00:03:19.280> you<00:03:19.440> know,<00:03:19.599> it's<00:03:20.159> sucks.<00:03:20.640> It's<00:03:20.879> hell. 00:03:21.110 --> 00:03:21.120 align:start position:0% driver, you know, it's sucks. It's hell. 00:03:21.120 --> 00:03:22.790 align:start position:0% driver, you know, it's sucks. It's hell. It's<00:03:21.280> awful.<00:03:21.760> You<00:03:21.920> go,<00:03:22.239> you<00:03:22.319> know,<00:03:22.400> you<00:03:22.560> go<00:03:22.640> to 00:03:22.790 --> 00:03:22.800 align:start position:0% It's awful. You go, you know, you go to 00:03:22.800 --> 00:03:25.190 align:start position:0% It's awful. You go, you know, you go to some<00:03:22.959> vendor<00:03:23.360> site<00:03:23.519> that<00:03:23.760> you<00:03:23.920> hope<00:03:24.800> is<00:03:25.040> the 00:03:25.190 --> 00:03:25.200 align:start position:0% some vendor site that you hope is the 00:03:25.200 --> 00:03:26.710 align:start position:0% some vendor site that you hope is the right<00:03:25.360> one.<00:03:25.760> You<00:03:25.920> download<00:03:26.159> a<00:03:26.400> package<00:03:26.560> that 00:03:26.710 --> 00:03:26.720 align:start position:0% right one. You download a package that 00:03:26.720 --> 00:03:29.190 align:start position:0% right one. You download a package that you<00:03:26.879> hope<00:03:27.040> is<00:03:27.120> the<00:03:27.280> right<00:03:27.440> package.<00:03:28.480> Place 00:03:29.190 --> 00:03:29.200 align:start position:0% you hope is the right package. Place 00:03:29.200 --> 00:03:30.550 align:start position:0% you hope is the right package. Place things<00:03:29.440> in<00:03:29.599> different<00:03:29.840> place.<00:03:30.000> Like,<00:03:30.239> it's 00:03:30.550 --> 00:03:30.560 align:start position:0% things in different place. Like, it's 00:03:30.560 --> 00:03:32.630 align:start position:0% things in different place. Like, it's insane.<00:03:31.360> Um,<00:03:31.680> it's<00:03:31.840> it's<00:03:32.080> insane<00:03:32.319> that<00:03:32.480> that's 00:03:32.630 --> 00:03:32.640 align:start position:0% insane. Um, it's it's insane that that's 00:03:32.640 --> 00:03:35.030 align:start position:0% insane. Um, it's it's insane that that's what<00:03:32.720> we've<00:03:32.879> been<00:03:32.959> doing<00:03:33.120> for<00:03:33.280> 30<00:03:33.519> years.<00:03:34.080> So, 00:03:35.030 --> 00:03:35.040 align:start position:0% what we've been doing for 30 years. So, 00:03:35.040 --> 00:03:37.589 align:start position:0% what we've been doing for 30 years. So, so<00:03:35.280> with<00:03:35.599> columner,<00:03:36.239> we<00:03:36.400> built<00:03:36.640> out<00:03:36.799> a<00:03:37.040> CLI<00:03:37.440> we 00:03:37.589 --> 00:03:37.599 align:start position:0% so with columner, we built out a CLI we 00:03:37.599 --> 00:03:39.509 align:start position:0% so with columner, we built out a CLI we called<00:03:37.760> DBC, 00:03:39.509 --> 00:03:39.519 align:start position:0% called DBC, 00:03:39.519 --> 00:03:41.270 align:start position:0% called DBC, which<00:03:39.760> we<00:03:39.920> like<00:03:40.080> to<00:03:40.159> say<00:03:40.400> basically<00:03:40.640> it's<00:03:40.879> UV 00:03:41.270 --> 00:03:41.280 align:start position:0% which we like to say basically it's UV 00:03:41.280 --> 00:03:42.229 align:start position:0% which we like to say basically it's UV for<00:03:41.519> drivers. 00:03:42.229 --> 00:03:42.239 align:start position:0% for drivers. 00:03:42.239 --> 00:03:42.630 align:start position:0% for drivers. Mhm. 00:03:42.630 --> 00:03:42.640 align:start position:0% Mhm. 00:03:42.640 --> 00:03:44.070 align:start position:0% Mhm. You<00:03:42.720> know,<00:03:42.799> it's<00:03:43.120> a<00:03:43.280> package<00:03:43.519> manager<00:03:43.840> to 00:03:44.070 --> 00:03:44.080 align:start position:0% You know, it's a package manager to 00:03:44.080 --> 00:03:46.070 align:start position:0% You know, it's a package manager to manage<00:03:44.239> your<00:03:44.400> ADBC<00:03:44.879> drivers.<00:03:45.440> Makes<00:03:45.680> it<00:03:45.840> super 00:03:46.070 --> 00:03:46.080 align:start position:0% manage your ADBC drivers. Makes it super 00:03:46.080 --> 00:03:49.030 align:start position:0% manage your ADBC drivers. Makes it super easy<00:03:46.239> where<00:03:46.480> you<00:03:46.640> can<00:03:46.720> just<00:03:46.879> do<00:03:47.280> DBC<00:03:48.000> install 00:03:49.030 --> 00:03:49.040 align:start position:0% easy where you can just do DBC install 00:03:49.040 --> 00:03:49.990 align:start position:0% easy where you can just do DBC install BigQuery 00:03:49.990 --> 00:03:50.000 align:start position:0% BigQuery 00:03:50.000 --> 00:03:53.430 align:start position:0% BigQuery or<00:03:50.159> DBC<00:03:50.720> install,<00:03:52.080> you<00:03:52.239> know,<00:03:52.480> flight<00:03:52.879> SQL, 00:03:53.430 --> 00:03:53.440 align:start position:0% or DBC install, you know, flight SQL, 00:03:53.440 --> 00:03:55.750 align:start position:0% or DBC install, you know, flight SQL, right?<00:03:53.920> And<00:03:54.080> then<00:03:54.239> you<00:03:54.400> can<00:03:54.560> connect<00:03:54.720> to<00:03:54.959> your 00:03:55.750 --> 00:03:55.760 align:start position:0% right? And then you can connect to your 00:03:55.760 --> 00:03:58.229 align:start position:0% right? And then you can connect to your favorite<00:03:56.080> data<00:03:56.480> system<00:03:57.120> using<00:03:57.519> ADBC<00:03:58.080> because 00:03:58.229 --> 00:03:58.239 align:start position:0% favorite data system using ADBC because 00:03:58.239 --> 00:04:00.149 align:start position:0% favorite data system using ADBC because it<00:03:58.400> just<00:03:58.560> downloads<00:03:58.879> the<00:03:59.120> driver,<00:03:59.680> installs 00:04:00.149 --> 00:04:00.159 align:start position:0% it just downloads the driver, installs 00:04:00.159 --> 00:04:01.670 align:start position:0% it just downloads the driver, installs it,<00:04:00.400> and<00:04:00.640> then<00:04:00.799> you<00:04:00.959> you<00:04:01.200> can<00:04:01.280> just,<00:04:01.519> you<00:04:01.599> know, 00:04:01.670 --> 00:04:01.680 align:start position:0% it, and then you you can just, you know, 00:04:01.680 --> 00:04:04.070 align:start position:0% it, and then you you can just, you know, DBC<00:04:02.080> install<00:04:02.319> flight<00:04:02.640> SQL<00:04:02.879> and<00:04:03.040> then<00:04:03.200> talk<00:04:03.360> to 00:04:04.070 --> 00:04:04.080 align:start position:0% DBC install flight SQL and then talk to 00:04:04.080 --> 00:04:06.149 align:start position:0% DBC install flight SQL and then talk to sale<00:04:04.400> or<00:04:04.720> talk<00:04:04.879> to<00:04:05.040> Spice<00:04:05.439> AI, 00:04:06.149 --> 00:04:06.159 align:start position:0% sale or talk to Spice AI, 00:04:06.159 --> 00:04:07.429 align:start position:0% sale or talk to Spice AI, you<00:04:06.319> know,<00:04:06.400> just<00:04:06.560> using<00:04:06.720> the<00:04:06.879> driver<00:04:07.120> and<00:04:07.280> the 00:04:07.429 --> 00:04:07.439 align:start position:0% you know, just using the driver and the 00:04:07.439 --> 00:04:09.110 align:start position:0% you know, just using the driver and the driver<00:04:07.680> manager. 00:04:09.110 --> 00:04:09.120 align:start position:0% driver manager. 00:04:09.120 --> 00:04:11.270 align:start position:0% driver manager. And<00:04:09.280> so<00:04:09.439> it<00:04:09.680> makes<00:04:09.920> everything<00:04:10.239> just<00:04:10.959> more 00:04:11.270 --> 00:04:11.280 align:start position:0% And so it makes everything just more 00:04:11.280 --> 00:04:12.949 align:start position:0% And so it makes everything just more seamless<00:04:11.599> and<00:04:11.840> a<00:04:12.000> better<00:04:12.480> developer 00:04:12.949 --> 00:04:12.959 align:start position:0% seamless and a better developer 00:04:12.959 --> 00:04:13.670 align:start position:0% seamless and a better developer experience. 00:04:13.670 --> 00:04:13.680 align:start position:0% experience. 00:04:13.680 --> 00:04:15.830 align:start position:0% experience. Mh.<00:04:13.920> And<00:04:14.239> also<00:04:14.480> gives<00:04:14.720> you<00:04:14.959> more<00:04:15.439> confidence 00:04:15.830 --> 00:04:15.840 align:start position:0% Mh. And also gives you more confidence 00:04:15.840 --> 00:04:18.789 align:start position:0% Mh. And also gives you more confidence in<00:04:16.239> the<00:04:17.120> supply<00:04:17.440> chain<00:04:18.079> because<00:04:18.479> all<00:04:18.639> the 00:04:18.789 --> 00:04:18.799 align:start position:0% in the supply chain because all the 00:04:18.799 --> 00:04:21.189 align:start position:0% in the supply chain because all the packages<00:04:19.120> on<00:04:19.280> the<00:04:19.359> CDN<00:04:20.160> are<00:04:20.400> themselves 00:04:21.189 --> 00:04:21.199 align:start position:0% packages on the CDN are themselves 00:04:21.199 --> 00:04:23.830 align:start position:0% packages on the CDN are themselves signed<00:04:21.759> by<00:04:22.000> us<00:04:22.320> validated.<00:04:23.120> DBC<00:04:23.520> is<00:04:23.680> going<00:04:23.759> to 00:04:23.830 --> 00:04:23.840 align:start position:0% signed by us validated. DBC is going to 00:04:23.840 --> 00:04:25.590 align:start position:0% signed by us validated. DBC is going to verify<00:04:24.160> the<00:04:24.320> signature<00:04:24.639> when<00:04:24.800> it<00:04:25.199> when<00:04:25.440> it 00:04:25.590 --> 00:04:25.600 align:start position:0% verify the signature when it when it 00:04:25.600 --> 00:04:27.110 align:start position:0% verify the signature when it when it downloads<00:04:25.840> and<00:04:26.000> installs<00:04:26.320> it<00:04:26.400> and<00:04:26.639> so<00:04:26.720> on<00:04:26.960> so 00:04:27.110 --> 00:04:27.120 align:start position:0% downloads and installs it and so on so 00:04:27.120 --> 00:04:27.430 align:start position:0% downloads and installs it and so on so forth. 00:04:27.430 --> 00:04:27.440 align:start position:0% forth. 00:04:27.440 --> 00:04:29.110 align:start position:0% forth. Is<00:04:27.600> it<00:04:27.759> a<00:04:27.840> binary<00:04:28.160> install<00:04:28.400> or<00:04:28.560> is<00:04:28.639> it<00:04:28.800> compiled 00:04:29.110 --> 00:04:29.120 align:start position:0% Is it a binary install or is it compiled 00:04:29.120 --> 00:04:29.990 align:start position:0% Is it a binary install or is it compiled from<00:04:29.280> source? 00:04:29.990 --> 00:04:30.000 align:start position:0% from source? 00:04:30.000 --> 00:04:30.710 align:start position:0% from source? Binary<00:04:30.400> install 00:04:30.710 --> 00:04:30.720 align:start position:0% Binary install 00:04:30.720 --> 00:04:32.550 align:start position:0% Binary install bin<00:04:30.880> install.<00:04:31.199> So<00:04:31.280> it<00:04:31.440> knows<00:04:31.759> basically<00:04:32.160> for 00:04:32.550 --> 00:04:32.560 align:start position:0% bin install. So it knows basically for 00:04:32.560 --> 00:04:33.030 align:start position:0% bin install. So it knows basically for given 00:04:33.030 --> 00:04:33.040 align:start position:0% given 00:04:33.040 --> 00:04:36.070 align:start position:0% given it<00:04:33.600> uses<00:04:33.759> your<00:04:34.000> it<00:04:34.240> uses<00:04:34.479> the<00:04:34.960> it<00:04:35.280> uses<00:04:35.680> the 00:04:36.070 --> 00:04:36.080 align:start position:0% it uses your it uses the it uses the 00:04:36.080 --> 00:04:38.710 align:start position:0% it uses your it uses the it uses the system<00:04:36.479> architecture<00:04:37.199> and<00:04:38.080> OS<00:04:38.400> that<00:04:38.560> you're 00:04:38.710 --> 00:04:38.720 align:start position:0% system architecture and OS that you're 00:04:38.720 --> 00:04:39.909 align:start position:0% system architecture and OS that you're running<00:04:38.960> DBC<00:04:39.440> on. 00:04:39.909 --> 00:04:39.919 align:start position:0% running DBC on. 00:04:39.919 --> 00:04:44.070 align:start position:0% running DBC on. Mhm.<00:04:40.720> and<00:04:41.360> grabs<00:04:41.680> the<00:04:41.919> appropriate<00:04:43.280> uh<00:04:43.600> binary 00:04:44.070 --> 00:04:44.080 align:start position:0% Mhm. and grabs the appropriate uh binary 00:04:44.080 --> 00:04:45.670 align:start position:0% Mhm. and grabs the appropriate uh binary for<00:04:44.240> the<00:04:44.400> platform<00:04:44.720> you're<00:04:44.960> running<00:04:45.120> on.<00:04:45.360> It's 00:04:45.670 --> 00:04:45.680 align:start position:0% for the platform you're running on. It's 00:04:45.680 --> 00:04:46.150 align:start position:0% for the platform you're running on. It's just 00:04:46.150 --> 00:04:46.160 align:start position:0% just 00:04:46.160 --> 00:04:47.749 align:start position:0% just we<00:04:46.400> are<00:04:46.560> currently<00:04:46.960> we<00:04:47.280> actually<00:04:47.600> are 00:04:47.749 --> 00:04:47.759 align:start position:0% we are currently we actually are 00:04:47.759 --> 00:04:48.950 align:start position:0% we are currently we actually are currently<00:04:48.000> someone<00:04:48.320> started<00:04:48.639> contributing 00:04:48.950 --> 00:04:48.960 align:start position:0% currently someone started contributing 00:04:48.960 --> 00:04:52.790 align:start position:0% currently someone started contributing to<00:04:49.040> DBC<00:04:49.919> a<00:04:50.320> platform<00:04:51.440> uh<00:04:51.600> option<00:04:52.320> so<00:04:52.479> that<00:04:52.639> if 00:04:52.790 --> 00:04:52.800 align:start position:0% to DBC a platform uh option so that if 00:04:52.800 --> 00:04:54.310 align:start position:0% to DBC a platform uh option so that if you<00:04:52.880> really<00:04:53.120> wanted<00:04:53.280> to<00:04:53.600> you<00:04:53.759> could<00:04:53.919> tell<00:04:54.080> it 00:04:54.310 --> 00:04:54.320 align:start position:0% you really wanted to you could tell it 00:04:54.320 --> 00:04:56.390 align:start position:0% you really wanted to you could tell it to<00:04:54.560> download<00:04:55.199> the<00:04:55.440> binary<00:04:55.840> for<00:04:56.000> a<00:04:56.160> different 00:04:56.390 --> 00:04:56.400 align:start position:0% to download the binary for a different 00:04:56.400 --> 00:04:57.830 align:start position:0% to download the binary for a different platform<00:04:56.960> than<00:04:57.120> the<00:04:57.280> one<00:04:57.440> you're<00:04:57.600> running<00:04:57.759> it 00:04:57.830 --> 00:04:57.840 align:start position:0% platform than the one you're running it 00:04:57.840 --> 00:04:59.830 align:start position:0% platform than the one you're running it on<00:04:58.000> if<00:04:58.160> that's<00:04:58.320> what<00:04:58.400> you<00:04:58.479> want<00:04:58.639> to<00:04:58.720> do<00:04:59.280> say<00:04:59.520> for 00:04:59.830 --> 00:04:59.840 align:start position:0% on if that's what you want to do say for 00:04:59.840 --> 00:05:01.749 align:start position:0% on if that's what you want to do say for doing<00:05:00.240> a<00:05:00.639> docker<00:05:00.960> image<00:05:01.280> build<00:05:01.440> or<00:05:01.600> something 00:05:01.749 --> 00:05:01.759 align:start position:0% doing a docker image build or something 00:05:01.759 --> 00:05:02.310 align:start position:0% doing a docker image build or something like<00:05:01.919> that 00:05:02.310 --> 00:05:02.320 align:start position:0% like that 00:05:02.320 --> 00:05:04.469 align:start position:0% like that right<00:05:02.880> it<00:05:03.040> like<00:05:03.199> cross<00:05:03.520> compile<00:05:04.000> kind<00:05:04.160> of 00:05:04.469 --> 00:05:04.479 align:start position:0% right it like cross compile kind of 00:05:04.479 --> 00:05:07.110 align:start position:0% right it like cross compile kind of exactly<00:05:05.040> it<00:05:05.440> so<00:05:05.680> cuz<00:05:05.840> because<00:05:06.000> we<00:05:06.160> we<00:05:06.720> when<00:05:06.960> we 00:05:07.110 --> 00:05:07.120 align:start position:0% exactly it so cuz because we we when we 00:05:07.120 --> 00:05:10.310 align:start position:0% exactly it so cuz because we we when we when<00:05:07.360> we<00:05:07.759> deploy<00:05:08.080> the<00:05:08.400> drivers<00:05:09.039> to<00:05:09.199> the<00:05:09.360> CDN<00:05:10.080> we 00:05:10.310 --> 00:05:10.320 align:start position:0% when we deploy the drivers to the CDN we 00:05:10.320 --> 00:05:11.430 align:start position:0% when we deploy the drivers to the CDN we build<00:05:10.479> the<00:05:10.639> drivers<00:05:10.880> for<00:05:11.039> the<00:05:11.280> different 00:05:11.430 --> 00:05:11.440 align:start position:0% build the drivers for the different 00:05:11.440 --> 00:05:12.870 align:start position:0% build the drivers for the different platforms<00:05:11.840> and<00:05:12.080> put<00:05:12.240> it<00:05:12.320> all<00:05:12.479> put<00:05:12.639> all<00:05:12.720> the 00:05:12.870 --> 00:05:12.880 align:start position:0% platforms and put it all put all the 00:05:12.880 --> 00:05:15.110 align:start position:0% platforms and put it all put all the different<00:05:13.039> platforms<00:05:13.280> in<00:05:13.440> the<00:05:13.520> CDN<00:05:14.240> and<00:05:14.560> then 00:05:15.110 --> 00:05:15.120 align:start position:0% different platforms in the CDN and then 00:05:15.120 --> 00:05:17.029 align:start position:0% different platforms in the CDN and then you<00:05:15.280> know<00:05:15.440> just<00:05:15.600> decide<00:05:16.320> which<00:05:16.560> one<00:05:16.720> are<00:05:16.960> you 00:05:17.029 --> 00:05:17.039 align:start position:0% you know just decide which one are you 00:05:17.039 --> 00:05:18.469 align:start position:0% you know just decide which one are you going<00:05:17.120> to<00:05:17.199> grab<00:05:17.440> when<00:05:17.680> you<00:05:17.759> install<00:05:18.080> it 00:05:18.469 --> 00:05:18.479 align:start position:0% going to grab when you install it 00:05:18.479 --> 00:05:21.749 align:start position:0% going to grab when you install it right<00:05:19.120> right<00:05:19.680> so<00:05:20.560> uh<00:05:20.880> it's<00:05:21.199> interesting<00:05:21.600> right 00:05:21.749 --> 00:05:21.759 align:start position:0% right right so uh it's interesting right 00:05:21.759 --> 00:05:24.070 align:start position:0% right right so uh it's interesting right so<00:05:22.000> I<00:05:22.240> think<00:05:22.639> it's<00:05:22.960> kind<00:05:23.039> of<00:05:23.199> the<00:05:23.360> the<00:05:23.600> contour 00:05:24.070 --> 00:05:24.080 align:start position:0% so I think it's kind of the the contour 00:05:24.080 --> 00:05:26.550 align:start position:0% so I think it's kind of the the contour so<00:05:24.400> the<00:05:24.800> AI<00:05:25.120> info<00:05:25.440> 2.0<00:05:25.759> zero<00:05:26.000> is<00:05:26.080> shaping<00:05:26.320> up 00:05:26.550 --> 00:05:26.560 align:start position:0% so the AI info 2.0 zero is shaping up 00:05:26.560 --> 00:05:28.230 align:start position:0% so the AI info 2.0 zero is shaping up right<00:05:26.720> it's<00:05:26.880> fast<00:05:27.120> it's<00:05:27.360> native<00:05:27.919> it's 00:05:28.230 --> 00:05:28.240 align:start position:0% right it's fast it's native it's 00:05:28.240 --> 00:05:30.310 align:start position:0% right it's fast it's native it's columner<00:05:29.039> everything<00:05:29.360> is<00:05:29.520> columner<00:05:30.000> right<00:05:30.080> so 00:05:30.310 --> 00:05:30.320 align:start position:0% columner everything is columner right so 00:05:30.320 --> 00:05:33.270 align:start position:0% columner everything is columner right so kind<00:05:30.479> of<00:05:30.560> the<00:05:31.199> uh<00:05:31.600> it's<00:05:31.840> it's<00:05:32.240> interesting<00:05:33.120> uh 00:05:33.270 --> 00:05:33.280 align:start position:0% kind of the uh it's it's interesting uh 00:05:33.280 --> 00:05:35.029 align:start position:0% kind of the uh it's it's interesting uh that<00:05:33.600> we<00:05:33.759> do<00:05:33.919> not<00:05:34.080> need<00:05:34.240> to<00:05:34.320> incur<00:05:34.639> now<00:05:34.880> the 00:05:35.029 --> 00:05:35.039 align:start position:0% that we do not need to incur now the 00:05:35.039 --> 00:05:36.790 align:start position:0% that we do not need to incur now the penalty<00:05:35.360> of<00:05:35.520> converting<00:05:36.160> from<00:05:36.560> rows<00:05:36.720> to 00:05:36.790 --> 00:05:36.800 align:start position:0% penalty of converting from rows to 00:05:36.800 --> 00:05:38.790 align:start position:0% penalty of converting from rows to columns<00:05:37.199> and<00:05:37.280> back<00:05:37.520> if<00:05:37.680> we<00:05:37.919> have<00:05:38.160> columner<00:05:38.639> for 00:05:38.790 --> 00:05:38.800 align:start position:0% columns and back if we have columner for 00:05:38.800 --> 00:05:41.990 align:start position:0% columns and back if we have columner for all<00:05:38.960> so<00:05:39.360> with<00:05:39.759> a<00:05:39.919> columner<00:05:40.560> so<00:05:40.800> we<00:05:41.120> natively 00:05:41.990 --> 00:05:42.000 align:start position:0% all so with a columner so we natively 00:05:42.000 --> 00:05:44.469 align:start position:0% all so with a columner so we natively kind<00:05:42.240> of<00:05:42.400> align<00:05:42.720> with<00:05:42.880> this<00:05:43.440> and<00:05:43.759> also<00:05:44.080> I<00:05:44.320> just 00:05:44.469 --> 00:05:44.479 align:start position:0% kind of align with this and also I just 00:05:44.479 --> 00:05:46.870 align:start position:0% kind of align with this and also I just learned<00:05:44.800> you<00:05:44.960> told<00:05:45.120> me<00:05:45.360> recently<00:05:46.160> that<00:05:46.639> you 00:05:46.870 --> 00:05:46.880 align:start position:0% learned you told me recently that you 00:05:46.880 --> 00:05:49.590 align:start position:0% learned you told me recently that you guys<00:05:47.039> have<00:05:47.440> spark<00:05:48.160> there<00:05:48.320> is<00:05:48.400> the<00:05:48.720> spark<00:05:49.039> adbc 00:05:49.590 --> 00:05:49.600 align:start position:0% guys have spark there is the spark adbc 00:05:49.600 --> 00:05:51.510 align:start position:0% guys have spark there is the spark adbc driver<00:05:50.000> you<00:05:50.160> can<00:05:50.240> just<00:05:50.400> do<00:05:50.639> dbcin<00:05:51.120> install 00:05:51.510 --> 00:05:51.520 align:start position:0% driver you can just do dbcin install 00:05:51.520 --> 00:05:52.469 align:start position:0% driver you can just do dbcin install spark<00:05:52.000> y 00:05:52.469 --> 00:05:52.479 align:start position:0% spark y 00:05:52.479 --> 00:05:54.230 align:start position:0% spark y and<00:05:52.880> when<00:05:53.120> you're<00:05:53.280> building<00:05:53.520> out<00:05:53.600> the<00:05:53.840> u<00:05:54.000> the 00:05:54.230 --> 00:05:54.240 align:start position:0% and when you're building out the u the 00:05:54.240 --> 00:05:55.670 align:start position:0% and when you're building out the u the URI<00:05:54.560> that<00:05:54.720> you<00:05:54.880> tell<00:05:54.960> it<00:05:55.120> you<00:05:55.360> how<00:05:55.520> you 00:05:55.670 --> 00:05:55.680 align:start position:0% URI that you tell it you how you 00:05:55.680 --> 00:05:56.950 align:start position:0% URI that you tell it you how you connect.<00:05:56.160> You<00:05:56.320> can<00:05:56.400> give<00:05:56.479> it,<00:05:56.720> you<00:05:56.800> know, 00:05:56.950 --> 00:05:56.960 align:start position:0% connect. You can give it, you know, 00:05:56.960 --> 00:05:59.990 align:start position:0% connect. You can give it, you know, spark<00:05:57.759> slash<00:05:58.800> tell<00:05:59.039> it,<00:05:59.280> you<00:05:59.360> know,<00:05:59.520> the<00:05:59.680> URI 00:05:59.990 --> 00:06:00.000 align:start position:0% spark slash tell it, you know, the URI 00:06:00.000 --> 00:06:01.189 align:start position:0% spark slash tell it, you know, the URI of<00:06:00.080> your<00:06:00.240> lake<00:06:00.560> sale<00:06:00.800> instance. 00:06:01.189 --> 00:06:01.199 align:start position:0% of your lake sale instance. 00:06:01.199 --> 00:06:01.670 align:start position:0% of your lake sale instance. Exactly. 00:06:01.670 --> 00:06:01.680 align:start position:0% Exactly. 00:06:01.680 --> 00:06:03.909 align:start position:0% Exactly. And<00:06:01.759> then<00:06:02.000> all<00:06:02.080> you<00:06:02.240> have<00:06:02.320> to<00:06:02.400> do<00:06:02.479> is<00:06:02.720> add<00:06:03.440> the 00:06:03.909 --> 00:06:03.919 align:start position:0% And then all you have to do is add the 00:06:03.919 --> 00:06:06.230 align:start position:0% And then all you have to do is add the uh<00:06:04.479> API<00:06:05.120> equals<00:06:05.680> connect. 00:06:06.230 --> 00:06:06.240 align:start position:0% uh API equals connect. 00:06:06.240 --> 00:06:06.629 align:start position:0% uh API equals connect. Yes. 00:06:06.629 --> 00:06:06.639 align:start position:0% Yes. 00:06:06.639 --> 00:06:08.150 align:start position:0% Yes. Uh<00:06:06.800> to<00:06:06.960> tell<00:06:07.120> it<00:06:07.199> to<00:06:07.360> use<00:06:07.440> the<00:06:07.600> spark<00:06:07.919> connect 00:06:08.150 --> 00:06:08.160 align:start position:0% Uh to tell it to use the spark connect 00:06:08.160 --> 00:06:09.029 align:start position:0% Uh to tell it to use the spark connect protocol.<00:06:08.639> That's<00:06:08.800> right. 00:06:09.029 --> 00:06:09.039 align:start position:0% protocol. That's right. 00:06:09.039 --> 00:06:09.749 align:start position:0% protocol. That's right. To<00:06:09.199> talk<00:06:09.360> to<00:06:09.440> you<00:06:09.520> guys. 00:06:09.749 --> 00:06:09.759 align:start position:0% To talk to you guys. 00:06:09.759 --> 00:06:12.150 align:start position:0% To talk to you guys. And<00:06:09.919> because<00:06:10.160> we're<00:06:10.400> call<00:06:11.120> already,<00:06:11.759> we'll 00:06:12.150 --> 00:06:12.160 align:start position:0% And because we're call already, we'll 00:06:12.160 --> 00:06:13.590 align:start position:0% And because we're call already, we'll you<00:06:12.319> guys<00:06:12.400> already<00:06:12.639> feed<00:06:12.880> arrow.<00:06:13.120> Well,<00:06:13.280> spark 00:06:13.590 --> 00:06:13.600 align:start position:0% you guys already feed arrow. Well, spark 00:06:13.600 --> 00:06:15.990 align:start position:0% you guys already feed arrow. Well, spark connect<00:06:13.919> itself<00:06:14.880> as<00:06:15.039> a<00:06:15.120> protocol<00:06:15.680> returns 00:06:15.990 --> 00:06:16.000 align:start position:0% connect itself as a protocol returns 00:06:16.000 --> 00:06:17.350 align:start position:0% connect itself as a protocol returns arrow<00:06:16.319> data.<00:06:16.639> Correct.<00:06:16.880> That's<00:06:16.960> the<00:06:17.120> spark 00:06:17.350 --> 00:06:17.360 align:start position:0% arrow data. Correct. That's the spark 00:06:17.360 --> 00:06:18.790 align:start position:0% arrow data. Correct. That's the spark connect<00:06:17.520> protocol<00:06:17.919> works.<00:06:18.240> Correct.<00:06:18.400> So<00:06:18.639> you 00:06:18.790 --> 00:06:18.800 align:start position:0% connect protocol works. Correct. So you 00:06:18.800 --> 00:06:20.309 align:start position:0% connect protocol works. Correct. So you guys<00:06:19.039> implement<00:06:19.360> the<00:06:19.440> spark<00:06:19.759> pro<00:06:20.000> the<00:06:20.080> spark 00:06:20.309 --> 00:06:20.319 align:start position:0% guys implement the spark pro the spark 00:06:20.319 --> 00:06:21.909 align:start position:0% guys implement the spark pro the spark connect<00:06:20.560> protocol<00:06:20.880> return<00:06:21.199> arrow<00:06:21.680> which 00:06:21.909 --> 00:06:21.919 align:start position:0% connect protocol return arrow which 00:06:21.919 --> 00:06:24.230 align:start position:0% connect protocol return arrow which means<00:06:22.160> you<00:06:22.319> get<00:06:22.400> the<00:06:22.560> zero<00:06:22.960> copy<00:06:23.919> no 00:06:24.230 --> 00:06:24.240 align:start position:0% means you get the zero copy no 00:06:24.240 --> 00:06:27.909 align:start position:0% means you get the zero copy no serialized<00:06:24.720> d<00:06:24.960> serialized<00:06:26.319> super<00:06:26.720> efficient 00:06:27.909 --> 00:06:27.919 align:start position:0% serialized d serialized super efficient 00:06:27.919 --> 00:06:29.909 align:start position:0% serialized d serialized super efficient column<00:06:28.319> oriented<00:06:28.720> the<00:06:28.880> whole<00:06:28.960> way<00:06:29.120> end<00:06:29.280> to<00:06:29.440> end 00:06:29.909 --> 00:06:29.919 align:start position:0% column oriented the whole way end to end 00:06:29.919 --> 00:06:31.749 align:start position:0% column oriented the whole way end to end right<00:06:30.400> right<00:06:30.880> and<00:06:31.120> so<00:06:31.520> uh 00:06:31.749 --> 00:06:31.759 align:start position:0% right right and so uh 00:06:31.759 --> 00:06:32.950 align:start position:0% right right and so uh and<00:06:31.919> you<00:06:32.000> guys<00:06:32.080> are<00:06:32.240> also<00:06:32.400> built<00:06:32.560> on<00:06:32.720> top<00:06:32.800> of 00:06:32.950 --> 00:06:32.960 align:start position:0% and you guys are also built on top of 00:06:32.960 --> 00:06:33.749 align:start position:0% and you guys are also built on top of data<00:06:33.280> fusion 00:06:33.749 --> 00:06:33.759 align:start position:0% data fusion 00:06:33.759 --> 00:06:34.070 align:start position:0% data fusion yes 00:06:34.070 --> 00:06:34.080 align:start position:0% yes 00:06:34.080 --> 00:06:36.550 align:start position:0% yes you<00:06:34.319> apache<00:06:34.639> data<00:06:34.880> fusion<00:06:35.199> which<00:06:35.440> itself<00:06:36.160> is 00:06:36.550 --> 00:06:36.560 align:start position:0% you apache data fusion which itself is 00:06:36.560 --> 00:06:37.590 align:start position:0% you apache data fusion which itself is arrow<00:06:36.880> native<00:06:37.199> also 00:06:37.590 --> 00:06:37.600 align:start position:0% arrow native also 00:06:37.600 --> 00:06:39.189 align:start position:0% arrow native also that's<00:06:37.759> right<00:06:38.000> that's<00:06:38.240> right<00:06:38.400> it<00:06:38.639> was<00:06:38.720> a<00:06:38.880> part 00:06:39.189 --> 00:06:39.199 align:start position:0% that's right that's right it was a part 00:06:39.199 --> 00:06:41.350 align:start position:0% that's right that's right it was a part you<00:06:39.520> told<00:06:39.759> me<00:06:39.919> again<00:06:40.319> I<00:06:40.560> learned<00:06:40.800> a<00:06:40.880> lot<00:06:41.039> of<00:06:41.199> new 00:06:41.350 --> 00:06:41.360 align:start position:0% you told me again I learned a lot of new 00:06:41.360 --> 00:06:44.150 align:start position:0% you told me again I learned a lot of new things<00:06:41.919> part<00:06:42.160> of<00:06:42.319> the<00:06:42.479> arrow<00:06:42.880> project 00:06:44.150 --> 00:06:44.160 align:start position:0% things part of the arrow project 00:06:44.160 --> 00:06:46.230 align:start position:0% things part of the arrow project yeah<00:06:44.560> originally<00:06:45.280> data<00:06:45.600> fusion<00:06:45.919> was<00:06:46.000> part<00:06:46.160> of 00:06:46.230 --> 00:06:46.240 align:start position:0% yeah originally data fusion was part of 00:06:46.240 --> 00:06:48.550 align:start position:0% yeah originally data fusion was part of the<00:06:46.319> arrow<00:06:46.720> project<00:06:47.360> and<00:06:47.520> then<00:06:47.680> it<00:06:48.000> got<00:06:48.319> the 00:06:48.550 --> 00:06:48.560 align:start position:0% the arrow project and then it got the 00:06:48.560 --> 00:06:50.870 align:start position:0% the arrow project and then it got the community<00:06:48.880> grew<00:06:49.120> large<00:06:49.360> enough<00:06:49.759> and<00:06:50.560> the 00:06:50.870 --> 00:06:50.880 align:start position:0% community grew large enough and the 00:06:50.880 --> 00:06:52.710 align:start position:0% community grew large enough and the following<00:06:51.280> got<00:06:51.440> big<00:06:51.600> enough<00:06:51.759> that<00:06:52.000> it<00:06:52.240> was<00:06:52.479> it 00:06:52.710 --> 00:06:52.720 align:start position:0% following got big enough that it was it 00:06:52.720 --> 00:06:54.950 align:start position:0% following got big enough that it was it spun<00:06:52.880> off<00:06:53.039> into<00:06:53.280> its<00:06:53.440> own<00:06:53.919> top<00:06:54.160> level<00:06:54.400> Apache 00:06:54.950 --> 00:06:54.960 align:start position:0% spun off into its own top level Apache 00:06:54.960 --> 00:06:55.430 align:start position:0% spun off into its own top level Apache project 00:06:55.430 --> 00:06:55.440 align:start position:0% project 00:06:55.440 --> 00:06:58.230 align:start position:0% project right<00:06:56.080> so<00:06:56.560> and<00:06:56.800> this<00:06:56.960> is<00:06:57.120> all<00:06:57.600> open<00:06:57.840> source 00:06:58.230 --> 00:06:58.240 align:start position:0% right so and this is all open source 00:06:58.240 --> 00:07:00.230 align:start position:0% right so and this is all open source which<00:06:58.400> is<00:06:58.639> which<00:06:58.800> is<00:06:58.960> awesome<00:06:59.440> and<00:06:59.680> so<00:07:00.000> uh<00:07:00.080> I 00:07:00.230 --> 00:07:00.240 align:start position:0% which is which is awesome and so uh I 00:07:00.240 --> 00:07:02.309 align:start position:0% which is which is awesome and so uh I just<00:07:00.479> wanted<00:07:00.720> to<00:07:00.880> kind<00:07:01.039> of<00:07:01.520> uh<00:07:01.680> segue<00:07:02.080> a<00:07:02.240> little 00:07:02.309 --> 00:07:02.319 align:start position:0% just wanted to kind of uh segue a little 00:07:02.319 --> 00:07:04.550 align:start position:0% just wanted to kind of uh segue a little bit<00:07:02.560> so<00:07:02.800> you<00:07:03.039> mentioned<00:07:03.360> that<00:07:03.840> uh<00:07:04.160> you<00:07:04.319> guys 00:07:04.550 --> 00:07:04.560 align:start position:0% bit so you mentioned that uh you guys 00:07:04.560 --> 00:07:06.550 align:start position:0% bit so you mentioned that uh you guys started<00:07:04.800> this<00:07:04.960> Apache<00:07:05.440> MacBY<00:07:05.840> project<00:07:06.240> and<00:07:06.400> I 00:07:06.550 --> 00:07:06.560 align:start position:0% started this Apache MacBY project and I 00:07:06.560 --> 00:07:08.469 align:start position:0% started this Apache MacBY project and I think<00:07:06.639> it's<00:07:06.800> top<00:07:06.960> of<00:07:07.120> mind<00:07:07.360> for<00:07:07.520> many<00:07:07.840> people 00:07:08.469 --> 00:07:08.479 align:start position:0% think it's top of mind for many people 00:07:08.479 --> 00:07:11.350 align:start position:0% think it's top of mind for many people how<00:07:08.720> do<00:07:08.960> you<00:07:09.840> uh<00:07:10.080> deal<00:07:10.319> with<00:07:10.479> AI<00:07:10.960> right<00:07:11.120> because 00:07:11.350 --> 00:07:11.360 align:start position:0% how do you uh deal with AI right because 00:07:11.360 --> 00:07:13.430 align:start position:0% how do you uh deal with AI right because a<00:07:11.520> lot<00:07:11.599> of<00:07:11.919> development<00:07:12.319> we<00:07:12.479> do<00:07:12.639> now<00:07:12.880> is<00:07:13.199> with 00:07:13.430 --> 00:07:13.440 align:start position:0% a lot of development we do now is with 00:07:13.440 --> 00:07:17.029 align:start position:0% a lot of development we do now is with AI<00:07:14.319> and<00:07:14.880> uh<00:07:15.199> that<00:07:15.759> is<00:07:15.919> something<00:07:16.240> you<00:07:16.479> guys 00:07:17.029 --> 00:07:17.039 align:start position:0% AI and uh that is something you guys 00:07:17.039 --> 00:07:18.230 align:start position:0% AI and uh that is something you guys started<00:07:17.599> I<00:07:17.759> think<00:07:17.840> a<00:07:18.000> lot<00:07:18.160> of 00:07:18.230 --> 00:07:18.240 align:start position:0% started I think a lot of 00:07:18.240 --> 00:07:19.909 align:start position:0% started I think a lot of folks<00:07:18.639> I<00:07:18.800> can't<00:07:18.880> take<00:07:19.039> credit<00:07:19.199> there<00:07:19.360> cuz<00:07:19.680> I 00:07:19.909 --> 00:07:19.919 align:start position:0% folks I can't take credit there cuz I 00:07:19.919 --> 00:07:20.950 align:start position:0% folks I can't take credit there cuz I wasn't<00:07:20.080> part<00:07:20.240> of<00:07:20.319> the<00:07:20.400> one<00:07:20.560> like<00:07:20.720> I<00:07:20.800> wasn't 00:07:20.950 --> 00:07:20.960 align:start position:0% wasn't part of the one like I wasn't 00:07:20.960 --> 00:07:22.309 align:start position:0% wasn't part of the one like I wasn't part<00:07:21.039> of<00:07:21.120> the<00:07:21.199> ones<00:07:21.360> who<00:07:21.520> started<00:07:21.680> it. 00:07:22.309 --> 00:07:22.319 align:start position:0% part of the ones who started it. 00:07:22.319 --> 00:07:25.189 align:start position:0% part of the ones who started it. Uh<00:07:22.560> Apache<00:07:22.960> Magpie<00:07:23.520> grew<00:07:23.759> out<00:07:23.919> of<00:07:24.720> uh<00:07:24.880> the 00:07:25.189 --> 00:07:25.199 align:start position:0% Uh Apache Magpie grew out of uh the 00:07:25.199 --> 00:07:26.629 align:start position:0% Uh Apache Magpie grew out of uh the Airflow<00:07:25.680> developer<00:07:26.080> community, 00:07:26.629 --> 00:07:26.639 align:start position:0% Airflow developer community, 00:07:26.639 --> 00:07:27.029 align:start position:0% Airflow developer community, right? 00:07:27.029 --> 00:07:27.039 align:start position:0% right? 00:07:27.039 --> 00:07:30.070 align:start position:0% right? Um<00:07:27.360> I<00:07:27.520> I<00:07:27.599> I<00:07:28.240> got<00:07:28.479> you<00:07:28.720> because<00:07:28.960> of<00:07:29.680> people<00:07:29.840> I 00:07:30.070 --> 00:07:30.080 align:start position:0% Um I I I got you because of people I 00:07:30.080 --> 00:07:32.950 align:start position:0% Um I I I got you because of people I know<00:07:30.319> and<00:07:30.880> being<00:07:31.039> an<00:07:31.199> ASF<00:07:31.680> member<00:07:32.479> uh<00:07:32.560> I<00:07:32.800> was 00:07:32.950 --> 00:07:32.960 align:start position:0% know and being an ASF member uh I was 00:07:32.960 --> 00:07:36.629 align:start position:0% know and being an ASF member uh I was asked<00:07:33.280> to<00:07:33.599> join<00:07:33.919> the<00:07:34.160> initial<00:07:34.560> PMC<00:07:35.599> for<00:07:35.919> Magpie 00:07:36.629 --> 00:07:36.639 align:start position:0% asked to join the initial PMC for Magpie 00:07:36.639 --> 00:07:38.309 align:start position:0% asked to join the initial PMC for Magpie by<00:07:36.880> the<00:07:37.039> people<00:07:37.199> who<00:07:37.360> were<00:07:37.520> organizing<00:07:37.840> it. 00:07:38.309 --> 00:07:38.319 align:start position:0% by the people who were organizing it. 00:07:38.319 --> 00:07:40.070 align:start position:0% by the people who were organizing it. And<00:07:38.479> so<00:07:38.639> I<00:07:38.880> that's<00:07:39.199> how<00:07:39.280> I<00:07:39.440> became<00:07:39.680> part<00:07:39.840> of<00:07:39.919> the 00:07:40.070 --> 00:07:40.080 align:start position:0% And so I that's how I became part of the 00:07:40.080 --> 00:07:42.629 align:start position:0% And so I that's how I became part of the project.<00:07:40.800> But<00:07:41.120> you<00:07:41.280> know,<00:07:41.520> but<00:07:42.080> originally<00:07:42.400> it 00:07:42.629 --> 00:07:42.639 align:start position:0% project. But you know, but originally it 00:07:42.639 --> 00:07:46.710 align:start position:0% project. But you know, but originally it spun<00:07:42.880> out<00:07:43.120> of<00:07:44.319> the<00:07:44.960> the<00:07:45.280> tools<00:07:45.599> and<00:07:45.919> utilities 00:07:46.710 --> 00:07:46.720 align:start position:0% spun out of the the tools and utilities 00:07:46.720 --> 00:07:48.629 align:start position:0% spun out of the the tools and utilities that<00:07:47.039> the<00:07:47.199> Airflow<00:07:47.680> maintainers<00:07:48.240> were<00:07:48.400> using 00:07:48.629 --> 00:07:48.639 align:start position:0% that the Airflow maintainers were using 00:07:48.639 --> 00:07:50.150 align:start position:0% that the Airflow maintainers were using were<00:07:48.800> building<00:07:49.120> for<00:07:49.280> themselves.<00:07:49.840> Yes. 00:07:50.150 --> 00:07:50.160 align:start position:0% were building for themselves. Yes. 00:07:50.160 --> 00:07:51.909 align:start position:0% were building for themselves. Yes. And<00:07:50.319> and<00:07:50.560> like<00:07:50.720> AI<00:07:51.039> skills,<00:07:51.599> right, 00:07:51.909 --> 00:07:51.919 align:start position:0% And and like AI skills, right, 00:07:51.919 --> 00:07:54.869 align:start position:0% And and like AI skills, right, for<00:07:52.160> to<00:07:52.639> make<00:07:52.800> it<00:07:53.039> easier<00:07:53.360> to<00:07:53.680> maintain 00:07:54.869 --> 00:07:54.879 align:start position:0% for to make it easier to maintain 00:07:54.879 --> 00:07:57.430 align:start position:0% for to make it easier to maintain Airflow<00:07:55.280> as<00:07:55.440> a<00:07:55.680> project<00:07:56.160> in<00:07:56.400> this<00:07:56.639> age<00:07:56.800> of<00:07:57.039> LLMs 00:07:57.430 --> 00:07:57.440 align:start position:0% Airflow as a project in this age of LLMs 00:07:57.440 --> 00:07:57.990 align:start position:0% Airflow as a project in this age of LLMs and<00:07:57.599> AI, 00:07:57.990 --> 00:07:58.000 align:start position:0% and AI, 00:07:58.000 --> 00:08:01.110 align:start position:0% and AI, right?<00:07:58.319> You<00:07:58.479> know,<00:07:59.680> Mac<00:07:59.919> Apache<00:08:00.319> Magpie<00:08:00.800> is<00:08:01.039> is 00:08:01.110 --> 00:08:01.120 align:start position:0% right? You know, Mac Apache Magpie is is 00:08:01.120 --> 00:08:07.510 align:start position:0% right? You know, Mac Apache Magpie is is is<00:08:02.000> a<00:08:02.160> collection<00:08:02.560> of<00:08:03.120> skills<00:08:03.919> and<00:08:04.879> AI<00:08:05.759> uh<00:08:06.720> AI 00:08:07.510 --> 00:08:07.520 align:start position:0% is a collection of skills and AI uh AI 00:08:07.520 --> 00:08:11.110 align:start position:0% is a collection of skills and AI uh AI utilities<00:08:08.400> for<00:08:09.520> improving<00:08:10.000> and<00:08:10.319> making 00:08:11.110 --> 00:08:11.120 align:start position:0% utilities for improving and making 00:08:11.120 --> 00:08:13.909 align:start position:0% utilities for improving and making open-source<00:08:12.160> maintainership<00:08:13.440> better<00:08:13.680> and 00:08:13.909 --> 00:08:13.919 align:start position:0% open-source maintainership better and 00:08:13.919 --> 00:08:15.670 align:start position:0% open-source maintainership better and easier,<00:08:14.720> you<00:08:14.800> know,<00:08:15.039> triage,<00:08:15.440> you<00:08:15.520> know, 00:08:15.670 --> 00:08:15.680 align:start position:0% easier, you know, triage, you know, 00:08:15.680 --> 00:08:19.830 align:start position:0% easier, you know, triage, you know, triaging<00:08:16.160> issues,<00:08:17.039> triaging<00:08:17.440> PRs,<00:08:18.879> uh<00:08:19.199> uh<00:08:19.520> uh 00:08:19.830 --> 00:08:19.840 align:start position:0% triaging issues, triaging PRs, uh uh uh 00:08:19.840 --> 00:08:22.469 align:start position:0% triaging issues, triaging PRs, uh uh uh assisting<00:08:20.240> with<00:08:20.479> automated<00:08:20.960> reviews,<00:08:22.240> you 00:08:22.469 --> 00:08:22.479 align:start position:0% assisting with automated reviews, you 00:08:22.479 --> 00:08:24.230 align:start position:0% assisting with automated reviews, you know,<00:08:23.120> and<00:08:23.280> so<00:08:23.440> on<00:08:23.599> and<00:08:23.680> so<00:08:23.840> forth, 00:08:24.230 --> 00:08:24.240 align:start position:0% know, and so on and so forth, 00:08:24.240 --> 00:08:26.230 align:start position:0% know, and so on and so forth, making<00:08:24.560> maintainers<00:08:25.280> life<00:08:25.520> easier, 00:08:26.230 --> 00:08:26.240 align:start position:0% making maintainers life easier, 00:08:26.240 --> 00:08:27.270 align:start position:0% making maintainers life easier, giving<00:08:26.479> them<00:08:26.720> time<00:08:26.879> back. 00:08:27.270 --> 00:08:27.280 align:start position:0% giving them time back. 00:08:27.280 --> 00:08:28.950 align:start position:0% giving them time back. Yes.<00:08:27.520> Yes.<00:08:27.680> And<00:08:27.919> I<00:08:28.080> think<00:08:28.240> I<00:08:28.400> really<00:08:28.639> like<00:08:28.720> what 00:08:28.950 --> 00:08:28.960 align:start position:0% Yes. Yes. And I think I really like what 00:08:28.960 --> 00:08:31.830 align:start position:0% Yes. Yes. And I think I really like what you<00:08:29.599> uh<00:08:29.759> said<00:08:30.000> yesterday<00:08:30.479> that<00:08:30.800> basically<00:08:31.520> it 00:08:31.830 --> 00:08:31.840 align:start position:0% you uh said yesterday that basically it 00:08:31.840 --> 00:08:34.230 align:start position:0% you uh said yesterday that basically it gives<00:08:32.080> you<00:08:32.880> uh<00:08:33.039> the<00:08:33.279> confidence<00:08:33.760> that 00:08:34.230 --> 00:08:34.240 align:start position:0% gives you uh the confidence that 00:08:34.240 --> 00:08:36.469 align:start position:0% gives you uh the confidence that somebody<00:08:35.039> comm<00:08:35.440> contributing<00:08:36.080> to<00:08:36.240> your 00:08:36.469 --> 00:08:36.479 align:start position:0% somebody comm contributing to your 00:08:36.479 --> 00:08:38.389 align:start position:0% somebody comm contributing to your project<00:08:36.800> is<00:08:37.360> is<00:08:37.760> knowledgeable<00:08:38.159> and 00:08:38.389 --> 00:08:38.399 align:start position:0% project is is knowledgeable and 00:08:38.399 --> 00:08:40.070 align:start position:0% project is is knowledgeable and thoughtful,<00:08:38.880> right?<00:08:39.120> Like<00:08:39.360> it's<00:08:39.599> fine<00:08:39.760> to<00:08:39.919> use 00:08:40.070 --> 00:08:40.080 align:start position:0% thoughtful, right? Like it's fine to use 00:08:40.080 --> 00:08:42.230 align:start position:0% thoughtful, right? Like it's fine to use AI.<00:08:40.320> Like<00:08:40.479> we're<00:08:40.640> not<00:08:41.200> anti-<00:08:41.519> AI,<00:08:41.919> but<00:08:42.080> if 00:08:42.230 --> 00:08:42.240 align:start position:0% AI. Like we're not anti- AI, but if 00:08:42.240 --> 00:08:43.990 align:start position:0% AI. Like we're not anti- AI, but if you're<00:08:42.399> using<00:08:42.719> AI,<00:08:43.360> you<00:08:43.599> should<00:08:43.760> be 00:08:43.990 --> 00:08:44.000 align:start position:0% you're using AI, you should be 00:08:44.000 --> 00:08:46.230 align:start position:0% you're using AI, you should be responsible<00:08:44.480> for<00:08:44.800> everything<00:08:45.600> you<00:08:45.839> send<00:08:46.080> to 00:08:46.230 --> 00:08:46.240 align:start position:0% responsible for everything you send to 00:08:46.240 --> 00:08:46.790 align:start position:0% responsible for everything you send to the<00:08:46.399> person. 00:08:46.790 --> 00:08:46.800 align:start position:0% the person. 00:08:46.800 --> 00:08:49.670 align:start position:0% the person. Exactly.<00:08:47.120> Like<00:08:47.519> like<00:08:48.240> Magpie<00:08:48.800> isn't<00:08:49.200> like<00:08:49.440> the 00:08:49.670 --> 00:08:49.680 align:start position:0% Exactly. Like like Magpie isn't like the 00:08:49.680 --> 00:08:51.590 align:start position:0% Exactly. Like like Magpie isn't like the skills<00:08:49.920> of<00:08:50.080> Magpie,<00:08:50.880> you<00:08:50.959> know,<00:08:51.040> it<00:08:51.200> requests 00:08:51.590 --> 00:08:51.600 align:start position:0% skills of Magpie, you know, it requests 00:08:51.600 --> 00:08:52.949 align:start position:0% skills of Magpie, you know, it requests confirmation<00:08:52.080> before<00:08:52.320> it<00:08:52.480> ever<00:08:52.640> posts 00:08:52.949 --> 00:08:52.959 align:start position:0% confirmation before it ever posts 00:08:52.959 --> 00:08:54.550 align:start position:0% confirmation before it ever posts anything<00:08:53.200> on<00:08:53.440> the<00:08:53.519> pub<00:08:53.839> on<00:08:54.080> GitHub<00:08:54.399> or 00:08:54.550 --> 00:08:54.560 align:start position:0% anything on the pub on GitHub or 00:08:54.560 --> 00:08:56.949 align:start position:0% anything on the pub on GitHub or anything.<00:08:54.880> you<00:08:54.959> know,<00:08:55.360> you<00:08:55.519> have<00:08:55.600> to<00:08:56.240> it<00:08:56.560> says 00:08:56.949 --> 00:08:56.959 align:start position:0% anything. you know, you have to it says 00:08:56.959 --> 00:08:59.430 align:start position:0% anything. you know, you have to it says here<00:08:57.200> is<00:08:57.360> what<00:08:57.519> I'm<00:08:57.680> suggesting. 00:08:59.430 --> 00:08:59.440 align:start position:0% here is what I'm suggesting. 00:08:59.440 --> 00:09:00.949 align:start position:0% here is what I'm suggesting. Do<00:08:59.600> you<00:08:59.760> want<00:08:59.839> me<00:08:59.920> to<00:09:00.080> post<00:09:00.320> this?<00:09:00.640> You<00:09:00.720> know, 00:09:00.949 --> 00:09:00.959 align:start position:0% Do you want me to post this? You know, 00:09:00.959 --> 00:09:03.030 align:start position:0% Do you want me to post this? You know, it<00:09:01.200> will<00:09:01.680> it<00:09:01.920> will<00:09:02.080> also<00:09:02.320> help<00:09:02.560> with,<00:09:02.959> you 00:09:03.030 --> 00:09:03.040 align:start position:0% it will it will also help with, you 00:09:03.040 --> 00:09:04.790 align:start position:0% it will it will also help with, you know,<00:09:03.600> suggesting<00:09:04.080> ways<00:09:04.240> of<00:09:04.399> helping<00:09:04.560> to 00:09:04.790 --> 00:09:04.800 align:start position:0% know, suggesting ways of helping to 00:09:04.800 --> 00:09:07.350 align:start position:0% know, suggesting ways of helping to mentor<00:09:05.760> new<00:09:06.080> committers,<00:09:06.560> new<00:09:06.720> contributors, 00:09:07.350 --> 00:09:07.360 align:start position:0% mentor new committers, new contributors, 00:09:07.360 --> 00:09:09.430 align:start position:0% mentor new committers, new contributors, right?<00:09:07.600> you<00:09:07.839> know,<00:09:07.920> while<00:09:08.320> also<00:09:08.640> helping<00:09:08.880> you 00:09:09.430 --> 00:09:09.440 align:start position:0% right? you know, while also helping you 00:09:09.440 --> 00:09:12.470 align:start position:0% right? you know, while also helping you uh<00:09:09.600> triage<00:09:10.240> and<00:09:10.800> al<00:09:11.120> and<00:09:11.440> align<00:09:11.760> issues<00:09:12.160> and 00:09:12.470 --> 00:09:12.480 align:start position:0% uh triage and al and align issues and 00:09:12.480 --> 00:09:15.110 align:start position:0% uh triage and al and align issues and PRs<00:09:12.959> with<00:09:13.200> labels<00:09:13.680> and<00:09:14.320> things<00:09:14.560> like<00:09:14.720> like<00:09:14.959> so 00:09:15.110 --> 00:09:15.120 align:start position:0% PRs with labels and things like like so 00:09:15.120 --> 00:09:16.710 align:start position:0% PRs with labels and things like like so like<00:09:15.360> the<00:09:15.519> like<00:09:15.760> like<00:09:16.000> my<00:09:16.240> workflow 00:09:16.710 --> 00:09:16.720 align:start position:0% like the like like my workflow 00:09:16.720 --> 00:09:19.990 align:start position:0% like the like like my workflow frequently<00:09:17.200> lately<00:09:18.320> with<00:09:18.720> you<00:09:18.880> know<00:09:19.040> a<00:09:19.440> arrows 00:09:19.990 --> 00:09:20.000 align:start position:0% frequently lately with you know a arrows 00:09:20.000 --> 00:09:22.470 align:start position:0% frequently lately with you know a arrows go<00:09:20.240> implementation<00:09:20.800> and<00:09:21.120> iceberg<00:09:21.600> go<00:09:22.240> has 00:09:22.470 --> 00:09:22.480 align:start position:0% go implementation and iceberg go has 00:09:22.480 --> 00:09:25.030 align:start position:0% go implementation and iceberg go has been<00:09:22.640> to<00:09:22.720> use<00:09:23.040> use<00:09:23.279> magpie<00:09:23.920> skills<00:09:24.240> to<00:09:24.560> do<00:09:24.720> a 00:09:25.030 --> 00:09:25.040 align:start position:0% been to use use magpie skills to do a 00:09:25.040 --> 00:09:26.870 align:start position:0% been to use use magpie skills to do a you<00:09:25.200> know<00:09:25.440> a<00:09:25.680> sweep<00:09:25.920> of<00:09:26.000> the<00:09:26.160> PRs<00:09:26.560> doing<00:09:26.720> an 00:09:26.870 --> 00:09:26.880 align:start position:0% you know a sweep of the PRs doing an 00:09:26.880 --> 00:09:28.230 align:start position:0% you know a sweep of the PRs doing an initial<00:09:27.200> review<00:09:27.519> through 00:09:28.230 --> 00:09:28.240 align:start position:0% initial review through 00:09:28.240 --> 00:09:30.389 align:start position:0% initial review through and<00:09:28.399> then<00:09:28.560> I<00:09:28.800> go<00:09:28.959> through<00:09:29.440> the<00:09:29.680> reviews<00:09:30.160> that 00:09:30.389 --> 00:09:30.399 align:start position:0% and then I go through the reviews that 00:09:30.399 --> 00:09:32.070 align:start position:0% and then I go through the reviews that magpie<00:09:30.959> produced 00:09:32.070 --> 00:09:32.080 align:start position:0% magpie produced 00:09:32.080 --> 00:09:34.470 align:start position:0% magpie produced and<00:09:32.240> then<00:09:32.480> one<00:09:32.640> by<00:09:32.800> one<00:09:33.040> go<00:09:33.200> through<00:09:33.360> those<00:09:34.080> and 00:09:34.470 --> 00:09:34.480 align:start position:0% and then one by one go through those and 00:09:34.480 --> 00:09:35.910 align:start position:0% and then one by one go through those and review<00:09:34.800> those<00:09:35.120> myself 00:09:35.910 --> 00:09:35.920 align:start position:0% review those myself 00:09:35.920 --> 00:09:37.430 align:start position:0% review those myself before<00:09:36.240> deciding<00:09:36.640> okay<00:09:36.880> yes<00:09:37.040> I<00:09:37.120> agree<00:09:37.360> with 00:09:37.430 --> 00:09:37.440 align:start position:0% before deciding okay yes I agree with 00:09:37.440 --> 00:09:39.350 align:start position:0% before deciding okay yes I agree with that?<00:09:37.600> Yes,<00:09:37.839> we<00:09:37.920> can<00:09:38.000> pass<00:09:38.240> that.<00:09:38.640> No,<00:09:39.120> change 00:09:39.350 --> 00:09:39.360 align:start position:0% that? Yes, we can pass that. No, change 00:09:39.360 --> 00:09:40.949 align:start position:0% that? Yes, we can pass that. No, change this<00:09:39.600> and<00:09:39.760> so<00:09:39.839> on<00:09:40.000> and<00:09:40.080> so<00:09:40.240> forth. 00:09:40.949 --> 00:09:40.959 align:start position:0% this and so on and so forth. 00:09:40.959 --> 00:09:43.509 align:start position:0% this and so on and so forth. So,<00:09:41.440> you<00:09:41.680> know,<00:09:42.640> in<00:09:42.880> order<00:09:42.959> to<00:09:43.120> actually<00:09:43.360> have 00:09:43.509 --> 00:09:43.519 align:start position:0% So, you know, in order to actually have 00:09:43.519 --> 00:09:46.070 align:start position:0% So, you know, in order to actually have be<00:09:43.600> able<00:09:43.760> to<00:09:43.920> keep<00:09:44.080> up<00:09:44.320> with<00:09:44.880> the<00:09:45.120> activity<00:09:45.519> on 00:09:46.070 --> 00:09:46.080 align:start position:0% be able to keep up with the activity on 00:09:46.080 --> 00:09:47.509 align:start position:0% be able to keep up with the activity on on<00:09:46.320> on<00:09:46.480> the<00:09:46.720> project, 00:09:47.509 --> 00:09:47.519 align:start position:0% on on the project, 00:09:47.519 --> 00:09:49.829 align:start position:0% on on the project, this<00:09:47.760> kind<00:09:47.839> of<00:09:48.000> AI<00:09:48.399> assistance 00:09:49.829 --> 00:09:49.839 align:start position:0% this kind of AI assistance 00:09:49.839 --> 00:09:53.590 align:start position:0% this kind of AI assistance for<00:09:50.000> the<00:09:50.160> review<00:09:50.480> cycle<00:09:51.440> is<00:09:51.680> just<00:09:52.080> invaluable 00:09:53.590 --> 00:09:53.600 align:start position:0% for the review cycle is just invaluable 00:09:53.600 --> 00:09:54.389 align:start position:0% for the review cycle is just invaluable for<00:09:53.760> that<00:09:53.920> way. 00:09:54.389 --> 00:09:54.399 align:start position:0% for that way. 00:09:54.399 --> 00:09:55.190 align:start position:0% for that way. Mhm. 00:09:55.190 --> 00:09:55.200 align:start position:0% Mhm. 00:09:55.200 --> 00:09:57.350 align:start position:0% Mhm. But<00:09:55.600> the<00:09:55.920> point<00:09:56.080> there<00:09:56.320> is<00:09:56.480> that<00:09:56.720> it<00:09:56.959> also 00:09:57.350 --> 00:09:57.360 align:start position:0% But the point there is that it also 00:09:57.360 --> 00:09:59.670 align:start position:0% But the point there is that it also denotes<00:09:58.320> anything<00:09:58.720> anything<00:09:58.959> posted,<00:09:59.600> you 00:09:59.670 --> 00:09:59.680 align:start position:0% denotes anything anything posted, you 00:09:59.680 --> 00:10:02.389 align:start position:0% denotes anything anything posted, you know,<00:09:59.920> hey,<00:10:00.240> this<00:10:00.480> was<00:10:01.200> assisted<00:10:01.680> by<00:10:01.839> an<00:10:02.000> AI 00:10:02.389 --> 00:10:02.399 align:start position:0% know, hey, this was assisted by an AI 00:10:02.399 --> 00:10:04.230 align:start position:0% know, hey, this was assisted by an AI but<00:10:02.800> signed<00:10:03.120> off<00:10:03.360> by<00:10:03.519> the<00:10:03.760> maintainer. 00:10:04.230 --> 00:10:04.240 align:start position:0% but signed off by the maintainer. 00:10:04.240 --> 00:10:07.509 align:start position:0% but signed off by the maintainer. Exactly.<00:10:04.959> Exactly.<00:10:06.160> A<00:10:06.720> a<00:10:07.120> and<00:10:07.360> the 00:10:07.509 --> 00:10:07.519 align:start position:0% Exactly. Exactly. A a and the 00:10:07.519 --> 00:10:09.030 align:start position:0% Exactly. Exactly. A a and the expectation<00:10:08.000> is<00:10:08.240> that<00:10:08.480> you<00:10:08.640> know<00:10:08.720> any 00:10:09.030 --> 00:10:09.040 align:start position:0% expectation is that you know any 00:10:09.040 --> 00:10:12.150 align:start position:0% expectation is that you know any responses<00:10:09.600> from<00:10:10.240> the<00:10:10.480> contributors<00:10:11.680> you<00:10:11.839> know 00:10:12.150 --> 00:10:12.160 align:start position:0% responses from the contributors you know 00:10:12.160 --> 00:10:14.389 align:start position:0% responses from the contributors you know are<00:10:12.480> responsible<00:10:13.040> for<00:10:13.360> what<00:10:13.600> they<00:10:13.839> put<00:10:14.240> right 00:10:14.389 --> 00:10:14.399 align:start position:0% are responsible for what they put right 00:10:14.399 --> 00:10:15.590 align:start position:0% are responsible for what they put right and<00:10:14.560> that's<00:10:14.640> that's<00:10:14.880> the<00:10:14.959> goal<00:10:15.120> here<00:10:15.279> is<00:10:15.440> that 00:10:15.590 --> 00:10:15.600 align:start position:0% and that's that's the goal here is that 00:10:15.600 --> 00:10:17.350 align:start position:0% and that's that's the goal here is that it's<00:10:15.760> it's<00:10:15.839> it's<00:10:16.399> as<00:10:16.640> you<00:10:16.800> said<00:10:17.040> you're<00:10:17.200> not 00:10:17.350 --> 00:10:17.360 align:start position:0% it's it's it's as you said you're not 00:10:17.360 --> 00:10:18.470 align:start position:0% it's it's it's as you said you're not anti-<00:10:17.680> AAI 00:10:18.470 --> 00:10:18.480 align:start position:0% anti- AAI 00:10:18.480 --> 00:10:22.630 align:start position:0% anti- AAI but<00:10:19.360> anything<00:10:19.760> you're<00:10:20.160> anything<00:10:20.640> your<00:10:21.839> LLM 00:10:22.630 --> 00:10:22.640 align:start position:0% but anything you're anything your LLM 00:10:22.640 --> 00:10:26.069 align:start position:0% but anything you're anything your LLM posts<00:10:23.680> or<00:10:24.079> sends<00:10:24.320> a<00:10:24.480> PR<00:10:24.880> or<00:10:25.120> what<00:10:25.279> code<00:10:25.519> writes 00:10:26.069 --> 00:10:26.079 align:start position:0% posts or sends a PR or what code writes 00:10:26.079 --> 00:10:27.430 align:start position:0% posts or sends a PR or what code writes you're<00:10:26.320> responsible<00:10:26.800> because<00:10:27.040> your<00:10:27.200> name's 00:10:27.430 --> 00:10:27.440 align:start position:0% you're responsible because your name's 00:10:27.440 --> 00:10:28.069 align:start position:0% you're responsible because your name's going to<00:10:27.519> be<00:10:27.600> on<00:10:27.760> it 00:10:28.069 --> 00:10:28.079 align:start position:0% going to be on it 00:10:28.079 --> 00:10:30.310 align:start position:0% going to be on it right<00:10:28.560> exactly<00:10:29.200> exactly<00:10:29.600> it's<00:10:29.760> like<00:10:29.920> they<00:10:30.160> put 00:10:30.310 --> 00:10:30.320 align:start position:0% right exactly exactly it's like they put 00:10:30.320 --> 00:10:32.630 align:start position:0% right exactly exactly it's like they put on<00:10:30.560> the<00:10:31.120> bottles<00:10:31.440> of<00:10:31.600> fine<00:10:31.920> scotch<00:10:32.320> drink 00:10:32.630 --> 00:10:32.640 align:start position:0% on the bottles of fine scotch drink 00:10:32.640 --> 00:10:34.150 align:start position:0% on the bottles of fine scotch drink responsibly 00:10:34.150 --> 00:10:34.160 align:start position:0% responsibly 00:10:34.160 --> 00:10:36.630 align:start position:0% responsibly like<00:10:34.399> usually<00:10:35.040> responsibly<00:10:35.360> Right.<00:10:36.320> It's<00:10:36.480> up 00:10:36.630 --> 00:10:36.640 align:start position:0% like usually responsibly Right. It's up 00:10:36.640 --> 00:10:37.350 align:start position:0% like usually responsibly Right. It's up to<00:10:36.720> you. 00:10:37.350 --> 00:10:37.360 align:start position:0% to you. 00:10:37.360 --> 00:10:38.949 align:start position:0% to you. We're<00:10:37.600> not<00:10:37.760> prohibiting<00:10:38.160> you<00:10:38.320> from<00:10:38.480> driving 00:10:38.949 --> 00:10:38.959 align:start position:0% We're not prohibiting you from driving 00:10:38.959 --> 00:10:40.710 align:start position:0% We're not prohibiting you from driving after<00:10:39.360> one<00:10:39.519> shot,<00:10:39.760> but<00:10:39.920> like<00:10:40.079> it's 00:10:40.710 --> 00:10:40.720 align:start position:0% after one shot, but like it's 00:10:40.720 --> 00:10:42.550 align:start position:0% after one shot, but like it's like<00:10:40.880> so<00:10:40.959> like<00:10:41.120> magpie<00:10:41.519> is<00:10:41.680> part<00:10:41.839> of<00:10:42.079> is<00:10:42.399> part 00:10:42.550 --> 00:10:42.560 align:start position:0% like so like magpie is part of is part 00:10:42.560 --> 00:10:44.949 align:start position:0% like so like magpie is part of is part of<00:10:43.200> the<00:10:43.519> responsible<00:10:44.000> AI<00:10:44.320> committee<00:10:44.640> at<00:10:44.800> the 00:10:44.949 --> 00:10:44.959 align:start position:0% of the responsible AI committee at the 00:10:44.959 --> 00:10:45.670 align:start position:0% of the responsible AI committee at the ASF. 00:10:45.670 --> 00:10:45.680 align:start position:0% ASF. 00:10:45.680 --> 00:10:47.990 align:start position:0% ASF. Yes.<00:10:46.160> Yes.<00:10:46.480> You<00:10:46.640> know<00:10:46.959> that<00:10:47.120> that's<00:10:47.360> where 00:10:47.990 --> 00:10:48.000 align:start position:0% Yes. Yes. You know that that's where 00:10:48.000 --> 00:10:50.310 align:start position:0% Yes. Yes. You know that that's where many<00:10:48.320> many<00:10:48.720> of<00:10:49.120> the<00:10:49.360> people<00:10:49.600> that<00:10:49.760> are<00:10:49.920> part<00:10:50.160> of 00:10:50.310 --> 00:10:50.320 align:start position:0% many many of the people that are part of 00:10:50.320 --> 00:10:52.710 align:start position:0% many many of the people that are part of that<00:10:50.560> that<00:10:50.880> are<00:10:51.120> the<00:10:51.360> PMC<00:10:51.920> and<00:10:52.079> initial<00:10:52.399> group 00:10:52.710 --> 00:10:52.720 align:start position:0% that that are the PMC and initial group 00:10:52.720 --> 00:10:55.990 align:start position:0% that that are the PMC and initial group for<00:10:52.959> Apache<00:10:53.279> Magpie<00:10:53.839> are<00:10:54.640> the<00:10:55.200> responsible<00:10:55.680> AI 00:10:55.990 --> 00:10:56.000 align:start position:0% for Apache Magpie are the responsible AI 00:10:56.000 --> 00:10:58.630 align:start position:0% for Apache Magpie are the responsible AI committee<00:10:56.560> or<00:10:56.800> at<00:10:56.880> least<00:10:57.360> related<00:10:57.760> to<00:10:58.079> people 00:10:58.630 --> 00:10:58.640 align:start position:0% committee or at least related to people 00:10:58.640 --> 00:11:00.389 align:start position:0% committee or at least related to people working<00:10:58.800> on<00:10:59.040> the<00:10:59.279> responsible<00:10:59.680> AI<00:11:00.000> committee 00:11:00.389 --> 00:11:00.399 align:start position:0% working on the responsible AI committee 00:11:00.399 --> 00:11:03.110 align:start position:0% working on the responsible AI committee with<00:11:00.640> the<00:11:01.279> AASF<00:11:01.920> you<00:11:02.079> know<00:11:02.399> which<00:11:02.640> are 00:11:03.110 --> 00:11:03.120 align:start position:0% with the AASF you know which are 00:11:03.120 --> 00:11:04.550 align:start position:0% with the AASF you know which are which<00:11:03.360> we<00:11:03.519> are<00:11:03.600> doing<00:11:03.920> you<00:11:04.000> know<00:11:04.160> there's<00:11:04.320> lots 00:11:04.550 --> 00:11:04.560 align:start position:0% which we are doing you know there's lots 00:11:04.560 --> 00:11:07.350 align:start position:0% which we are doing you know there's lots of<00:11:04.640> suggestions<00:11:05.279> and<00:11:05.760> recommendations<00:11:06.399> on 00:11:07.350 --> 00:11:07.360 align:start position:0% of suggestions and recommendations on 00:11:07.360 --> 00:11:09.269 align:start position:0% of suggestions and recommendations on you<00:11:07.440> know<00:11:07.680> policy<00:11:08.160> around<00:11:08.480> it<00:11:08.720> and<00:11:09.040> things 00:11:09.269 --> 00:11:09.279 align:start position:0% you know policy around it and things 00:11:09.279 --> 00:11:11.590 align:start position:0% you know policy around it and things like<00:11:09.360> that<00:11:09.760> just<00:11:10.079> because<00:11:10.640> at<00:11:10.880> this<00:11:11.040> point<00:11:11.279> you 00:11:11.590 --> 00:11:11.600 align:start position:0% like that just because at this point you 00:11:11.600 --> 00:11:13.990 align:start position:0% like that just because at this point you can't<00:11:11.839> just<00:11:12.160> blanket<00:11:12.640> ban<00:11:13.120> AI<00:11:13.680> no 00:11:13.990 --> 00:11:14.000 align:start position:0% can't just blanket ban AI no 00:11:14.000 --> 00:11:15.190 align:start position:0% can't just blanket ban AI no contributions<00:11:14.560> it<00:11:14.720> doesn't<00:11:14.880> work 00:11:15.190 --> 00:11:15.200 align:start position:0% contributions it doesn't work 00:11:15.200 --> 00:11:15.750 align:start position:0% contributions it doesn't work it<00:11:15.279> doesn't<00:11:15.440> work 00:11:15.750 --> 00:11:15.760 align:start position:0% it doesn't work 00:11:15.760 --> 00:11:17.269 align:start position:0% it doesn't work you<00:11:15.839> know<00:11:16.000> And<00:11:16.320> many<00:11:16.560> open<00:11:16.800> source<00:11:17.040> projects 00:11:17.269 --> 00:11:17.279 align:start position:0% you know And many open source projects 00:11:17.279 --> 00:11:19.030 align:start position:0% you know And many open source projects have<00:11:17.440> taken<00:11:17.600> that<00:11:17.760> tact<00:11:18.000> and<00:11:18.160> that's<00:11:18.720> that's 00:11:19.030 --> 00:11:19.040 align:start position:0% have taken that tact and that's that's 00:11:19.040 --> 00:11:19.990 align:start position:0% have taken that tact and that's that's up<00:11:19.200> to<00:11:19.279> them<00:11:19.440> to<00:11:19.600> do. 00:11:19.990 --> 00:11:20.000 align:start position:0% up to them to do. 00:11:20.000 --> 00:11:21.829 align:start position:0% up to them to do. Yeah,<00:11:20.160> it's<00:11:20.800> they<00:11:20.959> going<00:11:21.040> to<00:11:21.200> be<00:11:21.360> condemned<00:11:21.760> to 00:11:21.829 --> 00:11:21.839 align:start position:0% Yeah, it's they going to be condemned to 00:11:21.839 --> 00:11:23.350 align:start position:0% Yeah, it's they going to be condemned to be<00:11:21.920> a<00:11:22.160> niche<00:11:22.560> because<00:11:22.880> industrial 00:11:23.350 --> 00:11:23.360 align:start position:0% be a niche because industrial 00:11:23.360 --> 00:11:24.069 align:start position:0% be a niche because industrial development<00:11:23.680> is 00:11:24.069 --> 00:11:24.079 align:start position:0% development is 00:11:24.079 --> 00:11:25.750 align:start position:0% development is I<00:11:24.160> don't<00:11:24.320> necessarily<00:11:25.040> not<00:11:25.200> necessarily<00:11:25.600> on 00:11:25.750 --> 00:11:25.760 align:start position:0% I don't necessarily not necessarily on 00:11:25.760 --> 00:11:27.910 align:start position:0% I don't necessarily not necessarily on that<00:11:25.920> one<00:11:26.079> but<00:11:26.240> but<00:11:26.320> but<00:11:26.720> for<00:11:26.959> me<00:11:27.360> the<00:11:27.600> way<00:11:27.680> I 00:11:27.910 --> 00:11:27.920 align:start position:0% that one but but but for me the way I 00:11:27.920 --> 00:11:30.949 align:start position:0% that one but but but for me the way I see<00:11:28.079> it<00:11:28.240> is<00:11:28.560> that<00:11:29.920> you<00:11:30.000> you<00:11:30.240> need<00:11:30.399> the<00:11:30.560> barrier 00:11:30.949 --> 00:11:30.959 align:start position:0% see it is that you you need the barrier 00:11:30.959 --> 00:11:32.710 align:start position:0% see it is that you you need the barrier to<00:11:31.120> entry<00:11:31.440> to<00:11:31.600> be<00:11:31.680> as<00:11:31.760> low<00:11:31.920> as<00:11:32.160> possible 00:11:32.710 --> 00:11:32.720 align:start position:0% to entry to be as low as possible 00:11:32.720 --> 00:11:37.430 align:start position:0% to entry to be as low as possible because<00:11:34.000> open<00:11:34.240> source<00:11:34.560> projects<00:11:35.519> perpetually 00:11:37.430 --> 00:11:37.440 align:start position:0% because open source projects perpetually 00:11:37.440 --> 00:11:39.829 align:start position:0% because open source projects perpetually need<00:11:37.760> more<00:11:38.160> contributors<00:11:38.720> and<00:11:38.959> need<00:11:39.120> more 00:11:39.829 --> 00:11:39.839 align:start position:0% need more contributors and need more 00:11:39.839 --> 00:11:41.590 align:start position:0% need more contributors and need more maintainers<00:11:40.399> to<00:11:40.560> be<00:11:40.720> part<00:11:40.880> of<00:11:40.959> the<00:11:41.120> projects. 00:11:41.590 --> 00:11:41.600 align:start position:0% maintainers to be part of the projects. 00:11:41.600 --> 00:11:42.150 align:start position:0% maintainers to be part of the projects. Mhm. 00:11:42.150 --> 00:11:42.160 align:start position:0% Mhm. 00:11:42.160 --> 00:11:44.550 align:start position:0% Mhm. And<00:11:42.399> it's<00:11:42.560> just<00:11:42.720> a<00:11:42.800> perpetual<00:11:43.360> problem<00:11:44.079> that 00:11:44.550 --> 00:11:44.560 align:start position:0% And it's just a perpetual problem that 00:11:44.560 --> 00:11:46.550 align:start position:0% And it's just a perpetual problem that open<00:11:44.880> source<00:11:45.360> software<00:11:45.839> just<00:11:46.079> does<00:11:46.240> not<00:11:46.399> have 00:11:46.550 --> 00:11:46.560 align:start position:0% open source software just does not have 00:11:46.560 --> 00:11:48.150 align:start position:0% open source software just does not have enough<00:11:47.519> people 00:11:48.150 --> 00:11:48.160 align:start position:0% enough people 00:11:48.160 --> 00:11:48.630 align:start position:0% enough people Yes. 00:11:48.630 --> 00:11:48.640 align:start position:0% Yes. 00:11:48.640 --> 00:11:51.990 align:start position:0% Yes. on<00:11:48.880> any<00:11:49.120> given<00:11:49.440> project.<00:11:49.920> And<00:11:50.160> so 00:11:51.990 --> 00:11:52.000 align:start position:0% on any given project. And so 00:11:52.000 --> 00:11:54.069 align:start position:0% on any given project. And so if<00:11:52.320> the<00:11:52.560> first<00:11:52.800> way<00:11:52.959> that<00:11:53.279> someone<00:11:53.519> engages 00:11:54.069 --> 00:11:54.079 align:start position:0% if the first way that someone engages 00:11:54.079 --> 00:11:57.269 align:start position:0% if the first way that someone engages with<00:11:54.240> your<00:11:54.560> project<00:11:55.600> is<00:11:55.920> to<00:11:56.240> have<00:11:56.399> an<00:11:56.560> LLM<00:11:57.040> help 00:11:57.269 --> 00:11:57.279 align:start position:0% with your project is to have an LLM help 00:11:57.279 --> 00:11:58.710 align:start position:0% with your project is to have an LLM help them<00:11:57.680> file<00:11:57.920> a<00:11:58.079> PR. 00:11:58.710 --> 00:11:58.720 align:start position:0% them file a PR. 00:11:58.720 --> 00:11:59.430 align:start position:0% them file a PR. Mhm. 00:11:59.430 --> 00:11:59.440 align:start position:0% Mhm. 00:11:59.440 --> 00:12:01.750 align:start position:0% Mhm. I<00:11:59.680> don't<00:11:59.920> want<00:12:00.160> to<00:12:00.480> be<00:12:00.800> a<00:12:01.040> maintainer<00:12:01.519> that 00:12:01.750 --> 00:12:01.760 align:start position:0% I don't want to be a maintainer that 00:12:01.760 --> 00:12:03.030 align:start position:0% I don't want to be a maintainer that just<00:12:01.920> immediately<00:12:02.320> goes, 00:12:03.030 --> 00:12:03.040 align:start position:0% just immediately goes, 00:12:03.040 --> 00:12:05.990 align:start position:0% just immediately goes, "Nope,<00:12:03.440> that's<00:12:03.680> AIGN,<00:12:04.959> you<00:12:05.120> know,<00:12:05.440> not<00:12:05.760> not 00:12:05.990 --> 00:12:06.000 align:start position:0% "Nope, that's AIGN, you know, not not 00:12:06.000 --> 00:12:08.470 align:start position:0% "Nope, that's AIGN, you know, not not look<00:12:06.160> at<00:12:06.240> it,<00:12:06.399> not<00:12:06.560> create<00:12:07.839> AI,<00:12:08.160> go<00:12:08.240> away." 00:12:08.470 --> 00:12:08.480 align:start position:0% look at it, not create AI, go away." 00:12:08.480 --> 00:12:10.069 align:start position:0% look at it, not create AI, go away." Like<00:12:08.639> I<00:12:08.800> I<00:12:09.040> don't<00:12:09.120> want<00:12:09.200> to<00:12:09.360> do<00:12:09.440> that.<00:12:09.760> I<00:12:10.000> want 00:12:10.069 --> 00:12:10.079 align:start position:0% Like I I don't want to do that. I want 00:12:10.079 --> 00:12:12.150 align:start position:0% Like I I don't want to do that. I want to<00:12:10.320> encourage<00:12:10.720> that<00:12:10.959> person. 00:12:12.150 --> 00:12:12.160 align:start position:0% to encourage that person. 00:12:12.160 --> 00:12:14.310 align:start position:0% to encourage that person. I<00:12:12.399> want<00:12:12.560> to<00:12:12.959> see<00:12:13.440> are<00:12:13.680> they<00:12:13.839> someone<00:12:14.079> who's 00:12:14.310 --> 00:12:14.320 align:start position:0% I want to see are they someone who's 00:12:14.320 --> 00:12:16.629 align:start position:0% I want to see are they someone who's going<00:12:14.480> to<00:12:14.639> engage<00:12:15.600> with<00:12:15.839> the<00:12:16.079> project, 00:12:16.629 --> 00:12:16.639 align:start position:0% going to engage with the project, 00:12:16.639 --> 00:12:17.430 align:start position:0% going to engage with the project, right? 00:12:17.430 --> 00:12:17.440 align:start position:0% right? 00:12:17.440 --> 00:12:19.110 align:start position:0% right? You<00:12:17.600> know,<00:12:17.920> above<00:12:18.160> and<00:12:18.320> beyond<00:12:18.639> being<00:12:18.720> a<00:12:18.880> meat 00:12:19.110 --> 00:12:19.120 align:start position:0% You know, above and beyond being a meat 00:12:19.120 --> 00:12:20.150 align:start position:0% You know, above and beyond being a meat proxy<00:12:19.440> for<00:12:19.519> their<00:12:19.680> AI, 00:12:20.150 --> 00:12:20.160 align:start position:0% proxy for their AI, 00:12:20.160 --> 00:12:21.350 align:start position:0% proxy for their AI, right? 00:12:21.350 --> 00:12:21.360 align:start position:0% right? 00:12:21.360 --> 00:12:23.430 align:start position:0% right? Um<00:12:21.760> and<00:12:21.920> if<00:12:22.160> they're<00:12:22.399> willing<00:12:22.720> to<00:12:22.959> engage<00:12:23.279> with 00:12:23.430 --> 00:12:23.440 align:start position:0% Um and if they're willing to engage with 00:12:23.440 --> 00:12:25.350 align:start position:0% Um and if they're willing to engage with the<00:12:23.600> project<00:12:23.839> and<00:12:24.079> they're<00:12:24.240> mentorable<00:12:24.880> and 00:12:25.350 --> 00:12:25.360 align:start position:0% the project and they're mentorable and 00:12:25.360 --> 00:12:26.710 align:start position:0% the project and they're mentorable and you<00:12:25.440> know,<00:12:25.600> like<00:12:26.320> AI, 00:12:26.710 --> 00:12:26.720 align:start position:0% you know, like AI, 00:12:26.720 --> 00:12:28.629 align:start position:0% you know, like AI, it's<00:12:26.800> a<00:12:26.959> new<00:12:27.040> term<00:12:27.279> I<00:12:27.440> learned<00:12:27.680> from<00:12:27.839> you<00:12:28.079> also. 00:12:28.629 --> 00:12:28.639 align:start position:0% it's a new term I learned from you also. 00:12:28.639 --> 00:12:29.829 align:start position:0% it's a new term I learned from you also. Meet<00:12:28.959> proxy.<00:12:29.360> It's<00:12:29.519> a<00:12:29.600> good<00:12:29.680> one. 00:12:29.829 --> 00:12:29.839 align:start position:0% Meet proxy. It's a good one. 00:12:29.839 --> 00:12:30.870 align:start position:0% Meet proxy. It's a good one. Yeah.<00:12:30.000> They<00:12:30.160> they<00:12:30.320> use<00:12:30.560> they<00:12:30.638> [laughter]<00:12:30.720> used 00:12:30.870 --> 00:12:30.880 align:start position:0% Yeah. They they use they [laughter] used 00:12:30.880 --> 00:12:32.790 align:start position:0% Yeah. They they use they [laughter] used it<00:12:30.959> in<00:12:31.040> the<00:12:31.120> keynote<00:12:31.440> yesterday.<00:12:31.920> Yeah.<00:12:32.480> And<00:12:32.639> I 00:12:32.790 --> 00:12:32.800 align:start position:0% it in the keynote yesterday. Yeah. And I 00:12:32.800 --> 00:12:34.150 align:start position:0% it in the keynote yesterday. Yeah. And I I<00:12:32.959> heard<00:12:33.120> about<00:12:33.200> it<00:12:33.360> and<00:12:33.519> I've<00:12:33.680> heard<00:12:33.760> it<00:12:34.000> a 00:12:34.150 --> 00:12:34.160 align:start position:0% I heard about it and I've heard it a 00:12:34.160 --> 00:12:34.949 align:start position:0% I heard about it and I've heard it a couple<00:12:34.320> other<00:12:34.560> places. 00:12:34.949 --> 00:12:34.959 align:start position:0% couple other places. 00:12:34.959 --> 00:12:37.350 align:start position:0% couple other places. Yes.<00:12:35.200> Yes.<00:12:35.519> You<00:12:35.600> know,<00:12:35.760> but<00:12:35.920> but<00:12:36.240> like<00:12:36.480> like<00:12:37.040> AI 00:12:37.350 --> 00:12:37.360 align:start position:0% Yes. Yes. You know, but but like like AI 00:12:37.360 --> 00:12:39.750 align:start position:0% Yes. Yes. You know, but but like like AI is<00:12:38.079> LLMs<00:12:38.480> and<00:12:38.560> AI<00:12:38.880> are<00:12:39.040> a<00:12:39.120> tool<00:12:39.279> like<00:12:39.519> anything 00:12:39.750 --> 00:12:39.760 align:start position:0% is LLMs and AI are a tool like anything 00:12:39.760 --> 00:12:42.470 align:start position:0% is LLMs and AI are a tool like anything else.<00:12:40.079> And<00:12:40.240> as<00:12:40.480> developers<00:12:41.680> are<00:12:41.920> are<00:12:42.240> we 00:12:42.470 --> 00:12:42.480 align:start position:0% else. And as developers are are we 00:12:42.480 --> 00:12:43.990 align:start position:0% else. And as developers are are we should<00:12:42.639> be<00:12:42.720> using<00:12:42.959> as<00:12:43.120> many<00:12:43.279> tools<00:12:43.519> as<00:12:43.680> we<00:12:43.760> can. 00:12:43.990 --> 00:12:44.000 align:start position:0% should be using as many tools as we can. 00:12:44.000 --> 00:12:45.750 align:start position:0% should be using as many tools as we can. Like<00:12:44.639> I<00:12:44.800> I've<00:12:45.040> had<00:12:45.120> a<00:12:45.279> conversation<00:12:45.519> with 00:12:45.750 --> 00:12:45.760 align:start position:0% Like I I've had a conversation with 00:12:45.760 --> 00:12:48.949 align:start position:0% Like I I've had a conversation with people<00:12:45.920> where<00:12:46.800> you<00:12:46.959> know<00:12:47.200> half<00:12:47.440> of<00:12:47.600> my<00:12:47.839> career 00:12:48.949 --> 00:12:48.959 align:start position:0% people where you know half of my career 00:12:48.959 --> 00:12:51.509 align:start position:0% people where you know half of my career my<00:12:49.200> job<00:12:49.360> has<00:12:49.600> been<00:12:49.760> to<00:12:50.000> automate<00:12:50.639> my<00:12:50.959> job, 00:12:51.509 --> 00:12:51.519 align:start position:0% my job has been to automate my job, 00:12:51.519 --> 00:12:52.310 align:start position:0% my job has been to automate my job, right? 00:12:52.310 --> 00:12:52.320 align:start position:0% right? 00:12:52.320 --> 00:12:53.750 align:start position:0% right? And<00:12:52.639> that's<00:12:52.880> going<00:12:52.959> to<00:12:53.040> be<00:12:53.120> the<00:12:53.279> same<00:12:53.440> for<00:12:53.600> most 00:12:53.750 --> 00:12:53.760 align:start position:0% And that's going to be the same for most 00:12:53.760 --> 00:12:55.990 align:start position:0% And that's going to be the same for most developers.<00:12:54.320> Like<00:12:54.959> you're<00:12:55.360> the<00:12:55.600> it's<00:12:55.839> a 00:12:55.990 --> 00:12:56.000 align:start position:0% developers. Like you're the it's a 00:12:56.000 --> 00:12:57.670 align:start position:0% developers. Like you're the it's a neverending<00:12:56.560> search<00:12:56.880> for<00:12:57.279> software 00:12:57.670 --> 00:12:57.680 align:start position:0% neverending search for software 00:12:57.680 --> 00:13:00.230 align:start position:0% neverending search for software engineers<00:12:58.720> to<00:12:59.040> automate<00:12:59.600> as<00:12:59.839> much<00:13:00.000> as<00:13:00.160> we 00:13:00.230 --> 00:13:00.240 align:start position:0% engineers to automate as much as we 00:13:00.240 --> 00:13:01.030 align:start position:0% engineers to automate as much as we possibly 00:13:01.030 --> 00:13:01.040 align:start position:0% possibly 00:13:01.040 --> 00:13:02.949 align:start position:0% possibly yourself<00:13:01.519> out<00:13:01.680> of<00:13:01.839> the<00:13:02.079> job.<00:13:02.399> That's<00:13:02.560> always 00:13:02.949 --> 00:13:02.959 align:start position:0% yourself out of the job. That's always 00:13:02.959 --> 00:13:04.550 align:start position:0% yourself out of the job. That's always and<00:13:03.200> and<00:13:03.360> that's<00:13:03.519> the<00:13:03.680> goal.<00:13:04.000> That's<00:13:04.160> the<00:13:04.320> goal 00:13:04.550 --> 00:13:04.560 align:start position:0% and and that's the goal. That's the goal 00:13:04.560 --> 00:13:05.910 align:start position:0% and and that's the goal. That's the goal cuz<00:13:05.040> cuz<00:13:05.200> then<00:13:05.360> you<00:13:05.440> can<00:13:05.519> move<00:13:05.600> on<00:13:05.760> to 00:13:05.910 --> 00:13:05.920 align:start position:0% cuz cuz then you can move on to 00:13:05.920 --> 00:13:06.389 align:start position:0% cuz cuz then you can move on to something<00:13:06.079> else. 00:13:06.389 --> 00:13:06.399 align:start position:0% something else. 00:13:06.399 --> 00:13:07.110 align:start position:0% something else. That's<00:13:06.560> right. 00:13:07.110 --> 00:13:07.120 align:start position:0% That's right. 00:13:07.120 --> 00:13:12.069 align:start position:0% That's right. And<00:13:07.360> so<00:13:07.600> like<00:13:08.160> to<00:13:08.639> to<00:13:09.279> blanket<00:13:09.920> be<00:13:10.160> against<00:13:10.560> AI 00:13:12.069 --> 00:13:12.079 align:start position:0% And so like to to blanket be against AI 00:13:12.079 --> 00:13:14.629 align:start position:0% And so like to to blanket be against AI is<00:13:12.399> kind<00:13:12.560> of<00:13:12.720> weird 00:13:14.629 --> 00:13:14.639 align:start position:0% is kind of weird 00:13:14.639 --> 00:13:18.150 align:start position:0% is kind of weird in<00:13:14.959> that<00:13:15.200> scenario<00:13:16.160> because<00:13:17.360> it's<00:13:17.680> just<00:13:18.000> kind 00:13:18.150 --> 00:13:18.160 align:start position:0% in that scenario because it's just kind 00:13:18.160 --> 00:13:20.629 align:start position:0% in that scenario because it's just kind of<00:13:18.240> the<00:13:18.480> epitome<00:13:18.959> of<00:13:19.839> what<00:13:20.079> we've<00:13:20.320> been<00:13:20.399> doing 00:13:20.629 --> 00:13:20.639 align:start position:0% of the epitome of what we've been doing 00:13:20.639 --> 00:13:22.629 align:start position:0% of the epitome of what we've been doing anyways<00:13:21.440> in<00:13:21.680> terms<00:13:21.839> of<00:13:22.000> trying<00:13:22.160> to<00:13:22.320> automate 00:13:22.629 --> 00:13:22.639 align:start position:0% anyways in terms of trying to automate 00:13:22.639 --> 00:13:23.110 align:start position:0% anyways in terms of trying to automate ourselves. 00:13:23.110 --> 00:13:23.120 align:start position:0% ourselves. 00:13:23.120 --> 00:13:24.710 align:start position:0% ourselves. It's<00:13:23.279> just<00:13:23.440> next<00:13:23.680> step.<00:13:23.920> It's<00:13:24.079> next<00:13:24.320> step. 00:13:24.710 --> 00:13:24.720 align:start position:0% It's just next step. It's next step. 00:13:24.720 --> 00:13:28.230 align:start position:0% It's just next step. It's next step. It's<00:13:25.040> but<00:13:25.279> as<00:13:25.600> any<00:13:25.920> but<00:13:26.160> with<00:13:26.480> but<00:13:26.720> as<00:13:27.040> any<00:13:27.360> tool 00:13:28.230 --> 00:13:28.240 align:start position:0% It's but as any but with but as any tool 00:13:28.240 --> 00:13:30.069 align:start position:0% It's but as any but with but as any tool you<00:13:28.480> have<00:13:28.560> to<00:13:28.720> know<00:13:28.880> how<00:13:29.120> to<00:13:29.279> use<00:13:29.440> it.<00:13:29.839> You<00:13:30.000> have 00:13:30.069 --> 00:13:30.079 align:start position:0% you have to know how to use it. You have 00:13:30.079 --> 00:13:32.069 align:start position:0% you have to know how to use it. You have to<00:13:30.240> do<00:13:30.320> it<00:13:30.560> responsibly.<00:13:31.360> You<00:13:31.519> have<00:13:31.680> to<00:13:31.760> use<00:13:31.920> it 00:13:32.069 --> 00:13:32.079 align:start position:0% to do it responsibly. You have to use it 00:13:32.079 --> 00:13:33.910 align:start position:0% to do it responsibly. You have to use it correctly.<00:13:32.399> You<00:13:32.639> know,<00:13:32.800> if<00:13:33.040> you're<00:13:33.279> just<00:13:33.519> vibe 00:13:33.910 --> 00:13:33.920 align:start position:0% correctly. You know, if you're just vibe 00:13:33.920 --> 00:13:35.269 align:start position:0% correctly. You know, if you're just vibe coding<00:13:34.160> and<00:13:34.320> that's<00:13:34.480> all<00:13:34.639> you're<00:13:34.800> doing, 00:13:35.269 --> 00:13:35.279 align:start position:0% coding and that's all you're doing, 00:13:35.279 --> 00:13:36.870 align:start position:0% coding and that's all you're doing, cool.<00:13:35.600> It's<00:13:35.760> great<00:13:35.920> for<00:13:36.079> a<00:13:36.240> prototype. 00:13:36.870 --> 00:13:36.880 align:start position:0% cool. It's great for a prototype. 00:13:36.880 --> 00:13:37.670 align:start position:0% cool. It's great for a prototype. Mhm. 00:13:37.670 --> 00:13:37.680 align:start position:0% Mhm. 00:13:37.680 --> 00:13:39.590 align:start position:0% Mhm. But<00:13:38.639> if<00:13:38.880> you're<00:13:39.040> doing<00:13:39.200> anything<00:13:39.360> in 00:13:39.590 --> 00:13:39.600 align:start position:0% But if you're doing anything in 00:13:39.600 --> 00:13:40.949 align:start position:0% But if you're doing anything in production,<00:13:39.920> you<00:13:40.079> better<00:13:40.320> be<00:13:40.560> at<00:13:40.639> least 00:13:40.949 --> 00:13:40.959 align:start position:0% production, you better be at least 00:13:40.959 --> 00:13:42.230 align:start position:0% production, you better be at least glancing<00:13:41.279> at<00:13:41.440> the<00:13:41.519> code.<00:13:41.760> You<00:13:41.839> better<00:13:42.079> but<00:13:42.160> you 00:13:42.230 --> 00:13:42.240 align:start position:0% glancing at the code. You better but you 00:13:42.240 --> 00:13:43.910 align:start position:0% glancing at the code. You better but you better<00:13:42.480> also<00:13:42.720> be<00:13:42.880> understanding<00:13:43.600> what's 00:13:43.910 --> 00:13:43.920 align:start position:0% better also be understanding what's 00:13:43.920 --> 00:13:45.190 align:start position:0% better also be understanding what's going<00:13:44.000> on<00:13:44.160> and<00:13:44.320> what<00:13:44.480> it's<00:13:44.720> doing. 00:13:45.190 --> 00:13:45.200 align:start position:0% going on and what it's doing. 00:13:45.200 --> 00:13:45.829 align:start position:0% going on and what it's doing. Mhm. 00:13:45.829 --> 00:13:45.839 align:start position:0% Mhm. 00:13:45.839 --> 00:13:48.870 align:start position:0% Mhm. So<00:13:46.000> that<00:13:46.240> you<00:13:46.639> can,<00:13:47.120> you<00:13:47.279> know,<00:13:47.920> steer<00:13:48.639> your 00:13:48.870 --> 00:13:48.880 align:start position:0% So that you can, you know, steer your 00:13:48.880 --> 00:13:50.069 align:start position:0% So that you can, you know, steer your LLM<00:13:49.440> at<00:13:49.519> a<00:13:49.680> minimum. 00:13:50.069 --> 00:13:50.079 align:start position:0% LLM at a minimum. 00:13:50.079 --> 00:13:50.389 align:start position:0% LLM at a minimum. Yes. 00:13:50.389 --> 00:13:50.399 align:start position:0% Yes. 00:13:50.399 --> 00:13:52.150 align:start position:0% Yes. You<00:13:50.560> know,<00:13:50.720> you<00:13:51.200> the<00:13:51.600> knowledge<00:13:51.839> and 00:13:52.150 --> 00:13:52.160 align:start position:0% You know, you the knowledge and 00:13:52.160 --> 00:13:53.990 align:start position:0% You know, you the knowledge and experience<00:13:52.639> of<00:13:52.959> developers<00:13:53.440> is<00:13:53.760> still 00:13:53.990 --> 00:13:54.000 align:start position:0% experience of developers is still 00:13:54.000 --> 00:13:54.470 align:start position:0% experience of developers is still important. 00:13:54.470 --> 00:13:54.480 align:start position:0% important. 00:13:54.480 --> 00:13:56.790 align:start position:0% important. Yes.<00:13:54.720> You<00:13:54.959> have<00:13:55.040> to<00:13:55.680> show<00:13:56.000> you<00:13:56.240> have<00:13:56.320> critical 00:13:56.790 --> 00:13:56.800 align:start position:0% Yes. You have to show you have critical 00:13:56.800 --> 00:13:58.629 align:start position:0% Yes. You have to show you have critical thinking<00:13:57.600> capacity.<00:13:58.320> So 00:13:58.629 --> 00:13:58.639 align:start position:0% thinking capacity. So 00:13:58.639 --> 00:13:59.670 align:start position:0% thinking capacity. So because<00:13:58.880> because<00:13:59.120> they're<00:13:59.279> just<00:13:59.440> going<00:13:59.519> to<00:13:59.600> do 00:13:59.670 --> 00:13:59.680 align:start position:0% because because they're just going to do 00:13:59.680 --> 00:14:00.949 align:start position:0% because because they're just going to do because<00:13:59.839> the<00:14:00.000> AI<00:14:00.399> just<00:14:00.480> going<00:14:00.560> to<00:14:00.639> do<00:14:00.800> stupid 00:14:00.949 --> 00:14:00.959 align:start position:0% because the AI just going to do stupid 00:14:00.959 --> 00:14:02.710 align:start position:0% because the AI just going to do stupid things<00:14:01.120> anyways.<00:14:01.519> Exactly.<00:14:02.079> Exactly.<00:14:02.480> You 00:14:02.710 --> 00:14:02.720 align:start position:0% things anyways. Exactly. Exactly. You 00:14:02.720 --> 00:14:04.470 align:start position:0% things anyways. Exactly. Exactly. You need<00:14:02.800> to<00:14:02.959> be<00:14:03.440> in<00:14:03.680> the<00:14:03.760> you<00:14:04.000> show<00:14:04.240> some 00:14:04.470 --> 00:14:04.480 align:start position:0% need to be in the you show some 00:14:04.480 --> 00:14:06.470 align:start position:0% need to be in the you show some experience<00:14:04.800> and<00:14:04.959> driving<00:14:05.199> it.<00:14:05.519> Yeah.<00:14:05.760> So<00:14:06.079> like 00:14:06.470 --> 00:14:06.480 align:start position:0% experience and driving it. Yeah. So like 00:14:06.480 --> 00:14:08.949 align:start position:0% experience and driving it. Yeah. So like going<00:14:06.720> back<00:14:06.880> to<00:14:06.959> ADBC<00:14:07.600> and<00:14:07.839> so<00:14:08.320> I<00:14:08.480> really<00:14:08.800> kind 00:14:08.949 --> 00:14:08.959 align:start position:0% going back to ADBC and so I really kind 00:14:08.959 --> 00:14:11.750 align:start position:0% going back to ADBC and so I really kind of<00:14:09.199> I'm<00:14:09.519> thinking<00:14:10.000> right<00:14:10.240> like<00:14:10.959> like<00:14:11.279> I<00:14:11.440> mean<00:14:11.600> I 00:14:11.750 --> 00:14:11.760 align:start position:0% of I'm thinking right like like I mean I 00:14:11.760 --> 00:14:15.829 align:start position:0% of I'm thinking right like like I mean I think<00:14:11.920> we<00:14:12.079> met<00:14:12.320> at<00:14:12.720> uh<00:14:13.199> category<00:14:13.839> VC<00:14:14.320> and<00:14:14.720> Wes 00:14:15.829 --> 00:14:15.839 align:start position:0% think we met at uh category VC and Wes 00:14:15.839 --> 00:14:17.990 align:start position:0% think we met at uh category VC and Wes was<00:14:16.079> there<00:14:16.240> and<00:14:16.399> like<00:14:16.639> sale<00:14:17.040> and<00:14:17.199> other<00:14:17.519> like<00:14:17.760> I 00:14:17.990 --> 00:14:18.000 align:start position:0% was there and like sale and other like I 00:14:18.000 --> 00:14:20.550 align:start position:0% was there and like sale and other like I see<00:14:18.720> naturally<00:14:19.279> self-<00:14:19.519> selecting<00:14:20.079> companies 00:14:20.550 --> 00:14:20.560 align:start position:0% see naturally self- selecting companies 00:14:20.560 --> 00:14:24.470 align:start position:0% see naturally self- selecting companies emerging<00:14:21.360> who<00:14:21.600> build<00:14:22.399> fast<00:14:22.800> AI<00:14:23.120> infra<00:14:23.680> in<00:14:24.320> you 00:14:24.470 --> 00:14:24.480 align:start position:0% emerging who build fast AI infra in you 00:14:24.480 --> 00:14:26.389 align:start position:0% emerging who build fast AI infra in you know<00:14:24.800> in<00:14:25.040> rust<00:14:25.360> and<00:14:25.519> native<00:14:25.839> technologies 00:14:26.389 --> 00:14:26.399 align:start position:0% know in rust and native technologies 00:14:26.399 --> 00:14:29.030 align:start position:0% know in rust and native technologies like<00:14:26.560> ADBC<00:14:27.120> in<00:14:27.279> my<00:14:27.360> mind<00:14:27.519> it's<00:14:28.000> like<00:14:28.240> the<00:14:28.480> new 00:14:29.030 --> 00:14:29.040 align:start position:0% like ADBC in my mind it's like the new 00:14:29.040 --> 00:14:30.710 align:start position:0% like ADBC in my mind it's like the new kids<00:14:29.279> on<00:14:29.440> the<00:14:29.600> block<00:14:29.839> like<00:14:30.000> it's<00:14:30.160> a<00:14:30.320> new<00:14:30.399> crop 00:14:30.710 --> 00:14:30.720 align:start position:0% kids on the block like it's a new crop 00:14:30.720 --> 00:14:32.790 align:start position:0% kids on the block like it's a new crop of<00:14:30.880> tools<00:14:31.519> which<00:14:31.839> links<00:14:32.160> this<00:14:32.320> in<00:14:32.560> like 00:14:32.790 --> 00:14:32.800 align:start position:0% of tools which links this in like 00:14:32.800 --> 00:14:35.990 align:start position:0% of tools which links this in like obviously<00:14:33.279> arrow<00:14:33.839> and<00:14:34.079> data<00:14:34.399> fusion<00:14:35.360> and<00:14:35.839> you 00:14:35.990 --> 00:14:36.000 align:start position:0% obviously arrow and data fusion and you 00:14:36.000 --> 00:14:39.269 align:start position:0% obviously arrow and data fusion and you know<00:14:36.079> a<00:14:36.160> bunch<00:14:36.399> of<00:14:36.480> Rust<00:14:37.199> kind<00:14:37.360> of<00:14:37.680> systems.<00:14:38.720> uh 00:14:39.269 --> 00:14:39.279 align:start position:0% know a bunch of Rust kind of systems. uh 00:14:39.279 --> 00:14:42.310 align:start position:0% know a bunch of Rust kind of systems. uh to<00:14:39.519> me<00:14:39.680> it's<00:14:39.920> kind<00:14:40.079> of<00:14:40.720> all<00:14:41.040> part<00:14:41.279> of<00:14:41.440> this<00:14:41.920> and 00:14:42.310 --> 00:14:42.320 align:start position:0% to me it's kind of all part of this and 00:14:42.320 --> 00:14:45.350 align:start position:0% to me it's kind of all part of this and you<00:14:42.639> are<00:14:43.440> in<00:14:43.680> the<00:14:43.920> position<00:14:44.320> where<00:14:44.880> you<00:14:45.120> can 00:14:45.350 --> 00:14:45.360 align:start position:0% you are in the position where you can 00:14:45.360 --> 00:14:47.829 align:start position:0% you are in the position where you can basically<00:14:45.760> put<00:14:45.920> ADBC<00:14:46.720> into<00:14:47.040> multiple<00:14:47.440> systems 00:14:47.829 --> 00:14:47.839 align:start position:0% basically put ADBC into multiple systems 00:14:47.839 --> 00:14:49.670 align:start position:0% basically put ADBC into multiple systems right<00:14:48.079> also<00:14:48.320> your<00:14:48.480> talk<00:14:48.720> was<00:14:48.880> about<00:14:48.959> duck<00:14:49.279> DB 00:14:49.670 --> 00:14:49.680 align:start position:0% right also your talk was about duck DB 00:14:49.680 --> 00:14:52.150 align:start position:0% right also your talk was about duck DB which<00:14:49.920> is<00:14:50.000> another<00:14:50.639> cool<00:14:50.959> kids<00:14:51.279> database<00:14:52.000> like 00:14:52.150 --> 00:14:52.160 align:start position:0% which is another cool kids database like 00:14:52.160 --> 00:14:52.629 align:start position:0% which is another cool kids database like people 00:14:52.629 --> 00:14:52.639 align:start position:0% people 00:14:52.639 --> 00:14:57.430 align:start position:0% people uh<00:14:52.800> a<00:14:53.040> a<00:14:53.040> a<00:14:53.920> uh<00:14:54.160> so<00:14:54.560> columner<00:14:55.120> we<00:14:55.519> we<00:14:55.839> put<00:14:56.000> out<00:14:56.639> um 00:14:57.430 --> 00:14:57.440 align:start position:0% uh a a a uh so columner we we put out um 00:14:57.440 --> 00:14:59.990 align:start position:0% uh a a a uh so columner we we put out um a<00:14:57.839> community<00:14:58.160> extension<00:14:58.560> for<00:14:58.800> for<00:14:59.040> duct<00:14:59.360> DB 00:14:59.990 --> 00:15:00.000 align:start position:0% a community extension for for duct DB 00:15:00.000 --> 00:15:02.470 align:start position:0% a community extension for for duct DB for<00:15:00.240> ADBC<00:15:00.959> right<00:15:01.199> that<00:15:01.519> was<00:15:01.839> uh<00:15:02.000> that<00:15:02.160> was<00:15:02.320> it 00:15:02.470 --> 00:15:02.480 align:start position:0% for ADBC right that was uh that was it 00:15:02.480 --> 00:15:05.350 align:start position:0% for ADBC right that was uh that was it was<00:15:02.639> it<00:15:02.800> was<00:15:02.959> done<00:15:03.120> by<00:15:03.760> uh<00:15:04.320> a<00:15:04.480> a<00:15:04.800> PhD<00:15:05.199> student 00:15:05.350 --> 00:15:05.360 align:start position:0% was it was done by uh a a PhD student 00:15:05.360 --> 00:15:07.189 align:start position:0% was it was done by uh a a PhD student that<00:15:05.600> was<00:15:05.680> an<00:15:05.760> inter<00:15:06.079> that<00:15:06.160> was<00:15:06.320> interning<00:15:06.959> at 00:15:07.189 --> 00:15:07.199 align:start position:0% that was an inter that was interning at 00:15:07.199 --> 00:15:08.790 align:start position:0% that was an inter that was interning at columner<00:15:07.519> there<00:15:07.680> Sam<00:15:08.000> March 00:15:08.790 --> 00:15:08.800 align:start position:0% columner there Sam March 00:15:08.800 --> 00:15:10.230 align:start position:0% columner there Sam March uh<00:15:08.880> who<00:15:09.120> built<00:15:09.360> out<00:15:09.440> the<00:15:09.600> extension, 00:15:10.230 --> 00:15:10.240 align:start position:0% uh who built out the extension, 00:15:10.240 --> 00:15:10.470 align:start position:0% uh who built out the extension, right? 00:15:10.470 --> 00:15:10.480 align:start position:0% right? 00:15:10.480 --> 00:15:12.150 align:start position:0% right? And<00:15:10.639> and<00:15:10.880> we<00:15:11.040> contributed<00:15:11.360> to<00:15:11.519> the<00:15:11.600> community 00:15:12.150 --> 00:15:12.160 align:start position:0% And and we contributed to the community 00:15:12.160 --> 00:15:15.350 align:start position:0% And and we contributed to the community so<00:15:12.320> that<00:15:12.560> you<00:15:12.720> can<00:15:12.880> use<00:15:13.600> ADBC<00:15:14.160> drivers<00:15:15.040> through 00:15:15.350 --> 00:15:15.360 align:start position:0% so that you can use ADBC drivers through 00:15:15.360 --> 00:15:16.550 align:start position:0% so that you can use ADBC drivers through duct<00:15:15.680> DB 00:15:16.550 --> 00:15:16.560 align:start position:0% duct DB 00:15:16.560 --> 00:15:18.870 align:start position:0% duct DB to<00:15:16.880> communicate<00:15:17.519> with<00:15:17.920> whatever<00:15:18.320> system<00:15:18.639> you 00:15:18.870 --> 00:15:18.880 align:start position:0% to communicate with whatever system you 00:15:18.880 --> 00:15:19.509 align:start position:0% to communicate with whatever system you want. 00:15:19.509 --> 00:15:19.519 align:start position:0% want. 00:15:19.519 --> 00:15:21.509 align:start position:0% want. And<00:15:19.680> and<00:15:19.920> the<00:15:20.079> benefit<00:15:20.320> there<00:15:20.560> is<00:15:20.720> because<00:15:21.440> you 00:15:21.509 --> 00:15:21.519 align:start position:0% And and the benefit there is because you 00:15:21.519 --> 00:15:23.189 align:start position:0% And and the benefit there is because you know<00:15:21.600> when<00:15:21.839> you<00:15:21.920> think<00:15:22.000> about<00:15:22.160> it, 00:15:23.189 --> 00:15:23.199 align:start position:0% know when you think about it, 00:15:23.199 --> 00:15:24.949 align:start position:0% know when you think about it, if<00:15:23.440> you're<00:15:23.600> using<00:15:23.920> ductb<00:15:24.399> locally, 00:15:24.949 --> 00:15:24.959 align:start position:0% if you're using ductb locally, 00:15:24.959 --> 00:15:25.750 align:start position:0% if you're using ductb locally, right, 00:15:25.750 --> 00:15:25.760 align:start position:0% right, 00:15:25.760 --> 00:15:27.110 align:start position:0% right, to<00:15:26.000> do<00:15:26.079> your<00:15:26.320> analytics<00:15:26.800> stuff, 00:15:27.110 --> 00:15:27.120 align:start position:0% to do your analytics stuff, 00:15:27.120 --> 00:15:27.590 align:start position:0% to do your analytics stuff, right? 00:15:27.590 --> 00:15:27.600 align:start position:0% right? 00:15:27.600 --> 00:15:28.949 align:start position:0% right? And<00:15:27.760> then<00:15:27.920> there's<00:15:28.160> plenty<00:15:28.399> of<00:15:28.560> extensions 00:15:28.949 --> 00:15:28.959 align:start position:0% And then there's plenty of extensions 00:15:28.959 --> 00:15:31.030 align:start position:0% And then there's plenty of extensions people<00:15:29.199> have<00:15:29.440> for<00:15:30.000> letting<00:15:30.399> DuckDB 00:15:31.030 --> 00:15:31.040 align:start position:0% people have for letting DuckDB 00:15:31.040 --> 00:15:33.110 align:start position:0% people have for letting DuckDB communicate<00:15:31.440> with<00:15:31.680> external<00:15:32.240> systems<00:15:32.720> in 00:15:33.110 --> 00:15:33.120 align:start position:0% communicate with external systems in 00:15:33.120 --> 00:15:34.470 align:start position:0% communicate with external systems in efficient<00:15:33.600> ways 00:15:34.470 --> 00:15:34.480 align:start position:0% efficient ways 00:15:34.480 --> 00:15:36.470 align:start position:0% efficient ways to<00:15:34.639> talk<00:15:34.880> to,<00:15:35.199> you<00:15:35.360> know,<00:15:35.440> to<00:15:35.680> fetch<00:15:35.920> the<00:15:36.079> data, 00:15:36.470 --> 00:15:36.480 align:start position:0% to talk to, you know, to fetch the data, 00:15:36.480 --> 00:15:38.389 align:start position:0% to talk to, you know, to fetch the data, right?<00:15:37.199> And<00:15:37.600> and<00:15:37.760> that's<00:15:37.920> the<00:15:38.079> thing, 00:15:38.389 --> 00:15:38.399 align:start position:0% right? And and that's the thing, 00:15:38.399 --> 00:15:40.470 align:start position:0% right? And and that's the thing, analytics,<00:15:39.120> the<00:15:39.360> analytical<00:15:39.839> part,<00:15:40.079> this<00:15:40.240> the 00:15:40.470 --> 00:15:40.480 align:start position:0% analytics, the analytical part, this the 00:15:40.480 --> 00:15:42.069 align:start position:0% analytics, the analytical part, this the SQL,<00:15:40.959> that's<00:15:41.199> the<00:15:41.279> easy<00:15:41.519> part. 00:15:42.069 --> 00:15:42.079 align:start position:0% SQL, that's the easy part. 00:15:42.079 --> 00:15:43.829 align:start position:0% SQL, that's the easy part. The<00:15:42.160> hard<00:15:42.320> part<00:15:42.480> is<00:15:42.720> getting<00:15:42.880> the<00:15:43.120> data<00:15:43.600> over 00:15:43.829 --> 00:15:43.839 align:start position:0% The hard part is getting the data over 00:15:43.839 --> 00:15:44.310 align:start position:0% The hard part is getting the data over here, 00:15:44.310 --> 00:15:44.320 align:start position:0% here, 00:15:44.320 --> 00:15:44.790 align:start position:0% here, right? 00:15:44.790 --> 00:15:44.800 align:start position:0% right? 00:15:44.800 --> 00:15:48.870 align:start position:0% right? And<00:15:45.120> so<00:15:46.079> you<00:15:46.320> need<00:15:46.480> to<00:15:46.639> have<00:15:46.720> an<00:15:46.959> efficient<00:15:47.440> way 00:15:48.870 --> 00:15:48.880 align:start position:0% And so you need to have an efficient way 00:15:48.880 --> 00:15:50.629 align:start position:0% And so you need to have an efficient way to<00:15:49.120> actually<00:15:49.519> retrieve<00:15:49.920> that<00:15:50.160> data. 00:15:50.629 --> 00:15:50.639 align:start position:0% to actually retrieve that data. 00:15:50.639 --> 00:15:51.030 align:start position:0% to actually retrieve that data. Mhm. 00:15:51.030 --> 00:15:51.040 align:start position:0% Mhm. 00:15:51.040 --> 00:15:52.389 align:start position:0% Mhm. Whether<00:15:51.360> you're<00:15:51.519> going<00:15:51.600> through<00:15:51.839> ductb<00:15:52.320> or 00:15:52.389 --> 00:15:52.399 align:start position:0% Whether you're going through ductb or 00:15:52.399 --> 00:15:54.069 align:start position:0% Whether you're going through ductb or you're<00:15:52.560> going<00:15:52.720> through<00:15:52.959> a<00:15:53.279> script<00:15:53.519> yourself. 00:15:54.069 --> 00:15:54.079 align:start position:0% you're going through a script yourself. 00:15:54.079 --> 00:15:57.189 align:start position:0% you're going through a script yourself. Mhm.<00:15:54.560> And<00:15:54.880> so<00:15:55.440> the<00:15:55.759> ADBC<00:15:56.240> extension<00:15:56.560> of<00:15:56.880> DDB 00:15:57.189 --> 00:15:57.199 align:start position:0% Mhm. And so the ADBC extension of DDB 00:15:57.199 --> 00:15:59.590 align:start position:0% Mhm. And so the ADBC extension of DDB lets<00:15:57.360> you<00:15:57.519> be<00:15:57.680> able<00:15:57.759> to<00:15:58.000> leverage<00:15:58.880> that<00:15:59.120> column 00:15:59.590 --> 00:15:59.600 align:start position:0% lets you be able to leverage that column 00:15:59.600 --> 00:16:03.189 align:start position:0% lets you be able to leverage that column oriented<00:16:00.240> zero<00:16:00.639> copy<00:16:01.680> ADBC<00:16:02.480> arrow<00:16:02.959> based 00:16:03.189 --> 00:16:03.199 align:start position:0% oriented zero copy ADBC arrow based 00:16:03.199 --> 00:16:04.310 align:start position:0% oriented zero copy ADBC arrow based interaction 00:16:04.310 --> 00:16:04.320 align:start position:0% interaction 00:16:04.320 --> 00:16:07.509 align:start position:0% interaction with<00:16:04.880> any<00:16:05.279> ADBC<00:16:05.839> driver<00:16:06.160> you<00:16:06.399> want.<00:16:07.120> You<00:16:07.360> can 00:16:07.509 --> 00:16:07.519 align:start position:0% with any ADBC driver you want. You can 00:16:07.519 --> 00:16:10.389 align:start position:0% with any ADBC driver you want. You can attach<00:16:08.079> to<00:16:08.320> it.<00:16:08.639> You<00:16:08.800> can<00:16:09.680> send<00:16:09.839> the<00:16:10.079> queries 00:16:10.389 --> 00:16:10.399 align:start position:0% attach to it. You can send the queries 00:16:10.399 --> 00:16:12.550 align:start position:0% attach to it. You can send the queries and<00:16:10.560> pull<00:16:10.720> the<00:16:10.880> results<00:16:11.120> set<00:16:11.360> in<00:16:11.680> and<00:16:12.000> duct<00:16:12.240> DB 00:16:12.550 --> 00:16:12.560 align:start position:0% and pull the results set in and duct DB 00:16:12.560 --> 00:16:15.110 align:start position:0% and pull the results set in and duct DB natively<00:16:12.959> supports<00:16:13.279> arrow<00:16:13.839> anyways<00:16:14.639> and<00:16:14.880> so 00:16:15.110 --> 00:16:15.120 align:start position:0% natively supports arrow anyways and so 00:16:15.120 --> 00:16:18.629 align:start position:0% natively supports arrow anyways and so everything<00:16:15.440> is<00:16:16.079> is<00:16:16.720> exceptionally<00:16:17.519> efficient 00:16:18.629 --> 00:16:18.639 align:start position:0% everything is is exceptionally efficient 00:16:18.639 --> 00:16:23.189 align:start position:0% everything is is exceptionally efficient and<00:16:19.680> super<00:16:20.160> zero<00:16:20.560> copy<00:16:21.759> and<00:16:22.560> fast. 00:16:23.189 --> 00:16:23.199 align:start position:0% and super zero copy and fast. 00:16:23.199 --> 00:16:25.189 align:start position:0% and super zero copy and fast. Yes.<00:16:23.440> And<00:16:23.680> duct<00:16:24.000> DB<00:16:24.320> makes<00:16:24.480> it<00:16:24.639> super<00:16:24.800> easy<00:16:24.959> to 00:16:25.189 --> 00:16:25.199 align:start position:0% Yes. And duct DB makes it super easy to 00:16:25.199 --> 00:16:27.269 align:start position:0% Yes. And duct DB makes it super easy to load<00:16:25.440> extensions,<00:16:26.160> right?<00:16:26.399> So<00:16:26.639> this<00:16:26.800> is<00:16:26.959> all 00:16:27.269 --> 00:16:27.279 align:start position:0% load extensions, right? So this is all 00:16:27.279 --> 00:16:29.269 align:start position:0% load extensions, right? So this is all becoming<00:16:28.240> very<00:16:28.639> natural. 00:16:29.269 --> 00:16:29.279 align:start position:0% becoming very natural. 00:16:29.279 --> 00:16:30.310 align:start position:0% becoming very natural. Exactly.<00:16:29.600> I<00:16:29.759> mean<00:16:29.839> it's<00:16:30.000> a<00:16:30.079> community 00:16:30.310 --> 00:16:30.320 align:start position:0% Exactly. I mean it's a community 00:16:30.320 --> 00:16:31.910 align:start position:0% Exactly. I mean it's a community extension.<00:16:30.639> You<00:16:30.800> do,<00:16:31.040> you<00:16:31.120> know,<00:16:31.440> install 00:16:31.910 --> 00:16:31.920 align:start position:0% extension. You do, you know, install 00:16:31.920 --> 00:16:33.509 align:start position:0% extension. You do, you know, install ADBC<00:16:32.399> from<00:16:32.639> community.<00:16:33.120> That's<00:16:33.279> right. 00:16:33.509 --> 00:16:33.519 align:start position:0% ADBC from community. That's right. 00:16:33.519 --> 00:16:34.949 align:start position:0% ADBC from community. That's right. Done.<00:16:34.079> ADBC.<00:16:34.639> Done. 00:16:34.949 --> 00:16:34.959 align:start position:0% Done. ADBC. Done. 00:16:34.959 --> 00:16:35.670 align:start position:0% Done. ADBC. Done. That's<00:16:35.120> right. 00:16:35.670 --> 00:16:35.680 align:start position:0% That's right. 00:16:35.680 --> 00:16:38.550 align:start position:0% That's right. And<00:16:35.839> and<00:16:36.160> then<00:16:36.639> you<00:16:36.800> know<00:16:37.600> and<00:16:37.759> then<00:16:37.920> you<00:16:38.160> can 00:16:38.550 --> 00:16:38.560 align:start position:0% And and then you know and then you can 00:16:38.560 --> 00:16:43.269 align:start position:0% And and then you know and then you can easily<00:16:39.440> mix<00:16:40.320> local<00:16:40.720> data<00:16:41.600> with<00:16:42.320> your<00:16:42.880> remote 00:16:43.269 --> 00:16:43.279 align:start position:0% easily mix local data with your remote 00:16:43.279 --> 00:16:44.069 align:start position:0% easily mix local data with your remote systems. 00:16:44.069 --> 00:16:44.079 align:start position:0% systems. 00:16:44.079 --> 00:16:44.790 align:start position:0% systems. Mhm. 00:16:44.790 --> 00:16:44.800 align:start position:0% Mhm. 00:16:44.800 --> 00:16:46.389 align:start position:0% Mhm. Efficiently. 00:16:46.389 --> 00:16:46.399 align:start position:0% Efficiently. 00:16:46.399 --> 00:16:48.389 align:start position:0% Efficiently. Right.<00:16:46.800> So<00:16:47.120> and<00:16:47.360> then<00:16:47.600> you<00:16:47.839> also<00:16:48.079> mentioned 00:16:48.389 --> 00:16:48.399 align:start position:0% Right. So and then you also mentioned 00:16:48.399 --> 00:16:49.990 align:start position:0% Right. So and then you also mentioned that<00:16:48.480> you're<00:16:48.639> going<00:16:48.880> to<00:16:49.040> DBT<00:16:49.519> summit<00:16:49.839> and 00:16:49.990 --> 00:16:50.000 align:start position:0% that you're going to DBT summit and 00:16:50.000 --> 00:16:52.790 align:start position:0% that you're going to DBT summit and again<00:16:50.240> from<00:16:50.720> you<00:16:51.120> learn<00:16:51.360> that<00:16:51.519> DBT<00:16:52.079> is<00:16:52.399> basing 00:16:52.790 --> 00:16:52.800 align:start position:0% again from you learn that DBT is basing 00:16:52.800 --> 00:16:55.269 align:start position:0% again from you learn that DBT is basing its<00:16:53.600> driver<00:16:54.000> strategy<00:16:54.480> on<00:16:54.720> ADBC 00:16:55.269 --> 00:16:55.279 align:start position:0% its driver strategy on ADBC 00:16:55.279 --> 00:16:57.269 align:start position:0% its driver strategy on ADBC DBT<00:16:55.680> core<00:16:56.000> v2 00:16:57.269 --> 00:16:57.279 align:start position:0% DBT core v2 00:16:57.279 --> 00:16:59.110 align:start position:0% DBT core v2 uh<00:16:57.360> their<00:16:57.600> data<00:16:57.920> connectors<00:16:58.320> and<00:16:58.560> their<00:16:58.880> and 00:16:59.110 --> 00:16:59.120 align:start position:0% uh their data connectors and their and 00:16:59.120 --> 00:17:00.389 align:start position:0% uh their data connectors and their and their<00:16:59.360> their<00:16:59.519> database<00:16:59.920> connectors<00:17:00.240> and 00:17:00.389 --> 00:17:00.399 align:start position:0% their their database connectors and 00:17:00.399 --> 00:17:02.870 align:start position:0% their their database connectors and their<00:17:01.040> uh<00:17:01.199> connect<00:17:01.440> adapters<00:17:02.079> are<00:17:02.320> built<00:17:02.560> on 00:17:02.870 --> 00:17:02.880 align:start position:0% their uh connect adapters are built on 00:17:02.880 --> 00:17:04.949 align:start position:0% their uh connect adapters are built on ADBC<00:17:03.519> for<00:17:03.680> their<00:17:03.920> all<00:17:04.079> their<00:17:04.240> connections<00:17:04.959> uh 00:17:04.949 --> 00:17:04.959 align:start position:0% ADBC for their all their connections uh 00:17:04.959 --> 00:17:07.750 align:start position:0% ADBC for their all their connections uh and<00:17:05.199> DBT<00:17:05.600> fusion<00:17:05.919> is<00:17:06.160> also<00:17:06.640> using<00:17:06.959> ADBC 00:17:07.750 --> 00:17:07.760 align:start position:0% and DBT fusion is also using ADBC 00:17:07.760 --> 00:17:10.150 align:start position:0% and DBT fusion is also using ADBC right<00:17:08.400> so<00:17:08.720> what<00:17:09.199> I'm<00:17:09.439> I'm<00:17:09.679> just<00:17:09.839> thinking 00:17:10.150 --> 00:17:10.160 align:start position:0% right so what I'm I'm just thinking 00:17:10.160 --> 00:17:14.150 align:start position:0% right so what I'm I'm just thinking right<00:17:10.400> like<00:17:11.280> uh<00:17:11.679> we<00:17:12.000> want<00:17:12.480> AI<00:17:12.959> infra<00:17:13.520> it's<00:17:13.760> it's 00:17:14.150 --> 00:17:14.160 align:start position:0% right like uh we want AI infra it's it's 00:17:14.160 --> 00:17:16.949 align:start position:0% right like uh we want AI infra it's it's about<00:17:14.480> data<00:17:14.959> AI<00:17:15.199> agents<00:17:15.679> are<00:17:15.839> only<00:17:16.000> as<00:17:16.480> as<00:17:16.799> the 00:17:16.949 --> 00:17:16.959 align:start position:0% about data AI agents are only as as the 00:17:16.959 --> 00:17:18.150 align:start position:0% about data AI agents are only as as the data<00:17:17.199> that<00:17:17.360> you<00:17:17.520> feed<00:17:17.679> to<00:17:17.839> them 00:17:18.150 --> 00:17:18.160 align:start position:0% data that you feed to them 00:17:18.160 --> 00:17:19.510 align:start position:0% data that you feed to them and<00:17:18.400> only<00:17:18.559> as<00:17:18.799> fast<00:17:18.959> as<00:17:19.039> you<00:17:19.199> can<00:17:19.280> feed<00:17:19.360> it<00:17:19.439> to 00:17:19.510 --> 00:17:19.520 align:start position:0% and only as fast as you can feed it to 00:17:19.520 --> 00:17:19.750 align:start position:0% and only as fast as you can feed it to them 00:17:19.750 --> 00:17:19.760 align:start position:0% them 00:17:19.760 --> 00:17:21.829 align:start position:0% them and<00:17:20.240> as<00:17:20.400> fast<00:17:20.559> as<00:17:20.720> you<00:17:20.959> and<00:17:21.360> everybody 00:17:21.829 --> 00:17:21.839 align:start position:0% and as fast as you and everybody 00:17:21.839 --> 00:17:23.909 align:start position:0% and as fast as you and everybody everybody<00:17:22.240> wants<00:17:22.480> to<00:17:22.640> them<00:17:22.799> to<00:17:22.959> be<00:17:23.360> you<00:17:23.520> know 00:17:23.909 --> 00:17:23.919 align:start position:0% everybody wants to them to be you know 00:17:23.919 --> 00:17:26.870 align:start position:0% everybody wants to them to be you know fast<00:17:24.319> and<00:17:24.480> and<00:17:24.880> correct<00:17:25.280> and<00:17:25.600> you<00:17:25.760> know<00:17:26.319> feed 00:17:26.870 --> 00:17:26.880 align:start position:0% fast and and correct and you know feed 00:17:26.880 --> 00:17:28.950 align:start position:0% fast and and correct and you know feed you<00:17:26.959> know<00:17:27.120> a<00:17:27.280> lot<00:17:27.360> of<00:17:27.520> data<00:17:27.679> to<00:17:27.839> them<00:17:28.240> and<00:17:28.400> so<00:17:28.559> it 00:17:28.950 --> 00:17:28.960 align:start position:0% you know a lot of data to them and so it 00:17:28.960 --> 00:17:32.470 align:start position:0% you know a lot of data to them and so it seems<00:17:29.280> to<00:17:29.520> me<00:17:30.240> that<00:17:31.200> uh<00:17:31.679> you<00:17:31.840> know<00:17:31.919> if<00:17:32.160> you're<00:17:32.320> a 00:17:32.470 --> 00:17:32.480 align:start position:0% seems to me that uh you know if you're a 00:17:32.480 --> 00:17:35.750 align:start position:0% seems to me that uh you know if you're a good<00:17:32.640> engineer<00:17:33.280> building<00:17:34.400> uh<00:17:34.720> this<00:17:35.200> AI<00:17:35.600> in 00:17:35.750 --> 00:17:35.760 align:start position:0% good engineer building uh this AI in 00:17:35.760 --> 00:17:37.510 align:start position:0% good engineer building uh this AI in front<00:17:35.840> of<00:17:35.919> the<00:17:36.080> future<00:17:36.640> so<00:17:36.880> you<00:17:37.039> need<00:17:37.120> to<00:17:37.280> focus 00:17:37.510 --> 00:17:37.520 align:start position:0% front of the future so you need to focus 00:17:37.520 --> 00:17:39.990 align:start position:0% front of the future so you need to focus on<00:17:37.679> the<00:17:37.840> set<00:17:38.000> of<00:17:38.160> technologies<00:17:39.200> so<00:17:39.440> what<00:17:39.600> what 00:17:39.990 --> 00:17:40.000 align:start position:0% on the set of technologies so what what 00:17:40.000 --> 00:17:41.430 align:start position:0% on the set of technologies so what what would<00:17:40.240> would<00:17:40.400> be<00:17:40.559> your<00:17:40.720> advice<00:17:40.960> to<00:17:41.200> like 00:17:41.430 --> 00:17:41.440 align:start position:0% would would be your advice to like 00:17:41.440 --> 00:17:42.950 align:start position:0% would would be your advice to like companies<00:17:41.840> implementing<00:17:42.400> distributed 00:17:42.950 --> 00:17:42.960 align:start position:0% companies implementing distributed 00:17:42.960 --> 00:17:45.270 align:start position:0% companies implementing distributed systems<00:17:43.840> uh<00:17:43.919> for<00:17:44.160> AI<00:17:44.480> so<00:17:44.720> I<00:17:44.880> think<00:17:44.960> we 00:17:45.270 --> 00:17:45.280 align:start position:0% systems uh for AI so I think we 00:17:45.280 --> 00:17:47.669 align:start position:0% systems uh for AI so I think we mentioned<00:17:45.520> some<00:17:45.760> of<00:17:46.000> pieces<00:17:46.640> like<00:17:46.960> you<00:17:47.120> know 00:17:47.669 --> 00:17:47.679 align:start position:0% mentioned some of pieces like you know 00:17:47.679 --> 00:17:50.070 align:start position:0% mentioned some of pieces like you know data<00:17:48.000> fusion<00:17:48.480> like<00:17:49.039> how<00:17:49.280> can<00:17:49.440> we<00:17:49.600> get<00:17:49.760> to<00:17:49.919> the 00:17:50.070 --> 00:17:50.080 align:start position:0% data fusion like how can we get to the 00:17:50.080 --> 00:17:52.470 align:start position:0% data fusion like how can we get to the point<00:17:50.320> where<00:17:50.720> agents<00:17:51.200> exchange<00:17:51.679> data<00:17:52.240> through 00:17:52.470 --> 00:17:52.480 align:start position:0% point where agents exchange data through 00:17:52.480 --> 00:17:55.430 align:start position:0% point where agents exchange data through a<00:17:52.640> fast<00:17:52.960> bus<00:17:53.200> instead<00:17:53.520> of<00:17:54.240> like<00:17:54.720> derializing 00:17:55.430 --> 00:17:55.440 align:start position:0% a fast bus instead of like derializing 00:17:55.440 --> 00:17:57.350 align:start position:0% a fast bus instead of like derializing things<00:17:55.679> into<00:17:55.919> JSON<00:17:56.480> and<00:17:56.640> then 00:17:57.350 --> 00:17:57.360 align:start position:0% things into JSON and then 00:17:57.360 --> 00:17:59.190 align:start position:0% things into JSON and then I<00:17:57.440> mean<00:17:57.520> because<00:17:57.679> MCP<00:17:58.080> is<00:17:58.240> all<00:17:58.400> built<00:17:58.480> on<00:17:58.640> JSON 00:17:59.190 --> 00:17:59.200 align:start position:0% I mean because MCP is all built on JSON 00:17:59.200 --> 00:18:01.270 align:start position:0% I mean because MCP is all built on JSON right<00:17:59.520> like<00:17:59.760> why<00:17:59.919> would<00:18:00.080> we<00:18:00.240> spit<00:18:00.480> out<00:18:00.720> JSON 00:18:01.270 --> 00:18:01.280 align:start position:0% right like why would we spit out JSON 00:18:01.280 --> 00:18:03.270 align:start position:0% right like why would we spit out JSON feed<00:18:01.520> it<00:18:01.679> to<00:18:01.919> something<00:18:02.559> deserialize<00:18:03.200> and 00:18:03.270 --> 00:18:03.280 align:start position:0% feed it to something deserialize and 00:18:03.280 --> 00:18:04.230 align:start position:0% feed it to something deserialize and serialize<00:18:03.679> it<00:18:03.760> again 00:18:04.230 --> 00:18:04.240 align:start position:0% serialize it again 00:18:04.240 --> 00:18:05.830 align:start position:0% serialize it again because<00:18:04.480> people<00:18:04.640> like<00:18:04.880> human<00:18:05.120> readable<00:18:05.600> the 00:18:05.830 --> 00:18:05.840 align:start position:0% because people like human readable the 00:18:05.840 --> 00:18:07.270 align:start position:0% because people like human readable the human<00:18:06.080> readable<00:18:06.400> aspect<00:18:06.640> of<00:18:06.799> it 00:18:07.270 --> 00:18:07.280 align:start position:0% human readable aspect of it 00:18:07.280 --> 00:18:08.630 align:start position:0% human readable aspect of it you<00:18:07.600> the<00:18:07.760> other<00:18:07.919> I<00:18:08.080> mean<00:18:08.160> the<00:18:08.240> thing<00:18:08.320> is<00:18:08.480> like 00:18:08.630 --> 00:18:08.640 align:start position:0% you the other I mean the thing is like 00:18:08.640 --> 00:18:09.990 align:start position:0% you the other I mean the thing is like people<00:18:08.799> will<00:18:08.960> talk<00:18:09.360> people<00:18:09.520> will<00:18:09.679> talk<00:18:09.840> about 00:18:09.990 --> 00:18:10.000 align:start position:0% people will talk people will talk about 00:18:10.000 --> 00:18:10.789 align:start position:0% people will talk people will talk about how 00:18:10.789 --> 00:18:10.799 align:start position:0% how 00:18:10.799 --> 00:18:12.710 align:start position:0% how you<00:18:10.960> know<00:18:11.280> you<00:18:11.520> can't<00:18:11.840> you<00:18:11.919> know<00:18:12.080> you<00:18:12.320> can't 00:18:12.710 --> 00:18:12.720 align:start position:0% you know you can't you know you can't 00:18:12.720 --> 00:18:15.110 align:start position:0% you know you can't you know you can't efficiently<00:18:13.360> send<00:18:14.240> huge<00:18:14.559> amounts<00:18:14.799> of<00:18:14.960> data 00:18:15.110 --> 00:18:15.120 align:start position:0% efficiently send huge amounts of data 00:18:15.120 --> 00:18:16.230 align:start position:0% efficiently send huge amounts of data through<00:18:15.280> MCP 00:18:16.230 --> 00:18:16.240 align:start position:0% through MCP 00:18:16.240 --> 00:18:17.270 align:start position:0% through MCP Right? 00:18:17.270 --> 00:18:17.280 align:start position:0% Right? 00:18:17.280 --> 00:18:18.549 align:start position:0% Right? But<00:18:17.440> the<00:18:17.679> reason<00:18:17.840> why<00:18:18.000> you<00:18:18.080> can't<00:18:18.240> just<00:18:18.480> cuz 00:18:18.549 --> 00:18:18.559 align:start position:0% But the reason why you can't just cuz 00:18:18.559 --> 00:18:19.270 align:start position:0% But the reason why you can't just cuz it's<00:18:18.720> JSON, 00:18:19.270 --> 00:18:19.280 align:start position:0% it's JSON, 00:18:19.280 --> 00:18:19.909 align:start position:0% it's JSON, right? 00:18:19.909 --> 00:18:19.919 align:start position:0% right? 00:18:19.919 --> 00:18:21.270 align:start position:0% right? You<00:18:20.000> know,<00:18:20.160> if<00:18:20.240> you<00:18:20.400> if<00:18:20.559> it<00:18:20.720> was<00:18:20.799> a<00:18:20.960> binary 00:18:21.270 --> 00:18:21.280 align:start position:0% You know, if you if it was a binary 00:18:21.280 --> 00:18:21.990 align:start position:0% You know, if you if it was a binary protocol, 00:18:21.990 --> 00:18:22.000 align:start position:0% protocol, 00:18:22.000 --> 00:18:22.310 align:start position:0% protocol, right, 00:18:22.310 --> 00:18:22.320 align:start position:0% right, 00:18:22.320 --> 00:18:23.510 align:start position:0% right, you<00:18:22.480> could<00:18:22.559> do<00:18:22.720> it.<00:18:22.880> It<00:18:23.039> could<00:18:23.120> be<00:18:23.200> much<00:18:23.440> more 00:18:23.510 --> 00:18:23.520 align:start position:0% you could do it. It could be much more 00:18:23.520 --> 00:18:24.150 align:start position:0% you could do it. It could be much more efficient, 00:18:24.150 --> 00:18:24.160 align:start position:0% efficient, 00:18:24.160 --> 00:18:24.470 align:start position:0% efficient, right? 00:18:24.470 --> 00:18:24.480 align:start position:0% right? 00:18:24.480 --> 00:18:27.110 align:start position:0% right? And<00:18:24.640> but<00:18:24.880> MCP<00:18:25.280> is<00:18:25.440> JSON.<00:18:25.840> So<00:18:26.000> like<00:18:26.480> that<00:18:26.880> we 00:18:27.110 --> 00:18:27.120 align:start position:0% And but MCP is JSON. So like that we 00:18:27.120 --> 00:18:29.990 align:start position:0% And but MCP is JSON. So like that we need<00:18:27.280> a<00:18:27.600> binary<00:18:28.080> protocol<00:18:29.039> for<00:18:29.600> agent 00:18:29.990 --> 00:18:30.000 align:start position:0% need a binary protocol for agent 00:18:30.000 --> 00:18:30.789 align:start position:0% need a binary protocol for agent communication<00:18:30.320> like<00:18:30.480> that. 00:18:30.789 --> 00:18:30.799 align:start position:0% communication like that. 00:18:30.799 --> 00:18:31.750 align:start position:0% communication like that. That's<00:18:30.960> right.<00:18:31.280> That's<00:18:31.520> right. 00:18:31.750 --> 00:18:31.760 align:start position:0% That's right. That's right. 00:18:31.760 --> 00:18:32.789 align:start position:0% That's right. That's right. You<00:18:31.840> know,<00:18:31.919> and<00:18:32.080> and<00:18:32.240> that's<00:18:32.480> really<00:18:32.640> going<00:18:32.720> to 00:18:32.789 --> 00:18:32.799 align:start position:0% You know, and and that's really going to 00:18:32.799 --> 00:18:34.150 align:start position:0% You know, and and that's really going to be<00:18:32.960> the<00:18:33.120> next<00:18:33.280> big<00:18:33.440> thing<00:18:33.600> I<00:18:33.840> think<00:18:33.919> is<00:18:34.080> going 00:18:34.150 --> 00:18:34.160 align:start position:0% be the next big thing I think is going 00:18:34.160 --> 00:18:36.470 align:start position:0% be the next big thing I think is going to<00:18:34.240> be<00:18:34.880> someone<00:18:35.440> pump,<00:18:35.919> you<00:18:36.000> know, 00:18:36.470 --> 00:18:36.480 align:start position:0% to be someone pump, you know, 00:18:36.480 --> 00:18:40.230 align:start position:0% to be someone pump, you know, standardizing<00:18:37.919> a<00:18:38.240> binary<00:18:38.720> protocol 00:18:40.230 --> 00:18:40.240 align:start position:0% standardizing a binary protocol 00:18:40.240 --> 00:18:43.270 align:start position:0% standardizing a binary protocol for<00:18:41.440> what<00:18:41.679> MCP<00:18:42.240> does,<00:18:42.559> right?<00:18:42.880> But<00:18:43.039> the<00:18:43.200> other 00:18:43.270 --> 00:18:43.280 align:start position:0% for what MCP does, right? But the other 00:18:43.280 --> 00:18:44.549 align:start position:0% for what MCP does, right? But the other big<00:18:43.440> thing<00:18:43.520> is<00:18:43.679> also<00:18:43.919> getting<00:18:44.160> more<00:18:44.240> and<00:18:44.400> more 00:18:44.549 --> 00:18:44.559 align:start position:0% big thing is also getting more and more 00:18:44.559 --> 00:18:46.549 align:start position:0% big thing is also getting more and more of the<00:18:44.799> vendors<00:18:45.679> of<00:18:45.760> your<00:18:45.919> database<00:18:46.320> vendors, 00:18:46.549 --> 00:18:46.559 align:start position:0% of the vendors of your database vendors, 00:18:46.559 --> 00:18:48.150 align:start position:0% of the vendors of your database vendors, your<00:18:46.720> data<00:18:46.880> source<00:18:47.120> vendors<00:18:47.600> to<00:18:47.919> actually 00:18:48.150 --> 00:18:48.160 align:start position:0% your data source vendors to actually 00:18:48.160 --> 00:18:50.549 align:start position:0% your data source vendors to actually support<00:18:49.039> returning<00:18:49.679> arrow<00:18:50.080> data, 00:18:50.549 --> 00:18:50.559 align:start position:0% support returning arrow data, 00:18:50.559 --> 00:18:51.190 align:start position:0% support returning arrow data, right? 00:18:51.190 --> 00:18:51.200 align:start position:0% right? 00:18:51.200 --> 00:18:53.029 align:start position:0% right? You<00:18:51.280> know,<00:18:51.440> you<00:18:51.600> have<00:18:51.679> so<00:18:51.840> many<00:18:52.080> systems 00:18:53.029 --> 00:18:53.039 align:start position:0% You know, you have so many systems 00:18:53.039 --> 00:18:54.230 align:start position:0% You know, you have so many systems send<00:18:53.280> us<00:18:53.440> columnar<00:18:53.919> data. 00:18:54.230 --> 00:18:54.240 align:start position:0% send us columnar data. 00:18:54.240 --> 00:18:55.270 align:start position:0% send us columnar data. You<00:18:54.400> have<00:18:54.480> so<00:18:54.559> many<00:18:54.720> you<00:18:54.880> have<00:18:54.960> so<00:18:55.120> many 00:18:55.270 --> 00:18:55.280 align:start position:0% You have so many you have so many 00:18:55.280 --> 00:18:57.430 align:start position:0% You have so many you have so many systems<00:18:55.520> that<00:18:55.679> are<00:18:55.760> columnar 00:18:57.430 --> 00:18:57.440 align:start position:0% systems that are columnar 00:18:57.440 --> 00:18:58.390 align:start position:0% systems that are columnar data<00:18:57.840> systems. 00:18:58.390 --> 00:18:58.400 align:start position:0% data systems. 00:18:58.400 --> 00:18:58.789 align:start position:0% data systems. Yes. 00:18:58.789 --> 00:18:58.799 align:start position:0% Yes. 00:18:58.799 --> 00:19:00.710 align:start position:0% Yes. That<00:18:59.039> only<00:18:59.440> return<00:19:00.000> JSON, 00:19:00.710 --> 00:19:00.720 align:start position:0% That only return JSON, 00:19:00.720 --> 00:19:02.230 align:start position:0% That only return JSON, right? 00:19:02.230 --> 00:19:02.240 align:start position:0% right? 00:19:02.240 --> 00:19:05.430 align:start position:0% right? Trino<00:19:02.799> Presto,<00:19:04.160> you<00:19:04.320> know,<00:19:04.880> systems<00:19:05.200> that 00:19:05.430 --> 00:19:05.440 align:start position:0% Trino Presto, you know, systems that 00:19:05.440 --> 00:19:08.150 align:start position:0% Trino Presto, you know, systems that only<00:19:05.679> return<00:19:06.160> row<00:19:06.400> oriented<00:19:07.600> data, 00:19:08.150 --> 00:19:08.160 align:start position:0% only return row oriented data, 00:19:08.160 --> 00:19:08.390 align:start position:0% only return row oriented data, right, 00:19:08.390 --> 00:19:08.400 align:start position:0% right, 00:19:08.400 --> 00:19:09.990 align:start position:0% right, from<00:19:08.640> an<00:19:08.799> analytical<00:19:09.360> column<00:19:09.600> oriented 00:19:09.990 --> 00:19:10.000 align:start position:0% from an analytical column oriented 00:19:10.000 --> 00:19:10.630 align:start position:0% from an analytical column oriented comput<00:19:10.240> engine, 00:19:10.630 --> 00:19:10.640 align:start position:0% comput engine, 00:19:10.640 --> 00:19:13.830 align:start position:0% comput engine, right?<00:19:11.360> and<00:19:11.600> and<00:19:11.840> you<00:19:12.080> know<00:19:12.559> uh<00:19:12.880> uh<00:19:13.120> uh<00:19:13.360> uh<00:19:13.600> uh 00:19:13.830 --> 00:19:13.840 align:start position:0% right? and and you know uh uh uh uh uh 00:19:13.840 --> 00:19:16.150 align:start position:0% right? and and you know uh uh uh uh uh uh<00:19:14.320> you<00:19:14.480> know<00:19:14.559> and<00:19:14.720> and<00:19:15.039> so<00:19:15.200> like<00:19:15.679> it<00:19:15.840> would<00:19:16.000> be 00:19:16.150 --> 00:19:16.160 align:start position:0% uh you know and and so like it would be 00:19:16.160 --> 00:19:18.630 align:start position:0% uh you know and and so like it would be great<00:19:16.400> to<00:19:16.559> see<00:19:16.799> more<00:19:17.120> vendors<00:19:18.080> and<00:19:18.320> more 00:19:18.630 --> 00:19:18.640 align:start position:0% great to see more vendors and more 00:19:18.640 --> 00:19:20.710 align:start position:0% great to see more vendors and more systems<00:19:19.039> and<00:19:19.280> more<00:19:20.000> applica<00:19:20.480> more 00:19:20.710 --> 00:19:20.720 align:start position:0% systems and more applica more 00:19:20.720 --> 00:19:24.070 align:start position:0% systems and more applica more applications<00:19:22.000> support<00:19:22.799> arrow<00:19:23.200> in<00:19:23.520> and<00:19:23.760> arrow 00:19:24.070 --> 00:19:24.080 align:start position:0% applications support arrow in and arrow 00:19:24.080 --> 00:19:24.549 align:start position:0% applications support arrow in and arrow out. 00:19:24.549 --> 00:19:24.559 align:start position:0% out. 00:19:24.559 --> 00:19:25.190 align:start position:0% out. Yeah,<00:19:24.799> that's<00:19:24.960> right. 00:19:25.190 --> 00:19:25.200 align:start position:0% Yeah, that's right. 00:19:25.200 --> 00:19:26.870 align:start position:0% Yeah, that's right. And<00:19:25.360> even<00:19:25.600> many<00:19:25.840> of<00:19:26.000> the<00:19:26.160> systems<00:19:26.480> that 00:19:26.870 --> 00:19:26.880 align:start position:0% And even many of the systems that 00:19:26.880 --> 00:19:29.909 align:start position:0% And even many of the systems that support<00:19:27.679> arrow<00:19:28.080> output<00:19:29.039> still<00:19:29.360> don't<00:19:29.600> support 00:19:29.909 --> 00:19:29.919 align:start position:0% support arrow output still don't support 00:19:29.919 --> 00:19:31.350 align:start position:0% support arrow output still don't support arrow<00:19:30.400> input<00:19:30.880> yet. 00:19:31.350 --> 00:19:31.360 align:start position:0% arrow input yet. 00:19:31.360 --> 00:19:31.990 align:start position:0% arrow input yet. Mhm. 00:19:31.990 --> 00:19:32.000 align:start position:0% Mhm. 00:19:32.000 --> 00:19:33.590 align:start position:0% Mhm. Because<00:19:32.559> because<00:19:32.960> agents<00:19:33.280> we're<00:19:33.440> talking 00:19:33.590 --> 00:19:33.600 align:start position:0% Because because agents we're talking 00:19:33.600 --> 00:19:35.830 align:start position:0% Because because agents we're talking about<00:19:33.760> aren't<00:19:34.160> just<00:19:34.480> about<00:19:35.280> fetching<00:19:35.600> the 00:19:35.830 --> 00:19:35.840 align:start position:0% about aren't just about fetching the 00:19:35.840 --> 00:19:37.830 align:start position:0% about aren't just about fetching the data<00:19:36.400> so<00:19:36.640> the<00:19:36.880> agent<00:19:37.120> can<00:19:37.280> process<00:19:37.520> it. 00:19:37.830 --> 00:19:37.840 align:start position:0% data so the agent can process it. 00:19:37.840 --> 00:19:38.230 align:start position:0% data so the agent can process it. Right. 00:19:38.230 --> 00:19:38.240 align:start position:0% Right. 00:19:38.240 --> 00:19:39.669 align:start position:0% Right. The<00:19:38.400> agent<00:19:38.720> also<00:19:38.880> produces<00:19:39.280> data. 00:19:39.669 --> 00:19:39.679 align:start position:0% The agent also produces data. 00:19:39.679 --> 00:19:40.950 align:start position:0% The agent also produces data. That's<00:19:39.840> right.<00:19:40.240> And<00:19:40.480> you're<00:19:40.640> going<00:19:40.799> to<00:19:40.880> want 00:19:40.950 --> 00:19:40.960 align:start position:0% That's right. And you're going to want 00:19:40.960 --> 00:19:41.909 align:start position:0% That's right. And you're going to want to<00:19:41.120> write<00:19:41.360> stuff<00:19:41.520> back. 00:19:41.909 --> 00:19:41.919 align:start position:0% to write stuff back. 00:19:41.919 --> 00:19:43.909 align:start position:0% to write stuff back. That's<00:19:42.080> right.<00:19:42.400> An<00:19:42.640> agent<00:19:43.039> can<00:19:43.200> be<00:19:43.520> just<00:19:43.760> a 00:19:43.909 --> 00:19:43.919 align:start position:0% That's right. An agent can be just a 00:19:43.919 --> 00:19:46.310 align:start position:0% That's right. An agent can be just a filter<00:19:44.320> like<00:19:44.480> it's<00:19:44.559> a<00:19:44.720> Unix<00:19:45.039> pipe.<00:19:45.600> It<00:19:45.840> accepts 00:19:46.310 --> 00:19:46.320 align:start position:0% filter like it's a Unix pipe. It accepts 00:19:46.320 --> 00:19:48.390 align:start position:0% filter like it's a Unix pipe. It accepts error<00:19:46.559> data<00:19:46.799> and<00:19:47.039> it<00:19:47.280> sends<00:19:47.840> data. 00:19:48.390 --> 00:19:48.400 align:start position:0% error data and it sends data. 00:19:48.400 --> 00:19:50.870 align:start position:0% error data and it sends data. It's<00:19:48.720> crazy<00:19:49.360> that<00:19:49.840> the<00:19:50.160> most<00:19:50.320> efficient<00:19:50.720> way 00:19:50.870 --> 00:19:50.880 align:start position:0% It's crazy that the most efficient way 00:19:50.880 --> 00:19:54.870 align:start position:0% It's crazy that the most efficient way we<00:19:51.120> have<00:19:51.360> right<00:19:51.679> now<00:19:52.880> in<00:19:53.120> most<00:19:53.440> systems,<00:19:54.640> most 00:19:54.870 --> 00:19:54.880 align:start position:0% we have right now in most systems, most 00:19:54.880 --> 00:19:59.510 align:start position:0% we have right now in most systems, most like<00:19:55.200> cloud<00:19:55.520> systems<00:19:56.320> to<00:19:57.120> ingest<00:19:57.600> data<00:19:58.640> is<00:19:58.960> to 00:19:59.510 --> 00:19:59.520 align:start position:0% like cloud systems to ingest data is to 00:19:59.520 --> 00:20:01.909 align:start position:0% like cloud systems to ingest data is to write<00:19:59.760> it<00:19:59.919> to<00:20:00.080> parquet<00:20:00.640> files<00:20:00.960> on<00:20:01.440> object 00:20:01.909 --> 00:20:01.919 align:start position:0% write it to parquet files on object 00:20:01.919 --> 00:20:04.470 align:start position:0% write it to parquet files on object storage<00:20:02.640> and<00:20:02.880> then<00:20:03.120> run<00:20:03.440> SQL<00:20:03.760> queries<00:20:04.080> to<00:20:04.240> copy 00:20:04.470 --> 00:20:04.480 align:start position:0% storage and then run SQL queries to copy 00:20:04.480 --> 00:20:05.350 align:start position:0% storage and then run SQL queries to copy it<00:20:04.640> into<00:20:04.799> the<00:20:04.960> data. 00:20:05.350 --> 00:20:05.360 align:start position:0% it into the data. 00:20:05.360 --> 00:20:08.870 align:start position:0% it into the data. Yes.<00:20:06.000> because<00:20:06.559> that<00:20:06.880> system<00:20:08.080> it'll<00:20:08.559> you<00:20:08.640> know 00:20:08.870 --> 00:20:08.880 align:start position:0% Yes. because that system it'll you know 00:20:08.880 --> 00:20:11.270 align:start position:0% Yes. because that system it'll you know bigquery<00:20:09.360> and<00:20:09.600> snowflake<00:20:10.080> will<00:20:10.320> output<00:20:11.039> will 00:20:11.270 --> 00:20:11.280 align:start position:0% bigquery and snowflake will output will 00:20:11.280 --> 00:20:14.310 align:start position:0% bigquery and snowflake will output will output<00:20:11.600> arrow<00:20:12.799> but 00:20:14.310 --> 00:20:14.320 align:start position:0% output arrow but 00:20:14.320 --> 00:20:17.190 align:start position:0% output arrow but we<00:20:14.640> even<00:20:14.880> though<00:20:15.039> ABC<00:20:15.600> has<00:20:15.679> a<00:20:15.840> bulk<00:20:16.240> ingestion 00:20:17.190 --> 00:20:17.200 align:start position:0% we even though ABC has a bulk ingestion 00:20:17.200 --> 00:20:18.950 align:start position:0% we even though ABC has a bulk ingestion the<00:20:17.520> implementation<00:20:18.000> for<00:20:18.240> those<00:20:18.480> drivers<00:20:18.799> of 00:20:18.950 --> 00:20:18.960 align:start position:0% the implementation for those drivers of 00:20:18.960 --> 00:20:22.310 align:start position:0% the implementation for those drivers of the<00:20:19.039> bulk<00:20:19.360> ingest<00:20:20.160> is<00:20:20.400> to<00:20:21.360> take<00:20:21.600> the<00:20:21.840> stream<00:20:22.160> of 00:20:22.310 --> 00:20:22.320 align:start position:0% the bulk ingest is to take the stream of 00:20:22.320 --> 00:20:25.029 align:start position:0% the bulk ingest is to take the stream of arrow<00:20:22.640> data<00:20:22.960> and<00:20:23.520> write<00:20:23.679> it<00:20:23.840> to<00:20:24.000> parquet<00:20:24.480> files 00:20:25.029 --> 00:20:25.039 align:start position:0% arrow data and write it to parquet files 00:20:25.039 --> 00:20:27.110 align:start position:0% arrow data and write it to parquet files on<00:20:25.360> object<00:20:25.679> storage<00:20:26.080> and<00:20:26.240> feed<00:20:26.400> them<00:20:26.559> through 00:20:27.110 --> 00:20:27.120 align:start position:0% on object storage and feed them through 00:20:27.120 --> 00:20:29.669 align:start position:0% on object storage and feed them through and<00:20:27.280> then<00:20:27.440> call<00:20:27.760> copy<00:20:28.159> into<00:20:29.039> queries<00:20:29.520> that's 00:20:29.669 --> 00:20:29.679 align:start position:0% and then call copy into queries that's 00:20:29.679 --> 00:20:29.990 align:start position:0% and then call copy into queries that's crazy 00:20:29.990 --> 00:20:30.000 align:start position:0% crazy 00:20:30.000 --> 00:20:32.870 align:start position:0% crazy because<00:20:30.480> the<00:20:30.799> system<00:20:31.200> themselves<00:20:32.400> don't<00:20:32.720> have 00:20:32.870 --> 00:20:32.880 align:start position:0% because the system themselves don't have 00:20:32.880 --> 00:20:34.310 align:start position:0% because the system themselves don't have a<00:20:33.039> native 00:20:34.310 --> 00:20:34.320 align:start position:0% a native 00:20:34.320 --> 00:20:36.149 align:start position:0% a native here's<00:20:34.640> a<00:20:34.799> stream<00:20:35.039> of<00:20:35.200> arrow<00:20:35.679> data, 00:20:36.149 --> 00:20:36.159 align:start position:0% here's a stream of arrow data, 00:20:36.159 --> 00:20:36.950 align:start position:0% here's a stream of arrow data, right? 00:20:36.950 --> 00:20:36.960 align:start position:0% right? 00:20:36.960 --> 00:20:38.310 align:start position:0% right? Insert<00:20:37.280> that<00:20:37.440> into<00:20:37.679> my<00:20:37.840> table. 00:20:38.310 --> 00:20:38.320 align:start position:0% Insert that into my table. 00:20:38.320 --> 00:20:40.230 align:start position:0% Insert that into my table. Right.<00:20:38.720> Right.<00:20:39.520> Interesting. 00:20:40.230 --> 00:20:40.240 align:start position:0% Right. Right. Interesting. 00:20:40.240 --> 00:20:43.270 align:start position:0% Right. Right. Interesting. Even<00:20:40.480> though<00:20:41.360> I<00:20:41.600> can<00:20:41.760> do<00:20:41.919> select<00:20:42.240> star<00:20:42.559> and<00:20:42.799> get 00:20:43.270 --> 00:20:43.280 align:start position:0% Even though I can do select star and get 00:20:43.280 --> 00:20:44.950 align:start position:0% Even though I can do select star and get the<00:20:43.600> entire<00:20:43.840> table<00:20:44.080> as<00:20:44.320> arrow<00:20:44.559> out. 00:20:44.950 --> 00:20:44.960 align:start position:0% the entire table as arrow out. 00:20:44.960 --> 00:20:46.549 align:start position:0% the entire table as arrow out. Zero<00:20:45.120> out.<00:20:45.440> Okay.<00:20:45.679> Now,<00:20:45.919> this<00:20:46.080> I<00:20:46.320> think<00:20:46.400> this 00:20:46.549 --> 00:20:46.559 align:start position:0% Zero out. Okay. Now, this I think this 00:20:46.559 --> 00:20:49.669 align:start position:0% Zero out. Okay. Now, this I think this is<00:20:46.799> great.<00:20:47.440> Uh<00:20:47.919> I<00:20:48.159> think<00:20:48.320> it<00:20:48.559> it's<00:20:48.880> probably 00:20:49.669 --> 00:20:49.679 align:start position:0% is great. Uh I think it it's probably 00:20:49.679 --> 00:20:51.669 align:start position:0% is great. Uh I think it it's probably not<00:20:50.000> enough<00:20:50.320> people<00:20:50.640> asked<00:20:50.880> for<00:20:50.960> it<00:20:51.120> or<00:20:51.520> there 00:20:51.669 --> 00:20:51.679 align:start position:0% not enough people asked for it or there 00:20:51.679 --> 00:20:53.270 align:start position:0% not enough people asked for it or there was<00:20:51.840> not<00:20:52.000> enough<00:20:52.159> push.<00:20:52.559> But<00:20:52.799> again,<00:20:53.039> like 00:20:53.270 --> 00:20:53.280 align:start position:0% was not enough push. But again, like 00:20:53.280 --> 00:20:54.950 align:start position:0% was not enough push. But again, like this<00:20:53.440> is<00:20:53.520> I<00:20:53.679> think<00:20:53.760> the<00:20:54.000> power<00:20:54.159> of<00:20:54.240> community 00:20:54.950 --> 00:20:54.960 align:start position:0% this is I think the power of community 00:20:54.960 --> 00:20:58.310 align:start position:0% this is I think the power of community if<00:20:55.360> if<00:20:55.600> we<00:20:55.760> create<00:20:56.080> enough<00:20:56.799> kind<00:20:56.960> of<00:20:57.200> momentum 00:20:58.310 --> 00:20:58.320 align:start position:0% if if we create enough kind of momentum 00:20:58.320 --> 00:21:01.110 align:start position:0% if if we create enough kind of momentum uh<00:20:58.480> behind<00:20:59.039> the<00:20:59.280> idea<00:20:59.520> that<00:21:00.080> we<00:21:00.320> shall<00:21:00.640> all 00:21:01.110 --> 00:21:01.120 align:start position:0% uh behind the idea that we shall all 00:21:01.120 --> 00:21:03.510 align:start position:0% uh behind the idea that we shall all interchange<00:21:01.679> data<00:21:02.000> through<00:21:02.240> a<00:21:02.400> fast<00:21:02.880> bus 00:21:03.510 --> 00:21:03.520 align:start position:0% interchange data through a fast bus 00:21:03.520 --> 00:21:05.110 align:start position:0% interchange data through a fast bus behind<00:21:03.919> all<00:21:04.080> this<00:21:04.240> AI<00:21:04.480> system.<00:21:04.819> [laughter]<00:21:04.880> an 00:21:05.110 --> 00:21:05.120 align:start position:0% behind all this AI system. [laughter] an 00:21:05.120 --> 00:21:05.669 align:start position:0% behind all this AI system. [laughter] an open<00:21:05.280> standard 00:21:05.669 --> 00:21:05.679 align:start position:0% open standard 00:21:05.679 --> 00:21:07.590 align:start position:0% open standard use<00:21:05.840> an<00:21:05.919> open<00:21:06.159> standard<00:21:06.799> then<00:21:07.280> you<00:21:07.440> know 00:21:07.590 --> 00:21:07.600 align:start position:0% use an open standard then you know 00:21:07.600 --> 00:21:10.710 align:start position:0% use an open standard then you know hopefully<00:21:08.480> uh<00:21:08.720> you<00:21:08.880> know<00:21:09.440> others<00:21:10.240> dominoes 00:21:10.710 --> 00:21:10.720 align:start position:0% hopefully uh you know others dominoes 00:21:10.720 --> 00:21:13.669 align:start position:0% hopefully uh you know others dominoes will<00:21:11.280> fall<00:21:11.679> and<00:21:12.240> uh<00:21:12.400> we'll<00:21:12.640> have<00:21:12.720> a<00:21:12.960> faster 00:21:13.669 --> 00:21:13.679 align:start position:0% will fall and uh we'll have a faster 00:21:13.679 --> 00:21:15.510 align:start position:0% will fall and uh we'll have a faster and<00:21:13.760> and<00:21:13.919> for<00:21:14.159> those<00:21:14.320> who<00:21:14.799> like<00:21:14.960> we<00:21:15.200> mentioned 00:21:15.510 --> 00:21:15.520 align:start position:0% and and for those who like we mentioned 00:21:15.520 --> 00:21:16.870 align:start position:0% and and for those who like we mentioned arrow<00:21:15.840> a<00:21:15.919> bunch<00:21:16.080> of<00:21:16.159> times<00:21:16.320> and<00:21:16.480> I<00:21:16.559> said<00:21:16.799> you 00:21:16.870 --> 00:21:16.880 align:start position:0% arrow a bunch of times and I said you 00:21:16.880 --> 00:21:19.029 align:start position:0% arrow a bunch of times and I said you know<00:21:16.960> inmemory<00:21:17.919> format<00:21:18.240> but<00:21:18.480> for<00:21:18.720> those<00:21:18.880> who 00:21:19.029 --> 00:21:19.039 align:start position:0% know inmemory format but for those who 00:21:19.039 --> 00:21:20.710 align:start position:0% know inmemory format but for those who aren't<00:21:19.360> familiar<00:21:19.600> with<00:21:19.840> apache<00:21:20.240> arrow<00:21:20.559> in 00:21:20.710 --> 00:21:20.720 align:start position:0% aren't familiar with apache arrow in 00:21:20.720 --> 00:21:21.510 align:start position:0% aren't familiar with apache arrow in general 00:21:21.510 --> 00:21:21.520 align:start position:0% general 00:21:21.520 --> 00:21:23.270 align:start position:0% general highly<00:21:21.919> recommend<00:21:22.400> you<00:21:22.559> know<00:21:22.640> look<00:21:22.799> into<00:21:23.200> you 00:21:23.270 --> 00:21:23.280 align:start position:0% highly recommend you know look into you 00:21:23.280 --> 00:21:24.870 align:start position:0% highly recommend you know look into you know<00:21:23.440> arrow.apache.org 00:21:24.870 --> 00:21:24.880 align:start position:0% know arrow.apache.org 00:21:24.880 --> 00:21:26.310 align:start position:0% know arrow.apache.org The<00:21:25.120> the<00:21:25.360> important<00:21:25.520> piece<00:21:25.760> here<00:21:25.919> is<00:21:26.080> the<00:21:26.240> fact 00:21:26.310 --> 00:21:26.320 align:start position:0% The the important piece here is the fact 00:21:26.320 --> 00:21:26.950 align:start position:0% The the important piece here is the fact that 00:21:26.950 --> 00:21:26.960 align:start position:0% that 00:21:26.960 --> 00:21:29.750 align:start position:0% that you're<00:21:27.200> going<00:21:27.280> to<00:21:27.440> find<00:21:27.679> that<00:21:28.159> Arrow<00:21:28.640> is<00:21:29.440> and 00:21:29.750 --> 00:21:29.760 align:start position:0% you're going to find that Arrow is and 00:21:29.760 --> 00:21:31.270 align:start position:0% you're going to find that Arrow is and has<00:21:30.000> been<00:21:30.159> the<00:21:30.320> underpinning<00:21:30.799> of<00:21:31.039> pretty<00:21:31.200> much 00:21:31.270 --> 00:21:31.280 align:start position:0% has been the underpinning of pretty much 00:21:31.280 --> 00:21:32.950 align:start position:0% has been the underpinning of pretty much the<00:21:31.520> entire<00:21:31.760> data<00:21:32.000> ecosystem<00:21:32.480> for<00:21:32.640> a<00:21:32.799> while 00:21:32.950 --> 00:21:32.960 align:start position:0% the entire data ecosystem for a while 00:21:32.960 --> 00:21:33.590 align:start position:0% the entire data ecosystem for a while now. 00:21:33.590 --> 00:21:33.600 align:start position:0% now. 00:21:33.600 --> 00:21:35.270 align:start position:0% now. Arrow<00:21:33.840> is<00:21:34.000> 10<00:21:34.159> years<00:21:34.320> old<00:21:34.480> this<00:21:34.640> year.<00:21:34.960> Yes. 00:21:35.270 --> 00:21:35.280 align:start position:0% Arrow is 10 years old this year. Yes. 00:21:35.280 --> 00:21:37.990 align:start position:0% Arrow is 10 years old this year. Yes. And<00:21:35.440> it's<00:21:35.760> still<00:21:36.240> not<00:21:36.640> that<00:21:36.960> well<00:21:37.280> known<00:21:37.760> even 00:21:37.990 --> 00:21:38.000 align:start position:0% And it's still not that well known even 00:21:38.000 --> 00:21:39.029 align:start position:0% And it's still not that well known even though 00:21:39.029 --> 00:21:39.039 align:start position:0% though 00:21:39.039 --> 00:21:40.310 align:start position:0% though you<00:21:39.200> know<00:21:39.600> it 00:21:40.310 --> 00:21:40.320 align:start position:0% you know it 00:21:40.320 --> 00:21:43.590 align:start position:0% you know it I<00:21:40.640> will<00:21:41.360> almost<00:21:41.840> guarantee<00:21:42.640> that<00:21:42.960> any<00:21:43.200> data 00:21:43.590 --> 00:21:43.600 align:start position:0% I will almost guarantee that any data 00:21:43.600 --> 00:21:44.789 align:start position:0% I will almost guarantee that any data stack<00:21:43.840> you<00:21:44.080> have 00:21:44.789 --> 00:21:44.799 align:start position:0% stack you have 00:21:44.799 --> 00:21:46.149 align:start position:0% stack you have arrows<00:21:45.280> in<00:21:45.440> there<00:21:45.600> somewhere 00:21:46.149 --> 00:21:46.159 align:start position:0% arrows in there somewhere 00:21:46.159 --> 00:21:46.549 align:start position:0% arrows in there somewhere right 00:21:46.549 --> 00:21:46.559 align:start position:0% right 00:21:46.559 --> 00:21:48.630 align:start position:0% right because<00:21:46.960> Polers<00:21:47.440> is<00:21:47.600> built<00:21:47.760> on<00:21:47.840> top<00:21:47.919> of<00:21:48.080> arrow 00:21:48.630 --> 00:21:48.640 align:start position:0% because Polers is built on top of arrow 00:21:48.640 --> 00:21:49.029 align:start position:0% because Polers is built on top of arrow right 00:21:49.029 --> 00:21:49.039 align:start position:0% right 00:21:49.039 --> 00:21:52.149 align:start position:0% right pandas<00:21:50.000> uses<00:21:50.400> arrow<00:21:51.039> and<00:21:51.200> has<00:21:51.440> and<00:21:51.679> has<00:21:51.840> the<00:21:51.919> pi 00:21:52.149 --> 00:21:52.159 align:start position:0% pandas uses arrow and has and has the pi 00:21:52.159 --> 00:21:54.310 align:start position:0% pandas uses arrow and has and has the pi arrow<00:21:52.400> back<00:21:52.480> end<00:21:52.640> in<00:21:52.880> v3<00:21:53.280> now.<00:21:53.600> Yes, 00:21:54.310 --> 00:21:54.320 align:start position:0% arrow back end in v3 now. Yes, 00:21:54.320 --> 00:21:54.630 align:start position:0% arrow back end in v3 now. Yes, duct 00:21:54.630 --> 00:21:54.640 align:start position:0% duct 00:21:54.640 --> 00:21:57.110 align:start position:0% duct DB<00:21:55.039> input<00:21:55.520> takes<00:21:55.760> in<00:21:56.000> and<00:21:56.240> outputs<00:21:56.720> arrow. 00:21:57.110 --> 00:21:57.120 align:start position:0% DB input takes in and outputs arrow. 00:21:57.120 --> 00:21:57.510 align:start position:0% DB input takes in and outputs arrow. Yep. 00:21:57.510 --> 00:21:57.520 align:start position:0% Yep. 00:21:57.520 --> 00:21:59.029 align:start position:0% Yep. Snowflake<00:21:57.919> outputs<00:21:58.240> arrow.<00:21:58.559> BigQuery 00:21:59.029 --> 00:21:59.039 align:start position:0% Snowflake outputs arrow. BigQuery 00:21:59.039 --> 00:22:00.549 align:start position:0% Snowflake outputs arrow. BigQuery outputs<00:21:59.360> arrow. 00:22:00.549 --> 00:22:00.559 align:start position:0% outputs arrow. 00:22:00.559 --> 00:22:03.190 align:start position:0% outputs arrow. You<00:22:00.720> know,<00:22:00.960> PowerBI<00:22:01.520> uses<00:22:01.840> ADBC<00:22:02.320> drivers<00:22:02.720> now. 00:22:03.190 --> 00:22:03.200 align:start position:0% You know, PowerBI uses ADBC drivers now. 00:22:03.200 --> 00:22:05.110 align:start position:0% You know, PowerBI uses ADBC drivers now. Sale<00:22:04.159> like<00:22:04.320> sales<00:22:04.480> is<00:22:04.559> built<00:22:04.720> on<00:22:04.880> it's<00:22:05.039> built 00:22:05.110 --> 00:22:05.120 align:start position:0% Sale like sales is built on it's built 00:22:05.120 --> 00:22:06.549 align:start position:0% Sale like sales is built on it's built on<00:22:05.200> data<00:22:05.440> fusion.<00:22:05.760> Data<00:22:05.919> fusion<00:22:06.159> is<00:22:06.240> entirely 00:22:06.549 --> 00:22:06.559 align:start position:0% on data fusion. Data fusion is entirely 00:22:06.559 --> 00:22:07.029 align:start position:0% on data fusion. Data fusion is entirely arrow. 00:22:07.029 --> 00:22:07.039 align:start position:0% arrow. 00:22:07.039 --> 00:22:07.430 align:start position:0% arrow. Correct. 00:22:07.430 --> 00:22:07.440 align:start position:0% Correct. 00:22:07.440 --> 00:22:10.310 align:start position:0% Correct. You<00:22:07.600> know,<00:22:08.080> like<00:22:08.320> like<00:22:08.480> like 00:22:10.310 --> 00:22:10.320 align:start position:0% You know, like like like 00:22:10.320 --> 00:22:13.029 align:start position:0% You know, like like like Arrow<00:22:10.640> is<00:22:10.799> the<00:22:11.120> is<00:22:11.360> the<00:22:11.520> backbone<00:22:12.159> of<00:22:12.720> what 00:22:13.029 --> 00:22:13.039 align:start position:0% Arrow is the is the backbone of what 00:22:13.039 --> 00:22:15.830 align:start position:0% Arrow is the is the backbone of what makes<00:22:13.360> all<00:22:13.520> of<00:22:13.679> these<00:22:13.919> tools<00:22:14.159> and<00:22:14.480> utilities 00:22:15.830 --> 00:22:15.840 align:start position:0% makes all of these tools and utilities 00:22:15.840 --> 00:22:17.430 align:start position:0% makes all of these tools and utilities work<00:22:16.159> together<00:22:16.559> seamlessly<00:22:17.120> and 00:22:17.430 --> 00:22:17.440 align:start position:0% work together seamlessly and 00:22:17.440 --> 00:22:19.510 align:start position:0% work together seamlessly and efficiently.<00:22:18.720> Even<00:22:18.960> though<00:22:19.120> you're<00:22:19.360> not 00:22:19.510 --> 00:22:19.520 align:start position:0% efficiently. Even though you're not 00:22:19.520 --> 00:22:21.190 align:start position:0% efficiently. Even though you're not dealing<00:22:19.679> with<00:22:19.840> Arrow<00:22:20.240> directly<00:22:20.559> yourselves. 00:22:21.190 --> 00:22:21.200 align:start position:0% dealing with Arrow directly yourselves. 00:22:21.200 --> 00:22:22.390 align:start position:0% dealing with Arrow directly yourselves. Yes.<00:22:21.600> You<00:22:21.760> know,<00:22:21.840> if<00:22:22.000> you're<00:22:22.080> the<00:22:22.240> one 00:22:22.390 --> 00:22:22.400 align:start position:0% Yes. You know, if you're the one 00:22:22.400 --> 00:22:23.750 align:start position:0% Yes. You know, if you're the one building<00:22:22.640> the<00:22:22.799> tools,<00:22:23.120> then<00:22:23.280> you<00:22:23.360> use<00:22:23.520> Arrow 00:22:23.750 --> 00:22:23.760 align:start position:0% building the tools, then you use Arrow 00:22:23.760 --> 00:22:25.029 align:start position:0% building the tools, then you use Arrow directly.<00:22:24.240> If<00:22:24.400> you're<00:22:24.480> not<00:22:24.559> the<00:22:24.720> one<00:22:24.880> building 00:22:25.029 --> 00:22:25.039 align:start position:0% directly. If you're not the one building 00:22:25.039 --> 00:22:26.789 align:start position:0% directly. If you're not the one building the<00:22:25.200> tools,<00:22:26.000> you<00:22:26.159> aren't<00:22:26.400> necessarily 00:22:26.789 --> 00:22:26.799 align:start position:0% the tools, you aren't necessarily 00:22:26.799 --> 00:22:28.549 align:start position:0% the tools, you aren't necessarily familiar<00:22:27.120> with<00:22:27.280> Arrow<00:22:27.679> because<00:22:28.000> you're 00:22:28.549 --> 00:22:28.559 align:start position:0% familiar with Arrow because you're 00:22:28.559 --> 00:22:29.830 align:start position:0% familiar with Arrow because you're you're<00:22:28.799> just<00:22:28.960> benefiting<00:22:29.360> from<00:22:29.520> the<00:22:29.679> fact 00:22:29.830 --> 00:22:29.840 align:start position:0% you're just benefiting from the fact 00:22:29.840 --> 00:22:31.510 align:start position:0% you're just benefiting from the fact that<00:22:30.000> all<00:22:30.240> of<00:22:30.240> these<00:22:30.480> other<00:22:30.640> things<00:22:30.960> use<00:22:31.120> Arrow 00:22:31.510 --> 00:22:31.520 align:start position:0% that all of these other things use Arrow 00:22:31.520 --> 00:22:32.310 align:start position:0% that all of these other things use Arrow to<00:22:31.600> talk<00:22:31.760> to<00:22:31.840> each<00:22:32.000> other. 00:22:32.310 --> 00:22:32.320 align:start position:0% to talk to each other. 00:22:32.320 --> 00:22:34.950 align:start position:0% to talk to each other. Right.<00:22:32.720> Right.<00:22:33.280> And<00:22:33.520> so<00:22:33.679> I<00:22:33.840> think<00:22:34.000> the<00:22:34.320> agentic 00:22:34.950 --> 00:22:34.960 align:start position:0% Right. Right. And so I think the agentic 00:22:34.960 --> 00:22:36.549 align:start position:0% Right. Right. And so I think the agentic movement<00:22:35.280> is<00:22:35.679> kind<00:22:35.919> of<00:22:36.000> several<00:22:36.320> steps 00:22:36.549 --> 00:22:36.559 align:start position:0% movement is kind of several steps 00:22:36.559 --> 00:22:38.390 align:start position:0% movement is kind of several steps removed.<00:22:37.200> People<00:22:37.440> talk<00:22:37.679> about<00:22:37.840> agents<00:22:38.240> kind 00:22:38.390 --> 00:22:38.400 align:start position:0% removed. People talk about agents kind 00:22:38.400 --> 00:22:40.630 align:start position:0% removed. People talk about agents kind of<00:22:38.559> communicating<00:22:39.520> and<00:22:40.000> then<00:22:40.159> they<00:22:40.320> do<00:22:40.480> that 00:22:40.630 --> 00:22:40.640 align:start position:0% of communicating and then they do that 00:22:40.640 --> 00:22:43.110 align:start position:0% of communicating and then they do that they<00:22:41.200> think<00:22:41.440> chat,<00:22:42.000> but<00:22:42.240> the<00:22:42.480> underlying<00:22:42.880> data 00:22:43.110 --> 00:22:43.120 align:start position:0% they think chat, but the underlying data 00:22:43.120 --> 00:22:46.310 align:start position:0% they think chat, but the underlying data should<00:22:43.280> be<00:22:43.440> transferred<00:22:44.159> through<00:22:45.039> binary<00:22:46.000> uh 00:22:46.310 --> 00:22:46.320 align:start position:0% should be transferred through binary uh 00:22:46.320 --> 00:22:48.310 align:start position:0% should be transferred through binary uh fast<00:22:46.640> binary<00:22:47.120> channel.<00:22:47.679> It<00:22:47.760> just<00:22:48.000> made<00:22:48.159> me 00:22:48.310 --> 00:22:48.320 align:start position:0% fast binary channel. It just made me 00:22:48.320 --> 00:22:51.510 align:start position:0% fast binary channel. It just made me think<00:22:48.880> maybe<00:22:49.520> you<00:22:49.600> know<00:22:49.760> MCP<00:22:50.320> DBC<00:22:50.960> is<00:22:51.200> the<00:22:51.440> next 00:22:51.510 --> 00:22:51.520 align:start position:0% think maybe you know MCP DBC is the next 00:22:51.520 --> 00:22:52.789 align:start position:0% think maybe you know MCP DBC is the next thing<00:22:51.760> you<00:22:52.240> [laughter] 00:22:52.789 --> 00:22:52.799 align:start position:0% thing you [laughter] 00:22:52.799 --> 00:22:55.669 align:start position:0% thing you [laughter] guys<00:22:53.280> you<00:22:53.520> can<00:22:53.679> tackle<00:22:54.000> on<00:22:54.400> right<00:22:54.880> like<00:22:55.440> how 00:22:55.669 --> 00:22:55.679 align:start position:0% guys you can tackle on right like how 00:22:55.679 --> 00:22:57.750 align:start position:0% guys you can tackle on right like how hard<00:22:55.919> can<00:22:56.080> it<00:22:56.240> be<00:22:56.640> you<00:22:56.720> know<00:22:56.799> you<00:22:56.960> have<00:22:57.360> pie<00:22:57.679> you 00:22:57.750 --> 00:22:57.760 align:start position:0% hard can it be you know you have pie you 00:22:57.760 --> 00:22:58.870 align:start position:0% hard can it be you know you have pie you have<00:22:57.919> all<00:22:58.000> the<00:22:58.400> reviewing<00:22:58.640> tools 00:22:58.870 --> 00:22:58.880 align:start position:0% have all the reviewing tools 00:22:58.880 --> 00:22:59.909 align:start position:0% have all the reviewing tools arrow<00:22:59.200> MCP 00:22:59.909 --> 00:22:59.919 align:start position:0% arrow MCP 00:22:59.919 --> 00:23:01.909 align:start position:0% arrow MCP yeah<00:23:00.159> you<00:23:00.240> know<00:23:01.039> that<00:23:01.200> that<00:23:01.600> you<00:23:01.679> know<00:23:01.760> you 00:23:01.909 --> 00:23:01.919 align:start position:0% yeah you know that that you know you 00:23:01.919 --> 00:23:02.390 align:start position:0% yeah you know that that you know you heard<00:23:02.000> it<00:23:02.159> first 00:23:02.390 --> 00:23:02.400 align:start position:0% heard it first 00:23:02.400 --> 00:23:04.630 align:start position:0% heard it first if<00:23:02.480> I<00:23:02.559> had<00:23:02.720> if<00:23:02.880> I<00:23:02.960> had<00:23:03.039> the<00:23:03.200> time<00:23:04.030> [laughter]<00:23:04.320> so 00:23:04.630 --> 00:23:04.640 align:start position:0% if I had if I had the time [laughter] so 00:23:04.640 --> 00:23:05.909 align:start position:0% if I had if I had the time [laughter] so so<00:23:04.799> hey<00:23:05.039> someone<00:23:05.200> can<00:23:05.360> contribute<00:23:05.679> it 00:23:05.909 --> 00:23:05.919 align:start position:0% so hey someone can contribute it 00:23:05.919 --> 00:23:07.750 align:start position:0% so hey someone can contribute it exactly<00:23:06.320> contribute<00:23:06.640> it<00:23:07.120> well<00:23:07.440> thank<00:23:07.600> you 00:23:07.750 --> 00:23:07.760 align:start position:0% exactly contribute it well thank you 00:23:07.760 --> 00:23:10.230 align:start position:0% exactly contribute it well thank you very<00:23:07.919> much<00:23:08.080> Matt<00:23:08.400> that<00:23:08.559> was<00:23:09.280> illuminating<00:23:10.000> and 00:23:10.230 --> 00:23:10.240 align:start position:0% very much Matt that was illuminating and 00:23:10.240 --> 00:23:12.310 align:start position:0% very much Matt that was illuminating and you<00:23:10.400> have<00:23:10.480> a<00:23:10.720> bunch<00:23:11.360> uh<00:23:11.520> things<00:23:11.760> coming<00:23:11.919> up<00:23:12.080> for 00:23:12.310 --> 00:23:12.320 align:start position:0% you have a bunch uh things coming up for 00:23:12.320 --> 00:23:15.350 align:start position:0% you have a bunch uh things coming up for ADBC<00:23:12.880> so<00:23:13.440> huge<00:23:14.000> you<00:23:14.159> know<00:23:14.320> kudos<00:23:14.720> to<00:23:14.880> you<00:23:15.120> and 00:23:15.350 --> 00:23:15.360 align:start position:0% ADBC so huge you know kudos to you and 00:23:15.360 --> 00:23:16.630 align:start position:0% ADBC so huge you know kudos to you and thanks<00:23:15.600> for<00:23:15.760> sharing<00:23:16.000> with<00:23:16.159> the<00:23:16.400> community 00:23:16.630 --> 00:23:16.640 align:start position:0% thanks for sharing with the community 00:23:16.640 --> 00:23:18.630 align:start position:0% thanks for sharing with the community and<00:23:16.880> we<00:23:17.039> See<00:23:17.679> you<00:23:17.760> around<00:23:18.159> community.<00:23:18.559> Thank 00:23:18.630 --> 00:23:18.640 align:start position:0% and we See you around community. Thank 00:23:18.640 --> 00:23:18.870 align:start position:0% and we See you around community. Thank you. 00:23:18.870 --> 00:23:18.880 align:start position:0% you. 00:23:18.880 --> 00:23:19.830 align:start position:0% you. Thank<00:23:19.039> you. 00:23:19.830 --> 00:23:19.840 align:start position:0% Thank you. 00:23:19.840 --> 00:23:22.919 align:start position:0% Thank you. All<00:23:19.919> right.