I am migrating from MySql to Cassandra , In mysql I use OFFSET and LIMIT to
paginate , the problem is that we have Android client that request next
page and POST to server OFFSET and LIMIT so I don't know how can I migrate
to Cassandra and keep backward compatibility
Is there any technique for the
I have this schema
CREATE TABLE IF NOT EXISTS "blog" (
blog_id INT,
post_id INT,
body TEXT,
PRIMARY KEY (blog_id,post_id)
)WITH CLUSTERING ORDER BY (post_id DESC);
I want to get sorted list of blog_id by post_id , that means If I have
blog_id IN (1,2,3,4,5,6,7,8,9,
I have this table
CREATE TABLE users_by_username (
username text PRIMARY KEY,
email text,
age int
)
I want to run query like the following
select username from users where username LIKE 'shl%' LIMIT 10;
Always , I want to find only 10 username (Case insensitive) that start with
spe
I have this schema
CREATE TABLE IF NOT EXISTS "inbox" (
"groupId" BIGINT,
"createTime" TIMEUUID,
"mailId" BIGINT,
"body" TEXT,
PRIMARY KEY ("groupId","createTime","mailId")
)WITH CLUSTERING ORDER BY ("createTime" DESC);
This table
According to http://www.maigfrga.ntweb.co/counting-indexing-and-
ordering-cassandra
SELECT COUNT(*) FROM product limit 5000;
must return no more than 5000 , but Why it don't works? and count whole
number?
Some body told because the count return 1 row result and some body told
that it is a bug in
Assume this schema
CREATE TABLE t(
a int,
b int,
c int,
d int,
e text,
f date,
g int,
PRIMARY KEY (a,b)
)
I we create following mv
CREATE MATERIALIZED VIEW t_mv as
select a,b,c,d from t where c is not null and d is not null
Accoding to http://docs.datastax.com/en/cql/3.1/cql/ddl/ddl_when_use_
index_c.html#concept_ds_sgh_yzz_zj__upDatIndx
> Cassandra stores tombstones in the index until the tombstone limit
reaches 100K cells. After exceeding the tombstone limit, the query that
uses the indexed value will fail.
1- Is
