Hey,
I was wondering what your plans are concerning secondary indexes and
supported operators?
I looked over the code and so far there is only EQ which of course is
the easiest since it just compares byte values and that will work for
(almost) everything. Most index operations will however requir
On Tue, Jul 6, 2010 at 6:00 PM, Jonathan Ellis wrote:
> Because stateful keyspace is semantically closer to how people use it:
Hmm no other reason?
Writing a client-side wrapper which turns
get(key, column_path, clevel) into
get(@keyspace, key, column_path, clevel)
is trivial in pretty much an
Hey,
I wonder if there is any particular reasoning why the API
(thrift/avro) will become stateful in 0.7? Granted it already is doing
that for "login", but why is the keyspace argument moved to a stateful
level?
I wrote a ruby client to help me in my app development and while it
currently just co
