Jump to content

Standard column family

From Wikipedia, the free encyclopedia

This is the current revision of this page, as edited by Bender the Bot (talk | contribs) at 15:02, 13 May 2023 (top: HTTP to HTTPS for Wayback Machine, replaced: http://web.archive.org/ → https://web.archive.org/). The present address (URL) is a permanent link to this version.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
A standard column family consists of a (unique) row key and a number of columns.

The standard column family is a NoSQL object that contains columns of related data. It is a tuple (pair) that consists of a key–value pair, where the key is mapped to a value that is a set of columns. In analogy with relational databases, a standard column family is as a "table", each key–value pair being a "row".[1] Each column is a tuple (triplet) consisting of a column name, a value, and a timestamp.[2] In a relational database table, this data would be grouped together within a table with other non-related data.[3]

Standard column families are column containers sorted by their names can be referenced and sorted by their row key.[4]

Benefits

[edit]

Accessing the data in a distributed data store would be expensive (time-consuming), if it would be saved in form of a table. It would also be inefficient to read all column families that would make up a row in a relational table and put it together to form a row, as the data for it is distributed on a large number of nodes. Therefore, the user accesses only the related information required.

As an example, a relational table could consist of the columns UID, first name, surname, birthdate, gender, etc. In a distributed data store, the same table would be implemented by creating columns families for "UID, first name, surname", "birthdate, gender", etc. If one needs only the males that were born between 1950 and 1960, for a query in the relational database, all the table has to be read. In a distributed data store, it suffices to access only the second standard column family, as the rest of information is irrelevant.

Sorting and querying

[edit]

There is no way to sort columns, nor to query an arbitrary query in distributed data stores. Columns are sorted when they are added to the column family. The way of sorting is defined by an attribute. For instance, this is done by the CompareWith attribute in Apache Cassandra that can have the following values:

  • AsciiType
  • BytesType
  • LexicalUUIDType
  • LongType
  • TimeUUIDType
  • UTF8Type

It is also possible to add some user-defined sorting attributes. Using this way of sorting makes the process extremely quick.[5]

Standard column families vs. rows

[edit]

Standard column families have a schema-less nature so that each of their "row"s can contain a different number of columns, and even different column names could be in each row.[6] So, they are a very different concept than the rows in relational database management system (RDBMS)s. This is one of the reasons why the concept is not trivial for an experienced RDBMS expert.

Examples

[edit]

In JSON-like notation, a column family definition would look as follows:[6]

UserProfile = {
    Cassandra = {emailAddress:"cassandra@apache.org", age:20},
    TerryCho = {emailAddress:"terry.cho@apache.org", gender:"male"},
    Cath = {emailAddress:"cath@apache.org", age:20, gender:"female", address:"Seoul"},
}

where "Cassandra", "TerryCho", "Cath" correspond to row keys; and "emailAddress", "age", "gender", "address" correspond to the column names.

See also

[edit]

References

[edit]
  1. ^ "Column Families 101". Max's Output. Archived from the original on 2010-11-02. Retrieved 2011-03-18.
  2. ^ Max's Output (9 July 2010). "A Quick Introduction to the Cassandra Data Model: 1) Cassandra is based on a key–value model". Max Grinev. Retrieved 2011-03-18. A standard column family is a set of key–value pairs. I know the terminology is confusing but so far it is just basic key–value model. Drawing an analogy with relational databases, you can think about standard column family as table and a key–value pair as a record in a table.
  3. ^ "Column Families 101". Toad for Cloud. Retrieved 2011-03-18.
  4. ^ "Cassandra's data model cheat sheet: standard column family". Chaker Nakhli's Blog - Yet another technical blog. Retrieved 2011-03-29. A container for columns sorted by their names. Column Families are referenced and sorted by row keys.
  5. ^ "Installing and using Apache Cassandra With Java Part 3 (Data model 2)". Sodeso - Software Development Solutions. Retrieved 2011-03-30. Sorting can be specified on the ColumnFamily CompareWith attribute, these are the options you can choose from (it is possible to create custom sorting behavior but we will cover that later): BytesType, UTF8Type, LexicalUUIDType, TimeUUIDType, AsciiType, LongType
  6. ^ a b Terry (2010-03-22). "Apache Cassandra Quick tour". Terry.Cho's blog. Retrieved 2011-03-25. One of interest thing is each row can have different scheme. Cassandra row has "emailAddress" ,"age" column. TerryCho row has "emailAddress","gender" column. This characteristic is called as "Schemeless" (Data structure of each row in standard column family can be different).
[edit]