@GwtCompatible public interface Multimap<K,V>
Map, but in which
 each key may be associated with multiple values. You can visualize the
 contents of a multimap either as a map from keys to nonempty
 collections of values:
 Important: although the first interpretation resembles how most
 multimaps are implemented, the design of the Multimap API is
 based on the second form. So, using the multimap shown above as an
 example, the size() is 3, not 2, and the values() collection is [1, 2, 3], not [[1, 2], [3]]. For
 those times when the first style is more useful, use the multimap's asMap() view (or create a Map<K, Collection<V>> in the first place).
 
The following code:
   ListMultimap<String, String> multimap = ArrayListMultimap.create();
   for (President pres : US_PRESIDENTS_IN_ORDER) {
     multimap.put(pres.firstName(), pres.lastName());
   }
   for (String firstName : multimap.keySet()) {
     List<String> lastNames = multimap.get(firstName);
     out.println(firstName + ": " + lastNames);
   }
 ... produces output such as:    Zachary: [Taylor]
   John: [Adams, Adams, Tyler, Kennedy]  // Remember, Quincy!
   George: [Washington, Bush, Bush]
   Grover: [Cleveland, Cleveland]        // Two, non-consecutive terms, rep'ing NJ!
   ...
 Much of the power of the multimap API comes from the view collections it provides. These always reflect the latest state of the multimap itself. When they support modification, the changes are write-through (they automatically update the backing multimap). These view collections are:
asMap(), mentioned abovekeys(), keySet(), values(), entries(), which
     are similar to the corresponding view collections of Map
 get(key) is an
     active view of the values corresponding to key
 The collections returned by the replaceValues and
 removeAll methods, which contain values that have just
 been removed from the multimap, are naturally not views.
 
Instead of using the Multimap interface directly, prefer the
 subinterfaces ListMultimap and SetMultimap. These take their
 names from the fact that the collections they return from get behave
 like (and, of course, implement) List and Set, respectively.
 
For example, the "presidents" code snippet above used a ListMultimap; if it had used a SetMultimap instead, two presidents
 would have vanished, and last names might or might not appear in
 chronological order.
 
Warning: instances of type Multimap may not implement
 Object.equals(java.lang.Object) in the way you expect (multimaps containing the same
 key-value pairs, even in the same order, may or may not be equal). The
 recommended subinterfaces provide a much stronger guarantee.
 
Multimaps are commonly used in places where a Map<K,
 Collection<V>> would otherwise have appeared. The differences include:
 
put.
 get never returns null, only an empty collection.
 size().
 Collections.min(multimap.values()) finds the smallest value across all
     keys.
 As always, prefer the immutable implementations, ImmutableListMultimap and ImmutableSetMultimap. General-purpose
 mutable implementations are listed above under "All Known Implementing
 Classes". You can also create a custom multimap, backed by any Map and Collection types, using the Multimaps.newMultimap family of methods. Finally, another popular way to
 obtain a multimap is using Multimaps.index. See
 the Multimaps class for these and other static utilities related
 to multimaps.
 
As with Map, the behavior of a Multimap is not specified 
 if key objects already present in the multimap change in a manner that 
 affects equals comparisons.  Use caution if mutable objects are used 
 as keys in a Multimap.
 
All methods that modify the multimap are optional. The view collections
 returned by the multimap may or may not be modifiable. Any modification
 method that is not supported will throw UnsupportedOperationException.
 
See the Guava User Guide article on 
 Multimap.
| Modifier and Type | Method and Description | 
|---|---|
Map<K,Collection<V>> | 
asMap()
Returns a map view that associates each key with the corresponding values
 in the multimap. 
 | 
void | 
clear()
Removes all key-value pairs from the multimap. 
 | 
boolean | 
containsEntry(Object key,
                          Object value)
Returns  
true if the multimap contains the specified key-value pair. | 
boolean | 
containsKey(Object key)
Returns  
true if the multimap contains any values for the specified
 key. | 
boolean | 
containsValue(Object value)
Returns  
true if the multimap contains the specified value for any
 key. | 
Collection<Map.Entry<K,V>> | 
entries()
Returns a collection of all key-value pairs. 
 | 
boolean | 
equals(Object obj)
Compares the specified object with this multimap for equality. 
 | 
Collection<V> | 
get(K key)
Returns a collection view containing the values associated with  
key
 in this multimap, if any. | 
int | 
hashCode()
Returns the hash code for this multimap. 
 | 
boolean | 
isEmpty()
Returns  
true if the multimap contains no key-value pairs. | 
Multiset<K> | 
keys()
Returns a collection, which may contain duplicates, of all keys. 
 | 
Set<K> | 
keySet()
Returns the set of all keys, each appearing once in the returned set. 
 | 
boolean | 
put(K key,
      V value)
Stores a key-value pair in the multimap. 
 | 
boolean | 
putAll(K key,
            Iterable<? extends V> values)
Stores key-value pairs in this multimap with one key and multiple values. 
 | 
boolean | 
putAll(Multimap<? extends K,? extends V> multimap)
Copies all of another multimap's key-value pairs into this multimap. 
 | 
boolean | 
remove(Object key,
            Object value)
Removes a single key-value pair from the multimap. 
 | 
Collection<V> | 
removeAll(Object key)
Removes all values associated with a given key. 
 | 
Collection<V> | 
replaceValues(K key,
                          Iterable<? extends V> values)
Stores a collection of values with the same key, replacing any existing
 values for that key. 
 | 
int | 
size()
Returns the number of key-value pairs in the multimap. 
 | 
Collection<V> | 
values()
Returns a collection of all values in the multimap. 
 | 
int size()
boolean isEmpty()
true if the multimap contains no key-value pairs.boolean containsKey(@Nullable Object key)
true if the multimap contains any values for the specified
 key.key - key to search for in multimapboolean containsValue(@Nullable Object value)
true if the multimap contains the specified value for any
 key.value - value to search for in multimapboolean containsEntry(@Nullable Object key, @Nullable Object value)
true if the multimap contains the specified key-value pair.key - key to search for in multimapvalue - value to search for in multimapboolean put(@Nullable K key, @Nullable V value)
Some multimap implementations allow duplicate key-value pairs, in which
 case put always adds a new key-value pair and increases the
 multimap size by 1. Other implementations prohibit duplicates, and storing
 a key-value pair that's already in the multimap has no effect.
key - key to store in the multimapvalue - value to store in the multimaptrue if the method increased the size of the multimap, or
     false if the multimap already contained the key-value pair and
     doesn't allow duplicatesboolean remove(@Nullable Object key, @Nullable Object value)
key - key of entry to remove from the multimapvalue - value of entry to remove the multimaptrue if the multimap changedboolean putAll(@Nullable K key, Iterable<? extends V> values)
This is equivalent to
   for (V value : values) {
     put(key, value);
   } 
 
 In particular, this is a no-op if values is empty.
key - key to store in the multimapvalues - values to store in the multimaptrue if the multimap changedboolean putAll(Multimap<? extends K,? extends V> multimap)
multimap.entries().multimap - mappings to store in this multimaptrue if the multimap changedCollection<V> replaceValues(@Nullable K key, Iterable<? extends V> values)
If values is empty, this is equivalent to 
 removeAll(key).
key - key to store in the multimapvalues - values to store in the multimapCollection<V> removeAll(@Nullable Object key)
Once this method returns, key will not be mapped to any values,
 so it will not appear in keySet(), asMap(), or any other
 views.
key - key of entries to remove from the multimapvoid clear()
Collection<V> get(@Nullable K key)
key
 in this multimap, if any. Note that even when (containsKey(key) is
 false, get(key) still returns an empty collection, not null.
 Changes to the returned collection will update the underlying multimap, and vice versa.
key - key to search for in multimapSet<K> keySet()
Note that the key set contains a key if and only if this multimap maps that key to at least one value.
Multiset<K> keys()
Collection<V> values()
Collection<Map.Entry<K,V>> entries()
add or addAll operations.Map<K,Collection<V>> asMap()
setValue()
 on its entries, put, or putAll.
 When passed a key that is present in the map, asMap().get(Object) has the same behavior as get(K), returning a
 live collection. When passed a key that is not present, however, asMap().get(Object) returns null instead of an empty collection.
boolean equals(@Nullable Object obj)
asMap(),
 are also equal.
 In general, two multimaps with identical key-value mappings may or may
 not be equal, depending on the implementation. For example, two
 SetMultimap instances with the same key-value mappings are equal,
 but equality of two ListMultimap instances depends on the ordering
 of the values for each key.
 
A non-empty SetMultimap cannot be equal to a non-empty
 ListMultimap, since their asMap() views contain unequal
 collections as values. However, any two empty multimaps are equal, because
 they both have empty asMap() views.
equals in class Objectobj - the reference object with which to compare.true if this object is the same as the obj
          argument; false otherwise.Object.hashCode(), 
HashMapint hashCode()
The hash code of a multimap is defined as the hash code of the map view,
 as returned by asMap().
hashCode in class ObjectObject.equals(java.lang.Object), 
System.identityHashCode(java.lang.Object)Copyright © 2010-2013. All Rights Reserved.