Sounds good. You're right, CLI doesn't support this yet (but will shortly!)
On Fri, Oct 15, 2010 at 2:30 PM, J T wrote:
> Hmm, I don't have a java client that does all this. All of my stuff is in
> erlang using the thrift client.
> I can certainly raise a ticket and describe the problem though.
Hmm, I don't have a java client that does all this. All of my stuff is in
erlang using the thrift client.
I can certainly raise a ticket and describe the problem though.
If the CLI supported querying by index I'd see if I could knock up an script
that did it but I don't think it does.
If you want
can you create a ticket with a test case?
On Fri, Oct 15, 2010 at 1:06 PM, J T wrote:
> Hi,
> If I do a secondary index look up with multiple index expressions (>1) that
> do not result in a match then I get a looping entry in the log until I
> terminate the cassandra server.
> e.g. (I'll use a
Hi,
If I do a secondary index look up with multiple index expressions (>1) that
do not result in a match then I get a looping entry in the log until I
terminate the cassandra server.
e.g. (I'll use a pseudo notation to indicate the examples)
lookup( [ { SecondaryIndexedColumnName, "ColumnValue
