Re: Manual Repairs

The closest you can get to this kind of functionality is by breaking up your repairs by ranges and then you could pause/restart part way through the set of ranges. There are some basic scripted approaches around to doing this but Cassandra Reaper is probably your best bet to get this kind of

Re: Manual Repairs

what version of your cassandra and what kind repair you are doing? full repair or incremental repair? list your repair command On Wed, Jun 21, 2017 at 3:27 PM, Mark Furlong wrote: > Can a repair be paused, and if paused can it be restarted from the point > of the pause,

Manual Repairs

Can a repair be paused, and if paused can it be restarted from the point of the pause, or does it start over? Mark Furlong Sr. Database Administrator mfurl...@ancestry.com M: 801-859-7427 O: 801-705-7115 1300 W Traverse Pkwy Lehi, UT 84043

Re: Count limit

Hi, Some body told because the count return 1 row result He is right Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Wed, 21 Jun 2017 02:43:32 -0400 web master socketman2...@gmail.com wrote According to

Re: Pagination

Hi, can this https://docs.datastax.com/en/developer/java-driver/2.1/manual/paging/ help you? Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Wed, 21 Jun 2017 02:44:17 -0400 web master socketman2...@gmail.com wrote I am migrating from MySql to

RE: COUNT

Is it possible for you to share tracing info for the query? You can enable tracing at cqlsh prompt with command Cqlsh > TRACING ON Cqlsh> run your query Tracing session info should be printed on screen Tracing will enable us to know where most of the time is spent! From: web master

Re: LIKE

If you are sure , that you want to do LIKE , then you can go with SASI . https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/useSASIIndex.html Hope this will help you . On Wed, Jun 21, 2017 at 2:44 PM, web master wrote: > I have this table > > CREATE TABLE

Pagination

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

Ordering by last inserted row

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

LIKE

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

COUNT

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

Count limit

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

Question about materialized view

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

tombstone limit reaches 100K cells

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-