Closed thinxer closed 5 years ago
Like the view
concept in Database.
Or we can just switch to column storage.
On Sun, Jun 2, 2013 at 9:12 PM, Wei Chen notifications@github.com wrote:
Like the view concept in Database.
— Reply to this email directly or view it on GitHubhttps://github.com/THUKEG/saedb/issues/66#issuecomment-18806912 .
In a real world storage, fields in a table (or graph, in our application) can be quite messy. For example, the core fields for Author can be 'names, h-index, publication_count, citation_number' etc, while we can add more fields such as 'bio, affiliation, phd_year, phone' and so on.
However, when doing computation on the authors network, we may only be interested in a subset of the properties, such as the core fields. If we store all the fields altogether, we'll have to load all fields together into the memory, which is not optimal.
I suggest we add a feature as ColumnFamily, in which fields are stored together. Then we'll be able to load only the families we need.