>> Just so I understand, the file contents are *not* stored in the column value
>> ?
>
> No, on that particular CF the columns are SuperColumns with 5 sub columns
> (size, is_dir, hash, name, revision). Each super column is small, I didn't
> mention super columns before because they don't seem
On Jan 10, 2013, at 8:01 PM, aaron morton wrote:
>> So, one column represents a file in that directory and it has no value.
> Just so I understand, the file contents are *not* stored in the column value ?
No, on that particular CF the columns are SuperColumns with 5 sub columns
(size, is_dir,
> So, one column represents a file in that directory and it has no value.
Just so I understand, the file contents are *not* stored in the column value ?
> Basically the heap fills up and if several queries happens simultaneously,
> the heap is exhausted and the node stops.
Are you seeing the GCI
Hello.
I have a schema to represent a filesystem for my users. In this schema one of
the CF stores a directory listing this way:
CF DirList
Dir1:
File1:NOVAL File2:NOVAL ...
So, one column represents a file in that directory and it has no value. The
file metadata is stored els
