Great video! But video mentions that for choosing a clustering key or column, it should have high cardinality, but that's incorrect, ideally, the column should have, - large enough number of distinct values to enable effective pruning on the table. - small enough number of distinct values to allow Snowflake to effectively group rows in the same micro-partitions for. eg you cannot have UUID field for clustering or a Gender field for clustering for a table.
Thanks you for share us yours knowledge, Could you tell me how i can update de range of date on partition table?, my range date are between 2021-01-01 and 2021-08-30 but now i need the range date between 2021-09-01 and 2022-02-28. Thank you
What are the limitations of partitions? That is, I can see PARTITION is used only when I apply a FILTER. Cant we make use of PARTITION PRUNING by JUST using JOINS without a actual FILTER?
An index is way more awesome. It's a manageable layer on top of the data, as opposed to part of the structure of the physical data. Likely BigQuery tries to trade that off for physical-only data with the create-time partitioning schema accommodating lookup strategy so that they keep writes fast. There's nothing to strongly suggest they won't evolve to indexes in the future IMO.
![Who Wrote a Short Story That Seriously Disturbed a Teacher? | Dirty Laundry x Smosh [Full Episode]](http://i.ytimg.com/vi/bvHAy_rKoEI/mqdefault.jpg)
first time ever I that understand a content created by Google. Congratulations for the way of explaining it.
Deserves an oscar, what a performance
Not sure why we're in tech when we should be in Hollywood 😂
You all are so funny and informative! You deserve an Oscar !
Wow, thank you!
Love it! Thanks for making these videos and please create more of these!
Excellent video, may be one of the clearest explanation about partitioning and clustering
Simple and Clear explanation!
Impressive.. Thanks for sharing.
Thanks for this video! I would know how to create family columns tables if I have to manage a table of more than 10K of columns? thank you
Great video! But video mentions that for choosing a clustering key or column, it should have high cardinality, but that's incorrect, ideally, the column should have,
- large enough number of distinct values to enable effective pruning on the table.
- small enough number of distinct values to allow Snowflake to effectively group rows in the same micro-partitions
for. eg you cannot have UUID field for clustering or a Gender field for clustering for a table.
So just somewhere in between? Not too many and not too few?
also, the bitly links provided in the description are not working for me. Can you check it once?
Thank for your video!
Very useful tutorial
Bro how I can download this big query
Thanks you for share us yours knowledge, Could you tell me how i can update de range of date on partition table?, my range date are between 2021-01-01 and 2021-08-30 but now i need the range date between 2021-09-01 and 2022-02-28. Thank you
Awesome guys..
Can clustering only be applied on 'Text' columns?
More (Firebase style) videos like these please :D
thank!!!
You're welcome!
What are the limitations of partitions? That is, I can see PARTITION is used only when I apply a FILTER. Cant we make use of PARTITION PRUNING by JUST using JOINS without a actual FILTER?
Any changes in loading data?
is clustering same as adding index in regular table??
Hi ,can you please create a video on how to extract data to data warehouse by connecting to big query through Ssis
❤️ it!!
what is the difference between this and an index?
An index is way more awesome. It's a manageable layer on top of the data, as opposed to part of the structure of the physical data. Likely BigQuery tries to trade that off for physical-only data with the create-time partitioning schema accommodating lookup strategy so that they keep writes fast. There's nothing to strongly suggest they won't evolve to indexes in the future IMO.
The Watch more Take5 episodes here links in the video descrpition going to some spam site.