The important distinction here is that you can slice on columns in a
row, but you can't slice on column family (or keyspace) names, because
the data isn't stored contiguously. The row, within the columnfamily,
is the unit of data storage and api focus.
On Sat, Apr 17, 2010 at 12:42 AM, Benjamin B
The multi-level dictionary explanation holds. Regex on keys like that
is something specific language implementations support, not something
inherent in a dictionary data structure. The table model is
particularly fraught because it drags in a lot of relational
assumptions, none of which hold. An
On Mon, Apr 12, 2010 at 9:48 AM, Colin Yates wrote:
> I was hoping I could do a get_range_slices specifying 'project*' for the
> columnFamily and a keyRange start: 20100107, end:20100109 but I
> get an error 'InvalidRequestException(why:unconfigured columnfamily
> project*)'.
I think you've been
Hi,
Assume I have:
SCF: Projects : {
CF:"project1": {
20100101: {cost:10, other columns},
20100102: {cost:10, other columns},
.
20100120: {cost 10, other columns}
},
CF:"project2": {
20100105: {cost:12, other columns}
.
