thank you for explaining the topic in such a simple and effective manner.
@ghumofiro5661 Жыл бұрын
Excellent explaination in a very simpler way,thank you
@singhongchow89682 жыл бұрын
Thanks from Malaysia. It is really clear.
@paulo__vieira2 ай бұрын
Good explanation, very easy to follow. Thanks!
@MarcioBrenerCosta Жыл бұрын
Great Job Broo! The way you speak and explain is very clear!
@tanuvishu2 жыл бұрын
Your videos are amazing
@haphamdev2 жыл бұрын
Thank you for a very good tutorial.
@陈之-l3d4 жыл бұрын
good explanation. better than documentations I read before
@bhatanand2 жыл бұрын
Super video. Thanks
@TheHellishFrog2 жыл бұрын
Excellent explanation! Thank You!
@koderkev422 жыл бұрын
Well explained. Thank you!
@golgottera82054 ай бұрын
Nice visualization, thanks!
@lolopolos4 жыл бұрын
Great explanation, Redis provides bitmap data structure.
@consciousmi48424 жыл бұрын
Thanks for sharing. Good material
@Patiencelad2 жыл бұрын
Great explanation! Thanks so much!
@MrVitalirapalis Жыл бұрын
amazing ;)
@levelupskills77104 жыл бұрын
waow .. first time I opened this video.. It really made me fall in love with your teaching skills, way of communication and your kind body language ❤❤🔥🔥🔥🔥🔥.. Your are legend sir 👍👍👍
@Bruh-jw2ze4 жыл бұрын
Congrats bro , I opened it for the 100th time today Will continue opening it everyday till I reach my grave
@nandnibachani17653 жыл бұрын
Best explaination ever
@jennwng Жыл бұрын
Great video! Simple example to explain complex concept - love it! Thanks. : )
@wizardgaming1632 жыл бұрын
U explains things very clearly,love your content
@lucas.n Жыл бұрын
question: if you have to go row by row in the bitmap index to find the matches, how is it different than a fullscan?
@devenderyadav62094 жыл бұрын
Great tutorial! Thank for covering variety of topics. It would ge great if you start putting notes, slides, references to a Github repository. In this way, other developers can also contribute.
@vaibhavmewada45082 ай бұрын
Good explanation
@LovelyCreationsDIY4 жыл бұрын
Hey, it will be great if you also share the reference materials as well. thanks
@priyankabuqrdwaj49644 жыл бұрын
thank you so much sir your explanation is awesome
@dulanjanaliyanagama38233 жыл бұрын
Thank you, sir! You saved my day! Nice explanation 🙏
@cristianopassos52573 жыл бұрын
Hi, nice vídeo! I would like to have it short, but without losing any content. Thanks for sharing 👍
@bharath_v4 жыл бұрын
Good One!
@kottaravindar13 жыл бұрын
Good One
@mdtalibalam9743Ай бұрын
Very insightful video , can you also please tell me the book or document that you referred to understand this
@abdulrafay242011 ай бұрын
Hey, you explained Bitmap indexing concept really well 👍🏻. Do you have one for cluster indexing?
@jag1884 жыл бұрын
Great explanation, thanks for sharing knowledge, My only suggestion is to reduce repetitive statements.
@Ayush-lj6pq3 жыл бұрын
crystal clear
@SURESHRAJA-c5x Жыл бұрын
As for as oracle , the definition for cardinality is some what not same as you explained , but your explanation of bitmap is good
@masthanayapenumadi38554 жыл бұрын
Thank u very much
@大盗江南4 жыл бұрын
Thanks for this video!!! Man!!! Could u do a video about an example using bitmap and b-tree together :D Have a nice day!
@59sharmanalin3 жыл бұрын
Even if we find all 1st in bitwise array, it's O(N) ?
@YuraZavadenko6 ай бұрын
soo splendid, but what if the capacity (number of rows in the database) grows, so we will have bigger indexes, thus will need to interate through a larger portion of indexes?
@andreaolla82564 жыл бұрын
Thanks You!
@anamigator4 жыл бұрын
May be the table needs a better design here. Why not pull out status and stock in their own tables and use the status_id and stock_id as columns in the main table. Integer comparisons are faster.
@ranojaan1654 жыл бұрын
thanks
@sahilbajaj2190 Жыл бұрын
Question: What if any record from table is deleted ? Just turning that bit to 0 would not work much, as query could be number of users who are not approved, which in turn can include deleted users as well
@pabloe18024 жыл бұрын
What do you think of CrimsonDB?
@dinggorden2694 жыл бұрын
How about to have a session discussing about the design distributed message queue system?
@大盗江南4 жыл бұрын
Do some live with us!!!!!
@YT-yt-yt-33 жыл бұрын
Isn’t this same as columnar format the parquet uses?
@niyomwungerighad89654 жыл бұрын
thank you sir. it is really helpful. could you please suggest me a reference paper or book for this?
@subhrapratimde80163 жыл бұрын
If we create an index like CREATE INDEX index_name ON table_name (column_name). will the database handle it automatically for BITMAP or do I have to do any extra things to use BITMAP indexing for status column?
@hitzhangjie3 жыл бұрын
Hi, bro, I see you hadn't updated for nearly half a year. Are you OK?
@billylee18023 жыл бұрын
Good content, but the volume is very low.
@Extjac4 жыл бұрын
hey! can you do a system design for Expidia?
@wejdanalqhtani80922 жыл бұрын
What is the relationship between bitmap indexing and high dimensional indexing problem???
@Hmm1298-84 жыл бұрын
can you suggest the list of books plz?
@--sql4 жыл бұрын
What you described as "Cardinality" is what I learned as "data sparsity". Cardinality refers to the relationship between rows in different tables, e.g. 1 to many (1:M), 1 to 1 (1:1) or many to many (M:N).
@romangavrilovich84534 жыл бұрын
'cardinality' is the same as 'size' en.wikipedia.org/wiki/Cardinal_number sparsity describes the number of sparse items (e.g. empty rows in DB)
@youchiru14 жыл бұрын
Conventional wisdom hulds that bitmap indexes are most appropriate for columns having low distinct values--such as GENDER, MARITAL_STATUS, and RELATION. This assumption is not completely accurate, however. In reality, a bitmap index is always advisable for systems in which data is not frequently updated by many concurrent systems. In fact, as I'll demonstrate here, a bitmap index on a culumn with 100-percent unique values (a culumn candidate for primary key) is as efficient as a B-tree index. Usage of bitmap indexes is not in fact cardinality dependent but rather application dependent. SRC : www.oracle.com/technical-resources/articles/sharma-indexes.html
@AmanGarg954 жыл бұрын
Thanks for sharing. However this doesn't answer the following. 1) How is the bit map index updated when you add a new ID as well as add a new type called "ON HOLD". Is the index resized when it crosses a particular threshold (say 2^n -1 )? Is it a power of 2? 2) How is the complexity of the query reduced? For e.g select all products where status in ALL except rejected and stock in ALL. In this case, how are we saving on compute because we need to loop through all bitmaps on both columns. If that's the case, there's no exploitation of the fact that the cardinality of this column in reduced. For example. why not compute a bitmap for TRUE, FALSE, TRUE || FALSE, TRUE && FALSE and keep it ready as compared to just TRUE , FALSE now. We can afford to do this as the cardinality is less.
@romangavrilovich84534 жыл бұрын
actually this video is useless =/
@JayChakra4 жыл бұрын
I too had the same questions in mind.
@maxmuranov8764 Жыл бұрын
Omg you could explain everything in 5 minutes instead of repeating 100 times each simple idea. And you didn't explain why it's better than seq scan, great!! (no)
@mayankrathore75583 ай бұрын
how we scale this kind of operation lets say on 1M rows
@a.yashwanth4 жыл бұрын
Why can't we use 3 numbers for each row. 0 for approved, 1 for pending, 3 for rejected.
@TechDummiesNarendraL4 жыл бұрын
It is a bit, not character/string datatype
@jimsmart25224 жыл бұрын
In theory, yes, there are only 3 distinct values in this column, and yes, that means that one only really needs two bits to hold that info. But if we continue down that route, we now have a column that requires just two bits. How can one generalise that into anything useful? How can it be efficiently stored and indexed? What does one do when someone adds some new statuses? It’s just not practical. Using bitmap indexing where appropriate is a useful and good generalisation.
@anildangol4 жыл бұрын
Great Explanation! so you explained it nicely for 6 rows and it has 6 bits but how does it scale for millions of rows. we can't have millions of bits.
@devenderyadav62094 жыл бұрын
Whats' the issues with millions rows. If we you take 1 million rows and 4 cardinality, its just 500KB data.
@adithyapuram25413 жыл бұрын
Hi, thanks for the video, how will the update work, if I have to update the nth element from 1 to 0, how would I seek that element without having to go through all the numbers. Also having ids in order seem to be one of the biggest requirement for this use-case, which is not possible most times.
@raniketram3 жыл бұрын
Anyone knows his twitter handle, please let me know
@rosendo32194 ай бұрын
isn't this ridiculously wrong? you don't build bit map index, you build a btree index bitmap is index access, the way planner decides to access the btree index. dude, wtf, bitmap index access is all about not accessing the same block page
@tenminutetokyo26434 жыл бұрын
Indicies, not indexes. Thought you were all geniuses?