Modeling Multi-Valued Fields

[Cameron Leach]

~resending to hbase-u...@hadoop.apache.org~

Is there a best-practice for modeling multi-valued fields (fields that are
repeated or collections of fields)? Our current data model allows for a User
to store multiple email addresses:

User {
  Integer id; //row key
  List<Email> emails;

  Email {
    String type; //home, work, gmail, hotmail, etc...
    String address;
  }
}

So if I setup a 'User' table with an 'Email' column family, how would one
support multiple email addresses, storing values for the 'type' and
'address' columns? I've seen it suggested to have dynamic column names, but
this doesn't seem practical, unless someone can make it more clear how that
strategy would work.

Thanks!