How to store more than one string in a Map?

Question

Is it possible to set more than two pair value?

For example:

Map<String,String,String,String>

number,name,address,phone - All come together for display the values. Each value associated with others.

Answer 1

You're in object denial. You should use an object that holds the number, name, address, phone (maybe you could call it ContactInformation) and put that into the map.

Answer 2

No. a Map has only one key. If you want your value to contain more information, wrap the strings in a new class:

public class PersonalInfo {
   private final String name;
   private final String address;
   private final String phone;

   // constructor and getters
}

map.put(number, new PersonalInfo(name, address, phone));

Answer 3

The 'correct' solution is to use an object that holds the values in named fields, but in the spirit of answering the question asked, a simple (if unclean) solution would be to use:

Map<String,List<String>> yourMap = new HashMap<String,List<String>>();

List<String> info = new ArrayList<String>();
info.add(number);
info.add(name);
info.add(address);
info.add(phone);

yourMap.put(key, info);

Note google-collections has a series of classes that implement this structure right out of the box called ListMultimap and it's implementation ArrayListMultimap

Answer 4

Nope, A Map can have only one key and mapped to one value.

This is the Javadoc for Map:

An object that maps keys to values. A map cannot contain duplicate keys; each key can map to at most one value.

What you can do is to create an entity called User with some details e.g

public class User implements Serializable {

    private String firstName;
    private String lastNumber;
    private String address;
    private String phoneNumber;

    //Generated getters and setters here....
}

then add it to a map like so....

Map<String, User> userMap = new HashMap<String, User>();
User user = new User();
//populate user
userMap.put(uniqueUserID, user);

Answer 5

Just in case you want to maintain a map of: "number, name" --> "address, phone" and you do not wish to create a class to encapsulate these attributes. You may have a look in the handy MultiKey in Apache Commons Collections:

http://commons.apache.org/collections/apidocs/org/apache/commons/collections/keyvalue/MultiKey.html

Answer 6

Hmmm, You could create a class for Person with number, name, address and phoneno, then you create a Map

Answer 7

Your question suggests you want key on each of the 4 fields and all others become values. While in general, it is one key and multiple values packed on a object.

Please confirm what is required.

Answer 8

As others have said, a map is a mapping between a key and a value. That is why the javadoc for map says (since generics in v5):

Interface Map<K,V>

... where K is the type of the key, and V is the type of the value. Just <K, V>. You must define exactly two types.

It is worth mentioning that in mathematics 'map' is a term meaning to convert a value of one type into a value of another type. The Java Map is a reflection of this, (as is the method map available on collections in Scala).

Answer 9

No its not. In Java maps are interfaced as Map<K,V> - so only two generic arguments are allowed. The question you ask can now mean two things:

1. A map where a single key of type K relates to various values of type V. The values themselves may not be mutually related. e.g the key fruits with values apple,banana,guava etc. This is your use case, but only in syntax.

• One can use Map<K,List<V>> for this.
• Or better yet Guava's MultiMap, which was purpose built to be capable of storing multiple values for a given key. Note that though similar, it isn't identical to a Map. No List needed.

2. Since we are allowing multiple values for the same key, the values might as well as have different types. When do multiply typed data for the same key make sense? When they have some relationship to each other, e.g. a key customerId may have values name,number,address etc. potentially of different types. In other, words the data forms the properties of some Object. This is the perfect opportunity to use OOP to create a data structure. This is your use case, in spirit.

• One can then use Map<K,MyDataStructure> to store these multiple values. Note that the values stay mutable. One needs manual implementation of equals,hashCode though.

 class MyDataStructure{
     Type1 data1;
     Type2 data2;
      ...
 }

• As of Java 16, a better and recommended way to achieve something similar is by using record. One then uses Map<K,MyRecord>. Note that records are immutable but automatically supply Object related functionality.

record MyRecord(Type1 field1,Type2 field2//,Type3 ...)

In the above discussion, it becomes apparent that we are looking for a data structure each of whose rows or records is identified by a primary key and can contain fields of similar or differing type. Map<K,V> isn't designed for this. A database is.