One thing I have noticed is that when you query via the cli with an invalid "assume" you no longer get the MarshalException beyond 0.8.1, it just states "null"

Any chance this could be more user friendly? It kind of stumped me when I switched to 0.8.4.

Anthony


On Mon, Aug 29, 2011 at 2:35 PM, Anthony Ikeda <anthony.ikeda.dev@gmail.com> wrote:
Yeah I figured out what happened. I inadvertently set the keys to utf8 on the column family:

assume ColumnFamily keys as utf8;

which broke whichever default mechanism was in place to perform the colon separated values for the Composite key. When I restarted cassandra-cli, the query worked again.

Any idea what type the key is on a Composite key such that I may be able to re-assume it?

Anthony 


On Mon, Aug 29, 2011 at 2:21 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
Sounds like you need to specify a key_validation_class so the cli
knows how to encode the key.  (It used to assume keys were always
ascii.)

On Mon, Aug 29, 2011 at 4:02 PM, Anthony Ikeda
<anthony.ikeda.dev@gmail.com> wrote:
> Is there currently a way to query a composite key in cassandra-cli?
> I was sure I used to be able to call:
> get ColumnFamily['comp1:comp2']
> But this has recently stopped working.
> Anthony
>



--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com