mirror of
https://github.com/oxnr/awesome-bigdata.git
synced 2026-03-09 15:25:35 -05:00
Some column stores are not like other column stores #2
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/awesome-bigdata#2
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dvryaboy on GitHub (Aug 4, 2014).
This is a great collection of pointers!
The current list of column stores conflates two things: "key-map" data stores like Cassandra, BigTable, and HBase and the rest -- the majority of the list -- and actual column stores like C-Store, MonetDB, and the Parquet file format.
These two designs are aimed at very different workloads and are fundamentally different structurally; they should be broken out into different categories.
Unfortunately both groups have traditionally called their technology "columnar databases", while meaning completely different things, so there isn't a great term to use for one vs the other.
I've seen "wide-column key-value datastores" used to describe BigTable and friends; this is definitely more technically correct, though I am sure it's confusing to the reader who now has to find out what the difference is between that and a column store. But perhaps that's a good thing.
Prof. Dan Abadi has a few other naming suggestions, as well as a detailed explanation of why these things are fundamentally different, here: http://dbmsmusings.blogspot.com/2010/03/distinguishing-two-major-types-of_29.html
@oxnr commented on GitHub (Aug 5, 2014):
Sounds great. Feel free to create a pull request with the separation. Thats exactly why i put this list on github to put more brains into this topic ;)