MHB How to Insert Keys in a Hashtable Using Different Collision Resolution Methods?

  • Thread starter Thread starter evinda
  • Start date Start date
AI Thread Summary
The discussion revolves around inserting three keys (22, 15, 8) into a hashtable with 7 positions using two different collision resolution methods: coalesced chaining and open addressing. For coalesced chaining, participants confirm that the insertion process is correct. In the case of open addressing, the primary hash function places the first key (22) in slot 1, leading to a debate about whether the subsequent keys are placed correctly. One participant suggests that 22 should occupy slot 1, while another confirms their understanding and expresses gratitude for the clarification. The conversation highlights the importance of correctly applying hash functions and collision resolution strategies in hashtable implementations.
evinda
Gold Member
MHB
Messages
3,741
Reaction score
0
Hello! (Smile)

There are given three elements with keys $22, 15, 8$. Insert them in the given order in a hashtable of $7$ positions given that as method of treatement of the collisions we use:

  • hashing that follows the method coalesced chaining with the hash fuction $h(k)=k \mod m$
  • ordered hashing with open addressing strategies with the primary hash function $h_1(x)=x \mod m$ and the secondary hash function $h_2(x)=(x^2+1) \mod{7}$

That's what I have tried:

For the first case:

View attachment 3894

For the second case:

View attachment 3895Could you tell me if it is right? (Thinking)
 

Attachments

  • hash1.png
    hash1.png
    1.2 KB · Views: 112
  • hash2.png
    hash2.png
    1.1 KB · Views: 111
Technology news on Phys.org
Hey! (Wasntme)

I believe the first case is right. (Nod)

In the second case, the first value of 22 would still be inserted in slot 1 (using the primary hash function), so I think 22 should be there instead of 8. (Shake)
 
Did you figure it out? (Wondering)
 
I like Serena said:
Did you figure it out? (Wondering)

Yes, I did.. Thanks for your answer! (Smile)
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
Back
Top