WEBVTT Kind: captions Language: en 00:00:11.019 --> 00:00:13.359 align:start position:0% hello<00:00:12.019> everybody<00:00:12.200> I'm<00:00:12.590> Alexa<00:00:12.950> crabber<00:00:13.250> off 00:00:13.359 --> 00:00:13.369 align:start position:0% hello everybody I'm Alexa crabber off 00:00:13.369 --> 00:00:15.430 align:start position:0% hello everybody I'm Alexa crabber off the<00:00:13.610> organizer<00:00:14.089> of<00:00:14.330> sf's<00:00:14.660> park<00:00:14.870> in<00:00:14.990> France<00:00:15.230> and 00:00:15.430 --> 00:00:15.440 align:start position:0% the organizer of sf's park in France and 00:00:15.440 --> 00:00:18.060 align:start position:0% the organizer of sf's park in France and here<00:00:15.799> we<00:00:16.009> are<00:00:16.070> on<00:00:16.309> location<00:00:16.430> at<00:00:16.970> quantcast<00:00:17.540> a 00:00:18.060 --> 00:00:18.070 align:start position:0% here we are on location at quantcast a 00:00:18.070 --> 00:00:22.179 align:start position:0% here we are on location at quantcast a hosting<00:00:19.090> talk<00:00:20.090> on<00:00:20.390> kudu<00:00:20.930> kudu<00:00:21.710> is<00:00:21.980> a<00:00:22.010> new 00:00:22.179 --> 00:00:22.189 align:start position:0% hosting talk on kudu kudu is a new 00:00:22.189 --> 00:00:23.950 align:start position:0% hosting talk on kudu kudu is a new system<00:00:22.430> out<00:00:22.550> of<00:00:22.580> Cloudera<00:00:23.000> we<00:00:23.570> have<00:00:23.750> one<00:00:23.869> of 00:00:23.950 --> 00:00:23.960 align:start position:0% system out of Cloudera we have one of 00:00:23.960 --> 00:00:25.269 align:start position:0% system out of Cloudera we have one of the<00:00:24.050> core<00:00:24.230> members<00:00:24.500> of<00:00:24.619> the<00:00:24.710> team<00:00:24.920> with<00:00:25.130> us 00:00:25.269 --> 00:00:25.279 align:start position:0% the core members of the team with us 00:00:25.279 --> 00:00:29.650 align:start position:0% the core members of the team with us here<00:00:25.550> JD<00:00:26.000> crayons<00:00:27.099> and<00:00:28.119> we<00:00:29.119> just<00:00:29.330> heard<00:00:29.480> about 00:00:29.650 --> 00:00:29.660 align:start position:0% here JD crayons and we just heard about 00:00:29.660 --> 00:00:32.290 align:start position:0% here JD crayons and we just heard about kudu<00:00:30.109> announced<00:00:30.830> the<00:00:30.949> thing<00:00:31.160> we<00:00:31.310> are<00:00:31.910> happy<00:00:32.210> to 00:00:32.290 --> 00:00:32.300 align:start position:0% kudu announced the thing we are happy to 00:00:32.300 --> 00:00:34.960 align:start position:0% kudu announced the thing we are happy to host<00:00:32.480> one<00:00:32.570> of<00:00:32.750> the<00:00:32.839> first<00:00:33.019> talks<00:00:33.260> yeah<00:00:33.949> well<00:00:34.400> my 00:00:34.960 --> 00:00:34.970 align:start position:0% host one of the first talks yeah well my 00:00:34.970 --> 00:00:36.880 align:start position:0% host one of the first talks yeah well my my<00:00:35.480> first<00:00:35.750> talking<00:00:35.960> public<00:00:36.320> actually<00:00:36.470> that's 00:00:36.880 --> 00:00:36.890 align:start position:0% my first talking public actually that's 00:00:36.890 --> 00:00:38.469 align:start position:0% my first talking public actually that's fantastic<00:00:37.280> right<00:00:37.430> so<00:00:37.610> we<00:00:37.760> are<00:00:37.790> super 00:00:38.469 --> 00:00:38.479 align:start position:0% fantastic right so we are super 00:00:38.479 --> 00:00:41.079 align:start position:0% fantastic right so we are super fortunate<00:00:38.659> to<00:00:38.989> hear<00:00:39.739> about<00:00:39.830> it<00:00:39.920> and<00:00:40.280> we'll<00:00:40.909> ask 00:00:41.079 --> 00:00:41.089 align:start position:0% fortunate to hear about it and we'll ask 00:00:41.089 --> 00:00:43.450 align:start position:0% fortunate to hear about it and we'll ask GG<00:00:41.540> a<00:00:41.570> little<00:00:41.900> bit<00:00:42.019> about<00:00:42.260> like<00:00:43.010> a<00:00:43.040> system 00:00:43.450 --> 00:00:43.460 align:start position:0% GG a little bit about like a system 00:00:43.460 --> 00:00:45.939 align:start position:0% GG a little bit about like a system about<00:00:44.180> his<00:00:44.360> interest<00:00:44.659> then<00:00:45.260> you<00:00:45.530> know<00:00:45.650> why 00:00:45.939 --> 00:00:45.949 align:start position:0% about his interest then you know why 00:00:45.949 --> 00:00:47.670 align:start position:0% about his interest then you know why code<00:00:46.220> is<00:00:46.400> the<00:00:46.610> next<00:00:46.970> thing<00:00:47.119> we<00:00:47.210> should<00:00:47.269> try 00:00:47.670 --> 00:00:47.680 align:start position:0% code is the next thing we should try 00:00:47.680 --> 00:00:51.549 align:start position:0% code is the next thing we should try welcome<00:00:49.390> so<00:00:50.390> let's<00:00:50.570> go<00:00:50.690> a<00:00:50.720> little<00:00:51.019> bit<00:00:51.350> with 00:00:51.549 --> 00:00:51.559 align:start position:0% welcome so let's go a little bit with 00:00:51.559 --> 00:00:54.850 align:start position:0% welcome so let's go a little bit with the<00:00:51.860> the<00:00:52.190> history<00:00:52.879> right<00:00:53.269> so<00:00:53.589> so<00:00:54.589> I<00:00:54.650> know<00:00:54.710> you 00:00:54.850 --> 00:00:54.860 align:start position:0% the the history right so so I know you 00:00:54.860 --> 00:00:59.109 align:start position:0% the the history right so so I know you were<00:00:55.269> you<00:00:56.269> are<00:00:56.449> hbase<00:00:57.170> pmc<00:00:58.129> and<00:00:58.430> you<00:00:58.729> wear<00:00:58.939> at 00:00:59.109 --> 00:00:59.119 align:start position:0% were you are hbase pmc and you wear at 00:00:59.119 --> 00:01:02.590 align:start position:0% were you are hbase pmc and you wear at stumbleupon<00:00:59.780> where<00:01:00.619> is<00:01:00.979> base<00:01:01.220> kind<00:01:01.760> of<00:01:01.850> one<00:01:02.479> of 00:01:02.590 --> 00:01:02.600 align:start position:0% stumbleupon where is base kind of one of 00:01:02.600 --> 00:01:05.560 align:start position:0% stumbleupon where is base kind of one of the<00:01:02.689> places<00:01:02.900> for<00:01:03.170> hbase<00:01:03.500> grew<00:01:04.010> and<00:01:04.879> so<00:01:05.269> can<00:01:05.479> you 00:01:05.560 --> 00:01:05.570 align:start position:0% the places for hbase grew and so can you 00:01:05.570 --> 00:01:07.539 align:start position:0% the places for hbase grew and so can you tell<00:01:05.720> us<00:01:05.750> a<00:01:05.840> little<00:01:05.930> bit<00:01:06.140> how<00:01:06.950> this<00:01:07.130> happened 00:01:07.539 --> 00:01:07.549 align:start position:0% tell us a little bit how this happened 00:01:07.549 --> 00:01:09.550 align:start position:0% tell us a little bit how this happened why<00:01:08.030> stumbleupon<00:01:08.659> needed<00:01:09.020> something<00:01:09.409> like 00:01:09.550 --> 00:01:09.560 align:start position:0% why stumbleupon needed something like 00:01:09.560 --> 00:01:12.069 align:start position:0% why stumbleupon needed something like HBase<00:01:10.009> and<00:01:10.820> can<00:01:11.450> what<00:01:11.659> are<00:01:11.689> the<00:01:11.869> crucial 00:01:12.069 --> 00:01:12.079 align:start position:0% HBase and can what are the crucial 00:01:12.079 --> 00:01:14.529 align:start position:0% HBase and can what are the crucial lessons<00:01:12.829> he<00:01:12.920> learned<00:01:12.950> working<00:01:13.549> on<00:01:13.880> each<00:01:14.179> place 00:01:14.529 --> 00:01:14.539 align:start position:0% lessons he learned working on each place 00:01:14.539 --> 00:01:17.169 align:start position:0% lessons he learned working on each place there<00:01:14.920> that's<00:01:15.920> a<00:01:16.009> little<00:01:16.100> lot<00:01:16.759> of<00:01:16.820> questions 00:01:17.169 --> 00:01:17.179 align:start position:0% there that's a little lot of questions 00:01:17.179 --> 00:01:20.279 align:start position:0% there that's a little lot of questions so<00:01:17.929> if<00:01:18.170> we<00:01:18.289> start<00:01:18.350> from<00:01:19.070> the<00:01:19.219> beginning<00:01:19.549> so 00:01:20.279 --> 00:01:20.289 align:start position:0% so if we start from the beginning so 00:01:20.289 --> 00:01:22.870 align:start position:0% so if we start from the beginning so stumbleupon<00:01:21.289> was<00:01:21.439> funded<00:01:21.859> like<00:01:22.310> both<00:01:22.549> for 00:01:22.870 --> 00:01:22.880 align:start position:0% stumbleupon was funded like both for 00:01:22.880 --> 00:01:24.399 align:start position:0% stumbleupon was funded like both for Canadians<00:01:23.270> one<00:01:23.539> of<00:01:23.630> them<00:01:23.749> garrett<00:01:24.020> camp<00:01:24.259> who 00:01:24.399 --> 00:01:24.409 align:start position:0% Canadians one of them garrett camp who 00:01:24.409 --> 00:01:27.639 align:start position:0% Canadians one of them garrett camp who is<00:01:24.469> now<00:01:24.619> the<00:01:24.649> chairman<00:01:25.219> of<00:01:25.310> uber<00:01:25.640> so<00:01:26.539> back<00:01:27.499> then 00:01:27.639 --> 00:01:27.649 align:start position:0% is now the chairman of uber so back then 00:01:27.649 --> 00:01:29.859 align:start position:0% is now the chairman of uber so back then would<00:01:27.799> stumble<00:01:28.039> upon<00:01:28.219> what<00:01:28.520> he<00:01:28.609> saw<00:01:28.880> is<00:01:29.149> that 00:01:29.859 --> 00:01:29.869 align:start position:0% would stumble upon what he saw is that 00:01:29.869 --> 00:01:31.480 align:start position:0% would stumble upon what he saw is that they<00:01:29.960> have<00:01:30.140> a<00:01:30.170> business<00:01:30.740> model<00:01:30.979> that<00:01:31.219> can 00:01:31.480 --> 00:01:31.490 align:start position:0% they have a business model that can 00:01:31.490 --> 00:01:34.330 align:start position:0% they have a business model that can scale<00:01:31.700> and<00:01:31.939> Finn<00:01:32.090> Utley<00:01:32.679> as<00:01:33.679> long<00:01:33.890> as<00:01:34.070> they<00:01:34.189> can 00:01:34.330 --> 00:01:34.340 align:start position:0% scale and Finn Utley as long as they can 00:01:34.340 --> 00:01:35.770 align:start position:0% scale and Finn Utley as long as they can get<00:01:34.490> more<00:01:34.850> traffic<00:01:35.060> they<00:01:35.329> can<00:01:35.450> make<00:01:35.600> more 00:01:35.770 --> 00:01:35.780 align:start position:0% get more traffic they can make more 00:01:35.780 --> 00:01:37.809 align:start position:0% get more traffic they can make more money<00:01:35.840> so<00:01:36.289> they're<00:01:36.409> like<00:01:36.560> so<00:01:36.770> well<00:01:37.520> we<00:01:37.670> have 00:01:37.809 --> 00:01:37.819 align:start position:0% money so they're like so well we have 00:01:37.819 --> 00:01:40.090 align:start position:0% money so they're like so well we have this<00:01:37.850> infrastructure<00:01:38.210> with<00:01:38.719> my<00:01:38.840> sequel<00:01:39.289> it's 00:01:40.090 --> 00:01:40.100 align:start position:0% this infrastructure with my sequel it's 00:01:40.100 --> 00:01:42.760 align:start position:0% this infrastructure with my sequel it's scales<00:01:40.850> I<00:01:41.090> mean<00:01:41.479> you<00:01:41.840> can<00:01:41.990> make<00:01:42.170> it<00:01:42.289> scale<00:01:42.499> but 00:01:42.760 --> 00:01:42.770 align:start position:0% scales I mean you can make it scale but 00:01:42.770 --> 00:01:43.929 align:start position:0% scales I mean you can make it scale but like<00:01:42.920> is<00:01:43.039> there<00:01:43.189> something<00:01:43.490> better<00:01:43.700> out<00:01:43.819> there 00:01:43.929 --> 00:01:43.939 align:start position:0% like is there something better out there 00:01:43.939 --> 00:01:46.179 align:start position:0% like is there something better out there that<00:01:44.210> we<00:01:44.299> can<00:01:44.479> like<00:01:45.109> put<00:01:45.590> the<00:01:45.649> whole 00:01:46.179 --> 00:01:46.189 align:start position:0% that we can like put the whole 00:01:46.189 --> 00:01:47.830 align:start position:0% that we can like put the whole application<00:01:46.310> on<00:01:46.789> it<00:01:46.939> and<00:01:47.090> continue<00:01:47.479> scaling 00:01:47.830 --> 00:01:47.840 align:start position:0% application on it and continue scaling 00:01:47.840 --> 00:01:51.039 align:start position:0% application on it and continue scaling up<00:01:47.990> he<00:01:48.979> identified<00:01:49.600> actually<00:01:50.600> if<00:01:50.719> he<00:01:50.780> I<00:01:50.810> didn't 00:01:51.039 --> 00:01:51.049 align:start position:0% up he identified actually if he I didn't 00:01:51.049 --> 00:01:52.450 align:start position:0% up he identified actually if he I didn't feel<00:01:51.139> a<00:01:51.200> bunch<00:01:51.350> of<00:01:51.499> things<00:01:51.799> but<00:01:51.950> then<00:01:52.069> he<00:01:52.189> hired 00:01:52.450 --> 00:01:52.460 align:start position:0% feel a bunch of things but then he hired 00:01:52.460 --> 00:01:55.029 align:start position:0% feel a bunch of things but then he hired ryan<00:01:53.090> rawson<00:01:53.539> who<00:01:54.079> wasn't<00:01:54.409> at<00:01:54.499> Google<00:01:54.920> I 00:01:55.029 --> 00:01:55.039 align:start position:0% ryan rawson who wasn't at Google I 00:01:55.039 --> 00:01:57.520 align:start position:0% ryan rawson who wasn't at Google I believe<00:01:55.310> mm-hmm<00:01:55.850> and<00:01:55.969> he<00:01:56.719> tasked<00:01:57.049> Ryan<00:01:57.229> back 00:01:57.520 --> 00:01:57.530 align:start position:0% believe mm-hmm and he tasked Ryan back 00:01:57.530 --> 00:02:00.029 align:start position:0% believe mm-hmm and he tasked Ryan back then<00:01:57.740> to<00:01:58.149> find<00:01:59.149> what<00:01:59.450> what<00:01:59.719> would<00:01:59.869> the 00:02:00.029 --> 00:02:00.039 align:start position:0% then to find what what would the 00:02:00.039 --> 00:02:03.129 align:start position:0% then to find what what would the database<00:02:01.039> be<00:02:01.249> he<00:02:02.209> eventually<00:02:02.420> picked<00:02:02.780> h<00:02:02.899> place 00:02:03.129 --> 00:02:03.139 align:start position:0% database be he eventually picked h place 00:02:03.139 --> 00:02:05.139 align:start position:0% database be he eventually picked h place and<00:02:03.469> then<00:02:03.829> we<00:02:03.920> he<00:02:04.249> built<00:02:04.459> a<00:02:04.549> team<00:02:04.700> around<00:02:04.880> that 00:02:05.139 --> 00:02:05.149 align:start position:0% and then we he built a team around that 00:02:05.149 --> 00:02:07.359 align:start position:0% and then we he built a team around that so<00:02:05.329> i<00:02:05.359> was<00:02:05.600> the<00:02:06.350> second<00:02:06.709> harder<00:02:06.950> to<00:02:07.100> work<00:02:07.219> on 00:02:07.359 --> 00:02:07.369 align:start position:0% so i was the second harder to work on 00:02:07.369 --> 00:02:11.230 align:start position:0% so i was the second harder to work on HBase<00:02:07.670> there<00:02:07.850> yes<00:02:08.500> so<00:02:09.729> how<00:02:10.729> did<00:02:10.789> this<00:02:11.060> happen 00:02:11.230 --> 00:02:11.240 align:start position:0% HBase there yes so how did this happen 00:02:11.240 --> 00:02:13.360 align:start position:0% HBase there yes so how did this happen right<00:02:11.510> basically<00:02:11.870> you<00:02:12.709> know<00:02:12.860> you<00:02:12.920> have<00:02:13.310> a 00:02:13.360 --> 00:02:13.370 align:start position:0% right basically you know you have a 00:02:13.370 --> 00:02:16.510 align:start position:0% right basically you know you have a standard<00:02:13.760> kind<00:02:14.300> of<00:02:14.480> data<00:02:15.440> requirement<00:02:16.190> for 00:02:16.510 --> 00:02:16.520 align:start position:0% standard kind of data requirement for 00:02:16.520 --> 00:02:18.470 align:start position:0% standard kind of data requirement for web<00:02:17.210> scale<00:02:17.450> storage<00:02:17.630> never 00:02:18.470 --> 00:02:18.480 align:start position:0% web scale storage never 00:02:18.480 --> 00:02:21.140 align:start position:0% web scale storage never body<00:02:18.629> did<00:02:19.170> Charlotte<00:02:19.530> my<00:02:19.680> sequel<00:02:20.069> it<00:02:20.489> was<00:02:20.970> good 00:02:21.140 --> 00:02:21.150 align:start position:0% body did Charlotte my sequel it was good 00:02:21.150 --> 00:02:23.059 align:start position:0% body did Charlotte my sequel it was good enough<00:02:21.330> for<00:02:21.390> facebook<00:02:21.900> you<00:02:22.170> know<00:02:22.290> how<00:02:22.769> did<00:02:23.010> you 00:02:23.059 --> 00:02:23.069 align:start position:0% enough for facebook you know how did you 00:02:23.069 --> 00:02:26.270 align:start position:0% enough for facebook you know how did you guys<00:02:23.250> decide<00:02:23.640> to<00:02:24.200> to<00:02:25.200> implement<00:02:25.830> edge<00:02:26.010> base 00:02:26.270 --> 00:02:26.280 align:start position:0% guys decide to to implement edge base 00:02:26.280 --> 00:02:29.210 align:start position:0% guys decide to to implement edge base and<00:02:26.670> a<00:02:26.970> pistol<00:02:27.269> was<00:02:27.569> all<00:02:27.750> the<00:02:27.870> work<00:02:28.140> to<00:02:28.440> do<00:02:29.040> this 00:02:29.210 --> 00:02:29.220 align:start position:0% and a pistol was all the work to do this 00:02:29.220 --> 00:02:31.070 align:start position:0% and a pistol was all the work to do this and<00:02:29.519> how<00:02:29.700> did<00:02:29.760> you<00:02:29.970> manage<00:02:30.209> to<00:02:30.420> do<00:02:30.690> this<00:02:30.720> kind 00:02:31.070 --> 00:02:31.080 align:start position:0% and how did you manage to do this kind 00:02:31.080 --> 00:02:34.130 align:start position:0% and how did you manage to do this kind of<00:02:31.230> when<00:02:31.560> while<00:02:32.209> maintaining<00:02:33.209> stumbleupon 00:02:34.130 --> 00:02:34.140 align:start position:0% of when while maintaining stumbleupon 00:02:34.140 --> 00:02:35.869 align:start position:0% of when while maintaining stumbleupon going<00:02:34.440> yeah<00:02:34.799> that's<00:02:35.280> me<00:02:35.370> interesting<00:02:35.670> story 00:02:35.869 --> 00:02:35.879 align:start position:0% going yeah that's me interesting story 00:02:35.879 --> 00:02:38.030 align:start position:0% going yeah that's me interesting story because<00:02:36.000> when<00:02:36.420> when<00:02:37.080> we<00:02:37.200> started<00:02:37.500> using<00:02:37.620> hbss 00:02:38.030 --> 00:02:38.040 align:start position:0% because when when we started using hbss 00:02:38.040 --> 00:02:39.500 align:start position:0% because when when we started using hbss stumbleupon<00:02:38.549> so<00:02:38.640> these<00:02:38.849> are<00:02:39.030> using<00:02:39.360> it<00:02:39.480> just 00:02:39.500 --> 00:02:39.510 align:start position:0% stumbleupon so these are using it just 00:02:39.510 --> 00:02:41.900 align:start position:0% stumbleupon so these are using it just before<00:02:39.870> I<00:02:40.080> came<00:02:40.200> on<00:02:40.410> and<00:02:40.709> exactly<00:02:41.549> six<00:02:41.760> years 00:02:41.900 --> 00:02:41.910 align:start position:0% before I came on and exactly six years 00:02:41.910 --> 00:02:45.199 align:start position:0% before I came on and exactly six years ago<00:02:42.120> in<00:02:42.239> 2009<00:02:42.830> and<00:02:43.830> back<00:02:44.250> then<00:02:44.459> hdfs<00:02:45.000> didn't 00:02:45.199 --> 00:02:45.209 align:start position:0% ago in 2009 and back then hdfs didn't 00:02:45.209 --> 00:02:47.720 align:start position:0% ago in 2009 and back then hdfs didn't have<00:02:45.390> data<00:02:46.319> durability<00:02:46.680> guarantees<00:02:47.280> like<00:02:47.579> so 00:02:47.720 --> 00:02:47.730 align:start position:0% have data durability guarantees like so 00:02:47.730 --> 00:02:49.009 align:start position:0% have data durability guarantees like so if<00:02:47.849> you<00:02:47.940> lose<00:02:48.090> a<00:02:48.120> machine<00:02:48.450> you<00:02:48.480> actually<00:02:48.870> lose 00:02:49.009 --> 00:02:49.019 align:start position:0% if you lose a machine you actually lose 00:02:49.019 --> 00:02:51.289 align:start position:0% if you lose a machine you actually lose data<00:02:49.400> so<00:02:50.400> it<00:02:50.489> was<00:02:50.610> in<00:02:50.849> the<00:02:50.940> beginning<00:02:51.030> a<00:02:51.269> very 00:02:51.289 --> 00:02:51.299 align:start position:0% data so it was in the beginning a very 00:02:51.299 --> 00:02:53.600 align:start position:0% data so it was in the beginning a very wild<00:02:51.690> ride<00:02:51.989> so<00:02:52.260> they<00:02:52.620> just<00:02:52.650> first<00:02:53.099> identified 00:02:53.600 --> 00:02:53.610 align:start position:0% wild ride so they just first identified 00:02:53.610 --> 00:02:55.780 align:start position:0% wild ride so they just first identified the<00:02:53.760> things<00:02:53.970> that<00:02:54.120> they<00:02:54.239> needed<00:02:54.810> to<00:02:54.930> scale<00:02:55.319> the 00:02:55.780 --> 00:02:55.790 align:start position:0% the things that they needed to scale the 00:02:55.790 --> 00:02:58.099 align:start position:0% the things that they needed to scale the the<00:02:56.790> most<00:02:56.970> like<00:02:57.180> that<00:02:57.329> that<00:02:57.510> just<00:02:57.720> didn't<00:02:57.959> fit 00:02:58.099 --> 00:02:58.109 align:start position:0% the most like that that just didn't fit 00:02:58.109 --> 00:03:00.440 align:start position:0% the most like that that just didn't fit in<00:02:58.260> my<00:02:58.410> sequel<00:02:58.709> anymore<00:02:59.040> and<00:02:59.519> then<00:02:59.670> and<00:03:00.150> then 00:03:00.440 --> 00:03:00.450 align:start position:0% in my sequel anymore and then and then 00:03:00.450 --> 00:03:02.270 align:start position:0% in my sequel anymore and then and then like<00:03:00.780> the<00:03:01.290> rest<00:03:01.500> was<00:03:01.590> just<00:03:01.739> like<00:03:01.829> enough<00:03:02.099> flow 00:03:02.270 --> 00:03:02.280 align:start position:0% like the rest was just like enough flow 00:03:02.280 --> 00:03:03.740 align:start position:0% like the rest was just like enough flow there's<00:03:02.549> more<00:03:02.700> and<00:03:02.849> more<00:03:03.030> stuff<00:03:03.299> from<00:03:03.569> my 00:03:03.740 --> 00:03:03.750 align:start position:0% there's more and more stuff from my 00:03:03.750 --> 00:03:05.780 align:start position:0% there's more and more stuff from my sequel<00:03:04.109> and<00:03:04.260> what<00:03:04.410> remain<00:03:04.709> and<00:03:04.920> eventually<00:03:05.640> my 00:03:05.780 --> 00:03:05.790 align:start position:0% sequel and what remain and eventually my 00:03:05.790 --> 00:03:07.430 align:start position:0% sequel and what remain and eventually my secret<00:03:06.060> was<00:03:06.209> just<00:03:06.390> what<00:03:06.629> really<00:03:07.019> made<00:03:07.230> sense 00:03:07.430 --> 00:03:07.440 align:start position:0% secret was just what really made sense 00:03:07.440 --> 00:03:09.680 align:start position:0% secret was just what really made sense in<00:03:07.769> the<00:03:07.799> relational<00:03:08.310> world<00:03:08.549> all<00:03:09.299> the<00:03:09.540> other 00:03:09.680 --> 00:03:09.690 align:start position:0% in the relational world all the other 00:03:09.690 --> 00:03:11.150 align:start position:0% in the relational world all the other stuff<00:03:09.810> like<00:03:10.200> all<00:03:10.440> the<00:03:10.470> comments<00:03:10.950> they<00:03:11.010> were 00:03:11.150 --> 00:03:11.160 align:start position:0% stuff like all the comments they were 00:03:11.160 --> 00:03:13.250 align:start position:0% stuff like all the comments they were received<00:03:11.489> serve<00:03:11.790> straight<00:03:12.150> out<00:03:12.269> of<00:03:12.299> a<00:03:12.540> HBase 00:03:13.250 --> 00:03:13.260 align:start position:0% received serve straight out of a HBase 00:03:13.260 --> 00:03:16.099 align:start position:0% received serve straight out of a HBase I'll<00:03:13.829> declare<00:03:14.160> the<00:03:14.760> counters<00:03:15.480> the<00:03:15.660> badges 00:03:16.099 --> 00:03:16.109 align:start position:0% I'll declare the counters the badges 00:03:16.109 --> 00:03:18.220 align:start position:0% I'll declare the counters the badges that<00:03:16.140> was<00:03:16.500> all<00:03:16.620> done<00:03:16.739> in<00:03:16.769> HBase<00:03:17.129> mm-hmm 00:03:18.220 --> 00:03:18.230 align:start position:0% that was all done in HBase mm-hmm 00:03:18.230 --> 00:03:19.849 align:start position:0% that was all done in HBase mm-hmm interesting<00:03:19.230> so<00:03:19.349> they<00:03:19.440> took<00:03:19.560> a<00:03:19.680> big<00:03:19.829> risk 00:03:19.849 --> 00:03:19.859 align:start position:0% interesting so they took a big risk 00:03:19.859 --> 00:03:21.800 align:start position:0% interesting so they took a big risk Garrett<00:03:20.790> camp<00:03:21.000> actually<00:03:21.329> he<00:03:21.480> believes 00:03:21.800 --> 00:03:21.810 align:start position:0% Garrett camp actually he believes 00:03:21.810 --> 00:03:23.270 align:start position:0% Garrett camp actually he believes strongly<00:03:22.019> in<00:03:22.140> H<00:03:22.319> place<00:03:22.530> even<00:03:22.769> though<00:03:22.919> like 00:03:23.270 --> 00:03:23.280 align:start position:0% strongly in H place even though like 00:03:23.280 --> 00:03:24.650 align:start position:0% strongly in H place even though like back<00:03:23.549> then<00:03:23.700> as<00:03:23.910> I<00:03:24.030> said<00:03:24.180> didn't<00:03:24.419> have<00:03:24.510> their 00:03:24.650 --> 00:03:24.660 align:start position:0% back then as I said didn't have their 00:03:24.660 --> 00:03:26.900 align:start position:0% back then as I said didn't have their ability<00:03:24.989> maturity<00:03:25.950> was<00:03:26.250> like<00:03:26.549> it<00:03:26.730> was<00:03:26.849> a 00:03:26.900 --> 00:03:26.910 align:start position:0% ability maturity was like it was a 00:03:26.910 --> 00:03:29.270 align:start position:0% ability maturity was like it was a pretty<00:03:27.060> young<00:03:27.239> project<00:03:27.720> but<00:03:28.500> you<00:03:28.769> you<00:03:29.010> you 00:03:29.270 --> 00:03:29.280 align:start position:0% pretty young project but you you you 00:03:29.280 --> 00:03:30.979 align:start position:0% pretty young project but you you you read<00:03:29.459> the<00:03:29.579> big<00:03:29.730> table<00:03:30.030> paper<00:03:30.239> and<00:03:30.690> you<00:03:30.750> think 00:03:30.979 --> 00:03:30.989 align:start position:0% read the big table paper and you think 00:03:30.989 --> 00:03:33.140 align:start position:0% read the big table paper and you think man<00:03:31.260> maybe<00:03:31.769> I<00:03:31.889> maybe<00:03:32.400> I<00:03:32.549> can<00:03:32.700> have<00:03:32.880> my<00:03:33.000> own 00:03:33.140 --> 00:03:33.150 align:start position:0% man maybe I maybe I can have my own 00:03:33.150 --> 00:03:34.129 align:start position:0% man maybe I maybe I can have my own little<00:03:33.299> like<00:03:33.599> Google<00:03:34.049> infrastructure 00:03:34.129 --> 00:03:34.139 align:start position:0% little like Google infrastructure 00:03:34.139 --> 00:03:37.009 align:start position:0% little like Google infrastructure internally<00:03:34.950> right<00:03:35.190> mm-hmm<00:03:35.639> oh<00:03:35.910> so<00:03:36.599> i<00:03:36.780> just 00:03:37.009 --> 00:03:37.019 align:start position:0% internally right mm-hmm oh so i just 00:03:37.019 --> 00:03:38.690 align:start position:0% internally right mm-hmm oh so i just realized<00:03:37.410> when<00:03:37.769> you<00:03:37.859> mentioned<00:03:38.250> the<00:03:38.280> canadian 00:03:38.690 --> 00:03:38.700 align:start position:0% realized when you mentioned the canadian 00:03:38.700 --> 00:03:40.940 align:start position:0% realized when you mentioned the canadian origins<00:03:39.180> the<00:03:39.389> base<00:03:39.810> is<00:03:39.959> a<00:03:39.989> canadian<00:03:40.380> thing<00:03:40.410> no 00:03:40.940 --> 00:03:40.950 align:start position:0% origins the base is a canadian thing no 00:03:40.950 --> 00:03:42.740 align:start position:0% origins the base is a canadian thing no it's<00:03:41.099> not<00:03:41.160> it's<00:03:41.340> not<00:03:41.370> a<00:03:41.599> understand<00:03:42.599> herself 00:03:42.740 --> 00:03:42.750 align:start position:0% it's not it's not a understand herself 00:03:42.750 --> 00:03:44.629 align:start position:0% it's not it's not a understand herself okay<00:03:43.260> well<00:03:43.560> i<00:03:43.590> was<00:03:43.829> kind<00:03:44.010> of<00:03:44.040> funny<00:03:44.280> like<00:03:44.519> it 00:03:44.629 --> 00:03:44.639 align:start position:0% okay well i was kind of funny like it 00:03:44.639 --> 00:03:47.059 align:start position:0% okay well i was kind of funny like it all<00:03:44.910> came<00:03:45.090> into<00:03:45.269> focus<00:03:45.500> it's<00:03:46.500> interesting<00:03:46.650> it 00:03:47.059 --> 00:03:47.069 align:start position:0% all came into focus it's interesting it 00:03:47.069 --> 00:03:49.300 align:start position:0% all came into focus it's interesting it was<00:03:47.190> my<00:03:47.340> call<00:03:47.489> stack<00:03:47.730> and<00:03:47.940> Jim<00:03:48.510> Kellerman<00:03:48.959> at 00:03:49.300 --> 00:03:49.310 align:start position:0% was my call stack and Jim Kellerman at 00:03:49.310 --> 00:03:52.520 align:start position:0% was my call stack and Jim Kellerman at our<00:03:50.310> set<00:03:50.730> like<00:03:51.000> but<00:03:51.239> actually<00:03:51.510> they<00:03:52.049> took<00:03:52.410> it 00:03:52.520 --> 00:03:52.530 align:start position:0% our set like but actually they took it 00:03:52.530 --> 00:03:55.190 align:start position:0% our set like but actually they took it over<00:03:52.650> from<00:03:53.750> what's<00:03:54.750> his<00:03:54.870> face<00:03:55.019> will<00:03:55.169> be 00:03:55.190 --> 00:03:55.200 align:start position:0% over from what's his face will be 00:03:55.200 --> 00:03:57.710 align:start position:0% over from what's his face will be washing<00:03:55.530> girl<00:03:55.650> remember<00:03:56.010> but<00:03:56.940> it's<00:03:57.569> really 00:03:57.710 --> 00:03:57.720 align:start position:0% washing girl remember but it's really 00:03:57.720 --> 00:04:01.009 align:start position:0% washing girl remember but it's really stack<00:03:58.139> and<00:03:58.380> Jim<00:03:59.099> who<00:03:59.280> back<00:03:59.459> then<00:03:59.930> picked<00:04:00.930> up 00:04:01.009 --> 00:04:01.019 align:start position:0% stack and Jim who back then picked up 00:04:01.019 --> 00:04:03.470 align:start position:0% stack and Jim who back then picked up the<00:04:01.169> project<00:04:01.379> a<00:04:01.680> power<00:04:01.889> set<00:04:02.160> because<00:04:02.480> Chad 00:04:03.470 --> 00:04:03.480 align:start position:0% the project a power set because Chad 00:04:03.480 --> 00:04:05.449 align:start position:0% the project a power set because Chad there<00:04:03.780> Chad<00:04:04.169> Walters<00:04:04.560> I<00:04:04.829> remember<00:04:05.340> correctly 00:04:05.449 --> 00:04:05.459 align:start position:0% there Chad Walters I remember correctly 00:04:05.459 --> 00:04:07.909 align:start position:0% there Chad Walters I remember correctly like<00:04:06.419> they<00:04:06.810> had<00:04:06.989> pretty<00:04:07.169> much<00:04:07.260> same<00:04:07.530> issue<00:04:07.680> and 00:04:07.909 --> 00:04:07.919 align:start position:0% like they had pretty much same issue and 00:04:07.919 --> 00:04:10.159 align:start position:0% like they had pretty much same issue and they<00:04:08.010> had<00:04:08.129> the<00:04:08.280> same<00:04:08.459> goals<00:04:08.669> mm-hmm<00:04:09.510> but 00:04:10.159 --> 00:04:10.169 align:start position:0% they had the same goals mm-hmm but 00:04:10.169 --> 00:04:11.180 align:start position:0% they had the same goals mm-hmm but eventually<00:04:10.319> parcel<00:04:10.859> was<00:04:10.950> bought<00:04:11.099> by 00:04:11.180 --> 00:04:11.190 align:start position:0% eventually parcel was bought by 00:04:11.190 --> 00:04:14.420 align:start position:0% eventually parcel was bought by microsoft<00:04:11.340> yes<00:04:12.109> and<00:04:13.109> then<00:04:13.290> stack<00:04:13.709> also<00:04:14.280> came 00:04:14.420 --> 00:04:14.430 align:start position:0% microsoft yes and then stack also came 00:04:14.430 --> 00:04:17.089 align:start position:0% microsoft yes and then stack also came on<00:04:14.549> board<00:04:15.229> that's<00:04:16.229> not<00:04:16.410> ball<00:04:16.530> up<00:04:16.650> on<00:04:16.739> and<00:04:16.979> then 00:04:17.089 --> 00:04:17.099 align:start position:0% on board that's not ball up on and then 00:04:17.099 --> 00:04:20.060 align:start position:0% on board that's not ball up on and then we<00:04:17.609> had<00:04:17.729> our<00:04:17.820> own<00:04:17.940> little<00:04:18.680> HBase<00:04:19.680> Commodore<00:04:20.039> a 00:04:20.060 --> 00:04:20.070 align:start position:0% we had our own little HBase Commodore a 00:04:20.070 --> 00:04:21.770 align:start position:0% we had our own little HBase Commodore a team<00:04:20.250> i<00:04:20.340> stumbleupon<00:04:20.699> and<00:04:21.090> what<00:04:21.359> we<00:04:21.479> liked 00:04:21.770 --> 00:04:21.780 align:start position:0% team i stumbleupon and what we liked 00:04:21.780 --> 00:04:24.939 align:start position:0% team i stumbleupon and what we liked about<00:04:21.900> it<00:04:22.079> is<00:04:22.199> we<00:04:22.440> could<00:04:22.590> basically<00:04:23.310> like<00:04:23.940> a 00:04:24.939 --> 00:04:24.949 align:start position:0% about it is we could basically like a 00:04:24.949 --> 00:04:27.200 align:start position:0% about it is we could basically like a play<00:04:25.949> with<00:04:26.130> the<00:04:26.220> rest<00:04:26.400> of<00:04:26.520> the<00:04:26.610> community<00:04:26.789> as 00:04:27.200 --> 00:04:27.210 align:start position:0% play with the rest of the community as 00:04:27.210 --> 00:04:30.980 align:start position:0% play with the rest of the community as neutral<00:04:27.960> hmm<00:04:29.030> individuals<00:04:30.030> instead<00:04:30.750> of<00:04:30.870> we 00:04:30.980 --> 00:04:30.990 align:start position:0% neutral hmm individuals instead of we 00:04:30.990 --> 00:04:31.790 align:start position:0% neutral hmm individuals instead of we were 00:04:31.790 --> 00:04:31.800 align:start position:0% were 00:04:31.800 --> 00:04:33.290 align:start position:0% were and<00:04:31.889> vendors<00:04:32.340> like<00:04:32.550> we're<00:04:32.729> not<00:04:32.819> making<00:04:33.090> money 00:04:33.290 --> 00:04:33.300 align:start position:0% and vendors like we're not making money 00:04:33.300 --> 00:04:36.050 align:start position:0% and vendors like we're not making money directly<00:04:33.900> from<00:04:34.349> selling<00:04:34.740> HP<00:04:34.889> right<00:04:35.490> all<00:04:35.879> right 00:04:36.050 --> 00:04:36.060 align:start position:0% directly from selling HP right all right 00:04:36.060 --> 00:04:38.059 align:start position:0% directly from selling HP right all right I<00:04:36.300> think<00:04:36.659> this<00:04:36.900> is<00:04:36.960> fascinating<00:04:37.199> right<00:04:37.590> and<00:04:37.800> so 00:04:38.059 --> 00:04:38.069 align:start position:0% I think this is fascinating right and so 00:04:38.069 --> 00:04:42.980 align:start position:0% I think this is fascinating right and so so<00:04:38.729> the<00:04:39.509> way<00:04:39.659> kind<00:04:39.990> of<00:04:40.460> it<00:04:41.460> was<00:04:41.639> adopted<00:04:42.060> and<00:04:42.539> I 00:04:42.980 --> 00:04:42.990 align:start position:0% so the way kind of it was adopted and I 00:04:42.990 --> 00:04:44.990 align:start position:0% so the way kind of it was adopted and I mean<00:04:43.139> clearly<00:04:43.590> serves<00:04:44.039> the<00:04:44.280> king<00:04:44.460> he<00:04:44.580> tries<00:04:44.849> I 00:04:44.990 --> 00:04:45.000 align:start position:0% mean clearly serves the king he tries I 00:04:45.000 --> 00:04:46.820 align:start position:0% mean clearly serves the king he tries I quit<00:04:45.210> it<00:04:45.389> serves<00:04:45.900> the<00:04:46.020> need<00:04:46.169> of<00:04:46.199> data<00:04:46.470> store 00:04:46.820 --> 00:04:46.830 align:start position:0% quit it serves the need of data store 00:04:46.830 --> 00:04:49.460 align:start position:0% quit it serves the need of data store and<00:04:47.039> we<00:04:47.280> see<00:04:47.460> this<00:04:47.580> theme<00:04:47.819> recurring<00:04:48.000> and<00:04:48.629> it's 00:04:49.460 --> 00:04:49.470 align:start position:0% and we see this theme recurring and it's 00:04:49.470 --> 00:04:51.080 align:start position:0% and we see this theme recurring and it's an<00:04:49.590> avoidable<00:04:50.009> you<00:04:50.460> know<00:04:50.550> people<00:04:50.729> build 00:04:51.080 --> 00:04:51.090 align:start position:0% an avoidable you know people build 00:04:51.090 --> 00:04:52.610 align:start position:0% an avoidable you know people build different<00:04:51.240> engines<00:04:51.990> that<00:04:52.139> have<00:04:52.169> stream 00:04:52.610 --> 00:04:52.620 align:start position:0% different engines that have stream 00:04:52.620 --> 00:04:55.129 align:start position:0% different engines that have stream intentions<00:04:53.220> and<00:04:53.460> spark<00:04:54.060> right<00:04:54.330> but<00:04:54.479> still<00:04:55.020> you 00:04:55.129 --> 00:04:55.139 align:start position:0% intentions and spark right but still you 00:04:55.139 --> 00:04:56.600 align:start position:0% intentions and spark right but still you need<00:04:55.229> to<00:04:55.349> source<00:04:55.530> so<00:04:55.650> so<00:04:56.099> it's<00:04:56.220> very<00:04:56.310> anxious 00:04:56.600 --> 00:04:56.610 align:start position:0% need to source so so it's very anxious 00:04:56.610 --> 00:04:58.969 align:start position:0% need to source so so it's very anxious for<00:04:56.759> me<00:04:56.879> that<00:04:57.180> that<00:04:57.509> you<00:04:58.020> now<00:04:58.289> work<00:04:58.470> on<00:04:58.620> CUDA<00:04:58.830> so 00:04:58.969 --> 00:04:58.979 align:start position:0% for me that that you now work on CUDA so 00:04:58.979 --> 00:05:00.649 align:start position:0% for me that that you now work on CUDA so maybe<00:04:59.129> you<00:04:59.340> can<00:04:59.520> tell<00:04:59.699> us<00:04:59.729> I<00:05:00.000> mean<00:05:00.330> you<00:05:00.539> will 00:05:00.649 --> 00:05:00.659 align:start position:0% maybe you can tell us I mean you will 00:05:00.659 --> 00:05:02.619 align:start position:0% maybe you can tell us I mean you will have<00:05:00.810> a<00:05:00.840> technical<00:05:01.050> talk<00:05:01.319> but<00:05:01.500> but<00:05:01.979> kind<00:05:02.370> of 00:05:02.619 --> 00:05:02.629 align:start position:0% have a technical talk but but kind of 00:05:02.629 --> 00:05:05.270 align:start position:0% have a technical talk but but kind of obviously<00:05:03.629> HBase<00:05:03.990> was<00:05:04.169> not<00:05:04.319> enough<00:05:04.590> right 00:05:05.270 --> 00:05:05.280 align:start position:0% obviously HBase was not enough right 00:05:05.280 --> 00:05:06.379 align:start position:0% obviously HBase was not enough right because<00:05:05.400> the<00:05:05.580> fish<00:05:05.729> way<00:05:05.909> to<00:05:05.969> solve<00:05:06.240> all<00:05:06.270> the 00:05:06.379 --> 00:05:06.389 align:start position:0% because the fish way to solve all the 00:05:06.389 --> 00:05:08.680 align:start position:0% because the fish way to solve all the problems<00:05:06.719> you<00:05:06.930> will<00:05:06.990> just<00:05:07.199> do<00:05:07.409> is<00:05:07.469> base<00:05:07.680> right 00:05:08.680 --> 00:05:08.690 align:start position:0% problems you will just do is base right 00:05:08.690 --> 00:05:11.510 align:start position:0% problems you will just do is base right so<00:05:09.690> I<00:05:09.840> mean<00:05:10.050> this<00:05:10.169> is<00:05:10.229> this<00:05:10.620> is<00:05:10.770> basically<00:05:11.190> what 00:05:11.510 --> 00:05:11.520 align:start position:0% so I mean this is this is basically what 00:05:11.520 --> 00:05:13.100 align:start position:0% so I mean this is this is basically what I'm<00:05:11.639> coming<00:05:11.969> in<00:05:12.060> with<00:05:12.090> this<00:05:12.509> man<00:05:12.719> song<00:05:12.930> from 00:05:13.100 --> 00:05:13.110 align:start position:0% I'm coming in with this man song from 00:05:13.110 --> 00:05:15.379 align:start position:0% I'm coming in with this man song from right<00:05:13.710> and<00:05:14.340> I<00:05:14.490> think<00:05:14.699> it's<00:05:14.819> very<00:05:14.909> interested 00:05:15.379 --> 00:05:15.389 align:start position:0% right and I think it's very interested 00:05:15.389 --> 00:05:17.779 align:start position:0% right and I think it's very interested you<00:05:15.599> of<00:05:15.690> all<00:05:15.810> people<00:05:16.110> bourquin<00:05:16.800> kudo<00:05:17.099> right<00:05:17.639> so 00:05:17.779 --> 00:05:17.789 align:start position:0% you of all people bourquin kudo right so 00:05:17.789 --> 00:05:19.580 align:start position:0% you of all people bourquin kudo right so maybe<00:05:17.879> you<00:05:18.030> can<00:05:18.150> explain<00:05:18.270> basically<00:05:19.139> how<00:05:19.409> this 00:05:19.580 --> 00:05:19.590 align:start position:0% maybe you can explain basically how this 00:05:19.590 --> 00:05:21.770 align:start position:0% maybe you can explain basically how this happened<00:05:19.919> and<00:05:20.069> why<00:05:20.430> we<00:05:20.819> need<00:05:20.940> to<00:05:21.090> do<00:05:21.240> is<00:05:21.539> kind 00:05:21.770 --> 00:05:21.780 align:start position:0% happened and why we need to do is kind 00:05:21.780 --> 00:05:24.709 align:start position:0% happened and why we need to do is kind of<00:05:22.039> next<00:05:23.039> thing<00:05:23.280> is<00:05:23.639> it<00:05:23.849> a<00:05:23.940> success<00:05:24.270> sir<00:05:24.449> touch 00:05:24.709 --> 00:05:24.719 align:start position:0% of next thing is it a success sir touch 00:05:24.719 --> 00:05:27.770 align:start position:0% of next thing is it a success sir touch base<00:05:24.930> is<00:05:25.139> it<00:05:25.259> a<00:05:25.349> complementary<00:05:25.949> thing<00:05:26.310> how<00:05:27.060> how 00:05:27.770 --> 00:05:27.780 align:start position:0% base is it a complementary thing how how 00:05:27.780 --> 00:05:30.050 align:start position:0% base is it a complementary thing how how we're<00:05:28.110> could<00:05:28.620> is<00:05:28.800> on<00:05:28.979> this<00:05:29.159> spectrum<00:05:29.759> of<00:05:29.879> data 00:05:30.050 --> 00:05:30.060 align:start position:0% we're could is on this spectrum of data 00:05:30.060 --> 00:05:32.899 align:start position:0% we're could is on this spectrum of data databases<00:05:30.810> right<00:05:31.289> well<00:05:31.919> so<00:05:32.129> like<00:05:32.490> stonebraker 00:05:32.899 --> 00:05:32.909 align:start position:0% databases right well so like stonebraker 00:05:32.909 --> 00:05:35.689 align:start position:0% databases right well so like stonebraker said<00:05:33.240> one<00:05:33.629> size<00:05:33.810> doesn't<00:05:34.050> fit<00:05:34.169> all<00:05:34.289> so<00:05:35.129> H<00:05:35.460> plays 00:05:35.689 --> 00:05:35.699 align:start position:0% said one size doesn't fit all so H plays 00:05:35.699 --> 00:05:38.450 align:start position:0% said one size doesn't fit all so H plays very<00:05:36.300> solid<00:05:36.690> database<00:05:37.139> but<00:05:37.440> most<00:05:37.919> of<00:05:38.130> all<00:05:38.250> your 00:05:38.450 --> 00:05:38.460 align:start position:0% very solid database but most of all your 00:05:38.460 --> 00:05:40.760 align:start position:0% very solid database but most of all your problems<00:05:38.819> all<00:05:39.029> at<00:05:39.210> the<00:05:39.270> same<00:05:39.419> time<00:05:39.590> and<00:05:40.590> on<00:05:40.740> a 00:05:40.760 --> 00:05:40.770 align:start position:0% problems all at the same time and on a 00:05:40.770 --> 00:05:42.409 align:start position:0% problems all at the same time and on a more<00:05:40.889> personal<00:05:41.340> level<00:05:41.580> I<00:05:41.940> had<00:05:42.090> been<00:05:42.270> working 00:05:42.409 --> 00:05:42.419 align:start position:0% more personal level I had been working 00:05:42.419 --> 00:05:45.800 align:start position:0% more personal level I had been working on<00:05:42.659> HBase<00:05:42.990> for<00:05:43.949> four<00:05:44.460> or<00:05:44.490> five<00:05:44.610> years<00:05:44.789> and<00:05:45.690> when 00:05:45.800 --> 00:05:45.810 align:start position:0% on HBase for four or five years and when 00:05:45.810 --> 00:05:47.149 align:start position:0% on HBase for four or five years and when I<00:05:45.840> started<00:05:46.050> working<00:05:46.199> on<00:05:46.259> kudu<00:05:46.560> and<00:05:46.590> I<00:05:47.009> was 00:05:47.149 --> 00:05:47.159 align:start position:0% I started working on kudu and I was 00:05:47.159 --> 00:05:48.620 align:start position:0% I started working on kudu and I was ready<00:05:47.400> just<00:05:47.699> for<00:05:47.819> another<00:05:48.029> challenge<00:05:48.419> because 00:05:48.620 --> 00:05:48.630 align:start position:0% ready just for another challenge because 00:05:48.630 --> 00:05:50.059 align:start position:0% ready just for another challenge because HBase<00:05:48.900> was<00:05:49.020> like<00:05:49.139> the<00:05:49.259> first<00:05:49.409> thing<00:05:49.590> I<00:05:49.680> did<00:05:49.860> out 00:05:50.059 --> 00:05:50.069 align:start position:0% HBase was like the first thing I did out 00:05:50.069 --> 00:05:53.120 align:start position:0% HBase was like the first thing I did out of<00:05:50.180> university<00:05:51.180> okay<00:05:51.599> so<00:05:52.560> I<00:05:52.620> just<00:05:52.770> welcome<00:05:53.069> to 00:05:53.120 --> 00:05:53.130 align:start position:0% of university okay so I just welcome to 00:05:53.130 --> 00:05:55.399 align:start position:0% of university okay so I just welcome to challenge<00:05:53.490> also<00:05:54.180> a<00:05:54.210> different<00:05:54.419> language<00:05:54.840> c++ 00:05:55.399 --> 00:05:55.409 align:start position:0% challenge also a different language c++ 00:05:55.409 --> 00:05:57.439 align:start position:0% challenge also a different language c++ and<00:05:55.440> okay<00:05:56.009> so<00:05:56.580> what<00:05:56.759> could<00:05:56.880> you<00:05:56.969> tries<00:05:57.180> to<00:05:57.300> do 00:05:57.439 --> 00:05:57.449 align:start position:0% and okay so what could you tries to do 00:05:57.449 --> 00:06:01.070 align:start position:0% and okay so what could you tries to do it<00:05:58.380> tries<00:05:58.710> to<00:05:58.740> be<00:05:59.060> the<00:06:00.060> one<00:06:00.240> system<00:06:00.449> that<00:06:00.930> can 00:06:01.070 --> 00:06:01.080 align:start position:0% it tries to be the one system that can 00:06:01.080 --> 00:06:02.899 align:start position:0% it tries to be the one system that can replace<00:06:01.349> your<00:06:01.560> lambo<00:06:01.889> lab<00:06:02.190> the<00:06:02.340> architecture 00:06:02.899 --> 00:06:02.909 align:start position:0% replace your lambo lab the architecture 00:06:02.909 --> 00:06:04.939 align:start position:0% replace your lambo lab the architecture so<00:06:03.240> people<00:06:03.870> will<00:06:04.080> build<00:06:04.289> systems<00:06:04.680> where 00:06:04.939 --> 00:06:04.949 align:start position:0% so people will build systems where 00:06:04.949 --> 00:06:07.159 align:start position:0% so people will build systems where they're<00:06:05.340> going<00:06:05.550> to<00:06:05.610> have<00:06:05.789> that's<00:06:06.539> a<00:06:06.659> stream<00:06:07.139> of 00:06:07.159 --> 00:06:07.169 align:start position:0% they're going to have that's a stream of 00:06:07.169 --> 00:06:09.920 align:start position:0% they're going to have that's a stream of inserts<00:06:07.830> also<00:06:08.370> updates<00:06:08.729> and<00:06:08.909> deletes<00:06:09.000> that 00:06:09.920 --> 00:06:09.930 align:start position:0% inserts also updates and deletes that 00:06:09.930 --> 00:06:12.350 align:start position:0% inserts also updates and deletes that going<00:06:10.289> to<00:06:10.500> maybe<00:06:10.800> parque<00:06:11.610> files<00:06:11.849> then<00:06:12.210> they 00:06:12.350 --> 00:06:12.360 align:start position:0% going to maybe parque files then they 00:06:12.360 --> 00:06:15.050 align:start position:0% going to maybe parque files then they put<00:06:12.509> impala<00:06:12.840> on<00:06:12.960> top<00:06:13.229> or<00:06:13.469> some<00:06:13.740> other<00:06:14.060> query 00:06:15.050 --> 00:06:15.060 align:start position:0% put impala on top or some other query 00:06:15.060 --> 00:06:17.330 align:start position:0% put impala on top or some other query engine<00:06:15.180> hive<00:06:15.810> and<00:06:16.770> then<00:06:16.949> they<00:06:17.069> run<00:06:17.219> their 00:06:17.330 --> 00:06:17.340 align:start position:0% engine hive and then they run their 00:06:17.340 --> 00:06:20.540 align:start position:0% engine hive and then they run their analytics<00:06:17.789> and<00:06:18.060> the<00:06:18.870> problem<00:06:19.199> is<00:06:19.379> well<00:06:19.889> I<00:06:20.159> gfs 00:06:20.540 --> 00:06:20.550 align:start position:0% analytics and the problem is well I gfs 00:06:20.550 --> 00:06:24.350 align:start position:0% analytics and the problem is well I gfs is<00:06:21.199> right<00:06:22.199> runs<00:06:22.409> read<00:06:22.830> many<00:06:23.069> kind<00:06:23.819> of<00:06:23.909> system 00:06:24.350 --> 00:06:24.360 align:start position:0% is right runs read many kind of system 00:06:24.360 --> 00:06:26.450 align:start position:0% is right runs read many kind of system so<00:06:24.599> if<00:06:24.810> you<00:06:24.900> want<00:06:25.080> to<00:06:25.139> do<00:06:25.259> updates<00:06:25.680> and<00:06:26.009> you 00:06:26.450 --> 00:06:26.460 align:start position:0% so if you want to do updates and you 00:06:26.460 --> 00:06:28.430 align:start position:0% so if you want to do updates and you don't<00:06:26.639> have<00:06:26.729> a<00:06:26.759> system<00:06:27.060> like<00:06:27.180> HBase<00:06:27.569> then<00:06:28.229> you 00:06:28.430 --> 00:06:28.440 align:start position:0% don't have a system like HBase then you 00:06:28.440 --> 00:06:30.409 align:start position:0% don't have a system like HBase then you got<00:06:28.620> to<00:06:28.650> handle<00:06:29.069> your<00:06:29.279> own<00:06:29.310> compaction<00:06:30.120> of<00:06:30.300> the 00:06:30.409 --> 00:06:30.419 align:start position:0% got to handle your own compaction of the 00:06:30.419 --> 00:06:32.659 align:start position:0% got to handle your own compaction of the files<00:06:30.690> and<00:06:31.110> making<00:06:31.770> sure<00:06:31.919> that<00:06:32.069> the<00:06:32.129> data<00:06:32.279> that 00:06:32.659 --> 00:06:32.669 align:start position:0% files and making sure that the data that 00:06:32.669 --> 00:06:35.269 align:start position:0% files and making sure that the data that it<00:06:32.879> is<00:06:33.000> then<00:06:33.180> uploaded<00:06:33.719> into<00:06:33.840> whatever<00:06:34.620> a 00:06:35.269 --> 00:06:35.279 align:start position:0% it is then uploaded into whatever a 00:06:35.279 --> 00:06:38.540 align:start position:0% it is then uploaded into whatever a query<00:06:35.669> engine<00:06:35.759> that<00:06:36.060> you're<00:06:36.210> using<00:06:36.979> so<00:06:37.979> on<00:06:38.190> on 00:06:38.540 --> 00:06:38.550 align:start position:0% query engine that you're using so on on 00:06:38.550 --> 00:06:41.450 align:start position:0% query engine that you're using so on on the<00:06:38.789> other<00:06:38.909> side<00:06:39.710> you<00:06:40.710> can<00:06:40.830> use<00:06:40.949> HBase<00:06:41.279> for 00:06:41.450 --> 00:06:41.460 align:start position:0% the other side you can use HBase for 00:06:41.460 --> 00:06:43.189 align:start position:0% the other side you can use HBase for that<00:06:41.580> but<00:06:42.060> then<00:06:42.180> HBase<00:06:42.509> on<00:06:42.630> the<00:06:42.719> scan<00:06:42.960> side 00:06:43.189 --> 00:06:43.199 align:start position:0% that but then HBase on the scan side 00:06:43.199 --> 00:06:46.010 align:start position:0% that but then HBase on the scan side like<00:06:43.979> serious<00:06:44.279> long<00:06:44.940> sequential<00:06:45.449> read 00:06:46.010 --> 00:06:46.020 align:start position:0% like serious long sequential read 00:06:46.020 --> 00:06:48.140 align:start position:0% like serious long sequential read it's<00:06:46.259> very<00:06:47.039> slow<00:06:47.370> because<00:06:47.520> that's<00:06:47.759> not<00:06:47.849> really 00:06:48.140 --> 00:06:48.150 align:start position:0% it's very slow because that's not really 00:06:48.150 --> 00:06:50.510 align:start position:0% it's very slow because that's not really what<00:06:48.330> it<00:06:48.449> was<00:06:48.569> built<00:06:48.840> for<00:06:49.069> soku<00:06:50.069> do<00:06:50.190> what<00:06:50.430> it 00:06:50.510 --> 00:06:50.520 align:start position:0% what it was built for soku do what it 00:06:50.520 --> 00:06:54.950 align:start position:0% what it was built for soku do what it offers<00:06:50.940> is<00:06:51.270> like<00:06:52.199> being<00:06:52.560> on<00:06:52.860> one<00:06:53.759> hand<00:06:54.060> really 00:06:54.950 --> 00:06:54.960 align:start position:0% offers is like being on one hand really 00:06:54.960 --> 00:06:57.170 align:start position:0% offers is like being on one hand really doing<00:06:55.319> really<00:06:55.530> fast<00:06:55.889> sequential<00:06:56.310> reads 00:06:57.170 --> 00:06:57.180 align:start position:0% doing really fast sequential reads 00:06:57.180 --> 00:06:59.450 align:start position:0% doing really fast sequential reads mm-hmm<00:06:57.810> while<00:06:58.409> being<00:06:58.740> able<00:06:59.009> being<00:06:59.400> an 00:06:59.450 --> 00:06:59.460 align:start position:0% mm-hmm while being able being an 00:06:59.460 --> 00:07:01.430 align:start position:0% mm-hmm while being able being an updateable<00:06:59.909> store<00:07:00.120> mm-hmm<00:07:00.780> so<00:07:01.169> instead<00:07:01.379> of 00:07:01.430 --> 00:07:01.440 align:start position:0% updateable store mm-hmm so instead of 00:07:01.440 --> 00:07:03.379 align:start position:0% updateable store mm-hmm so instead of having<00:07:01.680> maybe<00:07:02.039> a<00:07:02.190> mix<00:07:02.520> of<00:07:02.669> HBase<00:07:02.970> and<00:07:03.150> follow 00:07:03.379 --> 00:07:03.389 align:start position:0% having maybe a mix of HBase and follow 00:07:03.389 --> 00:07:05.809 align:start position:0% having maybe a mix of HBase and follow or<00:07:03.750> your<00:07:03.930> whole<00:07:04.229> system<00:07:04.470> around<00:07:05.039> all<00:07:05.310> your<00:07:05.430> the 00:07:05.809 --> 00:07:05.819 align:start position:0% or your whole system around all your the 00:07:05.819 --> 00:07:07.279 align:start position:0% or your whole system around all your the managing<00:07:06.240> of<00:07:06.330> the<00:07:06.419> parkade<00:07:06.750> files<00:07:06.960> you<00:07:07.110> just 00:07:07.279 --> 00:07:07.289 align:start position:0% managing of the parkade files you just 00:07:07.289 --> 00:07:09.200 align:start position:0% managing of the parkade files you just have<00:07:07.379> one<00:07:07.590> system<00:07:07.889> it's<00:07:08.039> coo<00:07:08.190> do<00:07:08.340> it's<00:07:08.879> almost 00:07:09.200 --> 00:07:09.210 align:start position:0% have one system it's coo do it's almost 00:07:09.210 --> 00:07:11.839 align:start position:0% have one system it's coo do it's almost as<00:07:09.449> fast<00:07:09.690> when<00:07:09.960> you<00:07:10.139> do<00:07:10.379> sequential<00:07:10.849> scams 00:07:11.839 --> 00:07:11.849 align:start position:0% as fast when you do sequential scams 00:07:11.849 --> 00:07:13.700 align:start position:0% as fast when you do sequential scams when<00:07:12.449> you<00:07:12.509> do<00:07:12.629> scans<00:07:12.840> almost<00:07:13.319> as<00:07:13.409> fast<00:07:13.560> as 00:07:13.700 --> 00:07:13.710 align:start position:0% when you do scans almost as fast as 00:07:13.710 --> 00:07:16.369 align:start position:0% when you do scans almost as fast as parque<00:07:14.069> and<00:07:14.610> almost<00:07:15.449> as<00:07:15.629> fast<00:07:15.840> for<00:07:16.110> random 00:07:16.369 --> 00:07:16.379 align:start position:0% parque and almost as fast for random 00:07:16.379 --> 00:07:18.379 align:start position:0% parque and almost as fast for random reads<00:07:16.650> on<00:07:16.949> the<00:07:17.310> other<00:07:17.430> side<00:07:17.639> as<00:07:18.000> HBase 00:07:18.379 --> 00:07:18.389 align:start position:0% reads on the other side as HBase 00:07:18.389 --> 00:07:20.899 align:start position:0% reads on the other side as HBase interesting<00:07:19.199> so<00:07:19.949> we<00:07:20.159> are<00:07:20.310> claiming<00:07:20.460> to<00:07:20.759> be<00:07:20.880> the 00:07:20.899 --> 00:07:20.909 align:start position:0% interesting so we are claiming to be the 00:07:20.909 --> 00:07:23.210 align:start position:0% interesting so we are claiming to be the best<00:07:21.240> right<00:07:21.810> we're<00:07:21.960> claiming<00:07:22.440> that<00:07:22.650> it's 00:07:23.210 --> 00:07:23.220 align:start position:0% best right we're claiming that it's 00:07:23.220 --> 00:07:25.460 align:start position:0% best right we're claiming that it's going<00:07:23.370> to<00:07:23.430> be<00:07:23.550> enough<00:07:23.819> for<00:07:24.090> your<00:07:24.240> needs<00:07:24.270> so<00:07:25.139> if 00:07:25.460 --> 00:07:25.470 align:start position:0% going to be enough for your needs so if 00:07:25.470 --> 00:07:28.370 align:start position:0% going to be enough for your needs so if you<00:07:25.620> can<00:07:25.800> do<00:07:25.919> very<00:07:26.099> fast<00:07:26.630> sequential<00:07:27.630> scales 00:07:28.370 --> 00:07:28.380 align:start position:0% you can do very fast sequential scales 00:07:28.380 --> 00:07:30.680 align:start position:0% you can do very fast sequential scales it<00:07:29.130> means<00:07:29.520> so<00:07:29.759> it's<00:07:29.880> kind<00:07:30.060> of<00:07:30.120> it's<00:07:30.300> good 00:07:30.680 --> 00:07:30.690 align:start position:0% it means so it's kind of it's good 00:07:30.690 --> 00:07:32.719 align:start position:0% it means so it's kind of it's good solution<00:07:31.380> for<00:07:31.409> streaming<00:07:32.009> data<00:07:32.190> so<00:07:32.460> if<00:07:32.610> you 00:07:32.719 --> 00:07:32.729 align:start position:0% solution for streaming data so if you 00:07:32.729 --> 00:07:34.550 align:start position:0% solution for streaming data so if you have<00:07:32.880> some<00:07:33.000> like<00:07:33.120> Kafka<00:07:33.330> right<00:07:34.139> when<00:07:34.289> you<00:07:34.380> have 00:07:34.550 --> 00:07:34.560 align:start position:0% have some like Kafka right when you have 00:07:34.560 --> 00:07:36.320 align:start position:0% have some like Kafka right when you have a<00:07:34.680> lot<00:07:34.860> of<00:07:34.889> stuff<00:07:35.190> so<00:07:35.310> normally<00:07:35.699> people<00:07:35.940> debug 00:07:36.320 --> 00:07:36.330 align:start position:0% a lot of stuff so normally people debug 00:07:36.330 --> 00:07:38.240 align:start position:0% a lot of stuff so normally people debug the<00:07:36.599> stream<00:07:36.810> systems<00:07:37.229> by<00:07:37.440> having<00:07:37.800> that<00:07:37.830> dating 00:07:38.240 --> 00:07:38.250 align:start position:0% the stream systems by having that dating 00:07:38.250 --> 00:07:40.640 align:start position:0% the stream systems by having that dating Kafka<00:07:38.669> and<00:07:38.819> then<00:07:39.389> winding<00:07:40.110> and<00:07:40.259> we're<00:07:40.380> playing 00:07:40.640 --> 00:07:40.650 align:start position:0% Kafka and then winding and we're playing 00:07:40.650 --> 00:07:42.290 align:start position:0% Kafka and then winding and we're playing everything<00:07:41.430> right<00:07:41.639> look<00:07:41.729> like<00:07:41.909> this<00:07:42.120> is 00:07:42.290 --> 00:07:42.300 align:start position:0% everything right look like this is 00:07:42.300 --> 00:07:44.809 align:start position:0% everything right look like this is typical<00:07:43.050> sparks<00:07:43.349> Truman's<00:07:43.500> a<00:07:43.830> top<00:07:44.009> right<00:07:44.639> so 00:07:44.809 --> 00:07:44.819 align:start position:0% typical sparks Truman's a top right so 00:07:44.819 --> 00:07:48.589 align:start position:0% typical sparks Truman's a top right so you<00:07:44.879> have<00:07:45.150> Kafka<00:07:45.840> going<00:07:46.110> to<00:07:46.229> spark<00:07:46.530> so<00:07:47.389> you<00:07:48.389> can 00:07:48.589 --> 00:07:48.599 align:start position:0% you have Kafka going to spark so you can 00:07:48.599 --> 00:07:50.029 align:start position:0% you have Kafka going to spark so you can I<00:07:48.659> mean<00:07:48.780> it<00:07:48.990> sounds<00:07:49.199> like<00:07:49.500> I<00:07:49.560> should<00:07:49.740> be<00:07:49.979> able 00:07:50.029 --> 00:07:50.039 align:start position:0% I mean it sounds like I should be able 00:07:50.039 --> 00:07:52.189 align:start position:0% I mean it sounds like I should be able to<00:07:50.280> use<00:07:50.430> kudu<00:07:50.880> for<00:07:51.270> the<00:07:51.360> same<00:07:51.539> thing<00:07:51.810> like<00:07:52.020> can 00:07:52.189 --> 00:07:52.199 align:start position:0% to use kudu for the same thing like can 00:07:52.199 --> 00:07:53.809 align:start position:0% to use kudu for the same thing like can it<00:07:52.229> be<00:07:52.469> like<00:07:52.590> a<00:07:52.650> permanent<00:07:52.889> storage<00:07:53.310> or 00:07:53.809 --> 00:07:53.819 align:start position:0% it be like a permanent storage or 00:07:53.819 --> 00:07:56.300 align:start position:0% it be like a permanent storage or streaming<00:07:54.090> data<00:07:54.300> can<00:07:55.169> I<00:07:55.259> just<00:07:55.500> kind<00:07:55.650> of<00:07:55.710> store 00:07:56.300 --> 00:07:56.310 align:start position:0% streaming data can I just kind of store 00:07:56.310 --> 00:07:59.450 align:start position:0% streaming data can I just kind of store it<00:07:56.400> all<00:07:56.550> there<00:07:56.729> and<00:07:57.349> an<00:07:58.349> endlessly<00:07:59.009> and<00:07:59.219> then<00:07:59.370> I 00:07:59.450 --> 00:07:59.460 align:start position:0% it all there and an endlessly and then I 00:07:59.460 --> 00:08:01.159 align:start position:0% it all there and an endlessly and then I can<00:07:59.639> you<00:07:59.909> know<00:08:00.030> can<00:08:00.330> replace<00:08:00.690> some<00:08:00.930> of<00:08:00.960> this 00:08:01.159 --> 00:08:01.169 align:start position:0% can you know can replace some of this 00:08:01.169 --> 00:08:03.290 align:start position:0% can you know can replace some of this when<00:08:01.440> i'm<00:08:01.560> debugging<00:08:01.740> and<00:08:02.159> then<00:08:02.370> is<00:08:03.000> it<00:08:03.210> the 00:08:03.290 --> 00:08:03.300 align:start position:0% when i'm debugging and then is it the 00:08:03.300 --> 00:08:05.360 align:start position:0% when i'm debugging and then is it the kind<00:08:03.419> of<00:08:03.569> a<00:08:03.630> feasible<00:08:04.050> model<00:08:04.440> I<00:08:04.620> mean<00:08:05.219> yeah 00:08:05.360 --> 00:08:05.370 align:start position:0% kind of a feasible model I mean yeah 00:08:05.370 --> 00:08:06.769 align:start position:0% kind of a feasible model I mean yeah definitely<00:08:05.729> we<00:08:05.880> definitely<00:08:05.909> want<00:08:06.360> you<00:08:06.419> to<00:08:06.659> be 00:08:06.769 --> 00:08:06.779 align:start position:0% definitely we definitely want you to be 00:08:06.779 --> 00:08:09.080 align:start position:0% definitely we definitely want you to be your<00:08:06.930> one<00:08:07.229> data<00:08:07.469> store<00:08:07.770> and<00:08:08.009> in<00:08:08.099> those<00:08:08.310> kinds 00:08:09.080 --> 00:08:09.090 align:start position:0% your one data store and in those kinds 00:08:09.090 --> 00:08:11.600 align:start position:0% your one data store and in those kinds of<00:08:09.150> use<00:08:09.330> cases<00:08:09.949> because<00:08:10.949> what<00:08:11.370> we're<00:08:11.490> trying 00:08:11.600 --> 00:08:11.610 align:start position:0% of use cases because what we're trying 00:08:11.610 --> 00:08:13.399 align:start position:0% of use cases because what we're trying to<00:08:11.759> simplify<00:08:11.909> is<00:08:12.389> like<00:08:12.659> I<00:08:12.870> think<00:08:13.199> all<00:08:13.289> those 00:08:13.399 --> 00:08:13.409 align:start position:0% to simplify is like I think all those 00:08:13.409 --> 00:08:15.110 align:start position:0% to simplify is like I think all those different<00:08:13.650> storage<00:08:14.370> engines<00:08:14.729> that<00:08:14.880> you<00:08:15.000> have 00:08:15.110 --> 00:08:15.120 align:start position:0% different storage engines that you have 00:08:15.120 --> 00:08:16.580 align:start position:0% different storage engines that you have to<00:08:15.240> use<00:08:15.419> in<00:08:15.599> order<00:08:15.719> to<00:08:15.960> accomplish<00:08:16.169> whatever 00:08:16.580 --> 00:08:16.590 align:start position:0% to use in order to accomplish whatever 00:08:16.590 --> 00:08:20.450 align:start position:0% to use in order to accomplish whatever go<00:08:17.279> that<00:08:17.490> you<00:08:17.610> have<00:08:18.620> but<00:08:19.620> like<00:08:19.770> so<00:08:19.919> in<00:08:20.130> the<00:08:20.219> demo 00:08:20.450 --> 00:08:20.460 align:start position:0% go that you have but like so in the demo 00:08:20.460 --> 00:08:22.790 align:start position:0% go that you have but like so in the demo that<00:08:20.490> I'm<00:08:20.669> gonna<00:08:20.819> do<00:08:21.060> today<00:08:21.240> it's<00:08:21.630> 10<00:08:22.380> mollusca 00:08:22.790 --> 00:08:22.800 align:start position:0% that I'm gonna do today it's 10 mollusca 00:08:22.800 --> 00:08:24.439 align:start position:0% that I'm gonna do today it's 10 mollusca he<00:08:22.949> wrote<00:08:23.130> it<00:08:23.279> and<00:08:23.430> it's<00:08:23.550> you<00:08:23.969> have<00:08:24.120> like 00:08:24.439 --> 00:08:24.449 align:start position:0% he wrote it and it's you have like 00:08:24.449 --> 00:08:26.240 align:start position:0% he wrote it and it's you have like basically<00:08:24.930> online<00:08:25.590> games<00:08:25.800> are<00:08:25.979> being<00:08:26.130> played 00:08:26.240 --> 00:08:26.250 align:start position:0% basically online games are being played 00:08:26.250 --> 00:08:28.339 align:start position:0% basically online games are being played in<00:08:26.610> the<00:08:26.699> winners<00:08:27.120> and<00:08:27.479> then<00:08:27.599> there's<00:08:27.960> points 00:08:28.339 --> 00:08:28.349 align:start position:0% in the winners and then there's points 00:08:28.349 --> 00:08:30.529 align:start position:0% in the winners and then there's points all<00:08:28.800> that<00:08:29.009> data<00:08:29.159> is<00:08:29.340> being<00:08:29.520> streamed<00:08:29.880> likes<00:08:30.210> it 00:08:30.529 --> 00:08:30.539 align:start position:0% all that data is being streamed likes it 00:08:30.539 --> 00:08:32.959 align:start position:0% all that data is being streamed likes it directly<00:08:30.810> sent<00:08:31.050> to<00:08:31.139> Kafka<00:08:31.500> so<00:08:32.219> then<00:08:32.339> Kafka<00:08:32.729> can 00:08:32.959 --> 00:08:32.969 align:start position:0% directly sent to Kafka so then Kafka can 00:08:32.969 --> 00:08:34.940 align:start position:0% directly sent to Kafka so then Kafka can like<00:08:33.719> it's<00:08:34.020> a<00:08:34.110> permanent<00:08:34.500> Q<00:08:34.649> so<00:08:34.770> you<00:08:34.829> can 00:08:34.940 --> 00:08:34.950 align:start position:0% like it's a permanent Q so you can 00:08:34.950 --> 00:08:36.649 align:start position:0% like it's a permanent Q so you can buffer<00:08:35.250> up<00:08:35.370> like<00:08:35.669> if<00:08:36.060> there's<00:08:36.270> some<00:08:36.419> kind<00:08:36.630> of 00:08:36.649 --> 00:08:36.659 align:start position:0% buffer up like if there's some kind of 00:08:36.659 --> 00:08:38.870 align:start position:0% buffer up like if there's some kind of pushback<00:08:37.200> and<00:08:37.589> then<00:08:38.219> it<00:08:38.339> use<00:08:38.459> a<00:08:38.490> spark 00:08:38.870 --> 00:08:38.880 align:start position:0% pushback and then it use a spark 00:08:38.880 --> 00:08:41.269 align:start position:0% pushback and then it use a spark streaming<00:08:39.360> to<00:08:40.020> pull<00:08:40.260> from<00:08:40.469> kourou<00:08:40.829> on<00:08:41.070> one 00:08:41.269 --> 00:08:41.279 align:start position:0% streaming to pull from kourou on one 00:08:41.279 --> 00:08:42.860 align:start position:0% streaming to pull from kourou on one side<00:08:41.520> and<00:08:41.550> pull<00:08:41.849> from<00:08:42.029> kaka<00:08:42.390> and<00:08:42.599> the<00:08:42.719> other 00:08:42.860 --> 00:08:42.870 align:start position:0% side and pull from kaka and the other 00:08:42.870 --> 00:08:44.750 align:start position:0% side and pull from kaka and the other side<00:08:43.169> and<00:08:43.289> do<00:08:43.440> all<00:08:43.589> the<00:08:43.709> aggregations<00:08:44.430> and 00:08:44.750 --> 00:08:44.760 align:start position:0% side and do all the aggregations and 00:08:44.760 --> 00:08:47.360 align:start position:0% side and do all the aggregations and then<00:08:45.270> push<00:08:45.480> it<00:08:45.630> back<00:08:45.839> to<00:08:46.050> cool<00:08:46.230> interesting<00:08:46.950> so 00:08:47.360 --> 00:08:47.370 align:start position:0% then push it back to cool interesting so 00:08:47.370 --> 00:08:49.130 align:start position:0% then push it back to cool interesting so that<00:08:47.730> that's<00:08:47.970> really<00:08:48.209> one<00:08:48.480> use<00:08:48.720> case<00:08:48.899> that 00:08:49.130 --> 00:08:49.140 align:start position:0% that that's really one use case that 00:08:49.140 --> 00:08:50.630 align:start position:0% that that's really one use case that could<00:08:49.290> is<00:08:49.440> perfect<00:08:49.860> for<00:08:50.040> interesting 00:08:50.630 --> 00:08:50.640 align:start position:0% could is perfect for interesting 00:08:50.640 --> 00:08:52.190 align:start position:0% could is perfect for interesting interesting<00:08:51.000> it's<00:08:51.270> streaming<00:08:51.630> like<00:08:51.959> not<00:08:52.170> a 00:08:52.190 --> 00:08:52.200 align:start position:0% interesting it's streaming like not a 00:08:52.200 --> 00:08:53.510 align:start position:0% interesting it's streaming like not a whole<00:08:52.410> lot<00:08:52.500> of<00:08:52.560> interest<00:08:52.950> reaming<00:08:53.220> all<00:08:53.430> the 00:08:53.510 --> 00:08:53.520 align:start position:0% whole lot of interest reaming all the 00:08:53.520 --> 00:08:54.800 align:start position:0% whole lot of interest reaming all the new<00:08:53.640> players<00:08:53.970> on<00:08:54.180> the<00:08:54.240> new<00:08:54.329> data<00:08:54.510> points 00:08:54.800 --> 00:08:54.810 align:start position:0% new players on the new data points 00:08:54.810 --> 00:08:56.720 align:start position:0% new players on the new data points coming<00:08:54.959> in<00:08:55.199> updating<00:08:56.040> your<00:08:56.250> data<00:08:56.459> on<00:08:56.579> the<00:08:56.699> fly 00:08:56.720 --> 00:08:56.730 align:start position:0% coming in updating your data on the fly 00:08:56.730 --> 00:08:58.850 align:start position:0% coming in updating your data on the fly and<00:08:57.060> on<00:08:57.360> the<00:08:57.449> other<00:08:57.540> side<00:08:57.899> you<00:08:58.140> can<00:08:58.290> use<00:08:58.500> what 00:08:58.850 --> 00:08:58.860 align:start position:0% and on the other side you can use what 00:08:58.860 --> 00:08:59.740 align:start position:0% and on the other side you can use what you<00:08:58.949> can<00:08:59.070> use<00:08:59.160> sparks<00:08:59.430> equal 00:08:59.740 --> 00:08:59.750 align:start position:0% you can use sparks equal 00:08:59.750 --> 00:09:01.300 align:start position:0% you can use sparks equal are<00:08:59.810> you<00:08:59.960> in<00:09:00.230> my<00:09:00.560> case<00:09:00.770> I'm<00:09:00.860> going<00:09:00.890> to<00:09:01.040> use<00:09:01.100> in 00:09:01.300 --> 00:09:01.310 align:start position:0% are you in my case I'm going to use in 00:09:01.310 --> 00:09:03.550 align:start position:0% are you in my case I'm going to use in Palo<00:09:01.490> directly<00:09:02.090> query<00:09:02.360> data<00:09:02.600> live<00:09:03.290> including 00:09:03.550 --> 00:09:03.560 align:start position:0% Palo directly query data live including 00:09:03.560 --> 00:09:05.110 align:start position:0% Palo directly query data live including so<00:09:03.920> you'll<00:09:04.070> see<00:09:04.220> the<00:09:04.340> changes<00:09:04.670> coming<00:09:04.880> and 00:09:05.110 --> 00:09:05.120 align:start position:0% so you'll see the changes coming and 00:09:05.120 --> 00:09:07.120 align:start position:0% so you'll see the changes coming and young<00:09:05.360> there<00:09:05.900> is<00:09:05.990> no<00:09:06.140> delay<00:09:06.350> of<00:09:06.770> one<00:09:06.980> hour 00:09:07.120 --> 00:09:07.130 align:start position:0% young there is no delay of one hour 00:09:07.130 --> 00:09:09.040 align:start position:0% young there is no delay of one hour before<00:09:07.700> you<00:09:07.850> can<00:09:08.000> see<00:09:08.180> the<00:09:08.300> new<00:09:08.330> updates<00:09:08.780> like 00:09:09.040 --> 00:09:09.050 align:start position:0% before you can see the new updates like 00:09:09.050 --> 00:09:10.540 align:start position:0% before you can see the new updates like you<00:09:09.350> get<00:09:09.500> a<00:09:09.530> new<00:09:09.710> updates<00:09:09.980> as<00:09:10.130> soon<00:09:10.160> as<00:09:10.430> the 00:09:10.540 --> 00:09:10.550 align:start position:0% you get a new updates as soon as the 00:09:10.550 --> 00:09:12.280 align:start position:0% you get a new updates as soon as the line<00:09:10.730> you<00:09:11.120> just<00:09:11.330> saying<00:09:11.510> super<00:09:11.960> interesting 00:09:12.280 --> 00:09:12.290 align:start position:0% line you just saying super interesting 00:09:12.290 --> 00:09:14.200 align:start position:0% line you just saying super interesting actually<00:09:12.830> so<00:09:13.160> when<00:09:13.430> you<00:09:13.550> mentioned<00:09:14.030> that<00:09:14.060> you 00:09:14.200 --> 00:09:14.210 align:start position:0% actually so when you mentioned that you 00:09:14.210 --> 00:09:16.120 align:start position:0% actually so when you mentioned that you know<00:09:14.450> kudos<00:09:14.840> meant<00:09:15.260> to<00:09:15.380> replace<00:09:15.680> your<00:09:15.890> lungs 00:09:16.120 --> 00:09:16.130 align:start position:0% know kudos meant to replace your lungs 00:09:16.130 --> 00:09:17.620 align:start position:0% know kudos meant to replace your lungs architecture<00:09:16.730> that<00:09:17.180> was<00:09:17.330> very<00:09:17.450> interesting 00:09:17.620 --> 00:09:17.630 align:start position:0% architecture that was very interesting 00:09:17.630 --> 00:09:19.600 align:start position:0% architecture that was very interesting to<00:09:17.900> me<00:09:17.990> because<00:09:18.080> you<00:09:18.380> know<00:09:18.500> we<00:09:19.340> have<00:09:19.490> this 00:09:19.600 --> 00:09:19.610 align:start position:0% to me because you know we have this 00:09:19.610 --> 00:09:21.250 align:start position:0% to me because you know we have this conference<00:09:20.120> called<00:09:20.360> big<00:09:20.480> data<00:09:20.510> scholar<00:09:20.930> and 00:09:21.250 --> 00:09:21.260 align:start position:0% conference called big data scholar and 00:09:21.260 --> 00:09:23.230 align:start position:0% conference called big data scholar and you<00:09:21.860> know<00:09:21.980> in<00:09:22.250> order<00:09:22.430> to<00:09:22.610> kind<00:09:22.820> of<00:09:22.970> emphasize 00:09:23.230 --> 00:09:23.240 align:start position:0% you know in order to kind of emphasize 00:09:23.240 --> 00:09:25.980 align:start position:0% you know in order to kind of emphasize why<00:09:24.170> we<00:09:24.350> need<00:09:24.500> them<00:09:24.620> to<00:09:24.650> end<00:09:24.920> reactive<00:09:25.370> systems 00:09:25.980 --> 00:09:25.990 align:start position:0% why we need them to end reactive systems 00:09:25.990 --> 00:09:28.750 align:start position:0% why we need them to end reactive systems we<00:09:26.990> did<00:09:27.200> this<00:09:27.380> site<00:09:27.830> called<00:09:28.040> know<00:09:28.220> et<00:09:28.490> al<00:09:28.610> dot 00:09:28.750 --> 00:09:28.760 align:start position:0% we did this site called know et al dot 00:09:28.760 --> 00:09:31.300 align:start position:0% we did this site called know et al dot org<00:09:28.970> kind<00:09:29.810> of<00:09:29.900> prepared<00:09:30.350> in<00:09:30.530> no<00:09:30.680> sequel<00:09:31.100> right 00:09:31.300 --> 00:09:31.310 align:start position:0% org kind of prepared in no sequel right 00:09:31.310 --> 00:09:33.850 align:start position:0% org kind of prepared in no sequel right and<00:09:31.550> and<00:09:31.760> so<00:09:32.000> the<00:09:32.240> the<00:09:32.810> ocean<00:09:33.230> which<00:09:33.470> scale 00:09:33.850 --> 00:09:33.860 align:start position:0% and and so the the ocean which scale 00:09:33.860 --> 00:09:35.470 align:start position:0% and and so the the ocean which scale community<00:09:34.310> has<00:09:34.520> we<00:09:34.850> have<00:09:35.000> this<00:09:35.090> reactive 00:09:35.470 --> 00:09:35.480 align:start position:0% community has we have this reactive 00:09:35.480 --> 00:09:37.840 align:start position:0% community has we have this reactive systems<00:09:35.840> you<00:09:36.470> know<00:09:36.620> you<00:09:36.860> can<00:09:37.010> have<00:09:37.220> a<00:09:37.400> cow<00:09:37.640> as 00:09:37.840 --> 00:09:37.850 align:start position:0% systems you know you can have a cow as 00:09:37.850 --> 00:09:40.360 align:start position:0% systems you know you can have a cow as yo<00:09:38.120> a<00:09:38.150> TI<00:09:38.450> you<00:09:38.570> can<00:09:39.080> have<00:09:39.260> Kafka<00:09:39.710> in<00:09:39.980> the<00:09:40.100> middle 00:09:40.360 --> 00:09:40.370 align:start position:0% yo a TI you can have Kafka in the middle 00:09:40.370 --> 00:09:43.810 align:start position:0% yo a TI you can have Kafka in the middle as<00:09:40.840> message<00:09:41.840> boss<00:09:42.020> then<00:09:42.440> you<00:09:42.590> can<00:09:42.770> have<00:09:42.980> spark 00:09:43.810 --> 00:09:43.820 align:start position:0% as message boss then you can have spark 00:09:43.820 --> 00:09:48.130 align:start position:0% as message boss then you can have spark right<00:09:44.600> and<00:09:44.870> so<00:09:45.310> you<00:09:46.310> you're<00:09:46.580> never<00:09:47.140> dumping 00:09:48.130 --> 00:09:48.140 align:start position:0% right and so you you're never dumping 00:09:48.140 --> 00:09:51.520 align:start position:0% right and so you you're never dumping data<00:09:48.680> back<00:09:49.100> into<00:09:49.520> HDFS<00:09:50.270> as<00:09:50.660> text<00:09:51.080> for<00:09:51.260> instance 00:09:51.520 --> 00:09:51.530 align:start position:0% data back into HDFS as text for instance 00:09:51.530 --> 00:09:53.110 align:start position:0% data back into HDFS as text for instance like<00:09:51.620> this<00:09:51.680> so<00:09:52.010> there<00:09:52.160> is<00:09:52.220> this<00:09:52.340> typical<00:09:52.490> etl 00:09:53.110 --> 00:09:53.120 align:start position:0% like this so there is this typical etl 00:09:53.120 --> 00:09:54.670 align:start position:0% like this so there is this typical etl workflow<00:09:53.570> where<00:09:53.780> you<00:09:53.930> grab<00:09:54.140> stuff<00:09:54.350> for<00:09:54.530> one 00:09:54.670 --> 00:09:54.680 align:start position:0% workflow where you grab stuff for one 00:09:54.680 --> 00:09:56.770 align:start position:0% workflow where you grab stuff for one thing<00:09:54.920> you<00:09:55.670> transform<00:09:56.180> it<00:09:56.360> and<00:09:56.480> think<00:09:56.720> you 00:09:56.770 --> 00:09:56.780 align:start position:0% thing you transform it and think you 00:09:56.780 --> 00:09:59.320 align:start position:0% thing you transform it and think you dump<00:09:57.020> it<00:09:57.230> usually<00:09:57.860> into<00:09:58.130> HDFS<00:09:58.580> text<00:09:59.150> and<00:09:59.270> then 00:09:59.320 --> 00:09:59.330 align:start position:0% dump it usually into HDFS text and then 00:09:59.330 --> 00:10:01.690 align:start position:0% dump it usually into HDFS text and then you<00:09:59.480> read<00:09:59.810> it<00:09:59.930> back<00:10:00.140> and<00:10:00.350> parse<00:10:00.590> it<00:10:00.800> and<00:10:01.040> then 00:10:01.690 --> 00:10:01.700 align:start position:0% you read it back and parse it and then 00:10:01.700 --> 00:10:03.010 align:start position:0% you read it back and parse it and then something<00:10:01.910> else<00:10:02.120> does<00:10:02.420> something<00:10:02.720> else<00:10:02.840> to<00:10:02.990> it 00:10:03.010 --> 00:10:03.020 align:start position:0% something else does something else to it 00:10:03.020 --> 00:10:05.200 align:start position:0% something else does something else to it right<00:10:03.470> so<00:10:03.680> so<00:10:04.190> there<00:10:04.400> is<00:10:04.430> this<00:10:04.610> piece<00:10:04.850> of<00:10:05.000> it<00:10:05.120> I 00:10:05.200 --> 00:10:05.210 align:start position:0% right so so there is this piece of it I 00:10:05.210 --> 00:10:09.010 align:start position:0% right so so there is this piece of it I mean<00:10:05.330> in<00:10:05.480> etl<00:10:05.930> is<00:10:06.140> inherently<00:10:07.720> step<00:10:08.720> Orion 00:10:09.010 --> 00:10:09.020 align:start position:0% mean in etl is inherently step Orion 00:10:09.020 --> 00:10:10.780 align:start position:0% mean in etl is inherently step Orion basically<00:10:09.530> first<00:10:09.740> to<00:10:09.830> give<00:10:09.950> struct<00:10:10.370> you<00:10:10.670> know 00:10:10.780 --> 00:10:10.790 align:start position:0% basically first to give struct you know 00:10:10.790 --> 00:10:14.130 align:start position:0% basically first to give struct you know transform<00:10:11.330> and<00:10:11.480> a<00:10:11.540> new<00:10:11.690> law<00:10:11.870> so<00:10:12.589> so<00:10:13.070> we<00:10:13.760> kind<00:10:14.000> of 00:10:14.130 --> 00:10:14.140 align:start position:0% transform and a new law so so we kind of 00:10:14.140 --> 00:10:16.210 align:start position:0% transform and a new law so so we kind of want<00:10:15.140> to<00:10:15.230> emphasize<00:10:15.620> the<00:10:15.860> fact<00:10:15.890> that<00:10:16.070> you 00:10:16.210 --> 00:10:16.220 align:start position:0% want to emphasize the fact that you 00:10:16.220 --> 00:10:18.820 align:start position:0% want to emphasize the fact that you don't<00:10:16.400> need<00:10:16.640> to<00:10:16.910> do<00:10:17.510> too<00:10:17.540> low<00:10:18.050> that<00:10:18.290> anymore<00:10:18.530> is 00:10:18.820 --> 00:10:18.830 align:start position:0% don't need to do too low that anymore is 00:10:18.830 --> 00:10:21.970 align:start position:0% don't need to do too low that anymore is just<00:10:19.490> keep<00:10:19.730> it<00:10:19.880> there<00:10:20.089> so<00:10:20.690> I<00:10:20.720> wonder<00:10:21.170> from<00:10:21.650> the 00:10:21.970 --> 00:10:21.980 align:start position:0% just keep it there so I wonder from the 00:10:21.980 --> 00:10:23.170 align:start position:0% just keep it there so I wonder from the CUDA<00:10:22.160> standpoint<00:10:22.460> and<00:10:22.910> the<00:10:22.940> architecture 00:10:23.170 --> 00:10:23.180 align:start position:0% CUDA standpoint and the architecture 00:10:23.180 --> 00:10:25.600 align:start position:0% CUDA standpoint and the architecture proposed<00:10:23.870> would<00:10:24.620> you<00:10:24.770> agree<00:10:24.980> that<00:10:25.070> you<00:10:25.400> know 00:10:25.600 --> 00:10:25.610 align:start position:0% proposed would you agree that you know 00:10:25.610 --> 00:10:28.180 align:start position:0% proposed would you agree that you know this<00:10:25.790> kind<00:10:26.000> of<00:10:26.060> ETL<00:10:26.680> old-fashioned<00:10:27.680> I<00:10:27.740> dlf 00:10:28.180 --> 00:10:28.190 align:start position:0% this kind of ETL old-fashioned I dlf 00:10:28.190 --> 00:10:31.329 align:start position:0% this kind of ETL old-fashioned I dlf HDFS<00:10:28.640> text<00:10:29.060> storage<00:10:29.570> is<00:10:29.690> obsolete<00:10:29.990> in<00:10:30.620> kind<00:10:31.250> of 00:10:31.329 --> 00:10:31.339 align:start position:0% HDFS text storage is obsolete in kind of 00:10:31.339 --> 00:10:32.770 align:start position:0% HDFS text storage is obsolete in kind of your<00:10:31.550> place<00:10:31.880> and<00:10:32.120> so<00:10:32.210> you<00:10:32.270> have<00:10:32.300> now<00:10:32.540> can 00:10:32.770 --> 00:10:32.780 align:start position:0% your place and so you have now can 00:10:32.780 --> 00:10:34.510 align:start position:0% your place and so you have now can you're<00:10:33.140> supporting<00:10:33.650> kind<00:10:33.920> of<00:10:34.040> streaming 00:10:34.510 --> 00:10:34.520 align:start position:0% you're supporting kind of streaming 00:10:34.520 --> 00:10:37.329 align:start position:0% you're supporting kind of streaming continual<00:10:35.450> process<00:10:36.260> and<00:10:36.650> solution<00:10:37.160> can<00:10:37.310> you 00:10:37.329 --> 00:10:37.339 align:start position:0% continual process and solution can you 00:10:37.339 --> 00:10:39.070 align:start position:0% continual process and solution can you talk<00:10:37.580> a<00:10:37.610> little<00:10:37.700> bit<00:10:38.030> how<00:10:38.240> how<00:10:38.660> it<00:10:38.810> like<00:10:38.960> you 00:10:39.070 --> 00:10:39.080 align:start position:0% talk a little bit how how it like you 00:10:39.080 --> 00:10:41.140 align:start position:0% talk a little bit how how it like you envision<00:10:39.500> kudu<00:10:39.860> as<00:10:40.580> a<00:10:40.640> part<00:10:40.940> of<00:10:41.030> this 00:10:41.140 --> 00:10:41.150 align:start position:0% envision kudu as a part of this 00:10:41.150 --> 00:10:43.780 align:start position:0% envision kudu as a part of this architectures<00:10:41.750> I<00:10:42.110> think<00:10:42.740> for<00:10:42.920> the<00:10:42.980> the<00:10:43.580> live 00:10:43.780 --> 00:10:43.790 align:start position:0% architectures I think for the the live 00:10:43.790 --> 00:10:46.480 align:start position:0% architectures I think for the the live data<00:10:44.030> crew<00:10:44.960> will<00:10:45.320> be<00:10:45.350> able<00:10:45.560> to<00:10:45.830> replace<00:10:46.160> a<00:10:46.220> lot 00:10:46.480 --> 00:10:46.490 align:start position:0% data crew will be able to replace a lot 00:10:46.490 --> 00:10:48.430 align:start position:0% data crew will be able to replace a lot of<00:10:46.580> the<00:10:46.700> current<00:10:47.180> architectures<00:10:47.690> but<00:10:48.230> it's 00:10:48.430 --> 00:10:48.440 align:start position:0% of the current architectures but it's 00:10:48.440 --> 00:10:50.680 align:start position:0% of the current architectures but it's it's<00:10:48.890> not<00:10:49.100> it's<00:10:49.430> not<00:10:49.520> a<00:10:49.610> one<00:10:49.940> size<00:10:49.970> fit<00:10:50.330> all<00:10:50.450> so 00:10:50.680 --> 00:10:50.690 align:start position:0% it's not it's not a one size fit all so 00:10:50.690 --> 00:10:52.450 align:start position:0% it's not it's not a one size fit all so if<00:10:50.810> you<00:10:50.960> have<00:10:51.110> like<00:10:51.320> really<00:10:51.530> really<00:10:51.860> cold<00:10:52.160> data 00:10:52.450 --> 00:10:52.460 align:start position:0% if you have like really really cold data 00:10:52.460 --> 00:10:54.640 align:start position:0% if you have like really really cold data that's<00:10:53.240> going<00:10:53.510> to<00:10:53.570> go<00:10:53.690> like<00:10:53.930> stained<00:10:54.200> his<00:10:54.320> gfs 00:10:54.640 --> 00:10:54.650 align:start position:0% that's going to go like stained his gfs 00:10:54.650 --> 00:10:56.440 align:start position:0% that's going to go like stained his gfs in<00:10:54.800> your<00:10:54.920> pocket<00:10:55.280> files<00:10:55.460> it<00:10:55.730> like<00:10:56.089> if<00:10:56.270> you're 00:10:56.440 --> 00:10:56.450 align:start position:0% in your pocket files it like if you're 00:10:56.450 --> 00:10:57.640 align:start position:0% in your pocket files it like if you're never<00:10:56.630> going<00:10:56.870> to<00:10:56.930> update<00:10:57.110> it<00:10:57.350> there<00:10:57.470> is<00:10:57.560> no 00:10:57.640 --> 00:10:57.650 align:start position:0% never going to update it there is no 00:10:57.650 --> 00:10:59.410 align:start position:0% never going to update it there is no reason<00:10:57.800> to<00:10:57.980> pay<00:10:58.190> the<00:10:58.280> price<00:10:58.400> of<00:10:58.880> like<00:10:59.210> all<00:10:59.330> the 00:10:59.410 --> 00:10:59.420 align:start position:0% reason to pay the price of like all the 00:10:59.420 --> 00:11:00.670 align:start position:0% reason to pay the price of like all the managing<00:10:59.720> that<00:10:59.810> could<00:10:59.990> is<00:11:00.110> going<00:11:00.290> to<00:11:00.380> do<00:11:00.470> like 00:11:00.670 --> 00:11:00.680 align:start position:0% managing that could is going to do like 00:11:00.680 --> 00:11:03.910 align:start position:0% managing that could is going to do like extra<00:11:01.010> on<00:11:01.070> top<00:11:01.100> right<00:11:02.000> and<00:11:02.240> and<00:11:03.110> if<00:11:03.710> you're 00:11:03.910 --> 00:11:03.920 align:start position:0% extra on top right and and if you're 00:11:03.920 --> 00:11:05.500 align:start position:0% extra on top right and and if you're trying<00:11:04.130> to<00:11:04.250> serve<00:11:04.460> a<00:11:04.490> website<00:11:04.910> then<00:11:05.210> again 00:11:05.500 --> 00:11:05.510 align:start position:0% trying to serve a website then again 00:11:05.510 --> 00:11:07.750 align:start position:0% trying to serve a website then again like<00:11:05.780> that's<00:11:05.990> for<00:11:06.170> each<00:11:06.290> base<00:11:06.530> so<00:11:06.770> what<00:11:07.580> lens 00:11:07.750 --> 00:11:07.760 align:start position:0% like that's for each base so what lens 00:11:07.760 --> 00:11:09.910 align:start position:0% like that's for each base so what lens in<00:11:07.880> the<00:11:07.940> middle<00:11:08.240> is<00:11:08.530> exactly<00:11:09.530> what<00:11:09.680> could<00:11:09.800> use 00:11:09.910 --> 00:11:09.920 align:start position:0% in the middle is exactly what could use 00:11:09.920 --> 00:11:12.730 align:start position:0% in the middle is exactly what could use for<00:11:10.130> so<00:11:10.640> what<00:11:10.820> about<00:11:11.140> preserving<00:11:12.140> schemas 00:11:12.730 --> 00:11:12.740 align:start position:0% for so what about preserving schemas 00:11:12.740 --> 00:11:13.600 align:start position:0% for so what about preserving schemas right<00:11:12.980> so<00:11:13.190> one 00:11:13.600 --> 00:11:13.610 align:start position:0% right so one 00:11:13.610 --> 00:11:15.370 align:start position:0% right so one the<00:11:13.730> things<00:11:13.970> we<00:11:14.240> want<00:11:14.450> to<00:11:14.540> avoid<00:11:14.750> within 00:11:15.370 --> 00:11:15.380 align:start position:0% the things we want to avoid within 00:11:15.380 --> 00:11:16.540 align:start position:0% the things we want to avoid within old-fashioned<00:11:15.860> eight<00:11:15.950> year<00:11:16.100> we<00:11:16.190> don't<00:11:16.370> want 00:11:16.540 --> 00:11:16.550 align:start position:0% old-fashioned eight year we don't want 00:11:16.550 --> 00:11:18.790 align:start position:0% old-fashioned eight year we don't want to<00:11:16.610> extract<00:11:17.000> anymore<00:11:17.420> we<00:11:17.720> want<00:11:17.930> to<00:11:18.140> you<00:11:18.649> know 00:11:18.790 --> 00:11:18.800 align:start position:0% to extract anymore we want to you know 00:11:18.800 --> 00:11:20.920 align:start position:0% to extract anymore we want to you know receive<00:11:19.399> an<00:11:19.579> object<00:11:19.940> through<00:11:20.089> the<00:11:20.149> API<00:11:20.300> we 00:11:20.920 --> 00:11:20.930 align:start position:0% receive an object through the API we 00:11:20.930 --> 00:11:22.660 align:start position:0% receive an object through the API we won't<00:11:21.050> assign<00:11:21.380> it<00:11:21.560> to<00:11:21.589> a<00:11:21.769> type<00:11:22.040> you<00:11:22.310> know<00:11:22.430> well 00:11:22.660 --> 00:11:22.670 align:start position:0% won't assign it to a type you know well 00:11:22.670 --> 00:11:24.550 align:start position:0% won't assign it to a type you know well fortunately<00:11:23.060> kind<00:11:23.450> of<00:11:23.540> in<00:11:23.660> a<00:11:23.750> strongly<00:11:24.440> typed 00:11:24.550 --> 00:11:24.560 align:start position:0% fortunately kind of in a strongly typed 00:11:24.560 --> 00:11:28.329 align:start position:0% fortunately kind of in a strongly typed language<00:11:25.250> usually<00:11:25.810> hopefully<00:11:26.890> and<00:11:27.890> so<00:11:28.190> we 00:11:28.329 --> 00:11:28.339 align:start position:0% language usually hopefully and so we 00:11:28.339 --> 00:11:30.880 align:start position:0% language usually hopefully and so we want<00:11:28.579> to<00:11:28.730> we<00:11:29.450> were<00:11:29.600> validated<00:11:30.260> it<00:11:30.410> right<00:11:30.680> we 00:11:30.880 --> 00:11:30.890 align:start position:0% want to we were validated it right we 00:11:30.890 --> 00:11:33.460 align:start position:0% want to we were validated it right we want<00:11:31.100> to<00:11:31.250> preserve<00:11:31.570> that<00:11:32.570> and<00:11:32.870> hopefully<00:11:33.110> you 00:11:33.460 --> 00:11:33.470 align:start position:0% want to preserve that and hopefully you 00:11:33.470 --> 00:11:35.380 align:start position:0% want to preserve that and hopefully you know<00:11:33.589> that<00:11:33.980> some<00:11:34.220> consistencies<00:11:35.000> checking 00:11:35.380 --> 00:11:35.390 align:start position:0% know that some consistencies checking 00:11:35.390 --> 00:11:37.300 align:start position:0% know that some consistencies checking and<00:11:35.570> we<00:11:36.050> want<00:11:36.200> to<00:11:36.290> pass<00:11:36.470> the<00:11:36.649> object<00:11:37.010> bicycle 00:11:37.300 --> 00:11:37.310 align:start position:0% and we want to pass the object bicycle 00:11:37.310 --> 00:11:38.980 align:start position:0% and we want to pass the object bicycle through<00:11:37.459> the<00:11:37.610> whole<00:11:37.790> system<00:11:38.000> and<00:11:38.420> I<00:11:38.600> really 00:11:38.980 --> 00:11:38.990 align:start position:0% through the whole system and I really 00:11:38.990 --> 00:11:40.990 align:start position:0% through the whole system and I really want<00:11:39.170> to<00:11:39.260> store<00:11:39.529> it<00:11:39.560> in<00:11:39.829> that<00:11:40.010> way<00:11:40.040> right<00:11:40.370> is<00:11:40.820> it 00:11:40.990 --> 00:11:41.000 align:start position:0% want to store it in that way right is it 00:11:41.000 --> 00:11:43.150 align:start position:0% want to store it in that way right is it possible<00:11:41.209> like<00:11:41.870> it's<00:11:42.050> good<00:11:42.230> to<00:11:42.350> kind<00:11:42.649> of<00:11:42.709> built 00:11:43.150 --> 00:11:43.160 align:start position:0% possible like it's good to kind of built 00:11:43.160 --> 00:11:44.620 align:start position:0% possible like it's good to kind of built with<00:11:43.399> this<00:11:43.550> assumption<00:11:43.910> that<00:11:44.120> you<00:11:44.360> will<00:11:44.480> have 00:11:44.620 --> 00:11:44.630 align:start position:0% with this assumption that you will have 00:11:44.630 --> 00:11:46.090 align:start position:0% with this assumption that you will have typed<00:11:44.839> objects<00:11:45.350> we<00:11:45.410> all<00:11:45.529> have<00:11:45.649> schemas<00:11:45.980> like 00:11:46.090 --> 00:11:46.100 align:start position:0% typed objects we all have schemas like 00:11:46.100 --> 00:11:48.069 align:start position:0% typed objects we all have schemas like Kafka<00:11:46.399> right<00:11:47.029> combo<00:11:47.360> Kafka<00:11:47.690> has<00:11:47.810> a<00:11:47.839> schema 00:11:48.069 --> 00:11:48.079 align:start position:0% Kafka right combo Kafka has a schema 00:11:48.079 --> 00:11:51.100 align:start position:0% Kafka right combo Kafka has a schema server<00:11:48.350> how<00:11:48.529> does<00:11:48.860> could<00:11:49.010> work<00:11:49.190> there<00:11:49.390> so<00:11:50.390> kuru 00:11:51.100 --> 00:11:51.110 align:start position:0% server how does could work there so kuru 00:11:51.110 --> 00:11:53.440 align:start position:0% server how does could work there so kuru unlike<00:11:51.500> central<00:11:52.010> rage<00:11:52.190> base<00:11:52.459> is<00:11:53.180> strongly 00:11:53.440 --> 00:11:53.450 align:start position:0% unlike central rage base is strongly 00:11:53.450 --> 00:11:55.449 align:start position:0% unlike central rage base is strongly typed<00:11:53.750> like<00:11:53.899> that<00:11:54.079> when<00:11:54.800> you<00:11:54.920> use<00:11:54.950> a<00:11:55.220> normal 00:11:55.449 --> 00:11:55.459 align:start position:0% typed like that when you use a normal 00:11:55.459 --> 00:11:56.920 align:start position:0% typed like that when you use a normal relational<00:11:56.029> database<00:11:56.360> you<00:11:56.600> have<00:11:56.750> multiple 00:11:56.920 --> 00:11:56.930 align:start position:0% relational database you have multiple 00:11:56.930 --> 00:11:58.600 align:start position:0% relational database you have multiple columns<00:11:57.440> they<00:11:57.649> each<00:11:57.769> have<00:11:57.920> a<00:11:57.950> type<00:11:58.220> who<00:11:58.550> is 00:11:58.600 --> 00:11:58.610 align:start position:0% columns they each have a type who is 00:11:58.610 --> 00:12:00.400 align:start position:0% columns they each have a type who is exactly<00:11:59.000> the<00:11:59.329> same<00:11:59.540> way<00:11:59.720> there's<00:11:59.959> nothing<00:12:00.290> new 00:12:00.400 --> 00:12:00.410 align:start position:0% exactly the same way there's nothing new 00:12:00.410 --> 00:12:02.380 align:start position:0% exactly the same way there's nothing new there<00:12:00.649> and<00:12:00.980> the<00:12:01.519> same<00:12:01.700> same<00:12:02.060> thing<00:12:02.209> with<00:12:02.300> your 00:12:02.380 --> 00:12:02.390 align:start position:0% there and the same same thing with your 00:12:02.390 --> 00:12:03.519 align:start position:0% there and the same same thing with your keys<00:12:02.660> instead<00:12:02.899> of<00:12:03.050> having<00:12:03.230> a<00:12:03.350> special 00:12:03.519 --> 00:12:03.529 align:start position:0% keys instead of having a special 00:12:03.529 --> 00:12:05.680 align:start position:0% keys instead of having a special columnist<00:12:03.950> your<00:12:04.100> key<00:12:04.310> you<00:12:05.000> pick<00:12:05.269> the<00:12:05.390> columns 00:12:05.680 --> 00:12:05.690 align:start position:0% columnist your key you pick the columns 00:12:05.690 --> 00:12:07.600 align:start position:0% columnist your key you pick the columns that<00:12:05.810> you<00:12:05.930> want<00:12:06.079> as<00:12:06.200> your<00:12:06.529> keys<00:12:06.800> we<00:12:07.519> had 00:12:07.600 --> 00:12:07.610 align:start position:0% that you want as your keys we had 00:12:07.610 --> 00:12:09.220 align:start position:0% that you want as your keys we had composite<00:12:08.060> maybe<00:12:08.300> there's<00:12:08.510> only<00:12:08.660> one<00:12:08.899> and 00:12:09.220 --> 00:12:09.230 align:start position:0% composite maybe there's only one and 00:12:09.230 --> 00:12:11.050 align:start position:0% composite maybe there's only one and again<00:12:10.070> that's<00:12:10.220> something<00:12:10.370> that<00:12:10.550> people<00:12:10.940> are 00:12:11.050 --> 00:12:11.060 align:start position:0% again that's something that people are 00:12:11.060 --> 00:12:13.120 align:start position:0% again that's something that people are very<00:12:11.209> familiar<00:12:11.329> with<00:12:11.600> we<00:12:12.500> don't<00:12:12.589> have<00:12:12.740> nested 00:12:13.120 --> 00:12:13.130 align:start position:0% very familiar with we don't have nested 00:12:13.130 --> 00:12:14.800 align:start position:0% very familiar with we don't have nested data<00:12:13.279> types<00:12:13.640> yet<00:12:13.940> but<00:12:14.209> that's<00:12:14.269> also<00:12:14.480> something 00:12:14.800 --> 00:12:14.810 align:start position:0% data types yet but that's also something 00:12:14.810 --> 00:12:16.259 align:start position:0% data types yet but that's also something that's<00:12:14.990> going<00:12:15.260> to<00:12:15.350> be<00:12:15.440> on<00:12:15.529> the<00:12:15.620> road<00:12:15.769> map 00:12:16.259 --> 00:12:16.269 align:start position:0% that's going to be on the road map 00:12:16.269 --> 00:12:19.560 align:start position:0% that's going to be on the road map interesting<00:12:17.269> how<00:12:17.720> big<00:12:18.529> other<00:12:18.740> objects<00:12:19.130> I<00:12:19.250> do 00:12:19.560 --> 00:12:19.570 align:start position:0% interesting how big other objects I do 00:12:19.570 --> 00:12:22.990 align:start position:0% interesting how big other objects I do have<00:12:20.570> some<00:12:20.750> optimal<00:12:21.170> object<00:12:21.410> size<00:12:21.589> like<00:12:22.579> would 00:12:22.990 --> 00:12:23.000 align:start position:0% have some optimal object size like would 00:12:23.000 --> 00:12:24.220 align:start position:0% have some optimal object size like would you<00:12:23.029> handle<00:12:23.449> large<00:12:23.690> objects<00:12:23.990> like<00:12:24.019> you<00:12:24.170> know 00:12:24.220 --> 00:12:24.230 align:start position:0% you handle large objects like you know 00:12:24.230 --> 00:12:26.470 align:start position:0% you handle large objects like you know we<00:12:24.320> have<00:12:24.440> a<00:12:24.470> lot<00:12:24.529> of<00:12:24.620> PDFs<00:12:25.120> in<00:12:26.120> my<00:12:26.269> use<00:12:26.420> case 00:12:26.470 --> 00:12:26.480 align:start position:0% we have a lot of PDFs in my use case 00:12:26.480 --> 00:12:28.480 align:start position:0% we have a lot of PDFs in my use case like<00:12:26.839> can<00:12:26.990> you<00:12:27.019> send<00:12:27.380> binary<00:12:27.769> blobs<00:12:28.070> you<00:12:28.370> know 00:12:28.480 --> 00:12:28.490 align:start position:0% like can you send binary blobs you know 00:12:28.490 --> 00:12:30.819 align:start position:0% like can you send binary blobs you know several<00:12:28.970> you<00:12:29.779> can<00:12:30.230> but<00:12:30.440> that's<00:12:30.500> not<00:12:30.620> really 00:12:30.819 --> 00:12:30.829 align:start position:0% several you can but that's not really 00:12:30.829 --> 00:12:32.350 align:start position:0% several you can but that's not really the<00:12:31.010> kind<00:12:31.279> of<00:12:31.399> use<00:12:31.610> case<00:12:31.790> we're<00:12:31.940> targeting<00:12:32.060> in 00:12:32.350 --> 00:12:32.360 align:start position:0% the kind of use case we're targeting in 00:12:32.360 --> 00:12:33.880 align:start position:0% the kind of use case we're targeting in the<00:12:32.449> beginning<00:12:32.810> if<00:12:33.140> you<00:12:33.290> have<00:12:33.410> an<00:12:33.500> analytics 00:12:33.880 --> 00:12:33.890 align:start position:0% the beginning if you have an analytics 00:12:33.890 --> 00:12:35.110 align:start position:0% the beginning if you have an analytics use<00:12:34.040> case<00:12:34.220> you're<00:12:34.370> really<00:12:34.730> doing<00:12:34.880> analytics 00:12:35.110 --> 00:12:35.120 align:start position:0% use case you're really doing analytics 00:12:35.120 --> 00:12:37.269 align:start position:0% use case you're really doing analytics and<00:12:35.449> PDFs<00:12:35.779> maybe<00:12:36.500> you<00:12:36.649> are<00:12:36.800> but<00:12:36.980> I<00:12:37.040> don't<00:12:37.220> know 00:12:37.269 --> 00:12:37.279 align:start position:0% and PDFs maybe you are but I don't know 00:12:37.279 --> 00:12:38.829 align:start position:0% and PDFs maybe you are but I don't know about<00:12:37.399> your<00:12:37.610> use<00:12:37.730> case<00:12:37.940> okay<00:12:38.269> well<00:12:38.600> we<00:12:38.810> can 00:12:38.829 --> 00:12:38.839 align:start position:0% about your use case okay well we can 00:12:38.839 --> 00:12:40.660 align:start position:0% about your use case okay well we can extract<00:12:39.170> a<00:12:39.290> lot<00:12:39.440> of<00:12:39.620> sex<00:12:39.769> from<00:12:39.920> a<00:12:40.040> data<00:12:40.250> but<00:12:40.519> I 00:12:40.660 --> 00:12:40.670 align:start position:0% extract a lot of sex from a data but I 00:12:40.670 --> 00:12:42.759 align:start position:0% extract a lot of sex from a data but I mean<00:12:40.880> little<00:12:41.600> bunch<00:12:41.870> of<00:12:41.990> metadata<00:12:42.350> which<00:12:42.649> we 00:12:42.759 --> 00:12:42.769 align:start position:0% mean little bunch of metadata which we 00:12:42.769 --> 00:12:45.730 align:start position:0% mean little bunch of metadata which we can<00:12:42.980> which<00:12:43.399> is<00:12:43.550> not<00:12:44.000> as<00:12:44.180> big<00:12:44.779> party<00:12:45.170> no<00:12:45.290> and<00:12:45.500> but 00:12:45.730 --> 00:12:45.740 align:start position:0% can which is not as big party no and but 00:12:45.740 --> 00:12:48.040 align:start position:0% can which is not as big party no and but there<00:12:45.890> is<00:12:45.980> a<00:12:46.010> binary<00:12:46.220> blob<00:12:46.640> associated<00:12:47.480> right 00:12:48.040 --> 00:12:48.050 align:start position:0% there is a binary blob associated right 00:12:48.050 --> 00:12:50.949 align:start position:0% there is a binary blob associated right well<00:12:48.860> I<00:12:48.890> mean<00:12:49.279> you<00:12:49.459> could<00:12:49.640> I<00:12:50.120> mean<00:12:50.720> it<00:12:50.870> really 00:12:50.949 --> 00:12:50.959 align:start position:0% well I mean you could I mean it really 00:12:50.959 --> 00:12:52.030 align:start position:0% well I mean you could I mean it really depends<00:12:51.260> on<00:12:51.320> the<00:12:51.410> size<00:12:51.560> and<00:12:51.800> if<00:12:51.890> you're 00:12:52.030 --> 00:12:52.040 align:start position:0% depends on the size and if you're 00:12:52.040 --> 00:12:53.860 align:start position:0% depends on the size and if you're talking<00:12:52.339> about<00:12:52.490> megabytes<00:12:53.000> here<00:12:53.600> and<00:12:53.750> I<00:12:53.810> would 00:12:53.860 --> 00:12:53.870 align:start position:0% talking about megabytes here and I would 00:12:53.870 --> 00:12:56.620 align:start position:0% talking about megabytes here and I would say<00:12:54.079> the<00:12:54.199> kudu<00:12:54.910> it's<00:12:55.910> gonna<00:12:56.000> have<00:12:56.209> a<00:12:56.240> hard<00:12:56.480> time 00:12:56.620 --> 00:12:56.630 align:start position:0% say the kudu it's gonna have a hard time 00:12:56.630 --> 00:12:58.329 align:start position:0% say the kudu it's gonna have a hard time since<00:12:56.899> there's<00:12:57.019> like<00:12:57.199> no<00:12:57.470> optimization<00:12:57.829> what 00:12:58.329 --> 00:12:58.339 align:start position:0% since there's like no optimization what 00:12:58.339 --> 00:13:00.250 align:start position:0% since there's like no optimization what so<00:12:58.459> ever<00:12:58.519> done<00:12:58.910> for<00:12:59.120> dark<00:12:59.360> medium<00:12:59.870> or<00:13:00.019> big 00:13:00.250 --> 00:13:00.260 align:start position:0% so ever done for dark medium or big 00:13:00.260 --> 00:13:03.579 align:start position:0% so ever done for dark medium or big objects<00:13:01.750> but<00:13:02.750> there's<00:13:03.050> a<00:13:03.140> lot<00:13:03.260> of<00:13:03.290> stuff<00:13:03.500> in 00:13:03.579 --> 00:13:03.589 align:start position:0% objects but there's a lot of stuff in 00:13:03.589 --> 00:13:05.319 align:start position:0% objects but there's a lot of stuff in the<00:13:03.680> back<00:13:03.829> end<00:13:04.070> we<00:13:04.519> there's<00:13:05.000> always<00:13:05.180> this 00:13:05.319 --> 00:13:05.329 align:start position:0% the back end we there's always this 00:13:05.329 --> 00:13:07.680 align:start position:0% the back end we there's always this problem<00:13:05.839> like<00:13:06.170> in<00:13:06.500> other<00:13:06.589> systems<00:13:06.829> of<00:13:07.160> writing 00:13:07.680 --> 00:13:07.690 align:start position:0% problem like in other systems of writing 00:13:07.690 --> 00:13:10.060 align:start position:0% problem like in other systems of writing we<00:13:08.690> are<00:13:08.839> always<00:13:08.990> doing<00:13:09.260> background 00:13:10.060 --> 00:13:10.070 align:start position:0% we are always doing background 00:13:10.070 --> 00:13:11.350 align:start position:0% we are always doing background confections<00:13:10.640> and<00:13:10.880> you<00:13:10.940> if<00:13:11.060> you<00:13:11.149> want<00:13:11.300> to 00:13:11.350 --> 00:13:11.360 align:start position:0% confections and you if you want to 00:13:11.360 --> 00:13:13.420 align:start position:0% confections and you if you want to update<00:13:11.510> them<00:13:11.810> you<00:13:11.959> have<00:13:12.079> to<00:13:12.110> like<00:13:12.920> an<00:13:13.040> HBase<00:13:13.310> if 00:13:13.420 --> 00:13:13.430 align:start position:0% update them you have to like an HBase if 00:13:13.430 --> 00:13:14.920 align:start position:0% update them you have to like an HBase if you<00:13:13.490> do<00:13:13.610> a<00:13:13.640> major<00:13:13.790> compaction<00:13:14.240> you<00:13:14.630> have<00:13:14.810> to 00:13:14.920 --> 00:13:14.930 align:start position:0% you do a major compaction you have to 00:13:14.930 --> 00:13:17.860 align:start position:0% you do a major compaction you have to rewrite<00:13:15.589> the<00:13:15.649> whole<00:13:15.890> data<00:13:16.130> set<00:13:16.220> so<00:13:16.779> there's<00:13:17.779> a 00:13:17.860 --> 00:13:17.870 align:start position:0% rewrite the whole data set so there's a 00:13:17.870 --> 00:13:19.870 align:start position:0% rewrite the whole data set so there's a lot<00:13:18.019> of<00:13:18.050> smarts<00:13:18.410> inside<00:13:18.649> kudu<00:13:18.949> where<00:13:19.250> it's 00:13:19.870 --> 00:13:19.880 align:start position:0% lot of smarts inside kudu where it's 00:13:19.880 --> 00:13:22.150 align:start position:0% lot of smarts inside kudu where it's only<00:13:20.240> your<00:13:20.690> the<00:13:21.019> data<00:13:21.410> that's<00:13:21.620> the<00:13:21.800> most<00:13:21.920> fast 00:13:22.150 --> 00:13:22.160 align:start position:0% only your the data that's the most fast 00:13:22.160 --> 00:13:24.189 align:start position:0% only your the data that's the most fast changing<00:13:22.640> that<00:13:22.850> we're<00:13:23.060> going<00:13:23.270> to<00:13:23.329> wreak<00:13:24.020> um 00:13:24.189 --> 00:13:24.199 align:start position:0% changing that we're going to wreak um 00:13:24.199 --> 00:13:26.230 align:start position:0% changing that we're going to wreak um pack<00:13:24.380> if<00:13:24.529> you<00:13:24.649> have<00:13:24.860> like<00:13:25.040> large<00:13:25.640> blobs<00:13:26.060> that 00:13:26.230 --> 00:13:26.240 align:start position:0% pack if you have like large blobs that 00:13:26.240 --> 00:13:27.040 align:start position:0% pack if you have like large blobs that you<00:13:26.390> don't<00:13:26.540> really<00:13:26.630> change 00:13:27.040 --> 00:13:27.050 align:start position:0% you don't really change 00:13:27.050 --> 00:13:28.269 align:start position:0% you don't really change fan<00:13:27.260> because<00:13:27.410> that's<00:13:27.649> your<00:13:27.740> text<00:13:28.070> like<00:13:28.190> you 00:13:28.269 --> 00:13:28.279 align:start position:0% fan because that's your text like you 00:13:28.279 --> 00:13:29.620 align:start position:0% fan because that's your text like you might<00:13:28.430> be<00:13:28.459> computing<00:13:29.149> things<00:13:29.360> about<00:13:29.570> that 00:13:29.620 --> 00:13:29.630 align:start position:0% might be computing things about that 00:13:29.630 --> 00:13:31.090 align:start position:0% might be computing things about that text<00:13:29.959> that's<00:13:30.230> going<00:13:30.470> to<00:13:30.529> change<00:13:30.680> but<00:13:30.860> not<00:13:31.010> the 00:13:31.090 --> 00:13:31.100 align:start position:0% text that's going to change but not the 00:13:31.100 --> 00:13:34.000 align:start position:0% text that's going to change but not the text<00:13:31.399> itself<00:13:32.110> we're<00:13:33.110> never<00:13:33.260> going<00:13:33.649> to<00:13:33.709> try<00:13:33.980> to 00:13:34.000 --> 00:13:34.010 align:start position:0% text itself we're never going to try to 00:13:34.010 --> 00:13:36.460 align:start position:0% text itself we're never going to try to rewrite<00:13:34.519> the<00:13:34.580> text<00:13:34.970> if<00:13:35.060> you<00:13:35.120> have<00:13:35.350> updates<00:13:36.350> of 00:13:36.460 --> 00:13:36.470 align:start position:0% rewrite the text if you have updates of 00:13:36.470 --> 00:13:38.139 align:start position:0% rewrite the text if you have updates of the<00:13:36.500> other<00:13:36.740> columns<00:13:37.250> because<00:13:37.399> good<00:13:38.000> is<00:13:38.029> a 00:13:38.139 --> 00:13:38.149 align:start position:0% the other columns because good is a 00:13:38.149 --> 00:13:39.820 align:start position:0% the other columns because good is a columnar<00:13:38.540> store<00:13:38.810> a<00:13:38.990> true<00:13:39.320> corner<00:13:39.620> store 00:13:39.820 --> 00:13:39.830 align:start position:0% columnar store a true corner store 00:13:39.830 --> 00:13:41.920 align:start position:0% columnar store a true corner store unlike<00:13:40.100> its<00:13:40.760> misery<00:13:41.029> which<00:13:41.480> are<00:13:41.570> more<00:13:41.750> like 00:13:41.920 --> 00:13:41.930 align:start position:0% unlike its misery which are more like 00:13:41.930 --> 00:13:44.829 align:start position:0% unlike its misery which are more like Cohen<00:13:42.260> family<00:13:42.440> family<00:13:43.040> oriented<00:13:43.250> mm-hmm<00:13:44.060> so 00:13:44.829 --> 00:13:44.839 align:start position:0% Cohen family family oriented mm-hmm so 00:13:44.839 --> 00:13:46.480 align:start position:0% Cohen family family oriented mm-hmm so we<00:13:44.990> really<00:13:45.170> store<00:13:45.500> each<00:13:45.740> column<00:13:46.040> separately 00:13:46.480 --> 00:13:46.490 align:start position:0% we really store each column separately 00:13:46.490 --> 00:13:47.970 align:start position:0% we really store each column separately and<00:13:46.700> do<00:13:46.820> the<00:13:47.029> appropriate<00:13:47.420> encodings 00:13:47.970 --> 00:13:47.980 align:start position:0% and do the appropriate encodings 00:13:47.980 --> 00:13:51.370 align:start position:0% and do the appropriate encodings interesting<00:13:48.980> so<00:13:49.310> let's<00:13:49.850> say<00:13:50.029> you<00:13:50.420> know<00:13:50.630> I<00:13:51.019> have 00:13:51.370 --> 00:13:51.380 align:start position:0% interesting so let's say you know I have 00:13:51.380 --> 00:13:54.670 align:start position:0% interesting so let's say you know I have a<00:13:51.410> lot<00:13:51.500> of<00:13:52.870> documents<00:13:53.870> and<00:13:53.959> then<00:13:54.140> you<00:13:54.410> know<00:13:54.560> in 00:13:54.670 --> 00:13:54.680 align:start position:0% a lot of documents and then you know in 00:13:54.680 --> 00:13:56.470 align:start position:0% a lot of documents and then you know in my<00:13:54.890> use<00:13:55.040> case<00:13:55.130> I<00:13:55.279> will<00:13:55.430> constantly<00:13:55.760> improve<00:13:56.360> my 00:13:56.470 --> 00:13:56.480 align:start position:0% my use case I will constantly improve my 00:13:56.480 --> 00:13:58.060 align:start position:0% my use case I will constantly improve my machine<00:13:56.720> learning<00:13:57.110> and<00:13:57.440> extract<00:13:57.920> more 00:13:58.060 --> 00:13:58.070 align:start position:0% machine learning and extract more 00:13:58.070 --> 00:13:59.800 align:start position:0% machine learning and extract more metadata<00:13:58.430> and<00:13:58.880> more<00:13:59.089> I<00:13:59.120> mean<00:13:59.450> I<00:13:59.480> all<00:13:59.690> the 00:13:59.800 --> 00:13:59.810 align:start position:0% metadata and more I mean I all the 00:13:59.810 --> 00:14:01.480 align:start position:0% metadata and more I mean I all the different<00:14:00.110> extraction<00:14:00.410> right<00:14:00.829> so<00:14:01.279> for<00:14:01.459> each 00:14:01.480 --> 00:14:01.490 align:start position:0% different extraction right so for each 00:14:01.490 --> 00:14:04.540 align:start position:0% different extraction right so for each ID<00:14:02.269> document<00:14:03.260> ID<00:14:03.380> I<00:14:03.709> will<00:14:03.890> have<00:14:04.040> a<00:14:04.070> better<00:14:04.310> and 00:14:04.540 --> 00:14:04.550 align:start position:0% ID document ID I will have a better and 00:14:04.550 --> 00:14:05.800 align:start position:0% ID document ID I will have a better and improved<00:14:04.820> version<00:14:05.209> of<00:14:05.360> various<00:14:05.570> kinds<00:14:05.690> of 00:14:05.800 --> 00:14:05.810 align:start position:0% improved version of various kinds of 00:14:05.810 --> 00:14:10.329 align:start position:0% improved version of various kinds of metadata<00:14:06.940> this<00:14:07.940> is<00:14:08.149> kind<00:14:08.450> of<00:14:08.510> a<00:14:08.720> useful<00:14:09.339> good 00:14:10.329 --> 00:14:10.339 align:start position:0% metadata this is kind of a useful good 00:14:10.339 --> 00:14:12.190 align:start position:0% metadata this is kind of a useful good store<00:14:10.730> for<00:14:11.360> this<00:14:11.480> kind<00:14:11.660> of<00:14:11.720> stuff<00:14:11.959> where<00:14:12.170> I 00:14:12.190 --> 00:14:12.200 align:start position:0% store for this kind of stuff where I 00:14:12.200 --> 00:14:13.840 align:start position:0% store for this kind of stuff where I want<00:14:12.440> to<00:14:12.500> have<00:14:12.769> basically<00:14:13.279> I<00:14:13.370> want<00:14:13.490> to<00:14:13.550> replace 00:14:13.840 --> 00:14:13.850 align:start position:0% want to have basically I want to replace 00:14:13.850 --> 00:14:17.560 align:start position:0% want to have basically I want to replace you<00:14:14.750> know<00:14:14.959> a<00:14:14.990> lot<00:14:15.380> of<00:14:15.410> stuff<00:14:16.120> insert<00:14:17.120> columns 00:14:17.560 --> 00:14:17.570 align:start position:0% you know a lot of stuff insert columns 00:14:17.570 --> 00:14:21.550 align:start position:0% you know a lot of stuff insert columns and<00:14:18.279> I'd<00:14:19.279> say<00:14:19.490> depends<00:14:20.029> if<00:14:20.240> you're<00:14:20.269> if<00:14:20.810> if<00:14:21.170> like 00:14:21.550 --> 00:14:21.560 align:start position:0% and I'd say depends if you're if if like 00:14:21.560 --> 00:14:23.139 align:start position:0% and I'd say depends if you're if if like the<00:14:21.740> one<00:14:22.190> thing<00:14:22.339> you're<00:14:22.459> doing<00:14:22.490> the<00:14:22.790> most<00:14:22.970> is 00:14:23.139 --> 00:14:23.149 align:start position:0% the one thing you're doing the most is 00:14:23.149 --> 00:14:25.329 align:start position:0% the one thing you're doing the most is updates<00:14:23.600> and<00:14:24.019> deletes<00:14:24.140> I<00:14:24.620> would<00:14:24.829> say<00:14:25.010> like<00:14:25.160> use 00:14:25.329 --> 00:14:25.339 align:start position:0% updates and deletes I would say like use 00:14:25.339 --> 00:14:27.009 align:start position:0% updates and deletes I would say like use another<00:14:25.579> kind<00:14:25.850> of<00:14:25.940> data<00:14:26.120> store<00:14:26.329> like<00:14:26.480> HP's<00:14:26.839> or 00:14:27.009 --> 00:14:27.019 align:start position:0% another kind of data store like HP's or 00:14:27.019 --> 00:14:29.980 align:start position:0% another kind of data store like HP's or Cassandra<00:14:27.470> there<00:14:28.459> are<00:14:28.579> we're<00:14:29.360> like<00:14:29.690> writing 00:14:29.980 --> 00:14:29.990 align:start position:0% Cassandra there are we're like writing 00:14:29.990 --> 00:14:31.420 align:start position:0% Cassandra there are we're like writing is<00:14:30.170> free<00:14:30.470> you<00:14:30.500> don't<00:14:30.680> you<00:14:30.800> don't<00:14:31.220> need<00:14:31.339> to 00:14:31.420 --> 00:14:31.430 align:start position:0% is free you don't you don't need to 00:14:31.430 --> 00:14:32.949 align:start position:0% is free you don't you don't need to write<00:14:31.700> when<00:14:32.029> you<00:14:32.149> and<00:14:32.540> you<00:14:32.630> don't<00:14:32.779> need<00:14:32.839> to 00:14:32.949 --> 00:14:32.959 align:start position:0% write when you and you don't need to 00:14:32.959 --> 00:14:34.870 align:start position:0% write when you and you don't need to read<00:14:33.230> when<00:14:33.410> you're<00:14:33.560> right<00:14:33.829> you<00:14:34.010> just<00:14:34.550> write 00:14:34.870 --> 00:14:34.880 align:start position:0% read when you're right you just write 00:14:34.880 --> 00:14:36.760 align:start position:0% read when you're right you just write update<00:14:35.149> as<00:14:35.510> a<00:14:35.540> right<00:14:35.810> delete<00:14:36.350> as<00:14:36.500> a<00:14:36.529> right 00:14:36.760 --> 00:14:36.770 align:start position:0% update as a right delete as a right 00:14:36.770 --> 00:14:38.560 align:start position:0% update as a right delete as a right present<00:14:37.640> coo<00:14:37.790> do<00:14:37.910> we<00:14:38.089> have<00:14:38.240> this<00:14:38.360> drink 00:14:38.560 --> 00:14:38.570 align:start position:0% present coo do we have this drink 00:14:38.570 --> 00:14:41.410 align:start position:0% present coo do we have this drink enforcement<00:14:39.290> of<00:14:39.500> the<00:14:39.620> rookie<00:14:40.010> so<00:14:40.970> if<00:14:41.120> you<00:14:41.240> want 00:14:41.410 --> 00:14:41.420 align:start position:0% enforcement of the rookie so if you want 00:14:41.420 --> 00:14:43.420 align:start position:0% enforcement of the rookie so if you want to<00:14:41.480> write<00:14:42.410> something<00:14:42.620> or<00:14:42.890> did<00:14:43.010> something<00:14:43.070> we 00:14:43.420 --> 00:14:43.430 align:start position:0% to write something or did something we 00:14:43.430 --> 00:14:46.180 align:start position:0% to write something or did something we first<00:14:43.700> have<00:14:43.880> to<00:14:43.910> check<00:14:44.180> if<00:14:44.300> it<00:14:44.420> exists<00:14:44.870> yes<00:14:45.190> and 00:14:46.180 --> 00:14:46.190 align:start position:0% first have to check if it exists yes and 00:14:46.190 --> 00:14:48.040 align:start position:0% first have to check if it exists yes and then<00:14:46.459> there's<00:14:47.000> a<00:14:47.089> lot<00:14:47.240> of<00:14:47.270> optimizations<00:14:47.899> we 00:14:48.040 --> 00:14:48.050 align:start position:0% then there's a lot of optimizations we 00:14:48.050 --> 00:14:50.650 align:start position:0% then there's a lot of optimizations we do<00:14:48.230> on<00:14:49.100> this<00:14:49.310> on<00:14:49.700> the<00:14:49.790> scan<00:14:50.029> side<00:14:50.270> like<00:14:50.450> if<00:14:50.570> you 00:14:50.650 --> 00:14:50.660 align:start position:0% do on this on the scan side like if you 00:14:50.660 --> 00:14:52.090 align:start position:0% do on this on the scan side like if you want<00:14:50.899> those<00:14:51.020> fast<00:14:51.230> cans<00:14:51.500> there's<00:14:51.890> something 00:14:52.090 --> 00:14:52.100 align:start position:0% want those fast cans there's something 00:14:52.100 --> 00:14:55.810 align:start position:0% want those fast cans there's something you<00:14:52.279> gotta<00:14:52.459> trade<00:14:52.700> off<00:14:52.850> right<00:14:53.149> so<00:14:54.370> if<00:14:55.370> you<00:14:55.670> have 00:14:55.810 --> 00:14:55.820 align:start position:0% you gotta trade off right so if you have 00:14:55.820 --> 00:14:57.449 align:start position:0% you gotta trade off right so if you have a<00:14:55.850> lot<00:14:56.029> of<00:14:56.060> updates<00:14:56.420> we<00:14:56.630> use<00:14:56.779> what<00:14:57.020> they<00:14:57.200> call 00:14:57.449 --> 00:14:57.459 align:start position:0% a lot of updates we use what they call 00:14:57.459 --> 00:15:01.120 align:start position:0% a lot of updates we use what they call Delta<00:14:58.459> reduced<00:14:59.089> Delta<00:14:59.510> undos<00:14:59.899> so<00:15:00.620> from<00:15:01.010> your 00:15:01.120 --> 00:15:01.130 align:start position:0% Delta reduced Delta undos so from your 00:15:01.130 --> 00:15:02.889 align:start position:0% Delta reduced Delta undos so from your base<00:15:01.310> data<00:15:01.579> we<00:15:01.850> have<00:15:02.029> to<00:15:02.180> apply<00:15:02.450> all<00:15:02.720> the 00:15:02.889 --> 00:15:02.899 align:start position:0% base data we have to apply all the 00:15:02.899 --> 00:15:04.900 align:start position:0% base data we have to apply all the updates<00:15:03.230> that<00:15:03.290> you've<00:15:03.500> done<00:15:03.770> in<00:15:04.459> order<00:15:04.640> to<00:15:04.760> get 00:15:04.900 --> 00:15:04.910 align:start position:0% updates that you've done in order to get 00:15:04.910 --> 00:15:07.600 align:start position:0% updates that you've done in order to get you<00:15:05.089> your<00:15:05.300> final<00:15:05.570> data<00:15:05.899> so<00:15:06.770> if<00:15:07.100> you<00:15:07.220> only<00:15:07.370> have 00:15:07.600 --> 00:15:07.610 align:start position:0% you your final data so if you only have 00:15:07.610 --> 00:15:09.370 align:start position:0% you your final data so if you only have a<00:15:07.640> few<00:15:07.940> that's<00:15:08.270> fine<00:15:08.510> if<00:15:08.779> you<00:15:08.810> have<00:15:09.079> a<00:15:09.110> whole 00:15:09.370 --> 00:15:09.380 align:start position:0% a few that's fine if you have a whole 00:15:09.380 --> 00:15:10.930 align:start position:0% a few that's fine if you have a whole lot<00:15:09.529> and<00:15:09.709> that's<00:15:09.770> your<00:15:09.980> main<00:15:10.160> use<00:15:10.399> case<00:15:10.670> then 00:15:10.930 --> 00:15:10.940 align:start position:0% lot and that's your main use case then 00:15:10.940 --> 00:15:13.900 align:start position:0% lot and that's your main use case then it<00:15:11.060> a<00:15:11.170> kudu<00:15:12.170> will<00:15:12.380> not<00:15:12.920> be<00:15:13.040> as<00:15:13.190> performant<00:15:13.760> as 00:15:13.900 --> 00:15:13.910 align:start position:0% it a kudu will not be as performant as 00:15:13.910 --> 00:15:16.689 align:start position:0% it a kudu will not be as performant as interesting<00:15:14.480> so<00:15:15.170> I<00:15:15.470> would<00:15:15.620> say<00:15:15.770> you<00:15:16.310> know<00:15:16.459> we 00:15:16.689 --> 00:15:16.699 align:start position:0% interesting so I would say you know we 00:15:16.699 --> 00:15:17.980 align:start position:0% interesting so I would say you know we can<00:15:16.820> sell<00:15:17.000> a<00:15:17.209> little<00:15:17.540> bit<00:15:17.630> in<00:15:17.810> the<00:15:17.899> middle 00:15:17.980 --> 00:15:17.990 align:start position:0% can sell a little bit in the middle 00:15:17.990 --> 00:15:19.420 align:start position:0% can sell a little bit in the middle right<00:15:18.140> so<00:15:18.380> let's<00:15:18.560> say<00:15:18.649> we're<00:15:18.829> like<00:15:18.920> we<00:15:19.040> start<00:15:19.370> a 00:15:19.420 --> 00:15:19.430 align:start position:0% right so let's say we're like we start a 00:15:19.430 --> 00:15:20.860 align:start position:0% right so let's say we're like we start a bunch<00:15:19.610> of<00:15:19.699> text<00:15:20.089> and<00:15:20.180> that<00:15:20.360> probably<00:15:20.570> say<00:15:20.839> the 00:15:20.860 --> 00:15:20.870 align:start position:0% bunch of text and that probably say the 00:15:20.870 --> 00:15:24.340 align:start position:0% bunch of text and that probably say the same<00:15:21.020> so<00:15:21.709> we<00:15:22.100> will<00:15:22.670> improve<00:15:23.329> our<00:15:23.480> algorithms 00:15:24.340 --> 00:15:24.350 align:start position:0% same so we will improve our algorithms 00:15:24.350 --> 00:15:27.009 align:start position:0% same so we will improve our algorithms iteratively<00:15:25.250> right<00:15:25.640> and<00:15:25.850> so<00:15:26.060> so<00:15:26.779> a<00:15:26.810> typical 00:15:27.009 --> 00:15:27.019 align:start position:0% iteratively right and so so a typical 00:15:27.019 --> 00:15:28.480 align:start position:0% iteratively right and so so a typical this<00:15:27.350> case<00:15:27.529> will<00:15:27.680> become<00:15:27.920> whole<00:15:28.100> collection 00:15:28.480 --> 00:15:28.490 align:start position:0% this case will become whole collection 00:15:28.490 --> 00:15:30.939 align:start position:0% this case will become whole collection of<00:15:28.550> staff<00:15:28.850> and<00:15:29.209> the<00:15:30.170> the<00:15:30.470> middle<00:15:30.680> it<00:15:30.769> will 00:15:30.939 --> 00:15:30.949 align:start position:0% of staff and the the middle it will 00:15:30.949 --> 00:15:33.340 align:start position:0% of staff and the the middle it will mostly<00:15:31.279> stay<00:15:31.459> the<00:15:31.640> same<00:15:31.880> so<00:15:32.149> but<00:15:32.990> we<00:15:33.140> might 00:15:33.340 --> 00:15:33.350 align:start position:0% mostly stay the same so but we might 00:15:33.350 --> 00:15:35.439 align:start position:0% mostly stay the same so but we might improve<00:15:33.890> our<00:15:34.100> name<00:15:34.399> extraction<00:15:34.940> so<00:15:35.180> you<00:15:35.240> know 00:15:35.439 --> 00:15:35.449 align:start position:0% improve our name extraction so you know 00:15:35.449 --> 00:15:38.139 align:start position:0% improve our name extraction so you know maybe<00:15:35.750> ten<00:15:36.020> percent<00:15:36.380> maybe<00:15:36.500> five<00:15:36.770> percent<00:15:37.190> of 00:15:38.139 --> 00:15:38.149 align:start position:0% maybe ten percent maybe five percent of 00:15:38.149 --> 00:15:39.449 align:start position:0% maybe ten percent maybe five percent of text<00:15:38.839> will<00:15:39.079> change 00:15:39.449 --> 00:15:39.459 align:start position:0% text will change 00:15:39.459 --> 00:15:42.269 align:start position:0% text will change so<00:15:39.670> can<00:15:39.879> I<00:15:40.059> give<00:15:40.480> you<00:15:40.529> kind<00:15:41.529> of<00:15:41.740> catechin<00:15:42.189> I 00:15:42.269 --> 00:15:42.279 align:start position:0% so can I give you kind of catechin I 00:15:42.279 --> 00:15:44.069 align:start position:0% so can I give you kind of catechin I like<00:15:42.490> let's<00:15:42.699> say<00:15:42.759> I<00:15:42.819> maintain<00:15:43.300> my<00:15:43.329> metadata 00:15:44.069 --> 00:15:44.079 align:start position:0% like let's say I maintain my metadata 00:15:44.079 --> 00:15:46.980 align:start position:0% like let's say I maintain my metadata kind<00:15:45.069> of<00:15:45.160> an<00:15:45.249> adjacent<00:15:45.670> file<00:15:45.910> right<00:15:46.689> and<00:15:46.899> I 00:15:46.980 --> 00:15:46.990 align:start position:0% kind of an adjacent file right and I 00:15:46.990 --> 00:15:50.009 align:start position:0% kind of an adjacent file right and I know<00:15:47.129> on<00:15:48.129> my<00:15:48.429> side<00:15:48.730> like<00:15:48.970> I<00:15:49.089> know<00:15:49.389> how<00:15:49.629> to<00:15:49.689> deep 00:15:50.009 --> 00:15:50.019 align:start position:0% know on my side like I know how to deep 00:15:50.019 --> 00:15:53.309 align:start position:0% know on my side like I know how to deep my<00:15:50.319> metadata<00:15:50.670> right<00:15:51.670> so<00:15:51.910> I<00:15:51.939> you<00:15:52.329> know<00:15:52.360> can<00:15:53.110> you 00:15:53.309 --> 00:15:53.319 align:start position:0% my metadata right so I you know can you 00:15:53.319 --> 00:15:55.319 align:start position:0% my metadata right so I you know can you take<00:15:53.499> my<00:15:53.740> d<00:15:53.800> function<00:15:54.369> and<00:15:54.699> would<00:15:55.089> it<00:15:55.179> make 00:15:55.319 --> 00:15:55.329 align:start position:0% take my d function and would it make 00:15:55.329 --> 00:15:57.629 align:start position:0% take my d function and would it make your<00:15:55.449> life<00:15:55.600> easier<00:15:55.990> if<00:15:56.589> I<00:15:56.740> would<00:15:56.889> tell<00:15:57.129> you<00:15:57.339> I 00:15:57.629 --> 00:15:57.639 align:start position:0% your life easier if I would tell you I 00:15:57.639 --> 00:16:01.619 align:start position:0% your life easier if I would tell you I know<00:15:58.029> how<00:15:58.509> to<00:15:58.569> update<00:15:58.869> this<00:16:00.059> column<00:16:01.059> with<00:16:01.300> this 00:16:01.619 --> 00:16:01.629 align:start position:0% know how to update this column with this 00:16:01.629 --> 00:16:03.179 align:start position:0% know how to update this column with this field<00:16:01.869> because<00:16:02.230> it's<00:16:02.529> kind<00:16:02.649> of<00:16:02.769> my<00:16:02.920> metadata 00:16:03.179 --> 00:16:03.189 align:start position:0% field because it's kind of my metadata 00:16:03.189 --> 00:16:05.970 align:start position:0% field because it's kind of my metadata which<00:16:03.550> is<00:16:03.699> structured<00:16:04.240> and<00:16:04.540> I<00:16:05.230> only<00:16:05.410> kind<00:16:05.889> of 00:16:05.970 --> 00:16:05.980 align:start position:0% which is structured and I only kind of 00:16:05.980 --> 00:16:07.470 align:start position:0% which is structured and I only kind of you<00:16:06.069> know<00:16:06.100> I<00:16:06.220> have<00:16:06.519> a<00:16:06.550> list<00:16:06.879> of<00:16:07.059> you<00:16:07.360> know 00:16:07.470 --> 00:16:07.480 align:start position:0% you know I have a list of you know 00:16:07.480 --> 00:16:09.480 align:start position:0% you know I have a list of you know people<00:16:07.899> names<00:16:08.110> in<00:16:08.290> this<00:16:08.439> document<00:16:08.740> so<00:16:09.279> like 00:16:09.480 --> 00:16:09.490 align:start position:0% people names in this document so like 00:16:09.490 --> 00:16:11.579 align:start position:0% people names in this document so like inside<00:16:09.790> of<00:16:09.939> Jace<00:16:10.149> and<00:16:10.480> there<00:16:10.689> is<00:16:10.809> an<00:16:10.929> array<00:16:11.259> in 00:16:11.579 --> 00:16:11.589 align:start position:0% inside of Jace and there is an array in 00:16:11.589 --> 00:16:13.739 align:start position:0% inside of Jace and there is an array in that<00:16:12.100> array<00:16:12.429> I<00:16:12.459> did<00:16:12.819> three<00:16:13.059> my<00:16:13.179> name's<00:16:13.420> and<00:16:13.720> a 00:16:13.739 --> 00:16:13.749 align:start position:0% that array I did three my name's and a 00:16:13.749 --> 00:16:15.329 align:start position:0% that array I did three my name's and a replacement<00:16:14.230> like<00:16:14.350> so<00:16:14.529> that<00:16:14.709> like<00:16:14.889> I<00:16:15.069> know 00:16:15.329 --> 00:16:15.339 align:start position:0% replacement like so that like I know 00:16:15.339 --> 00:16:17.549 align:start position:0% replacement like so that like I know specifically<00:16:16.029> she<00:16:16.269> records<00:16:16.449> changed<00:16:16.869> would 00:16:17.549 --> 00:16:17.559 align:start position:0% specifically she records changed would 00:16:17.559 --> 00:16:21.629 align:start position:0% specifically she records changed would knowing<00:16:17.920> how<00:16:18.399> my<00:16:18.999> my<00:16:19.619> fields<00:16:20.619> differ<00:16:21.100> like 00:16:21.629 --> 00:16:21.639 align:start position:0% knowing how my my fields differ like 00:16:21.639 --> 00:16:22.949 align:start position:0% knowing how my my fields differ like having<00:16:22.029> a<00:16:22.089> diff<00:16:22.240> function<00:16:22.540> for<00:16:22.720> me<00:16:22.809> which<00:16:22.929> is 00:16:22.949 --> 00:16:22.959 align:start position:0% having a diff function for me which is 00:16:22.959 --> 00:16:27.210 align:start position:0% having a diff function for me which is most<00:16:23.259> efficient<00:16:23.879> simplify<00:16:24.879> life<00:16:25.920> not<00:16:26.920> really 00:16:27.210 --> 00:16:27.220 align:start position:0% most efficient simplify life not really 00:16:27.220 --> 00:16:29.069 align:start position:0% most efficient simplify life not really right<00:16:27.490> now<00:16:27.610> if<00:16:27.730> you<00:16:27.850> try<00:16:28.089> to<00:16:28.119> update<00:16:28.360> a<00:16:28.720> field 00:16:29.069 --> 00:16:29.079 align:start position:0% right now if you try to update a field 00:16:29.079 --> 00:16:31.290 align:start position:0% right now if you try to update a field like<00:16:29.290> you<00:16:29.559> just<00:16:29.709> you<00:16:29.889> have<00:16:30.069> to<00:16:30.220> provide<00:16:30.970> the 00:16:31.290 --> 00:16:31.300 align:start position:0% like you just you have to provide the 00:16:31.300 --> 00:16:33.119 align:start position:0% like you just you have to provide the whole<00:16:31.449> field<00:16:31.689> that<00:16:32.139> you<00:16:32.170> want<00:16:32.439> to<00:16:32.499> update<00:16:32.619> so 00:16:33.119 --> 00:16:33.129 align:start position:0% whole field that you want to update so 00:16:33.129 --> 00:16:35.489 align:start position:0% whole field that you want to update so but<00:16:33.459> as<00:16:33.670> I<00:16:34.119> was<00:16:34.269> saying<00:16:34.540> earlier<00:16:34.629> we<00:16:35.050> want<00:16:35.439> to 00:16:35.489 --> 00:16:35.499 align:start position:0% but as I was saying earlier we want to 00:16:35.499 --> 00:16:37.169 align:start position:0% but as I was saying earlier we want to add<00:16:35.649> those<00:16:35.920> nests<00:16:36.189> nested<00:16:36.550> data<00:16:36.639> type<00:16:36.939> so<00:16:37.089> you 00:16:37.169 --> 00:16:37.179 align:start position:0% add those nests nested data type so you 00:16:37.179 --> 00:16:38.429 align:start position:0% add those nests nested data type so you have<00:16:37.420> one<00:16:37.660> field<00:16:37.959> which<00:16:38.139> is<00:16:38.259> actually 00:16:38.429 --> 00:16:38.439 align:start position:0% have one field which is actually 00:16:38.439 --> 00:16:39.960 align:start position:0% have one field which is actually composed<00:16:38.949> of<00:16:39.129> many<00:16:39.249> fields<00:16:39.639> and<00:16:39.730> you<00:16:39.790> only 00:16:39.960 --> 00:16:39.970 align:start position:0% composed of many fields and you only 00:16:39.970 --> 00:16:41.730 align:start position:0% composed of many fields and you only want<00:16:40.240> to<00:16:40.300> update<00:16:40.420> one<00:16:40.809> thing<00:16:41.079> in<00:16:41.290> there<00:16:41.529> these 00:16:41.730 --> 00:16:41.740 align:start position:0% want to update one thing in there these 00:16:41.740 --> 00:16:43.949 align:start position:0% want to update one thing in there these are<00:16:41.889> that's<00:16:42.879> the<00:16:43.119> kind<00:16:43.300> of<00:16:43.329> optimization<00:16:43.839> that 00:16:43.949 --> 00:16:43.959 align:start position:0% are that's the kind of optimization that 00:16:43.959 --> 00:16:46.919 align:start position:0% are that's the kind of optimization that nested<00:16:44.290> data<00:16:44.350> types<00:16:45.209> usually<00:16:46.209> handle<00:16:46.749> and 00:16:46.919 --> 00:16:46.929 align:start position:0% nested data types usually handle and 00:16:46.929 --> 00:16:48.179 align:start position:0% nested data types usually handle and that's<00:16:47.079> not<00:16:47.170> something<00:16:47.319> that<00:16:47.589> we<00:16:47.679> have<00:16:47.920> that's 00:16:48.179 --> 00:16:48.189 align:start position:0% that's not something that we have that's 00:16:48.189 --> 00:16:50.489 align:start position:0% that's not something that we have that's something<00:16:48.490> we<00:16:48.579> want<00:16:48.730> to<00:16:48.819> have<00:16:48.910> oh<00:16:49.290> kudi<00:16:50.290> is 00:16:50.489 --> 00:16:50.499 align:start position:0% something we want to have oh kudi is 00:16:50.499 --> 00:16:53.009 align:start position:0% something we want to have oh kudi is only<00:16:50.709> a<00:16:50.829> little<00:16:51.309> bit<00:16:51.670> and<00:16:51.819> see<00:16:51.999> how<00:16:52.119> can<00:16:52.990> i 00:16:53.009 --> 00:16:53.019 align:start position:0% only a little bit and see how can i 00:16:53.019 --> 00:16:54.629 align:start position:0% only a little bit and see how can i still<00:16:53.259> only<00:16:53.379> in<00:16:53.470> better<00:16:53.740> and<00:16:54.069> we<00:16:54.189> release<00:16:54.459> the 00:16:54.629 --> 00:16:54.639 align:start position:0% still only in better and we release the 00:16:54.639 --> 00:16:56.460 align:start position:0% still only in better and we release the three<00:16:54.879> weeks<00:16:55.059> ago<00:16:55.209> so<00:16:55.420> we<00:16:55.509> still<00:16:55.689> but<00:16:56.290> the 00:16:56.460 --> 00:16:56.470 align:start position:0% three weeks ago so we still but the 00:16:56.470 --> 00:16:58.889 align:start position:0% three weeks ago so we still but the thing<00:16:56.619> is<00:16:56.649> the<00:16:57.160> the<00:16:57.189> reason<00:16:57.610> it<00:16:58.449> was<00:16:58.600> closed 00:16:58.889 --> 00:16:58.899 align:start position:0% thing is the the reason it was closed 00:16:58.899 --> 00:17:00.600 align:start position:0% thing is the the reason it was closed source<00:16:59.199> I've<00:16:59.619> brought<00:16:59.829> her<00:17:00.009> for<00:17:00.189> a<00:17:00.249> long<00:17:00.369> time 00:17:00.600 --> 00:17:00.610 align:start position:0% source I've brought her for a long time 00:17:00.610 --> 00:17:03.569 align:start position:0% source I've brought her for a long time like<00:17:00.850> almost<00:17:01.449> three<00:17:01.600> years<00:17:01.990> all<00:17:02.410> right<00:17:02.579> and 00:17:03.569 --> 00:17:03.579 align:start position:0% like almost three years all right and 00:17:03.579 --> 00:17:05.039 align:start position:0% like almost three years all right and now<00:17:04.029> we're<00:17:04.209> releasing<00:17:04.449> we're<00:17:04.809> not<00:17:04.899> really 00:17:05.039 --> 00:17:05.049 align:start position:0% now we're releasing we're not really 00:17:05.049 --> 00:17:06.389 align:start position:0% now we're releasing we're not really seeing<00:17:05.169> a<00:17:05.350> final<00:17:05.620> product<00:17:05.949> we're<00:17:06.159> really 00:17:06.389 --> 00:17:06.399 align:start position:0% seeing a final product we're really 00:17:06.399 --> 00:17:07.980 align:start position:0% seeing a final product we're really seeing<00:17:06.699> as<00:17:06.880> a<00:17:06.909> public<00:17:07.480> bit<00:17:07.630> oh<00:17:07.659> and<00:17:07.870> that's 00:17:07.980 --> 00:17:07.990 align:start position:0% seeing as a public bit oh and that's 00:17:07.990 --> 00:17:10.079 align:start position:0% seeing as a public bit oh and that's because<00:17:08.230> we<00:17:08.559> were<00:17:09.130> in<00:17:09.250> a<00:17:09.279> mode<00:17:09.459> where<00:17:09.490> we<00:17:09.880> want 00:17:10.079 --> 00:17:10.089 align:start position:0% because we were in a mode where we want 00:17:10.089 --> 00:17:11.970 align:start position:0% because we were in a mode where we want people<00:17:10.270> to<00:17:10.449> tell<00:17:11.110> us<00:17:11.230> about<00:17:11.350> their<00:17:11.589> use<00:17:11.770> cases 00:17:11.970 --> 00:17:11.980 align:start position:0% people to tell us about their use cases 00:17:11.980 --> 00:17:14.220 align:start position:0% people to tell us about their use cases and<00:17:12.309> see<00:17:12.970> like<00:17:13.120> a<00:17:13.149> we<00:17:13.630> don't<00:17:13.990> want<00:17:14.140> to 00:17:14.220 --> 00:17:14.230 align:start position:0% and see like a we don't want to 00:17:14.230 --> 00:17:16.980 align:start position:0% and see like a we don't want to prioritize<00:17:14.439> like<00:17:15.399> things<00:17:15.760> too<00:17:16.000> soon<00:17:16.299> yes<00:17:16.750> oh 00:17:16.980 --> 00:17:16.990 align:start position:0% prioritize like things too soon yes oh 00:17:16.990 --> 00:17:19.139 align:start position:0% prioritize like things too soon yes oh like<00:17:17.709> just<00:17:18.069> by<00:17:18.189> ourselves<00:17:18.220> you<00:17:18.669> want<00:17:18.850> to<00:17:18.939> write 00:17:19.139 --> 00:17:19.149 align:start position:0% like just by ourselves you want to write 00:17:19.149 --> 00:17:20.669 align:start position:0% like just by ourselves you want to write based<00:17:19.630> on<00:17:19.779> feedback<00:17:19.929> what<00:17:20.350> should<00:17:20.500> we<00:17:20.559> be 00:17:20.669 --> 00:17:20.679 align:start position:0% based on feedback what should we be 00:17:20.679 --> 00:17:22.559 align:start position:0% based on feedback what should we be building<00:17:21.010> for<00:17:21.250> this<00:17:21.399> data<00:17:21.640> store<00:17:21.880> cool<00:17:22.209> so 00:17:22.559 --> 00:17:22.569 align:start position:0% building for this data store cool so 00:17:22.569 --> 00:17:24.389 align:start position:0% building for this data store cool so it's<00:17:22.720> good<00:17:22.870> you<00:17:23.169> know<00:17:23.260> to<00:17:23.319> become<00:17:23.589> like<00:17:24.189> you 00:17:24.389 --> 00:17:24.399 align:start position:0% it's good you know to become like you 00:17:24.399 --> 00:17:26.789 align:start position:0% it's good you know to become like you know<00:17:24.520> if<00:17:24.760> you<00:17:24.909> like<00:17:25.059> somebody<00:17:25.569> wants<00:17:25.899> to<00:17:25.959> work 00:17:26.789 --> 00:17:26.799 align:start position:0% know if you like somebody wants to work 00:17:26.799 --> 00:17:28.049 align:start position:0% know if you like somebody wants to work well<00:17:27.069> for<00:17:27.159> the<00:17:27.250> use<00:17:27.370> case<00:17:27.549> you<00:17:27.819> know<00:17:27.939> this 00:17:28.049 --> 00:17:28.059 align:start position:0% well for the use case you know this 00:17:28.059 --> 00:17:29.549 align:start position:0% well for the use case you know this should<00:17:28.179> become<00:17:28.270> Apollo<00:17:28.600> customer<00:17:29.140> and<00:17:29.440> let's 00:17:29.549 --> 00:17:29.559 align:start position:0% should become Apollo customer and let's 00:17:29.559 --> 00:17:31.799 align:start position:0% should become Apollo customer and let's try<00:17:29.860> it<00:17:29.919> with<00:17:30.159> just<00:17:30.399> contribute<00:17:30.820> feedback<00:17:31.149> and 00:17:31.799 --> 00:17:31.809 align:start position:0% try it with just contribute feedback and 00:17:31.809 --> 00:17:33.720 align:start position:0% try it with just contribute feedback and also<00:17:32.320> it's<00:17:32.500> it's<00:17:32.890> an<00:17:32.980> open<00:17:33.190> source<00:17:33.370> database 00:17:33.720 --> 00:17:33.730 align:start position:0% also it's it's an open source database 00:17:33.730 --> 00:17:36.659 align:start position:0% also it's it's an open source database of<00:17:33.940> the<00:17:34.090> if<00:17:34.240> you<00:17:34.390> wanna<00:17:34.630> contribute<00:17:35.399> the<00:17:36.399> next 00:17:36.659 --> 00:17:36.669 align:start position:0% of the if you wanna contribute the next 00:17:36.669 --> 00:17:38.340 align:start position:0% of the if you wanna contribute the next data<00:17:36.880> type<00:17:37.149> implementation<00:17:37.809> patches<00:17:38.200> are 00:17:38.340 --> 00:17:38.350 align:start position:0% data type implementation patches are 00:17:38.350 --> 00:17:41.250 align:start position:0% data type implementation patches are welcome<00:17:38.740> as<00:17:38.919> we<00:17:39.070> say<00:17:39.220> yeah<00:17:39.490> well<00:17:39.760> I<00:17:40.390> did<00:17:40.840> a<00:17:41.049> lot 00:17:41.250 --> 00:17:41.260 align:start position:0% welcome as we say yeah well I did a lot 00:17:41.260 --> 00:17:44.700 align:start position:0% welcome as we say yeah well I did a lot of<00:17:41.289> C++<00:17:41.919> and<00:17:41.950> very<00:17:42.429> to<00:17:42.640> thousands<00:17:43.620> and<00:17:44.620> I 00:17:44.700 --> 00:17:44.710 align:start position:0% of C++ and very to thousands and I 00:17:44.710 --> 00:17:46.500 align:start position:0% of C++ and very to thousands and I vividly<00:17:44.919> remember<00:17:45.190> right<00:17:45.880> in<00:17:46.029> corpus<00:17:46.390> or 00:17:46.500 --> 00:17:46.510 align:start position:0% vividly remember right in corpus or 00:17:46.510 --> 00:17:48.100 align:start position:0% vividly remember right in corpus or cincy<00:17:46.929> possible 00:17:48.100 --> 00:17:48.110 align:start position:0% cincy possible 00:17:48.110 --> 00:17:52.030 align:start position:0% cincy possible yes<00:17:49.010> who<00:17:49.880> actually<00:17:50.030> proposed<00:17:50.570> to<00:17:50.990> add<00:17:51.170> a<00:17:51.590> flag 00:17:52.030 --> 00:17:52.040 align:start position:0% yes who actually proposed to add a flag 00:17:52.040 --> 00:17:54.160 align:start position:0% yes who actually proposed to add a flag to<00:17:52.520> g<00:17:52.700> +<00:17:52.880> +<00:17:53.059> cold<00:17:53.299> air<00:17:53.510> there's<00:17:53.750> not<00:17:53.929> an<00:17:54.049> idiot 00:17:54.160 --> 00:17:54.170 align:start position:0% to g + + cold air there's not an idiot 00:17:54.170 --> 00:17:57.039 align:start position:0% to g + + cold air there's not an idiot which<00:17:54.890> will<00:17:55.070> remove<00:17:55.429> certain<00:17:55.820> warnings<00:17:56.360> from 00:17:57.039 --> 00:17:57.049 align:start position:0% which will remove certain warnings from 00:17:57.049 --> 00:18:01.600 align:start position:0% which will remove certain warnings from auto-generated<00:17:57.740> korba<00:17:58.309> so<00:17:58.790> I<00:18:00.460> here's<00:18:01.460> a 00:18:01.600 --> 00:18:01.610 align:start position:0% auto-generated korba so I here's a 00:18:01.610 --> 00:18:04.350 align:start position:0% auto-generated korba so I here's a question<00:18:01.730> for<00:18:02.059> you<00:18:02.210> I<00:18:02.710> mean<00:18:03.710> this<00:18:03.890> is<00:18:04.070> pretty 00:18:04.350 --> 00:18:04.360 align:start position:0% question for you I mean this is pretty 00:18:04.360 --> 00:18:06.910 align:start position:0% question for you I mean this is pretty big<00:18:05.360> difference<00:18:05.480> right<00:18:05.900> so<00:18:06.200> you<00:18:06.350> work<00:18:06.470> in<00:18:06.650> Java 00:18:06.910 --> 00:18:06.920 align:start position:0% big difference right so you work in Java 00:18:06.920 --> 00:18:09.430 align:start position:0% big difference right so you work in Java and<00:18:07.490> it's<00:18:08.270> understandable<00:18:08.870> for<00:18:09.170> each<00:18:09.260> base 00:18:09.430 --> 00:18:09.440 align:start position:0% and it's understandable for each base 00:18:09.440 --> 00:18:10.930 align:start position:0% and it's understandable for each base you<00:18:09.590> almost<00:18:09.799> have<00:18:10.070> to<00:18:10.100> kind<00:18:10.340> of<00:18:10.429> fried<00:18:10.700> jar 00:18:10.930 --> 00:18:10.940 align:start position:0% you almost have to kind of fried jar 00:18:10.940 --> 00:18:12.460 align:start position:0% you almost have to kind of fried jar which<00:18:11.090> is<00:18:11.210> almost<00:18:11.360> like<00:18:11.540> assembly<00:18:12.080> like<00:18:12.320> its 00:18:12.460 --> 00:18:12.470 align:start position:0% which is almost like assembly like its 00:18:12.470 --> 00:18:14.380 align:start position:0% which is almost like assembly like its job<00:18:12.620> which<00:18:12.770> is<00:18:12.890> almost<00:18:13.040> like<00:18:13.250> see<00:18:13.549> right<00:18:14.210> like 00:18:14.380 --> 00:18:14.390 align:start position:0% job which is almost like see right like 00:18:14.390 --> 00:18:17.710 align:start position:0% job which is almost like see right like we<00:18:14.540> have<00:18:14.809> to<00:18:14.929> do<00:18:15.320> low-level<00:18:15.770> java<00:18:16.490> and<00:18:16.850> and<00:18:17.540> so 00:18:17.710 --> 00:18:17.720 align:start position:0% we have to do low-level java and and so 00:18:17.720 --> 00:18:20.710 align:start position:0% we have to do low-level java and and so kind<00:18:18.470> of<00:18:18.620> his<00:18:18.770> writing<00:18:19.580> the<00:18:19.850> database<00:18:20.179> in<00:18:20.270> C++ 00:18:20.710 --> 00:18:20.720 align:start position:0% kind of his writing the database in C++ 00:18:20.720 --> 00:18:22.840 align:start position:0% kind of his writing the database in C++ liberating<00:18:21.350> like<00:18:21.380> do<00:18:21.679> you<00:18:21.770> really<00:18:21.950> kind<00:18:22.760> of 00:18:22.840 --> 00:18:22.850 align:start position:0% liberating like do you really kind of 00:18:22.850 --> 00:18:24.250 align:start position:0% liberating like do you really kind of like<00:18:23.059> you<00:18:23.150> don't<00:18:23.299> want<00:18:23.480> me<00:18:23.660> to<00:18:23.809> pretend<00:18:23.960> it<00:18:24.169> to 00:18:24.250 --> 00:18:24.260 align:start position:0% like you don't want me to pretend it to 00:18:24.260 --> 00:18:26.350 align:start position:0% like you don't want me to pretend it to see<00:18:24.440> you<00:18:24.559> can<00:18:24.679> actually<00:18:25.010> write<00:18:25.250> it<00:18:25.400> and<00:18:25.549> see<00:18:25.820> is 00:18:26.350 --> 00:18:26.360 align:start position:0% see you can actually write it and see is 00:18:26.360 --> 00:18:28.720 align:start position:0% see you can actually write it and see is it<00:18:26.600> is<00:18:26.780> it<00:18:26.960> you<00:18:27.290> know<00:18:27.410> and<00:18:27.440> I<00:18:27.860> think<00:18:28.040> you<00:18:28.669> know 00:18:28.720 --> 00:18:28.730 align:start position:0% it is it you know and I think you know 00:18:28.730 --> 00:18:30.220 align:start position:0% it is it you know and I think you know the<00:18:29.000> same<00:18:29.179> thing<00:18:29.330> goes<00:18:29.360> for<00:18:29.510> in<00:18:29.720> Pollock<00:18:30.080> is 00:18:30.220 --> 00:18:30.230 align:start position:0% the same thing goes for in Pollock is 00:18:30.230 --> 00:18:32.919 align:start position:0% the same thing goes for in Pollock is this<00:18:30.470> is<00:18:30.950> this<00:18:31.370> like<00:18:31.910> what<00:18:32.270> is<00:18:32.390> your<00:18:32.419> take<00:18:32.720> on 00:18:32.919 --> 00:18:32.929 align:start position:0% this is this like what is your take on 00:18:32.929 --> 00:18:35.740 align:start position:0% this is this like what is your take on this<00:18:33.169> you<00:18:33.620> know<00:18:33.799> choice<00:18:34.490> you<00:18:34.940> know<00:18:35.059> Java<00:18:35.510> on 00:18:35.740 --> 00:18:35.750 align:start position:0% this you know choice you know Java on 00:18:35.750 --> 00:18:37.620 align:start position:0% this you know choice you know Java on the<00:18:35.929> one<00:18:36.080> hand<00:18:36.290> and<00:18:36.500> all<00:18:36.740> the<00:18:36.860> whole<00:18:36.980> ecosystem 00:18:37.620 --> 00:18:37.630 align:start position:0% the one hand and all the whole ecosystem 00:18:37.630 --> 00:18:41.820 align:start position:0% the one hand and all the whole ecosystem versus<00:18:38.630> applause<00:18:38.990> pause<00:18:39.260> for<00:18:39.950> the<00:18:40.040> database 00:18:41.820 --> 00:18:41.830 align:start position:0% versus applause pause for the database 00:18:41.830 --> 00:18:44.799 align:start position:0% versus applause pause for the database yeah<00:18:42.830> we<00:18:43.040> always<00:18:43.280> get<00:18:43.429> this<00:18:43.549> question<00:18:43.940> and 00:18:44.799 --> 00:18:44.809 align:start position:0% yeah we always get this question and 00:18:44.809 --> 00:18:46.690 align:start position:0% yeah we always get this question and again<00:18:45.350> there's<00:18:45.530> like<00:18:45.679> two<00:18:45.860> sides<00:18:46.130> for<00:18:46.429> it<00:18:46.549> like 00:18:46.690 --> 00:18:46.700 align:start position:0% again there's like two sides for it like 00:18:46.700 --> 00:18:48.250 align:start position:0% again there's like two sides for it like there's<00:18:46.910> a<00:18:46.970> personal<00:18:47.450> side<00:18:47.630> where<00:18:47.870> for<00:18:48.080> me<00:18:48.230> I 00:18:48.250 --> 00:18:48.260 align:start position:0% there's a personal side where for me I 00:18:48.260 --> 00:18:50.950 align:start position:0% there's a personal side where for me I have<00:18:48.890> been<00:18:49.040> working<00:18:49.220> in<00:18:49.669> Java<00:18:50.059> for<00:18:50.419> basically 00:18:50.950 --> 00:18:50.960 align:start position:0% have been working in Java for basically 00:18:50.960 --> 00:18:53.020 align:start position:0% have been working in Java for basically my<00:18:51.200> whole<00:18:51.230> professional<00:18:51.559> career<00:18:52.130> and<00:18:52.370> like 00:18:53.020 --> 00:18:53.030 align:start position:0% my whole professional career and like 00:18:53.030 --> 00:18:55.120 align:start position:0% my whole professional career and like hard<00:18:53.270> core<00:18:53.419> java<00:18:53.690> right<00:18:54.049> like<00:18:54.679> where<00:18:54.860> you're 00:18:55.120 --> 00:18:55.130 align:start position:0% hard core java right like where you're 00:18:55.130 --> 00:18:58.659 align:start position:0% hard core java right like where you're handling<00:18:55.429> and<00:18:55.820> terabytes<00:18:56.510> of<00:18:56.660> data<00:18:56.809> yes<00:18:57.669> and 00:18:58.659 --> 00:18:58.669 align:start position:0% handling and terabytes of data yes and 00:18:58.669 --> 00:19:01.240 align:start position:0% handling and terabytes of data yes and now<00:18:58.850> making<00:18:59.120> this<00:18:59.390> switch<00:18:59.660> to<00:18:59.690> C++<00:19:00.350> so<00:19:00.559> again 00:19:01.240 --> 00:19:01.250 align:start position:0% now making this switch to C++ so again 00:19:01.250 --> 00:19:02.860 align:start position:0% now making this switch to C++ so again on<00:19:01.400> the<00:19:01.490> personal<00:19:01.880> side<00:19:01.940> that<00:19:02.330> this<00:19:02.540> is<00:19:02.690> like 00:19:02.860 --> 00:19:02.870 align:start position:0% on the personal side that this is like 00:19:02.870 --> 00:19:04.210 align:start position:0% on the personal side that this is like this<00:19:03.020> was<00:19:03.169> like<00:19:03.200> a<00:19:03.350> new<00:19:03.530> challenge<00:19:03.890> for<00:19:03.950> me<00:19:04.190> I 00:19:04.210 --> 00:19:04.220 align:start position:0% this was like a new challenge for me I 00:19:04.220 --> 00:19:05.680 align:start position:0% this was like a new challenge for me I wanted<00:19:04.460> to<00:19:04.580> learn<00:19:04.790> something<00:19:05.179> you<00:19:05.330> don't<00:19:05.540> want 00:19:05.680 --> 00:19:05.690 align:start position:0% wanted to learn something you don't want 00:19:05.690 --> 00:19:07.720 align:start position:0% wanted to learn something you don't want to<00:19:05.809> do<00:19:05.990> something<00:19:06.679> that<00:19:06.950> I've<00:19:07.040> been<00:19:07.070> doing<00:19:07.490> but 00:19:07.720 --> 00:19:07.730 align:start position:0% to do something that I've been doing but 00:19:07.730 --> 00:19:10.480 align:start position:0% to do something that I've been doing but in<00:19:08.090> a<00:19:08.270> different<00:19:08.419> language<00:19:08.740> helps<00:19:09.740> you<00:19:09.890> like 00:19:10.480 --> 00:19:10.490 align:start position:0% in a different language helps you like 00:19:10.490 --> 00:19:13.030 align:start position:0% in a different language helps you like understand<00:19:10.970> other<00:19:11.929> things<00:19:12.140> better<00:19:12.290> I'd<00:19:12.830> say 00:19:13.030 --> 00:19:13.040 align:start position:0% understand other things better I'd say 00:19:13.040 --> 00:19:14.340 align:start position:0% understand other things better I'd say like<00:19:13.190> it<00:19:13.309> gives<00:19:13.520> you<00:19:13.580> another<00:19:13.730> perspective 00:19:14.340 --> 00:19:14.350 align:start position:0% like it gives you another perspective 00:19:14.350 --> 00:19:17.049 align:start position:0% like it gives you another perspective can<00:19:15.350> you<00:19:15.500> elaborate<00:19:16.280> like<00:19:16.700> what<00:19:16.850> is<00:19:16.970> the 00:19:17.049 --> 00:19:17.059 align:start position:0% can you elaborate like what is the 00:19:17.059 --> 00:19:19.900 align:start position:0% can you elaborate like what is the perspective<00:19:18.070> after<00:19:19.070> the<00:19:19.160> first<00:19:19.340> perspective 00:19:19.900 --> 00:19:19.910 align:start position:0% perspective after the first perspective 00:19:19.910 --> 00:19:22.030 align:start position:0% perspective after the first perspective is<00:19:20.090> like<00:19:20.270> the<00:19:20.870> garbage<00:19:21.110> collector<00:19:21.380> in<00:19:21.770> Java 00:19:22.030 --> 00:19:22.040 align:start position:0% is like the garbage collector in Java 00:19:22.040 --> 00:19:24.700 align:start position:0% is like the garbage collector in Java man<00:19:22.460> this<00:19:23.150> is<00:19:23.390> like<00:19:23.570> this<00:19:23.840> is<00:19:23.960> the<00:19:24.080> one<00:19:24.380> thing 00:19:24.700 --> 00:19:24.710 align:start position:0% man this is like this is the one thing 00:19:24.710 --> 00:19:27.700 align:start position:0% man this is like this is the one thing that<00:19:24.770> really<00:19:25.070> kills<00:19:25.640> it's<00:19:26.540> useful<00:19:26.990> it's 00:19:27.700 --> 00:19:27.710 align:start position:0% that really kills it's useful it's 00:19:27.710 --> 00:19:31.600 align:start position:0% that really kills it's useful it's useful<00:19:29.500> but<00:19:30.500> in<00:19:30.620> big<00:19:30.799> systems<00:19:31.190> where<00:19:31.370> you<00:19:31.490> have 00:19:31.600 --> 00:19:31.610 align:start position:0% useful but in big systems where you have 00:19:31.610 --> 00:19:33.400 align:start position:0% useful but in big systems where you have a<00:19:31.640> lot<00:19:31.790> of<00:19:31.820> data<00:19:31.970> going<00:19:32.240> through<00:19:32.780> the<00:19:32.960> JVM 00:19:33.400 --> 00:19:33.410 align:start position:0% a lot of data going through the JVM 00:19:33.410 --> 00:19:37.330 align:start position:0% a lot of data going through the JVM mm-hmm<00:19:33.980> it's<00:19:34.640> it's<00:19:35.059> it's<00:19:35.809> mostly<00:19:36.200> a<00:19:36.320> hassle<00:19:37.070> so 00:19:37.330 --> 00:19:37.340 align:start position:0% mm-hmm it's it's it's mostly a hassle so 00:19:37.340 --> 00:19:38.470 align:start position:0% mm-hmm it's it's it's mostly a hassle so you're<00:19:37.490> always<00:19:37.700> trying<00:19:38.059> to<00:19:38.179> put<00:19:38.330> stuff 00:19:38.470 --> 00:19:38.480 align:start position:0% you're always trying to put stuff 00:19:38.480 --> 00:19:40.840 align:start position:0% you're always trying to put stuff outside<00:19:38.929> of<00:19:39.110> the<00:19:39.260> heat<00:19:39.470> like<00:19:39.830> in<00:19:40.460> each<00:19:40.640> phase 00:19:40.840 --> 00:19:40.850 align:start position:0% outside of the heat like in each phase 00:19:40.850 --> 00:19:42.460 align:start position:0% outside of the heat like in each phase like<00:19:41.150> the<00:19:41.270> first<00:19:41.480> thing<00:19:41.660> we<00:19:41.780> got<00:19:41.929> outside<00:19:42.080> of 00:19:42.460 --> 00:19:42.470 align:start position:0% like the first thing we got outside of 00:19:42.470 --> 00:19:45.370 align:start position:0% like the first thing we got outside of the<00:19:42.770> heap<00:19:42.980> was<00:19:43.630> was<00:19:44.630> not<00:19:44.809> i'll<00:19:44.960> be<00:19:45.080> outside<00:19:45.230> the 00:19:45.370 --> 00:19:45.380 align:start position:0% the heap was was not i'll be outside the 00:19:45.380 --> 00:19:47.409 align:start position:0% the heap was was not i'll be outside the heat<00:19:45.590> like<00:19:45.799> we<00:19:45.919> use<00:19:46.070> dark<00:19:46.280> byte<00:19:46.460> buffers<00:19:46.820> for 00:19:47.409 --> 00:19:47.419 align:start position:0% heat like we use dark byte buffers for 00:19:47.419 --> 00:19:49.750 align:start position:0% heat like we use dark byte buffers for them<00:19:48.110> or<00:19:48.559> just<00:19:48.590> by<00:19:48.919> buffer<00:19:49.160> for<00:19:49.280> the<00:19:49.340> mem<00:19:49.549> store 00:19:49.750 --> 00:19:49.760 align:start position:0% them or just by buffer for the mem store 00:19:49.760 --> 00:19:52.060 align:start position:0% them or just by buffer for the mem store so<00:19:49.910> now<00:19:50.030> you're<00:19:50.240> managing<00:19:50.720> your<00:19:50.900> big<00:19:51.200> blob<00:19:52.040> of 00:19:52.060 --> 00:19:52.070 align:start position:0% so now you're managing your big blob of 00:19:52.070 --> 00:19:54.760 align:start position:0% so now you're managing your big blob of bytes<00:19:52.549> and<00:19:52.940> then<00:19:53.600> the<00:19:53.990> next<00:19:54.350> thing<00:19:54.500> was<00:19:54.710> like 00:19:54.760 --> 00:19:54.770 align:start position:0% bytes and then the next thing was like 00:19:54.770 --> 00:19:56.409 align:start position:0% bytes and then the next thing was like for<00:19:55.040> the<00:19:55.130> block<00:19:55.340> cash<00:19:55.580> because<00:19:55.940> you<00:19:56.150> want<00:19:56.300> to 00:19:56.409 --> 00:19:56.419 align:start position:0% for the block cash because you want to 00:19:56.419 --> 00:19:59.080 align:start position:0% for the block cash because you want to let<00:19:56.900> like<00:19:57.140> four<00:19:57.350> machines<00:19:57.590> today<00:19:57.800> 256<00:19:58.730> gigs<00:19:58.940> of 00:19:59.080 --> 00:19:59.090 align:start position:0% let like four machines today 256 gigs of 00:19:59.090 --> 00:19:59.820 align:start position:0% let like four machines today 256 gigs of ram<00:19:59.300> is 00:19:59.820 --> 00:19:59.830 align:start position:0% ram is 00:19:59.830 --> 00:20:02.130 align:start position:0% ram is it's<00:20:00.490> a<00:20:00.640> lot<00:20:00.909> but<00:20:01.179> it's<00:20:01.330> not<00:20:01.450> it's<00:20:01.899> something 00:20:02.130 --> 00:20:02.140 align:start position:0% it's a lot but it's not it's something 00:20:02.140 --> 00:20:05.880 align:start position:0% it's a lot but it's not it's something like<00:20:02.169> crazy<00:20:02.590> right<00:20:03.360> and<00:20:04.360> years<00:20:05.110> ago<00:20:05.320> was<00:20:05.440> 64 00:20:05.880 --> 00:20:05.890 align:start position:0% like crazy right and years ago was 64 00:20:05.890 --> 00:20:08.759 align:start position:0% like crazy right and years ago was 64 but<00:20:06.010> like<00:20:06.250> try<00:20:06.519> creating<00:20:07.299> a<00:20:07.539> JVM<00:20:08.019> that's<00:20:08.350> fans 00:20:08.759 --> 00:20:08.769 align:start position:0% but like try creating a JVM that's fans 00:20:08.769 --> 00:20:11.370 align:start position:0% but like try creating a JVM that's fans those<00:20:09.100> like<00:20:09.340> 250<00:20:10.090> something<00:20:10.450> gigabytes<00:20:11.110> and 00:20:11.370 --> 00:20:11.380 align:start position:0% those like 250 something gigabytes and 00:20:11.380 --> 00:20:14.669 align:start position:0% those like 250 something gigabytes and then<00:20:12.130> you<00:20:12.250> hit<00:20:12.370> the<00:20:12.399> gc's<00:20:13.080> LGC<00:20:14.080> it's<00:20:14.320> like<00:20:14.470> end 00:20:14.669 --> 00:20:14.679 align:start position:0% then you hit the gc's LGC it's like end 00:20:14.679 --> 00:20:17.370 align:start position:0% then you hit the gc's LGC it's like end of<00:20:14.799> the<00:20:14.919> world<00:20:15.159> that<00:20:15.429> Noah's<00:20:15.610> gone<00:20:16.120> right<00:20:16.570> so 00:20:17.370 --> 00:20:17.380 align:start position:0% of the world that Noah's gone right so 00:20:17.380 --> 00:20:19.470 align:start position:0% of the world that Noah's gone right so you<00:20:17.440> want<00:20:17.769> a<00:20:17.799> black<00:20:17.980> ash<00:20:18.190> that<00:20:18.370> fits<00:20:18.820> in<00:20:19.090> ram 00:20:19.470 --> 00:20:19.480 align:start position:0% you want a black ash that fits in ram 00:20:19.480 --> 00:20:22.320 align:start position:0% you want a black ash that fits in ram but<00:20:20.289> not<00:20:20.470> on<00:20:20.590> the<00:20:20.769> JVM<00:20:21.190> that<00:20:21.789> again<00:20:22.149> you're 00:20:22.320 --> 00:20:22.330 align:start position:0% but not on the JVM that again you're 00:20:22.330 --> 00:20:26.039 align:start position:0% but not on the JVM that again you're going<00:20:22.539> off<00:20:22.809> the<00:20:23.019> heap<00:20:23.460> so<00:20:24.460> all<00:20:25.149> that<00:20:25.210> all<00:20:25.720> the 00:20:26.039 --> 00:20:26.049 align:start position:0% going off the heap so all that all the 00:20:26.049 --> 00:20:29.159 align:start position:0% going off the heap so all that all the effort<00:20:26.799> like<00:20:27.100> in<00:20:27.700> C++<00:20:28.360> as<00:20:28.570> long<00:20:28.929> as<00:20:29.049> you're 00:20:29.159 --> 00:20:29.169 align:start position:0% effort like in C++ as long as you're 00:20:29.169 --> 00:20:30.870 align:start position:0% effort like in C++ as long as you're managing<00:20:29.620> you're<00:20:30.070> managing<00:20:30.340> your<00:20:30.429> own<00:20:30.519> memory 00:20:30.870 --> 00:20:30.880 align:start position:0% managing you're managing your own memory 00:20:30.880 --> 00:20:31.980 align:start position:0% managing you're managing your own memory and<00:20:31.059> there's<00:20:31.179> a<00:20:31.210> lot<00:20:31.360> of<00:20:31.390> tools<00:20:31.659> now<00:20:31.840> that 00:20:31.980 --> 00:20:31.990 align:start position:0% and there's a lot of tools now that 00:20:31.990 --> 00:20:33.389 align:start position:0% and there's a lot of tools now that exist<00:20:32.320> to<00:20:32.409> make<00:20:32.529> sure<00:20:32.649> you<00:20:32.769> don't<00:20:32.919> have<00:20:33.010> memory 00:20:33.389 --> 00:20:33.399 align:start position:0% exist to make sure you don't have memory 00:20:33.399 --> 00:20:35.129 align:start position:0% exist to make sure you don't have memory leak<00:20:33.580> that<00:20:34.210> you're<00:20:34.389> always<00:20:34.659> destroying<00:20:35.019> the 00:20:35.129 --> 00:20:35.139 align:start position:0% leak that you're always destroying the 00:20:35.139 --> 00:20:37.549 align:start position:0% leak that you're always destroying the object<00:20:35.409> you're<00:20:35.500> supposed<00:20:35.799> to<00:20:35.889> be<00:20:35.980> destroying 00:20:37.549 --> 00:20:37.559 align:start position:0% object you're supposed to be destroying 00:20:37.559 --> 00:20:40.919 align:start position:0% object you're supposed to be destroying like<00:20:38.559> our<00:20:38.769> built<00:20:39.250> environment<00:20:39.309> has<00:20:39.970> like<00:20:40.779> we 00:20:40.919 --> 00:20:40.929 align:start position:0% like our built environment has like we 00:20:40.929 --> 00:20:42.539 align:start position:0% like our built environment has like we have<00:20:41.080> memory<00:20:41.409> checker<00:20:41.710> we<00:20:42.100> have<00:20:42.250> address 00:20:42.539 --> 00:20:42.549 align:start position:0% have memory checker we have address 00:20:42.549 --> 00:20:45.330 align:start position:0% have memory checker we have address checker<00:20:42.760> we<00:20:43.210> have<00:20:43.330> thread<00:20:43.570> checker<00:20:44.130> and<00:20:45.130> we 00:20:45.330 --> 00:20:45.340 align:start position:0% checker we have thread checker and we 00:20:45.340 --> 00:20:47.250 align:start position:0% checker we have thread checker and we limit<00:20:45.610> ourselves<00:20:45.730> to<00:20:46.179> a<00:20:46.870> set<00:20:47.049> of<00:20:47.139> libraries 00:20:47.250 --> 00:20:47.260 align:start position:0% limit ourselves to a set of libraries 00:20:47.260 --> 00:20:49.710 align:start position:0% limit ourselves to a set of libraries that<00:20:47.710> are<00:20:47.769> like<00:20:48.100> well<00:20:48.639> known<00:20:48.880> in<00:20:49.090> c++<00:20:49.570> that 00:20:49.710 --> 00:20:49.720 align:start position:0% that are like well known in c++ that 00:20:49.720 --> 00:20:51.360 align:start position:0% that are like well known in c++ that we're<00:20:49.929> not<00:20:50.049> actively<00:20:50.620> trying<00:20:50.980> to<00:20:51.220> show 00:20:51.360 --> 00:20:51.370 align:start position:0% we're not actively trying to show 00:20:51.370 --> 00:20:54.690 align:start position:0% we're not actively trying to show ourselves<00:20:51.429> in<00:20:51.940> our<00:20:52.450> food<00:20:52.659> okay<00:20:53.200> so<00:20:54.010> but<00:20:54.610> you 00:20:54.690 --> 00:20:54.700 align:start position:0% ourselves in our food okay so but you 00:20:54.700 --> 00:20:57.330 align:start position:0% ourselves in our food okay so but you know<00:20:55.049> gvm<00:20:56.049> has<00:20:56.169> come<00:20:56.350> almost<00:20:56.830> an<00:20:56.950> extreme 00:20:57.330 --> 00:20:57.340 align:start position:0% know gvm has come almost an extreme 00:20:57.340 --> 00:20:59.519 align:start position:0% know gvm has come almost an extreme linked<00:20:57.730> with<00:20:57.880> the<00:20:58.120> big<00:20:58.630> data<00:20:58.809> like<00:20:59.110> a<00:20:59.200> system 00:20:59.519 --> 00:20:59.529 align:start position:0% linked with the big data like a system 00:20:59.529 --> 00:21:01.860 align:start position:0% linked with the big data like a system ipod<00:20:59.799> us<00:20:59.919> and<00:21:00.340> we're<00:21:00.549> soon<00:21:00.789> big<00:21:00.909> data<00:21:01.090> is<00:21:01.269> kadu 00:21:01.860 --> 00:21:01.870 align:start position:0% ipod us and we're soon big data is kadu 00:21:01.870 --> 00:21:04.259 align:start position:0% ipod us and we're soon big data is kadu panas<00:21:02.230> JVM<00:21:02.769> and<00:21:02.980> basically<00:21:03.700> assume<00:21:04.000> you<00:21:04.090> have 00:21:04.259 --> 00:21:04.269 align:start position:0% panas JVM and basically assume you have 00:21:04.269 --> 00:21:05.759 align:start position:0% panas JVM and basically assume you have a<00:21:04.299> distributed<00:21:04.809> system<00:21:04.840> and<00:21:05.169> GV<00:21:05.380> m<00:21:05.529> and 00:21:05.759 --> 00:21:05.769 align:start position:0% a distributed system and GV m and 00:21:05.769 --> 00:21:08.399 align:start position:0% a distributed system and GV m and everything<00:21:06.309> we<00:21:06.399> should<00:21:06.549> details<00:21:06.850> how<00:21:07.419> do<00:21:08.350> you 00:21:08.399 --> 00:21:08.409 align:start position:0% everything we should details how do you 00:21:08.409 --> 00:21:12.120 align:start position:0% everything we should details how do you find<00:21:08.679> a<00:21:09.039> system<00:21:09.370> written<00:21:09.580> in<00:21:09.639> C++<00:21:11.130> interacting 00:21:12.120 --> 00:21:12.130 align:start position:0% find a system written in C++ interacting 00:21:12.130 --> 00:21:14.580 align:start position:0% find a system written in C++ interacting with<00:21:12.250> this<00:21:12.429> like<00:21:12.700> do<00:21:12.880> you<00:21:12.970> do<00:21:13.210> you<00:21:13.299> hear<00:21:13.899> is<00:21:14.110> it 00:21:14.580 --> 00:21:14.590 align:start position:0% with this like do you do you hear is it 00:21:14.590 --> 00:21:18.210 align:start position:0% with this like do you do you hear is it is<00:21:14.889> it<00:21:15.070> a<00:21:15.539> disadvantage<00:21:16.539> that<00:21:16.960> it's<00:21:17.919> you<00:21:18.159> know 00:21:18.210 --> 00:21:18.220 align:start position:0% is it a disadvantage that it's you know 00:21:18.220 --> 00:21:20.190 align:start position:0% is it a disadvantage that it's you know you<00:21:18.370> don't<00:21:18.639> have<00:21:18.909> everything<00:21:19.659> with<00:21:19.960> Java 00:21:20.190 --> 00:21:20.200 align:start position:0% you don't have everything with Java 00:21:20.200 --> 00:21:23.129 align:start position:0% you don't have everything with Java gives<00:21:20.470> you<00:21:20.590> for<00:21:20.769> free<00:21:21.010> already<00:21:21.880> how<00:21:22.809> did<00:21:23.049> you 00:21:23.129 --> 00:21:23.139 align:start position:0% gives you for free already how did you 00:21:23.139 --> 00:21:25.889 align:start position:0% gives you for free already how did you find<00:21:23.169> it<00:21:23.500> in<00:21:23.799> practice<00:21:24.269> it's<00:21:25.269> a<00:21:25.360> trade-off<00:21:25.600> I 00:21:25.889 --> 00:21:25.899 align:start position:0% find it in practice it's a trade-off I 00:21:25.899 --> 00:21:26.850 align:start position:0% find it in practice it's a trade-off I would<00:21:26.019> say<00:21:26.110> it's<00:21:26.169> definitely<00:21:26.590> a<00:21:26.620> trade<00:21:26.830> of 00:21:26.850 --> 00:21:26.860 align:start position:0% would say it's definitely a trade of 00:21:26.860 --> 00:21:29.419 align:start position:0% would say it's definitely a trade of like<00:21:27.070> I<00:21:27.100> wouldn't<00:21:27.610> say<00:21:27.730> like<00:21:27.909> oh<00:21:28.059> my<00:21:28.210> god<00:21:28.389> C++ 00:21:29.419 --> 00:21:29.429 align:start position:0% like I wouldn't say like oh my god C++ 00:21:29.429 --> 00:21:31.889 align:start position:0% like I wouldn't say like oh my god C++ best<00:21:30.429> solution<00:21:30.850> why<00:21:31.120> isn't<00:21:31.360> everybody<00:21:31.539> going 00:21:31.889 --> 00:21:31.899 align:start position:0% best solution why isn't everybody going 00:21:31.899 --> 00:21:34.259 align:start position:0% best solution why isn't everybody going c<00:21:32.049> plus<00:21:32.200> plus<00:21:32.230> there's<00:21:33.130> a<00:21:33.190> lot<00:21:33.370> of<00:21:33.399> people<00:21:33.580> well 00:21:34.259 --> 00:21:34.269 align:start position:0% c plus plus there's a lot of people well 00:21:34.269 --> 00:21:36.149 align:start position:0% c plus plus there's a lot of people well like<00:21:34.480> me<00:21:34.720> like<00:21:35.080> three<00:21:35.409> years<00:21:35.559> ago<00:21:35.889> that 00:21:36.149 --> 00:21:36.159 align:start position:0% like me like three years ago that 00:21:36.159 --> 00:21:38.490 align:start position:0% like me like three years ago that wouldn't<00:21:36.460> touch<00:21:36.639> c++<00:21:37.389> projects<00:21:37.899> so<00:21:38.470> that 00:21:38.490 --> 00:21:38.500 align:start position:0% wouldn't touch c++ projects so that 00:21:38.500 --> 00:21:39.899 align:start position:0% wouldn't touch c++ projects so that right<00:21:39.070> there<00:21:39.130> there's<00:21:39.610> a<00:21:39.669> bunch<00:21:39.850> of 00:21:39.899 --> 00:21:39.909 align:start position:0% right there there's a bunch of 00:21:39.909 --> 00:21:41.870 align:start position:0% right there there's a bunch of contributors<00:21:40.419> that<00:21:40.539> you<00:21:40.870> can't<00:21:41.409> really<00:21:41.470> get 00:21:41.870 --> 00:21:41.880 align:start position:0% contributors that you can't really get 00:21:41.880 --> 00:21:43.769 align:start position:0% contributors that you can't really get on<00:21:42.880> the<00:21:43.059> other<00:21:43.149> side<00:21:43.240> there's<00:21:43.570> a<00:21:43.630> lot<00:21:43.750> of 00:21:43.769 --> 00:21:43.779 align:start position:0% on the other side there's a lot of 00:21:43.779 --> 00:21:45.240 align:start position:0% on the other side there's a lot of people<00:21:44.049> are<00:21:44.200> like<00:21:44.380> oh<00:21:44.500> my<00:21:44.710> god<00:21:44.889> finally 00:21:45.240 --> 00:21:45.250 align:start position:0% people are like oh my god finally 00:21:45.250 --> 00:21:48.690 align:start position:0% people are like oh my god finally something<00:21:45.730> in<00:21:45.850> C++<00:21:46.389> on<00:21:46.539> the<00:21:46.630> storage<00:21:46.840> side<00:21:47.700> and 00:21:48.690 --> 00:21:48.700 align:start position:0% something in C++ on the storage side and 00:21:48.700 --> 00:21:50.190 align:start position:0% something in C++ on the storage side and then<00:21:48.820> we<00:21:48.909> have<00:21:49.029> Impala<00:21:49.360> which<00:21:49.659> is<00:21:49.809> already<00:21:50.110> in 00:21:50.190 --> 00:21:50.200 align:start position:0% then we have Impala which is already in 00:21:50.200 --> 00:21:52.500 align:start position:0% then we have Impala which is already in C++<00:21:50.710> yes<00:21:51.039> and<00:21:51.340> other<00:21:51.730> projects<00:21:52.240> are<00:21:52.389> also 00:21:52.500 --> 00:21:52.510 align:start position:0% C++ yes and other projects are also 00:21:52.510 --> 00:21:54.480 align:start position:0% C++ yes and other projects are also looking<00:21:52.779> at<00:21:52.960> like<00:21:53.769> spark<00:21:54.100> the<00:21:54.190> tungsten 00:21:54.480 --> 00:21:54.490 align:start position:0% looking at like spark the tungsten 00:21:54.490 --> 00:21:56.940 align:start position:0% looking at like spark the tungsten project<00:21:55.120> isn't<00:21:55.419> isn't<00:21:55.899> isn't<00:21:56.200> it<00:21:56.409> like<00:21:56.590> also 00:21:56.940 --> 00:21:56.950 align:start position:0% project isn't isn't isn't it like also 00:21:56.950 --> 00:22:00.600 align:start position:0% project isn't isn't isn't it like also going<00:21:57.190> away<00:21:57.399> from<00:21:58.090> from<00:21:58.809> Scala<00:21:59.110> well<00:21:59.889> and<00:22:00.130> I 00:22:00.600 --> 00:22:00.610 align:start position:0% going away from from Scala well and I 00:22:00.610 --> 00:22:03.090 align:start position:0% going away from from Scala well and I think<00:22:00.639> its<00:22:00.880> memory<00:22:01.210> management<00:22:01.950> kind<00:22:02.950> of<00:22:03.010> i 00:22:03.090 --> 00:22:03.100 align:start position:0% think its memory management kind of i 00:22:03.100 --> 00:22:04.740 align:start position:0% think its memory management kind of i mean<00:22:03.220> i<00:22:03.279> think<00:22:03.399> people<00:22:03.639> people<00:22:04.299> want<00:22:04.630> to 00:22:04.740 --> 00:22:04.750 align:start position:0% mean i think people people want to 00:22:04.750 --> 00:22:06.360 align:start position:0% mean i think people people want to manage<00:22:05.019> memory<00:22:05.260> kind<00:22:05.590> of<00:22:05.710> an<00:22:05.889> artisanal 00:22:06.360 --> 00:22:06.370 align:start position:0% manage memory kind of an artisanal 00:22:06.370 --> 00:22:07.620 align:start position:0% manage memory kind of an artisanal fashion 00:22:07.620 --> 00:22:07.630 align:start position:0% fashion 00:22:07.630 --> 00:22:09.990 align:start position:0% fashion but<00:22:08.230> but<00:22:08.770> i<00:22:08.830> think<00:22:09.130> i'm<00:22:09.370> a<00:22:09.400> lot<00:22:09.670> of<00:22:09.790> them<00:22:09.880> us 00:22:09.990 --> 00:22:10.000 align:start position:0% but but i think i'm a lot of them us 00:22:10.000 --> 00:22:12.320 align:start position:0% but but i think i'm a lot of them us trying<00:22:10.210> to<00:22:10.360> stay<00:22:10.930> within<00:22:11.140> GV<00:22:11.440> m<00:22:11.680> I<00:22:11.800> think<00:22:12.010> flink 00:22:12.320 --> 00:22:12.330 align:start position:0% trying to stay within GV m I think flink 00:22:12.330 --> 00:22:15.090 align:start position:0% trying to stay within GV m I think flink did<00:22:13.330> this<00:22:13.510> right<00:22:13.780> so<00:22:13.960> I<00:22:14.170> think<00:22:14.290> the<00:22:14.530> question 00:22:15.090 --> 00:22:15.100 align:start position:0% did this right so I think the question 00:22:15.100 --> 00:22:16.830 align:start position:0% did this right so I think the question like<00:22:15.190> what<00:22:15.340> you've<00:22:15.460> done<00:22:15.490> with<00:22:15.940> HBase<00:22:16.480> right 00:22:16.830 --> 00:22:16.840 align:start position:0% like what you've done with HBase right 00:22:16.840 --> 00:22:20.040 align:start position:0% like what you've done with HBase right so<00:22:16.990> if<00:22:17.590> you<00:22:17.740> can<00:22:17.980> do<00:22:18.190> a<00:22:18.400> reasonable<00:22:18.790> job<00:22:19.050> from 00:22:20.040 --> 00:22:20.050 align:start position:0% so if you can do a reasonable job from 00:22:20.050 --> 00:22:23.370 align:start position:0% so if you can do a reasonable job from within<00:22:20.380> Java<00:22:21.150> but<00:22:22.150> yeah<00:22:22.660> that's<00:22:22.840> interesting 00:22:23.370 --> 00:22:23.380 align:start position:0% within Java but yeah that's interesting 00:22:23.380 --> 00:22:24.780 align:start position:0% within Java but yeah that's interesting and<00:22:23.650> there's<00:22:24.100> a<00:22:24.160> lot<00:22:24.280> of<00:22:24.340> things<00:22:24.550> that<00:22:24.610> we're 00:22:24.780 --> 00:22:24.790 align:start position:0% and there's a lot of things that we're 00:22:24.790 --> 00:22:26.370 align:start position:0% and there's a lot of things that we're doing<00:22:24.880> kudu<00:22:25.540> that<00:22:25.690> we<00:22:25.780> you<00:22:26.020> wouldn't<00:22:26.260> be<00:22:26.320> able 00:22:26.370 --> 00:22:26.380 align:start position:0% doing kudu that we you wouldn't be able 00:22:26.380 --> 00:22:28.080 align:start position:0% doing kudu that we you wouldn't be able to<00:22:26.530> do<00:22:26.680> the<00:22:26.770> JVM<00:22:27.160> like<00:22:27.340> using<00:22:27.550> the<00:22:27.760> SSE 00:22:28.080 --> 00:22:28.090 align:start position:0% to do the JVM like using the SSE 00:22:28.090 --> 00:22:29.430 align:start position:0% to do the JVM like using the SSE instructions<00:22:28.120> orders<00:22:28.780> in<00:22:28.930> the<00:22:28.960> instructions 00:22:29.430 --> 00:22:29.440 align:start position:0% instructions orders in the instructions 00:22:29.440 --> 00:22:31.020 align:start position:0% instructions orders in the instructions you'll<00:22:29.920> have<00:22:30.070> to<00:22:30.190> go<00:22:30.280> through<00:22:30.310> the<00:22:30.730> J'naii 00:22:31.020 --> 00:22:31.030 align:start position:0% you'll have to go through the J'naii 00:22:31.030 --> 00:22:32.550 align:start position:0% you'll have to go through the J'naii interface<00:22:31.510> in<00:22:31.690> order<00:22:31.840> to<00:22:31.990> be<00:22:32.080> able<00:22:32.170> to<00:22:32.380> get 00:22:32.550 --> 00:22:32.560 align:start position:0% interface in order to be able to get 00:22:32.560 --> 00:22:34.650 align:start position:0% interface in order to be able to get there<00:22:32.770> right<00:22:33.010> so<00:22:33.940> this<00:22:34.090> is<00:22:34.120> something<00:22:34.360> that<00:22:34.480> we 00:22:34.650 --> 00:22:34.660 align:start position:0% there right so this is something that we 00:22:34.660 --> 00:22:38.010 align:start position:0% there right so this is something that we can<00:22:34.810> just<00:22:34.840> naturally<00:22:35.470> do<00:22:35.650> in<00:22:36.430> C++<00:22:36.940> ok<00:22:37.450> no<00:22:37.840> this 00:22:38.010 --> 00:22:38.020 align:start position:0% can just naturally do in C++ ok no this 00:22:38.020 --> 00:22:42.360 align:start position:0% can just naturally do in C++ ok no this is<00:22:38.110> interesting<00:22:38.880> so<00:22:40.170> so<00:22:41.170> I<00:22:41.200> don't<00:22:41.980> realized 00:22:42.360 --> 00:22:42.370 align:start position:0% is interesting so so I don't realized 00:22:42.370 --> 00:22:44.550 align:start position:0% is interesting so so I don't realized that<00:22:42.670> kudos<00:22:43.120> in<00:22:43.300> gestation<00:22:43.600> for<00:22:44.050> three<00:22:44.230> years 00:22:44.550 --> 00:22:44.560 align:start position:0% that kudos in gestation for three years 00:22:44.560 --> 00:22:46.710 align:start position:0% that kudos in gestation for three years and<00:22:44.830> maybe<00:22:45.520> like<00:22:45.760> the<00:22:45.880> best<00:22:46.060> kept<00:22:46.360> secret 00:22:46.710 --> 00:22:46.720 align:start position:0% and maybe like the best kept secret 00:22:46.720 --> 00:22:49.380 align:start position:0% and maybe like the best kept secret because<00:22:46.840> I<00:22:47.050> haven't<00:22:47.230> heard<00:22:47.440> about<00:22:47.530> it<00:22:47.650> so<00:22:48.390> you 00:22:49.380 --> 00:22:49.390 align:start position:0% because I haven't heard about it so you 00:22:49.390 --> 00:22:51.480 align:start position:0% because I haven't heard about it so you can<00:22:49.600> go<00:22:49.780> on<00:22:49.960> there's<00:22:50.290> a<00:22:50.350> question<00:22:50.770> on<00:22:50.800> Quora<00:22:51.160> I 00:22:51.480 --> 00:22:51.490 align:start position:0% can go on there's a question on Quora I 00:22:51.490 --> 00:22:53.280 align:start position:0% can go on there's a question on Quora I think<00:22:51.700> was<00:22:51.850> asked<00:22:52.150> two<00:22:52.270> years<00:22:52.510> ago<00:22:52.690> and<00:22:52.930> it<00:22:53.080> was 00:22:53.280 --> 00:22:53.290 align:start position:0% think was asked two years ago and it was 00:22:53.290 --> 00:22:55.320 align:start position:0% think was asked two years ago and it was what<00:22:53.920> is<00:22:54.040> that<00:22:54.220> lip<00:22:54.460> con<00:22:54.640> doing<00:22:54.910> these<00:22:55.030> days 00:22:55.320 --> 00:22:55.330 align:start position:0% what is that lip con doing these days 00:22:55.330 --> 00:22:57.480 align:start position:0% what is that lip con doing these days uh-huh<00:22:55.900> cuz<00:22:56.290> toddlercon<00:22:56.590> is<00:22:56.830> the<00:22:56.980> tech<00:22:57.370> lead 00:22:57.480 --> 00:22:57.490 align:start position:0% uh-huh cuz toddlercon is the tech lead 00:22:57.490 --> 00:22:59.160 align:start position:0% uh-huh cuz toddlercon is the tech lead for<00:22:57.550> kudi<00:22:57.970> net<00:22:58.150> it's<00:22:58.360> basically<00:22:58.750> his 00:22:59.160 --> 00:22:59.170 align:start position:0% for kudi net it's basically his 00:22:59.170 --> 00:23:00.630 align:start position:0% for kudi net it's basically his brainchild<00:22:59.470> like<00:22:59.860> he<00:22:59.980> thought<00:23:00.220> about<00:23:00.250> this 00:23:00.630 --> 00:23:00.640 align:start position:0% brainchild like he thought about this 00:23:00.640 --> 00:23:01.890 align:start position:0% brainchild like he thought about this for<00:23:00.700> three<00:23:01.120> years<00:23:01.240> ago<00:23:01.330> he<00:23:01.570> was<00:23:01.690> the<00:23:01.780> one 00:23:01.890 --> 00:23:01.900 align:start position:0% for three years ago he was the one 00:23:01.900 --> 00:23:03.510 align:start position:0% for three years ago he was the one working<00:23:02.080> on<00:23:02.260> it<00:23:02.380> mostly<00:23:02.650> and<00:23:02.920> uh<00:23:02.980> huh<00:23:03.100> he's 00:23:03.510 --> 00:23:03.520 align:start position:0% working on it mostly and uh huh he's 00:23:03.520 --> 00:23:05.820 align:start position:0% working on it mostly and uh huh he's he's<00:23:04.300> a<00:23:04.330> he's<00:23:04.720> the<00:23:04.750> one<00:23:05.020> that<00:23:05.230> knows<00:23:05.500> like 00:23:05.820 --> 00:23:05.830 align:start position:0% he's a he's the one that knows like 00:23:05.830 --> 00:23:07.680 align:start position:0% he's a he's the one that knows like everything<00:23:05.980> about<00:23:06.340> cool<00:23:06.670> so<00:23:07.120> how<00:23:07.300> come<00:23:07.510> we 00:23:07.680 --> 00:23:07.690 align:start position:0% everything about cool so how come we 00:23:07.690 --> 00:23:10.230 align:start position:0% everything about cool so how come we never<00:23:07.720> heard<00:23:08.020> about<00:23:08.290> it<00:23:08.410> was<00:23:08.710> it<00:23:08.860> like<00:23:09.610> a<00:23:09.640> skunk 00:23:10.230 --> 00:23:10.240 align:start position:0% never heard about it was it like a skunk 00:23:10.240 --> 00:23:11.880 align:start position:0% never heard about it was it like a skunk works<00:23:10.390> project<00:23:10.570> was<00:23:11.140> it<00:23:11.260> kind<00:23:11.470> of<00:23:11.590> you<00:23:11.830> know 00:23:11.880 --> 00:23:11.890 align:start position:0% works project was it kind of you know 00:23:11.890 --> 00:23:16.140 align:start position:0% works project was it kind of you know slowly<00:23:12.420> brewing<00:23:13.420> or<00:23:14.730> like<00:23:15.730> we're<00:23:15.940> still<00:23:16.090> a 00:23:16.140 --> 00:23:16.150 align:start position:0% slowly brewing or like we're still a 00:23:16.150 --> 00:23:18.360 align:start position:0% slowly brewing or like we're still a very<00:23:16.390> small<00:23:16.660> team<00:23:16.870> like<00:23:17.050> six<00:23:17.590> people<00:23:17.740> mm-hmm 00:23:18.360 --> 00:23:18.370 align:start position:0% very small team like six people mm-hmm 00:23:18.370 --> 00:23:21.780 align:start position:0% very small team like six people mm-hmm so<00:23:19.120> we<00:23:19.240> were<00:23:19.360> just<00:23:19.390> the<00:23:20.380> first<00:23:20.950> thing<00:23:21.280> that<00:23:21.310> was 00:23:21.780 --> 00:23:21.790 align:start position:0% so we were just the first thing that was 00:23:21.790 --> 00:23:24.120 align:start position:0% so we were just the first thing that was built<00:23:22.090> was<00:23:22.510> just<00:23:22.900> a<00:23:22.990> really<00:23:23.290> fast<00:23:23.560> call<00:23:23.830> nor 00:23:24.120 --> 00:23:24.130 align:start position:0% built was just a really fast call nor 00:23:24.130 --> 00:23:27.000 align:start position:0% built was just a really fast call nor datastore<00:23:24.490> and<00:23:24.820> then<00:23:25.690> on<00:23:25.870> top<00:23:26.020> of<00:23:26.080> it<00:23:26.290> we<00:23:26.530> build 00:23:27.000 --> 00:23:27.010 align:start position:0% datastore and then on top of it we build 00:23:27.010 --> 00:23:29.880 align:start position:0% datastore and then on top of it we build the<00:23:27.100> rest<00:23:27.340> but<00:23:27.610> we<00:23:28.020> we<00:23:29.020> wanted<00:23:29.440> to<00:23:29.470> be<00:23:29.590> able<00:23:29.680> to 00:23:29.880 --> 00:23:29.890 align:start position:0% the rest but we we wanted to be able to 00:23:29.890 --> 00:23:32.070 align:start position:0% the rest but we we wanted to be able to iterate<00:23:30.040> really<00:23:30.520> fast<00:23:30.900> internally<00:23:31.900> before 00:23:32.070 --> 00:23:32.080 align:start position:0% iterate really fast internally before 00:23:32.080 --> 00:23:34.260 align:start position:0% iterate really fast internally before going<00:23:32.560> outside<00:23:32.800> and<00:23:33.310> then<00:23:33.460> like<00:23:33.730> going<00:23:34.090> for 00:23:34.260 --> 00:23:34.270 align:start position:0% going outside and then like going for 00:23:34.270 --> 00:23:36.210 align:start position:0% going outside and then like going for contributions<00:23:34.510> which<00:23:34.960> is<00:23:35.140> like<00:23:35.650> a<00:23:35.680> model<00:23:36.190> that 00:23:36.210 --> 00:23:36.220 align:start position:0% contributions which is like a model that 00:23:36.220 --> 00:23:38.220 align:start position:0% contributions which is like a model that drill<00:23:36.640> took<00:23:37.210> like<00:23:37.450> they<00:23:37.600> went<00:23:37.900> from<00:23:38.020> like 00:23:38.220 --> 00:23:38.230 align:start position:0% drill took like they went from like 00:23:38.230 --> 00:23:40.800 align:start position:0% drill took like they went from like let's<00:23:38.530> design<00:23:39.010> by<00:23:39.250> committee<00:23:39.430> then<00:23:40.330> and<00:23:40.660> then 00:23:40.800 --> 00:23:40.810 align:start position:0% let's design by committee then and then 00:23:40.810 --> 00:23:42.120 align:start position:0% let's design by committee then and then build<00:23:41.020> that<00:23:41.140> way<00:23:41.320> which<00:23:41.500> is<00:23:41.530> also<00:23:41.740> like 00:23:42.120 --> 00:23:42.130 align:start position:0% build that way which is also like 00:23:42.130 --> 00:23:43.680 align:start position:0% build that way which is also like another<00:23:42.550> very<00:23:42.820> valid<00:23:43.120> way<00:23:43.240> of<00:23:43.270> doing<00:23:43.540> things 00:23:43.680 --> 00:23:43.690 align:start position:0% another very valid way of doing things 00:23:43.690 --> 00:23:47.070 align:start position:0% another very valid way of doing things that's<00:23:44.380> the<00:23:44.500> way<00:23:44.590> we<00:23:44.740> chose<00:23:44.950> ok<00:23:45.660> and<00:23:46.660> ok<00:23:46.690> so 00:23:47.070 --> 00:23:47.080 align:start position:0% that's the way we chose ok and ok so 00:23:47.080 --> 00:23:48.330 align:start position:0% that's the way we chose ok and ok so I'll<00:23:47.350> get<00:23:47.560> the<00:23:47.650> wrap<00:23:47.860> up<00:23:48.010> with<00:23:48.160> a<00:23:48.190> very 00:23:48.330 --> 00:23:48.340 align:start position:0% I'll get the wrap up with a very 00:23:48.340 --> 00:23:50.310 align:start position:0% I'll get the wrap up with a very philosophical<00:23:49.060> question<00:23:49.450> and<00:23:49.600> even<00:23:49.960> kind<00:23:50.230> of 00:23:50.310 --> 00:23:50.320 align:start position:0% philosophical question and even kind of 00:23:50.320 --> 00:23:52.260 align:start position:0% philosophical question and even kind of very<00:23:51.130> abstract<00:23:51.490> so<00:23:51.670> I've<00:23:51.760> had<00:23:51.910> the<00:23:52.000> viscera 00:23:52.260 --> 00:23:52.270 align:start position:0% very abstract so I've had the viscera 00:23:52.270 --> 00:23:54.480 align:start position:0% very abstract so I've had the viscera variance<00:23:52.840> conversation<00:23:53.620> with<00:23:53.800> Evan<00:23:54.250> Weaver 00:23:54.480 --> 00:23:54.490 align:start position:0% variance conversation with Evan Weaver 00:23:54.490 --> 00:23:57.720 align:start position:0% variance conversation with Evan Weaver who<00:23:54.790> is<00:23:54.940> a<00:23:54.970> has<00:23:55.900> a<00:23:55.930> comical<00:23:56.290> fauna<00:23:56.530> DB<00:23:56.890> which<00:23:57.490> is 00:23:57.720 --> 00:23:57.730 align:start position:0% who is a has a comical fauna DB which is 00:23:57.730 --> 00:23:59.310 align:start position:0% who is a has a comical fauna DB which is you<00:23:58.120> know<00:23:58.180> a<00:23:58.300> different<00:23:58.510> take<00:23:58.810> on<00:23:58.930> a<00:23:58.990> database 00:23:59.310 --> 00:23:59.320 align:start position:0% you know a different take on a database 00:23:59.320 --> 00:24:02.760 align:start position:0% you know a different take on a database and<00:23:59.830> kind<00:24:00.310> of<00:24:00.400> its<00:24:00.930> you<00:24:01.930> know<00:24:02.080> hasn't<00:24:02.410> launched 00:24:02.760 --> 00:24:02.770 align:start position:0% and kind of its you know hasn't launched 00:24:02.770 --> 00:24:04.950 align:start position:0% and kind of its you know hasn't launched properly<00:24:03.190> yet<00:24:03.400> so<00:24:03.640> you<00:24:03.700> know<00:24:03.970> I<00:24:04.210> don't<00:24:04.690> know 00:24:04.950 --> 00:24:04.960 align:start position:0% properly yet so you know I don't know 00:24:04.960 --> 00:24:06.630 align:start position:0% properly yet so you know I don't know much<00:24:05.470> about<00:24:05.620> it<00:24:05.740> but<00:24:05.920> we<00:24:06.070> just<00:24:06.310> had<00:24:06.460> this 00:24:06.630 --> 00:24:06.640 align:start position:0% much about it but we just had this 00:24:06.640 --> 00:24:08.610 align:start position:0% much about it but we just had this channel<00:24:07.000> discussion<00:24:07.360> of<00:24:07.480> Evan<00:24:07.810> about<00:24:08.110> you 00:24:08.610 --> 00:24:08.620 align:start position:0% channel discussion of Evan about you 00:24:08.620 --> 00:24:09.990 align:start position:0% channel discussion of Evan about you know<00:24:08.710> the<00:24:08.740> role<00:24:08.950> of<00:24:08.980> the<00:24:09.160> database<00:24:09.550> and<00:24:09.700> so<00:24:09.850> he 00:24:09.990 --> 00:24:10.000 align:start position:0% know the role of the database and so he 00:24:10.000 --> 00:24:12.210 align:start position:0% know the role of the database and so he built<00:24:10.150> it<00:24:10.330> a<00:24:10.360> sort<00:24:10.630> of<00:24:10.690> Twitter<00:24:10.930> in<00:24:11.740> handle 00:24:12.210 --> 00:24:12.220 align:start position:0% built it a sort of Twitter in handle 00:24:12.220 --> 00:24:15.240 align:start position:0% built it a sort of Twitter in handle dramatic<00:24:12.850> throughput<00:24:13.720> so<00:24:14.470> he<00:24:14.770> has<00:24:15.040> got<00:24:15.220> a 00:24:15.240 --> 00:24:15.250 align:start position:0% dramatic throughput so he has got a 00:24:15.250 --> 00:24:17.790 align:start position:0% dramatic throughput so he has got a first-hand<00:24:15.550> experience<00:24:16.180> with<00:24:16.930> the<00:24:17.440> systems 00:24:17.790 --> 00:24:17.800 align:start position:0% first-hand experience with the systems 00:24:17.800 --> 00:24:19.950 align:start position:0% first-hand experience with the systems and<00:24:17.950> an<00:24:18.670> obviously<00:24:19.120> with<00:24:19.360> reduced 00:24:19.950 --> 00:24:19.960 align:start position:0% and an obviously with reduced 00:24:19.960 --> 00:24:21.360 align:start position:0% and an obviously with reduced us<00:24:20.110> and<00:24:20.440> kind<00:24:20.740> of<00:24:20.860> they<00:24:20.980> have<00:24:21.130> their<00:24:21.280> own 00:24:21.360 --> 00:24:21.370 align:start position:0% us and kind of they have their own 00:24:21.370 --> 00:24:22.890 align:start position:0% us and kind of they have their own strument<00:24:21.850> so<00:24:22.030> they<00:24:22.150> need<00:24:22.330> to<00:24:22.360> build<00:24:22.570> the<00:24:22.750> whole 00:24:22.890 --> 00:24:22.900 align:start position:0% strument so they need to build the whole 00:24:22.900 --> 00:24:24.240 align:start position:0% strument so they need to build the whole big<00:24:23.140> data<00:24:23.290> stack<00:24:23.530> because<00:24:23.620> they<00:24:23.860> have<00:24:24.010> a<00:24:24.040> user 00:24:24.240 --> 00:24:24.250 align:start position:0% big data stack because they have a user 00:24:24.250 --> 00:24:27.090 align:start position:0% big data stack because they have a user so<00:24:24.910> he<00:24:25.240> actually<00:24:25.960> better<00:24:26.290> some<00:24:26.560> interesting 00:24:27.090 --> 00:24:27.100 align:start position:0% so he actually better some interesting 00:24:27.100 --> 00:24:28.650 align:start position:0% so he actually better some interesting ideas<00:24:27.310> in<00:24:27.820> he<00:24:28.000> basically<00:24:28.240> said<00:24:28.390> like<00:24:28.510> you<00:24:28.570> know 00:24:28.650 --> 00:24:28.660 align:start position:0% ideas in he basically said like you know 00:24:28.660 --> 00:24:32.220 align:start position:0% ideas in he basically said like you know he's<00:24:29.110> thinking<00:24:29.410> of<00:24:29.470> you<00:24:29.800> know<00:24:29.920> using<00:24:31.230> query 00:24:32.220 --> 00:24:32.230 align:start position:0% he's thinking of you know using query 00:24:32.230 --> 00:24:35.040 align:start position:0% he's thinking of you know using query level<00:24:32.650> processes<00:24:33.190> as<00:24:33.750> granularity<00:24:34.750> level 00:24:35.040 --> 00:24:35.050 align:start position:0% level processes as granularity level 00:24:35.050 --> 00:24:37.410 align:start position:0% level processes as granularity level right<00:24:35.230> so<00:24:35.410> and<00:24:35.620> in<00:24:35.950> kind<00:24:36.160> of<00:24:36.310> if<00:24:36.880> you<00:24:37.120> think<00:24:37.150> of 00:24:37.410 --> 00:24:37.420 align:start position:0% right so and in kind of if you think of 00:24:37.420 --> 00:24:38.640 align:start position:0% right so and in kind of if you think of this<00:24:37.510> whole<00:24:37.570> land<00:24:37.930> architectures<00:24:38.410> whole 00:24:38.640 --> 00:24:38.650 align:start position:0% this whole land architectures whole 00:24:38.650 --> 00:24:40.200 align:start position:0% this whole land architectures whole stack<00:24:38.980> so<00:24:39.160> you're<00:24:39.490> assuming<00:24:39.760> that<00:24:40.060> you<00:24:40.180> have 00:24:40.200 --> 00:24:40.210 align:start position:0% stack so you're assuming that you have 00:24:40.210 --> 00:24:42.420 align:start position:0% stack so you're assuming that you have distributed<00:24:41.080> systems<00:24:41.440> such<00:24:41.560> as<00:24:41.590> aqua<00:24:42.010> Kafka 00:24:42.420 --> 00:24:42.430 align:start position:0% distributed systems such as aqua Kafka 00:24:42.430 --> 00:24:44.910 align:start position:0% distributed systems such as aqua Kafka spark<00:24:43.090> cassandra<00:24:43.810> and<00:24:43.930> there<00:24:44.500> but<00:24:44.650> kind<00:24:44.830> of 00:24:44.910 --> 00:24:44.920 align:start position:0% spark cassandra and there but kind of 00:24:44.920 --> 00:24:46.890 align:start position:0% spark cassandra and there but kind of you<00:24:45.040> know<00:24:45.070> they<00:24:45.280> have<00:24:45.400> this<00:24:45.490> big<00:24:45.700> knowles<00:24:45.940> the 00:24:46.890 --> 00:24:46.900 align:start position:0% you know they have this big knowles the 00:24:46.900 --> 00:24:48.810 align:start position:0% you know they have this big knowles the assuming<00:24:47.290> they<00:24:47.410> have<00:24:47.560> a<00:24:47.590> machine<00:24:47.770> to<00:24:48.550> put<00:24:48.790> a 00:24:48.810 --> 00:24:48.820 align:start position:0% assuming they have a machine to put a 00:24:48.820 --> 00:24:51.150 align:start position:0% assuming they have a machine to put a demon<00:24:49.300> all<00:24:49.450> and<00:24:49.600> do<00:24:49.750> something<00:24:50.110> there<00:24:50.290> but<00:24:50.950> in 00:24:51.150 --> 00:24:51.160 align:start position:0% demon all and do something there but in 00:24:51.160 --> 00:24:52.650 align:start position:0% demon all and do something there but in the<00:24:51.310> end<00:24:51.340> everything<00:24:51.760> or<00:24:52.030> the<00:24:52.150> only<00:24:52.480> thing 00:24:52.650 --> 00:24:52.660 align:start position:0% the end everything or the only thing 00:24:52.660 --> 00:24:54.450 align:start position:0% the end everything or the only thing they're<00:24:52.810> doing<00:24:52.990> they're<00:24:53.260> running<00:24:53.500> queries<00:24:53.650> so 00:24:54.450 --> 00:24:54.460 align:start position:0% they're doing they're running queries so 00:24:54.460 --> 00:24:57.690 align:start position:0% they're doing they're running queries so why<00:24:54.670> not<00:24:55.080> focus<00:24:56.080> on<00:24:56.380> queries<00:24:56.830> and<00:24:57.100> basically 00:24:57.690 --> 00:24:57.700 align:start position:0% why not focus on queries and basically 00:24:57.700 --> 00:25:00.390 align:start position:0% why not focus on queries and basically have<00:24:57.880> this<00:24:58.000> whole<00:24:58.150> cluster<00:24:59.100> instead<00:25:00.100> of<00:25:00.130> kind 00:25:00.390 --> 00:25:00.400 align:start position:0% have this whole cluster instead of kind 00:25:00.400 --> 00:25:02.100 align:start position:0% have this whole cluster instead of kind of<00:25:00.550> putting<00:25:00.790> together<00:25:00.910> all<00:25:01.300> the<00:25:01.630> things<00:25:01.900> and 00:25:02.100 --> 00:25:02.110 align:start position:0% of putting together all the things and 00:25:02.110 --> 00:25:03.900 align:start position:0% of putting together all the things and putting<00:25:02.320> them<00:25:02.440> in<00:25:02.590> docker<00:25:02.950> containers<00:25:03.520> and 00:25:03.900 --> 00:25:03.910 align:start position:0% putting them in docker containers and 00:25:03.910 --> 00:25:07.110 align:start position:0% putting them in docker containers and using<00:25:04.540> masses<00:25:05.050> to<00:25:05.740> to<00:25:06.040> balance<00:25:06.550> them<00:25:06.820> and 00:25:07.110 --> 00:25:07.120 align:start position:0% using masses to to balance them and 00:25:07.120 --> 00:25:09.810 align:start position:0% using masses to to balance them and schedule<00:25:07.660> them<00:25:08.080> why<00:25:08.620> don't<00:25:08.860> we<00:25:09.010> drop<00:25:09.250> down<00:25:09.580> to 00:25:09.810 --> 00:25:09.820 align:start position:0% schedule them why don't we drop down to 00:25:09.820 --> 00:25:11.580 align:start position:0% schedule them why don't we drop down to the<00:25:09.940> level<00:25:10.120> of<00:25:10.390> the<00:25:10.450> final<00:25:10.900> work<00:25:11.110> result<00:25:11.470> which 00:25:11.580 --> 00:25:11.590 align:start position:0% the level of the final work result which 00:25:11.590 --> 00:25:14.010 align:start position:0% the level of the final work result which is<00:25:11.680> a<00:25:11.710> query<00:25:12.070> and<00:25:12.400> think<00:25:13.060> of<00:25:13.180> it<00:25:13.570> as<00:25:13.690> a<00:25:13.720> process 00:25:14.010 --> 00:25:14.020 align:start position:0% is a query and think of it as a process 00:25:14.020 --> 00:25:15.780 align:start position:0% is a query and think of it as a process right<00:25:14.560> and<00:25:14.800> then<00:25:14.920> basically<00:25:15.160> when<00:25:15.610> Anna 00:25:15.780 --> 00:25:15.790 align:start position:0% right and then basically when Anna 00:25:15.790 --> 00:25:17.700 align:start position:0% right and then basically when Anna schedule<00:25:16.090> is<00:25:16.210> queries<00:25:16.510> on<00:25:16.600> the<00:25:16.690> cluster<00:25:16.900> we 00:25:17.700 --> 00:25:17.710 align:start position:0% schedule is queries on the cluster we 00:25:17.710 --> 00:25:19.140 align:start position:0% schedule is queries on the cluster we know<00:25:17.920> exactly<00:25:18.160> what<00:25:18.640> we're<00:25:18.820> working<00:25:18.970> with 00:25:19.140 --> 00:25:19.150 align:start position:0% know exactly what we're working with 00:25:19.150 --> 00:25:21.000 align:start position:0% know exactly what we're working with instead<00:25:19.960> of<00:25:20.110> having<00:25:20.320> tag<00:25:20.530> to<00:25:20.680> move<00:25:20.830> like 00:25:21.000 --> 00:25:21.010 align:start position:0% instead of having tag to move like 00:25:21.010 --> 00:25:23.370 align:start position:0% instead of having tag to move like little<00:25:21.370> Linux<00:25:21.670> light<00:25:22.540> containers<00:25:23.110> around 00:25:23.370 --> 00:25:23.380 align:start position:0% little Linux light containers around 00:25:23.380 --> 00:25:26.550 align:start position:0% little Linux light containers around it's<00:25:24.010> also<00:25:24.430> so<00:25:25.090> it<00:25:25.360> really<00:25:25.630> struck<00:25:26.050> me<00:25:26.080> as<00:25:26.530> a 00:25:26.550 --> 00:25:26.560 align:start position:0% it's also so it really struck me as a 00:25:26.560 --> 00:25:29.280 align:start position:0% it's also so it really struck me as a revelation<00:25:27.430> right<00:25:28.000> that<00:25:28.210> you<00:25:28.540> know<00:25:28.630> if<00:25:28.780> in<00:25:29.170> the 00:25:29.280 --> 00:25:29.290 align:start position:0% revelation right that you know if in the 00:25:29.290 --> 00:25:32.130 align:start position:0% revelation right that you know if in the end<00:25:29.410> if<00:25:29.560> all<00:25:29.740> we<00:25:29.980> want<00:25:30.130> to<00:25:30.190> do<00:25:30.430> is<00:25:30.730> run<00:25:31.600> you<00:25:32.020> know 00:25:32.130 --> 00:25:32.140 align:start position:0% end if all we want to do is run you know 00:25:32.140 --> 00:25:34.770 align:start position:0% end if all we want to do is run you know queries<00:25:32.650> against<00:25:32.920> some<00:25:33.130> stream<00:25:33.460> of<00:25:33.610> data<00:25:33.780> why 00:25:34.770 --> 00:25:34.780 align:start position:0% queries against some stream of data why 00:25:34.780 --> 00:25:36.990 align:start position:0% queries against some stream of data why don't<00:25:35.020> we<00:25:35.140> optimize<00:25:35.470> the<00:25:35.650> whole<00:25:35.830> thing<00:25:36.130> for 00:25:36.990 --> 00:25:37.000 align:start position:0% don't we optimize the whole thing for 00:25:37.000 --> 00:25:39.630 align:start position:0% don't we optimize the whole thing for this<00:25:37.180> purpose<00:25:37.560> so<00:25:38.560> I'm<00:25:38.890> just<00:25:39.160> wondering<00:25:39.400> what 00:25:39.630 --> 00:25:39.640 align:start position:0% this purpose so I'm just wondering what 00:25:39.640 --> 00:25:41.550 align:start position:0% this purpose so I'm just wondering what your<00:25:39.790> take<00:25:39.940> on<00:25:39.970> this<00:25:40.300> having<00:25:40.810> built<00:25:41.020> kudo<00:25:41.320> for 00:25:41.550 --> 00:25:41.560 align:start position:0% your take on this having built kudo for 00:25:41.560 --> 00:25:45.030 align:start position:0% your take on this having built kudo for this<00:25:41.800> criminal<00:25:42.130> case<00:25:42.280> right<00:25:43.150> I<00:25:43.840> mean<00:25:44.650> this<00:25:44.860> is 00:25:45.030 --> 00:25:45.040 align:start position:0% this criminal case right I mean this is 00:25:45.040 --> 00:25:46.710 align:start position:0% this criminal case right I mean this is like<00:25:45.070> very<00:25:45.550> new<00:25:45.820> to<00:25:46.000> me<00:25:46.030> I'm<00:25:46.240> trying<00:25:46.540> to 00:25:46.710 --> 00:25:46.720 align:start position:0% like very new to me I'm trying to 00:25:46.720 --> 00:25:48.930 align:start position:0% like very new to me I'm trying to understand<00:25:47.230> you<00:25:47.470> know<00:25:48.040> the<00:25:48.580> meaning<00:25:48.790> of<00:25:48.880> this 00:25:48.930 --> 00:25:48.940 align:start position:0% understand you know the meaning of this 00:25:48.940 --> 00:25:51.030 align:start position:0% understand you know the meaning of this so<00:25:49.330> I'm<00:25:49.420> just<00:25:49.450> kind<00:25:49.720> of<00:25:49.870> narrated<00:25:50.560> relating<00:25:50.950> it 00:25:51.030 --> 00:25:51.040 align:start position:0% so I'm just kind of narrated relating it 00:25:51.040 --> 00:25:52.380 align:start position:0% so I'm just kind of narrated relating it back<00:25:51.100> to<00:25:51.370> you<00:25:51.490> and<00:25:51.610> kind<00:25:51.760> of<00:25:51.880> am<00:25:52.000> wondering 00:25:52.380 --> 00:25:52.390 align:start position:0% back to you and kind of am wondering 00:25:52.390 --> 00:25:53.970 align:start position:0% back to you and kind of am wondering what<00:25:52.510> what<00:25:52.720> what's<00:25:53.020> your<00:25:53.170> take<00:25:53.290> on<00:25:53.320> that<00:25:53.530> I 00:25:53.970 --> 00:25:53.980 align:start position:0% what what what's your take on that I 00:25:53.980 --> 00:25:55.560 align:start position:0% what what what's your take on that I would<00:25:54.490> say<00:25:54.640> I'm<00:25:54.760> exactly<00:25:55.030> where<00:25:55.300> you<00:25:55.450> are 00:25:55.560 --> 00:25:55.570 align:start position:0% would say I'm exactly where you are 00:25:55.570 --> 00:25:56.910 align:start position:0% would say I'm exactly where you are actually<00:25:55.780> that's<00:25:56.080> the<00:25:56.140> first<00:25:56.380> time<00:25:56.500> I<00:25:56.650> hear 00:25:56.910 --> 00:25:56.920 align:start position:0% actually that's the first time I hear 00:25:56.920 --> 00:25:59.880 align:start position:0% actually that's the first time I hear about<00:25:57.160> this<00:25:57.250> idea<00:25:57.640> and<00:25:57.940> I<00:25:58.420> definitely<00:25:59.230> need<00:25:59.770> to 00:25:59.880 --> 00:25:59.890 align:start position:0% about this idea and I definitely need to 00:25:59.890 --> 00:26:03.180 align:start position:0% about this idea and I definitely need to spend<00:26:00.100> more<00:26:00.160> time<00:26:00.280> thinking<00:26:00.460> about<00:26:00.880> it<00:26:02.070> well<00:26:03.070> I 00:26:03.180 --> 00:26:03.190 align:start position:0% spend more time thinking about it well I 00:26:03.190 --> 00:26:04.770 align:start position:0% spend more time thinking about it well I wonder<00:26:03.670> what<00:26:03.850> the<00:26:03.910> trade-offs<00:26:04.270> are<00:26:04.390> because 00:26:04.770 --> 00:26:04.780 align:start position:0% wonder what the trade-offs are because 00:26:04.780 --> 00:26:06.060 align:start position:0% wonder what the trade-offs are because there's<00:26:04.930> nothing<00:26:05.230> perfect<00:26:05.410> right<00:26:05.770> so<00:26:05.920> if 00:26:06.060 --> 00:26:06.070 align:start position:0% there's nothing perfect right so if 00:26:06.070 --> 00:26:07.470 align:start position:0% there's nothing perfect right so if you're<00:26:06.220> doing<00:26:06.430> this<00:26:06.580> where<00:26:06.820> are<00:26:06.880> you<00:26:07.090> not<00:26:07.360> able 00:26:07.470 --> 00:26:07.480 align:start position:0% you're doing this where are you not able 00:26:07.480 --> 00:26:09.480 align:start position:0% you're doing this where are you not able to<00:26:07.720> do<00:26:07.870> that<00:26:08.830> that<00:26:09.010> would<00:26:09.040> be<00:26:09.130> my<00:26:09.340> first 00:26:09.480 --> 00:26:09.490 align:start position:0% to do that that would be my first 00:26:09.490 --> 00:26:12.390 align:start position:0% to do that that would be my first question<00:26:09.910> right<00:26:10.330> right<00:26:10.810> right<00:26:10.870> so<00:26:11.860> but<00:26:12.280> in 00:26:12.390 --> 00:26:12.400 align:start position:0% question right right right so but in 00:26:12.400 --> 00:26:14.820 align:start position:0% question right right right so but in that<00:26:12.550> sense<00:26:12.790> so<00:26:12.940> you<00:26:13.300> do<00:26:13.450> is<00:26:13.570> kind<00:26:13.720> of<00:26:13.870> it's 00:26:14.820 --> 00:26:14.830 align:start position:0% that sense so you do is kind of it's 00:26:14.830 --> 00:26:16.470 align:start position:0% that sense so you do is kind of it's enough<00:26:15.250> the<00:26:15.340> distributed<00:26:15.880> system<00:26:15.910> right<00:26:16.330> so 00:26:16.470 --> 00:26:16.480 align:start position:0% enough the distributed system right so 00:26:16.480 --> 00:26:18.870 align:start position:0% enough the distributed system right so like<00:26:16.600> so<00:26:16.870> you<00:26:16.930> you<00:26:17.440> know<00:26:17.740> you<00:26:18.010> want<00:26:18.340> to<00:26:18.370> coexist 00:26:18.870 --> 00:26:18.880 align:start position:0% like so you you know you want to coexist 00:26:18.880 --> 00:26:21.330 align:start position:0% like so you you know you want to coexist effectively<00:26:19.510> like<00:26:19.810> if<00:26:19.960> you<00:26:20.080> run<00:26:20.290> Kafka<00:26:20.800> spark 00:26:21.330 --> 00:26:21.340 align:start position:0% effectively like if you run Kafka spark 00:26:21.340 --> 00:26:23.670 align:start position:0% effectively like if you run Kafka spark and<00:26:21.520> guru<00:26:21.730> you<00:26:22.450> will<00:26:22.630> have<00:26:22.870> the<00:26:23.080> demons<00:26:23.470> on 00:26:23.670 --> 00:26:23.680 align:start position:0% and guru you will have the demons on 00:26:23.680 --> 00:26:26.430 align:start position:0% and guru you will have the demons on each<00:26:23.830> node<00:26:24.520> right<00:26:25.450> so<00:26:25.900> so<00:26:26.080> like<00:26:26.230> in<00:26:26.350> the 00:26:26.430 --> 00:26:26.440 align:start position:0% each node right so so like in the 00:26:26.440 --> 00:26:28.950 align:start position:0% each node right so so like in the current<00:26:26.800> situation<00:26:27.240> like<00:26:28.240> will<00:26:28.420> hope<00:26:28.690> you 00:26:28.950 --> 00:26:28.960 align:start position:0% current situation like will hope you 00:26:28.960 --> 00:26:30.360 align:start position:0% current situation like will hope you know<00:26:29.080> like<00:26:29.410> the<00:26:29.560> locality<00:26:30.040> will<00:26:30.130> be<00:26:30.280> achieved 00:26:30.360 --> 00:26:30.370 align:start position:0% know like the locality will be achieved 00:26:30.370 --> 00:26:32.440 align:start position:0% know like the locality will be achieved by<00:26:30.880> somehow<00:26:31.330> making<00:26:31.690> everybody 00:26:32.440 --> 00:26:32.450 align:start position:0% by somehow making everybody 00:26:32.450 --> 00:26:36.550 align:start position:0% by somehow making everybody together<00:26:32.840> right<00:26:33.740> so<00:26:34.810> yeah<00:26:35.810> I<00:26:35.840> mean<00:26:36.290> just 00:26:36.550 --> 00:26:36.560 align:start position:0% together right so yeah I mean just 00:26:36.560 --> 00:26:38.320 align:start position:0% together right so yeah I mean just something<00:26:36.770> I<00:26:36.860> kind<00:26:37.010> of<00:26:37.130> final<00:26:37.550> five 00:26:38.320 --> 00:26:38.330 align:start position:0% something I kind of final five 00:26:38.330 --> 00:26:40.360 align:start position:0% something I kind of final five fascinating<00:26:38.540> well<00:26:39.020> I<00:26:39.050> mean<00:26:39.230> the<00:26:39.440> design<00:26:40.220> by 00:26:40.360 --> 00:26:40.370 align:start position:0% fascinating well I mean the design by 00:26:40.370 --> 00:26:42.700 align:start position:0% fascinating well I mean the design by composition<00:26:41.000> I<00:26:41.300> think<00:26:41.780> everyone<00:26:42.230> working<00:26:42.440> on 00:26:42.700 --> 00:26:42.710 align:start position:0% composition I think everyone working on 00:26:42.710 --> 00:26:43.990 align:start position:0% composition I think everyone working on their<00:26:42.860> own<00:26:42.950> piece<00:26:43.220> that's<00:26:43.490> basically<00:26:43.790> what 00:26:43.990 --> 00:26:44.000 align:start position:0% their own piece that's basically what 00:26:44.000 --> 00:26:46.240 align:start position:0% their own piece that's basically what the<00:26:44.120> Linux<00:26:44.450> model<00:26:44.780> is<00:26:44.900> right<00:26:45.140> mm-hmm<00:26:45.590> and<00:26:45.800> I 00:26:46.240 --> 00:26:46.250 align:start position:0% the Linux model is right mm-hmm and I 00:26:46.250 --> 00:26:48.460 align:start position:0% the Linux model is right mm-hmm and I think<00:26:46.280> it's<00:26:46.550> a<00:26:46.580> good<00:26:46.670> model<00:26:46.850> all<00:26:47.780> right<00:26:47.990> well 00:26:48.460 --> 00:26:48.470 align:start position:0% think it's a good model all right well 00:26:48.470 --> 00:26:49.660 align:start position:0% think it's a good model all right well thank<00:26:48.770> you<00:26:48.830> very<00:26:48.920> much<00:26:49.100> for<00:26:49.130> sharing<00:26:49.430> and 00:26:49.660 --> 00:26:49.670 align:start position:0% thank you very much for sharing and 00:26:49.670 --> 00:26:51.100 align:start position:0% thank you very much for sharing and we're<00:26:49.790> looking<00:26:50.000> forward<00:26:50.180> to<00:26:50.270> talk<00:26:50.510> thank<00:26:51.020> you 00:26:51.100 --> 00:26:51.110 align:start position:0% we're looking forward to talk thank you 00:26:51.110 --> 00:26:53.320 align:start position:0% we're looking forward to talk thank you very<00:26:51.140> much