I would try a fetch size other then 1. Cassandras slices are start
inclusive so maybe that is a bug.
On Tuesday, February 18, 2014, Katsutoshi nagapad.0...@gmail.com wrote:
Hi.
I am using Cassandra 2.0.5 version. If null is explicitly set to a
column, paging_state will not work. My test
That does sound like a bug. Would you mind opening a JIRA (
https://issues.apache.org/jira/browse/CASSANDRA) ticket for it?
On Thu, Feb 20, 2014 at 3:06 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
I would try a fetch size other then 1. Cassandras slices are start
inclusive so maybe that
Cassandra has no null. So in this context setting a column to null or
updating null is a delete. I think. I remember debating the semantics of
null once.
On Tuesday, February 18, 2014, Katsutoshi nagapad.0...@gmail.com wrote:
Hi.
I am using Cassandra 2.0.5 version. If null is explicitly set to
Thank you for the reply. Added:
https://issues.apache.org/jira/browse/CASSANDRA-6748
Katsutoshi
2014-02-21 2:14 GMT+09:00 Sylvain Lebresne sylv...@datastax.com:
That does sound like a bug. Would you mind opening a JIRA (
https://issues.apache.org/jira/browse/CASSANDRA) ticket for it?
On
Hi.
I am using Cassandra 2.0.5 version. If null is explicitly set to a column,
paging_state will not work. My test procedure is as follows:
--
create a table and insert 10 records using cqlsh. the query is as follows:
cqlsh:test CREATE TABLE mytable (id int, range int, value text,
