<transcript><audio_121>point to the new A5 which is a lot of updates so One update to the record will cause every secondary index to be updated right so you can see how this starts to become a huge problem right</transcript><transcript><audio_122>it I already showed you yeah good good good but you paying attention that's great see in computer science indirection is a very powerful technique you know 50% of problems can be solved with indirection right uh so instead of secondary indices</transcript><transcript><audio_123>pointing to the record IDs what you would do is you would say because the primary key is kind of like a record ID the secondary index will say I'm just going to point to the primary key which does mean that when I'm accessing a record through the secondary key I have to go to the primary key and then get</transcript><transcript><audio_124>the record ID one extra but if it's if it's hot then probably the primary key index is already in the buffer pool so it's not too bad but what that gives me is that now if I change a record all I do is make the changes in the primary index the secondary index</transcript><transcript><audio_125>stuff doesn't have to change so a single update to a single column think about in Uber's case if they changed the rate for uh uh taxi service and that's changing all the time and that's one field that was changed in a record now all the indices have to change that just causes</transcript> point to the new A5 which is a lot of updates so One update to the record will cause every secondary index to be updated right so you can see how this starts to become a huge problem right it I already showed you yeah good good good but you paying attention that's great see in computer science indirection is a very powerful technique you know 50% of problems can be solved with indirection right uh so instead of secondary indices pointing to the record IDs what you would do is you would say because the primary key is kind of like a record ID the secondary index will say I'm just going to point to the primary key which does mean that when I'm accessing a record through the secondary key I have to go to the primary key and then get the record ID one extra but if it's if it's hot then probably the primary key index is already in the buffer pool so it's not too bad but what that gives me is that now if I change a record all I do is make the changes in the primary index the secondary index stuff doesn't have to change so a single update to a single column think about in Uber's case if they changed the rate for uh uh taxi service and that's changing all the time and that's one field that was changed in a record now all the indices have to change that just causes
{"source": "grass-yt-cc-by.-mY8ALcJVTk|shard_1_1|create_multimodal_data.extract_yt_and_generate_transcripts.62|shard_1|create_multimodal_data.generate_captions.62|shard_1|create_multimodal_data.generate_captions.62", "params": {"id": "-mY8ALcJVTk", "channel_id": "UCHnBsf2rH-K7pn09rb3qvkA", "duration": 5000, "view_count": 4483, "age_limit": 0, "like_count": 50, "channel_follower_count": 71100, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@CMUDatabaseGroup", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_1/-mY8ALcJVTk.tar.gz"}}