Editing Open addressing

{{Short description|Hash collision resolution technique}}
[[Image:HASHTB12.svg|thumb|362px|right|Hash collision resolved by linear probing (interval=1).]]
'''Open addressing''', or '''closed hashing''', is a method of [[Hash table#Collision resolution|collision resolution in hash tables]].  With this method a hash collision is resolved by '''probing''', or searching through alternative locations in the array (the ''probe sequence'') until either the target record is found, or an unused array slot is found, which indicates that there is no such key in the table.<ref name="tenenbaum90">{{Citation | title=Data Structures Using C | first1=Aaron M. | last1=Tenenbaum | first2=Yedidyah | last2=Langsam | first3=Moshe J. | last3=Augenstein | publisher=Prentice Hall | year=1990 | isbn=0-13-199746-7 | pages=456–461, pp. 472}}</ref> Well-known probe sequences include:

; [[Linear probing]] : in which the interval between probes is fixed — often set to 1.
; [[Quadratic probing]] : in which the interval between probes increases linearly (hence, the indices are described by a quadratic function).
; [[Double hashing]] : in which the interval between probes is fixed for each record but is computed by another hash function.

The main trade offs between these methods are that linear probing has the best [[Locality of reference|cache performance]] but is most sensitive to [[Primary clustering|clustering]], while double hashing has poor cache performance but exhibits virtually no clustering; quadratic probing falls in between in both areas. Double hashing can also require more computation than other forms of probing.

Some open addressing methods, such as [[Hopscotch hashing]], [[hash table#Robin Hood hashing | Robin Hood hashing]], [[last-come-first-served hashing]] and [[cuckoo hashing]] move existing keys around in the array to make room for the new key. This gives better maximum search times than the methods based on probing.<ref>
Poblete; Viola; Munro.
"The Analysis of a Hashing Scheme by the Diagonal Poisson Transform".
p. 95 of
Jan van Leeuwen (Ed.)
[https://books.google.com/books?id=2aCoW8m40AwC "Algorithms - ESA '94"].
1994.
</ref><ref>
Steve Heller.
[https://books.google.com/books?id=gaajBQAAQBAJ "Efficient C/C++ Programming: Smaller, Faster, Better"]
2014.
p. 33.
</ref><ref>
Patricio V. Poblete, Alfredo Viola.
[https://arxiv.org/abs/1605.04031 "Robin Hood Hashing really has constant average search cost and variance in full tables"].
2016.
</ref><ref>
Paul E. Black, [https://xlinux.nist.gov/dads/HTML/LastComeFirstServedHashing.html "Last-Come First-Served Hashing"], in Dictionary of Algorithms and Data Structures [online], Vreda Pieterse and Paul E. Black, eds. 17 September 2015.
</ref><ref>
Paul E. Black, [https://www.nist.gov/dads/HTML/robinHoodHashing.html "Robin Hood hashing"], in Dictionary of Algorithms and Data Structures [online], Vreda Pieterse and Paul E. Black, eds. 17 September 2015.
</ref>

A critical influence on performance of an open addressing hash table is the ''load factor''; that is, the proportion of the slots in the array that are used. As the load factor increases towards 100%, the number of probes that may be required to find or insert a given key rises dramatically. Once the table becomes full, probing algorithms may even fail to terminate. Even with good hash functions, load factors are normally limited to 80%. A poor hash function can exhibit poor performance even at very low load factors by generating significant clustering, especially with the simplest linear addressing method. Generally typical load factors with most open addressing methods are 50%, while [[Hash_table#Separate_chaining|separate chaining]] typically can use up to 100%.

==Example pseudocode==

The following [[pseudocode]] is an implementation of an open addressing hash table with linear probing and single-slot stepping, a common approach that is effective if the hash function is good. Each of the '''lookup''', '''set''' and '''remove''' functions use a common internal function '''find_slot''' to locate the array slot that either does or should contain a given key.

 '''record''' pair { key, value, occupied flag (initially unset) }
 '''var''' pair slot[0], slot[1], ..., slot[num_slots - 1]

 '''function''' find_slot(key)
     i := hash(key) modulo num_slots
     ''// search until we either find the key, or find an empty slot.''
     '''while''' (slot[i] is occupied) and (slot[i].key ≠ key)
         i := (i + 1) modulo num_slots
     '''return''' i

 '''function''' lookup(key)
     i := find_slot(key)
     '''if''' slot[i] is occupied   ''// key is in table''
         '''return''' slot[i].value
     '''else'''                     ''// key is not in table''
         '''return''' not found

 '''function''' set(key, value)
     i := find_slot(key)
     '''if''' slot[i] is occupied   ''// we found our key''
         slot[i].value := value
         '''return'''
     '''if''' the table is almost full
         rebuild the table larger ''(note 1)''
         i := find_slot(key)
     mark slot[i] as occupied
     slot[i].key := key
     slot[i].value := value

; note 1 : Rebuilding the table requires allocating a larger array and recursively using the '''set''' operation to insert all the elements of the old array into the new larger array. It is common to increase the array size [[exponential growth|exponentially]], for example by doubling the old array size.

 '''function''' remove(key)
     i := find_slot(key)
     '''if''' slot[i] is unoccupied
         '''return'''   ''// key is not in the table''
     mark slot[i] as unoccupied
     j := i
     '''loop''' ''(note 2)''
         j := (j + 1) modulo num_slots
         '''if''' slot[j] is unoccupied
             '''exit loop'''
         k := hash(slot[j].key) modulo num_slots
         ''// determine if k lies cyclically in (i,j]''
         ''// i ≤ j: |    i..k..j    |''
         ''// i > j: |.k..j     i....| or |....j     i..k.|''
         '''if''' i ≤ j
             '''if''' (i < k) and (k ≤ j)
                 '''continue loop'''
         '''else'''
             '''if''' (k ≤ j) or (i < k)
                 '''continue loop'''
         mark slot[i] as occupied
         slot[i].key := slot[j].key
         slot[i].value := slot[j].value
         mark slot[j] as unoccupied
         i := j

; note 2 : For all records in a cluster, there must be no vacant slots between their natural hash position and their current position (else lookups will terminate before finding the record). At this point in the pseudocode, {{var|i}} is a vacant slot that might be invalidating this property for subsequent records in the cluster. {{var|j}} is such a subsequent record. {{var|k}} is the raw hash where the record at {{var|j}} would naturally land in the hash table if there were no collisions. This test is asking if the record at {{var|j}} is invalidly positioned with respect to the required properties of a cluster now that {{var|i}} is vacant.

Another technique for removal is simply to mark the slot as deleted. However this eventually requires rebuilding the table simply to remove deleted records. The methods above provide ''O''(1) updating and removal of existing records, with occasional rebuilding if the high-water mark of the table size grows.

The ''O''(1) remove method above is only possible in linearly probed hash tables with single-slot stepping.  In the case where many records are to be deleted in one operation, marking the slots for deletion and later rebuilding may be more efficient.

==See also==
* [[Lazy deletion]] – a method of deleting from a hash table using open addressing.

==References==
<references />

[[Category:Hashing]]