Could you look at the cassandra log? This is probably due to an error on the server side.
On Fri, Nov 18, 2011 at 4:20 AM, Maxim Potekhin <potek...@bnl.gov> wrote: > Should I file a ticket? I consistently see this behavior after a mass > delete. > > On 11/17/2011 12:46 PM, Maxim Potekhin wrote: >> >> Thanks Jonathan. I get the bellow error. Don't have a clue as to what it >> means. >> >> >> null >> java.lang.RuntimeException >> at >> org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:310) >> at >> org.apache.cassandra.cli.CliMain.processStatement(CliMain.java:217) >> at org.apache.cassandra.cli.CliMain.main(CliMain.java:345) >> Caused by: java.lang.RuntimeException >> at >> org.apache.cassandra.cli.CliClient.executeGetWithConditions(CliClient.java:814) >> at >> org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:208) >> ... 2 more >> >> >> On 11/17/2011 12:28 PM, Jonathan Ellis wrote: >>> >>> If CLI returns null it means there was an error -- run with --debug to >>> check the exception. >>> >>> On Thu, Nov 17, 2011 at 11:20 AM, Maxim Potekhin<potek...@bnl.gov> >>> wrote: >>>> >>>> Hello everyone, >>>> >>>> I run a query on a secondary index. For some queries, I get 0 rows >>>> returned. >>>> In other cases, >>>> I just get a string that reads "null". >>>> >>>> What's going on? >>>> >>>> TIA >>>> >>>> Maxim >>>> >>>> >>> >>> > >
