HashMap vs. TreeMap vs. HashTable vs. LinkedHashMap
Learn all about important data structures like HashMap, HashTable, and TreeMap.
Join the DZone community and get the full member experience.
Join For FreeMap is an important data structure. In this article, let's play with dogs and see how maps can be helpful in development.
Map Overview
There are four . commonly used implementations of Map in Java SE: HashMap, TreeMap, Hashtable, and LinkedHashMap. If we use one sentence to describe each implementation, it would be the following:
-
HashMap
is implemented as a hash table, and there is no ordering on keys or values. -
TreeMap
is implemented based on red-black tree structure, and it is ordered by the key. -
LinkedHashMap
preserves the insertion order -
Hashtable
is synchronized in contrast toHashMap
.
This gives us the reason that HashMap
should be used if it is thread-safe since Hashtable
has overhead for synchronization.
HashMap
If the key of the HashMap
is self-defined objects, then equals()
and hashCode()
contract need to be followed.
class Dog {
String color;
Dog(String c) {
color = c;
}
public String toString(){
return color + " dog";
}
}
public class TestHashMap {
public static void main(String[] args) {
HashMap hashMap = new HashMap();
Dog d1 = new Dog("red");
Dog d2 = new Dog("black");
Dog d3 = new Dog("white");
Dog d4 = new Dog("white");
hashMap.put(d1, 10);
hashMap.put(d2, 15);
hashMap.put(d3, 5);
hashMap.put(d4, 20);
//print size
System.out.println(hashMap.size());
//loop HashMap
for (Entry entry : hashMap.entrySet()) {
System.out.println(entry.getKey().toString() + " - " + entry.getValue());
}
}
}
Output:
white dog – 5
black dog – 15
red dog – 10
white dog – 20
Note here: We add "white dogs" twice by mistake, but the HashMap
takes it. This does not make sense, because now we are confused how many white dogs are really there. The Dog class should be defined as follows:
class Dog {
String color;
Dog(String c) {
color = c;
}
public boolean equals(Object o) {
return ((Dog) o).color == this.color;
}
public int hashCode() {
return color.length();
}
public String toString(){
return color + " dog";
}
}
Now the output is:
red dog – 10
white dog – 20
black dog – 15
The reason is that HashMap
doesn't allow two identical elements. By default, the hashCode()
and equals()
methods implemented in Object class are used. The default hashCode()
method gives distinct integers for distinct objects, and the equals()
method only returns true when two references refer to the same object.
Check out the hashCode() and equals() contract if this is not obvious to you.
TreeMap
A TreeMap
is sorted by keys. Let's first take a look at the following example to understand the "sorted by keys" idea.
class Dog {
String color;
Dog(String c) {
color = c;
}
public boolean equals(Object o) {
return ((Dog) o).color == this.color;
}
public int hashCode() {
return color.length();
}
public String toString(){
return color + " dog";
}
}
public class TestTreeMap {
public static void main(String[] args) {
Dog d1 = new Dog("red");
Dog d2 = new Dog("black");
Dog d3 = new Dog("white");
Dog d4 = new Dog("white");
TreeMap treeMap = new TreeMap();
treeMap.put(d1, 10);
treeMap.put(d2, 15);
treeMap.put(d3, 5);
treeMap.put(d4, 20);
for (Entry entry : treeMap.entrySet()) {
System.out.println(entry.getKey() + " - " + entry.getValue());
}
}
}
Output:
Exception in thread “main” java.lang.ClassCastException: collection.Dog cannot be cast to java.lang.Comparable
at java.util.TreeMap.put(Unknown Source)
at collection.TestHashMap.main(TestHashMap.java:35)
Since TreeMaps
are sorted by keys, the object for key has to be able to compare with each other, that's why it has to implement Comparable interface. For example, you use String as key, because String implements Comparable interface. Let's change the Dog, and make it comparable.
class Dog implements Comparable{
String color;
int size;
Dog(String c, int s) {
color = c;
size = s;
}
public String toString(){
return color + " dog";
}
@Override
public int compareTo(Dog o) {
return o.size - this.size;
}
}
public class TestTreeMap {
public static void main(String[] args) {
Dog d1 = new Dog("red", 30);
Dog d2 = new Dog("black", 20);
Dog d3 = new Dog("white", 10);
Dog d4 = new Dog("white", 10);
TreeMap treeMap = new TreeMap();
treeMap.put(d1, 10);
treeMap.put(d2, 15);
treeMap.put(d3, 5);
treeMap.put(d4, 20);
for (Entry entry : treeMap.entrySet()) {
System.out.println(entry.getKey() + " - " + entry.getValue());
}
}
}
Output:
red dog – 10
black dog – 15
white dog – 20
It is sorted by key, i.e., dog size in this case. If "Dog d4 = new Dog("white", 10);" is replaced with "Dog d4 = new Dog("white", 40);", the output would be:
white dog – 20
red dog – 10
black dog – 15
white dog – 5
The reason is that TreeMap
now uses the compareTo()
method to compare keys. Different sizes make different dogs!
Hashtable
From Java Doc: "The HashMap
class is roughly equivalent to Hashtable
, except that it is unsynchronized and permits nulls.
LinkedHashMap
LinkedHashMap
is a subclass of HashMap
. That means it inherits the features of HashMap
. In addition, the linked list preserves the insertion-order. Let's replace the HashMap
with LinkedHashMap
using the same code used for HashMap
.
class Dog {
String color;
Dog(String c) {
color = c;
}
public boolean equals(Object o) {
return ((Dog) o).color == this.color;
}
public int hashCode() {
return color.length();
}
public String toString(){
return color + " dog";
}
}
public class TestHashMap {
public static void main(String[] args) {
Dog d1 = new Dog("red");
Dog d2 = new Dog("black");
Dog d3 = new Dog("white");
Dog d4 = new Dog("white");
LinkedHashMap linkedHashMap = new LinkedHashMap();
linkedHashMap.put(d1, 10);
linkedHashMap.put(d2, 15);
linkedHashMap.put(d3, 5);
linkedHashMap.put(d4, 20);
for (Entry entry : linkedHashMap.entrySet()) {
System.out.println(entry.getKey() + " - " + entry.getValue());
}
}
}
Output:
red dog – 10
black dog – 15
white dog – 20
The difference is that if we use HashMap
the output could be the following: the insertion order is not preserved.
red dog – 10
white dog – 20
black dog – 15
If you enjoyed this article and want to learn more about Java Collections, check out this collection of tutorials and articles on all things Java Collections.
Published at DZone with permission of Ryan Wang. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments