u get only prints of bytes.
You can then test the type of the column (variable 'def') in order to call
the best suited method of 'row', so that the variable 'value' can be more
readable.
Fabrice LARCHER
2014-08-19 3:29 GMT+02:00 Kevin Burton :
> The DataStax jav
Hello, I created https://issues.apache.org/jira/browse/CASSANDRA-7766 about
that
Fabrice LARCHER
2014-08-13 14:58 GMT+02:00 DuyHai Doan :
> Hello Fabrice.
>
> A quick hint, try to create your secondary index WITHOUT the "IF NOT
> EXISTS" clause to see if you still hav
Hello,
I have used C* 2.1.0-rc1, 2.1.0-rc2, 2.1.0-rc3 and I currently use
2.1.0-rc5. Since 2.1.0-rc2, it appears that the secondary indexes are not
always working. Just after the INSERT of a row, the index seems to be
there. But after a while (I do not know when or why), SELECT statements
based on
ore.java:553)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:245)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:455)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:544)
Exception encountered during startup: null
I do not now if it can help.
Fa
Hello,
I still experience a similar issue after a 'DROP KEYSPACE' command with C*
2.1-rc3. Connection to the node may fail after a 'DROP'.
But I did not see this issue with 2.1-rc1 (-> it seems like to be a
regression brought with 2.1-rc2).
Fabrice LARCHER
2014-07-17
​Hello,
I am using the 'development' version 2.1-rc2.
With one node (=localhost), I get timeouts trying to connect to C* after
running a 'DROP KEYSPACE' command. I have following error messages in
system.log :
INFO [SharedPool-Worker-3] 2014-07-09 16:29:36,578
MigrationManager.java:319 - Drop K
