Look inside a secondary index

Hi I am curious about the internals of the Secondary Index, and in particular how the data is stored The article dated 2016 here (is that still valid ? ) https://www.datastax.com/blog/2016/04/cassandra-native-secondary-index-deep-dive indicates that a Secondary Index is really represented just

Re: Secondary Index Cleanup

We use 3.11.0 on Linux. What's the C* version do you use? Sounds like the secondary index is very out of sync with the parent cf. On Fri, Mar 2, 2018 at 6:23 AM, Malte Krüger wrote: hi, we have an CF which is about 2 gb in size, it has a seondary index on one field (UUID). the inde

Re: Secondary Index Cleanup

What's the C* version do you use? Sounds like the secondary index is very out of sync with the parent cf. On Fri, Mar 2, 2018 at 6:23 AM, Malte Krüger wrote: > hi, > > we have an CF which is about 2 gb in size, it has a seondary index on one > field (UUID). > > the inde

Secondary Index Cleanup

hi, we have an CF which is about 2 gb in size, it has a seondary index on one field (UUID). the index has a size on disk of about 10 gb. it only shrinks a little when forcing a compaction through jmx. if i use sstabledump i see a lot of these:     "partition" : {   "key" : [ "123c50d1-

?????? secondary index creation causes C* oom

Thanks Kurt. -- -- ??: "kurt";; : 2018??1??11??(??) 11:46 ??: "User"; : Re: secondary index creation causes C* oom 1.not sure if secondary index creation is the same as index rebuild Fairly sure they

Re: secondary index creation causes C* oom

> 1.not sure if secondary index creation is the same as index rebuild > Fairly sure they are the same. > 2.we noticed that the memory table flush looks still working,not the same > as CASSANDRA-12796 mentioned,but the compactionExecutor pending is > increasing. > Do

secondary index creation causes C* oom

Dear All, We met some C* nodes oom during secondary index creation with C* 2.1.18. As per https://issues.apache.org/jira/browse/CASSANDRA-12796,the flush writer will be blocked by index rebuild.but we still have some confusions: 1.not sure if secondary index creation is the same as index

Re: secondary index use case

<mich...@fantasymail.de> wrote Hi, even after reading much about secondary index usage I'm not sure if I have the correct use case for it. My table will contain about 150'000'000 records (each about 2KB data). There are two uuids used to identify a row. O

secondary index use case

Hi, even after reading much about secondary index usage I'm not sure if I have the correct use case for it. My table will contain about 150'000'000 records (each about 2KB data). There are two uuids used to identify a row. One uuid is unique for each row, the other uuid is s

RE: SASI and secondary index simultaniously

Hi, According to SASI source code (3.11.0) it will always have priority over regular secondary index: https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/index/sasi/SASIIndex.java#L234 public long getEstimatedResultRows() { // this is temporary

Re: SASI and secondary index simultaniously

In the original source code Sasi will be chosen instead of secondary index Le 12 juil. 2017 09:13, "Vlad" a écrit : > Hi, > > it's possible to create both regular secondary index and SASI on the same > column: > > > > > *CREATE TABLE ks.tb (id int PR

SASI and secondary index simultaniously

Hi, it's possible to create both regular secondary index and SASI on the same column: CREATE TABLE ks.tb (id int PRIMARY KEY,  name text); CREATE CUSTOM INDEX tb_name_idx_1 ON ks.tb (name) USING 'org.apache.cassandra.index.sasi.SASIIndex'; CREATE INDEX tb_name_idx ON ks.tb (nam

Re: Secondary Index

>> >> >> Like other suggested before adding more index , look for opportunity to >> de-normalize your data model OR create composite keys for your primary >> index – if that works for you. >> >> Secondary index are there so you can leverage them they come wi

Re: Secondary Index

Thanks for the reply vladimir but we can't upgrade c* binary that soon as we have a quick requirement for the use case I said in my first mail. So just wanted to know the difference between the 2 queries I asked in my last mail 1. select * from ks1.cf1 where status=1; 2. select * from ks1.cf1 wh

Re: Secondary Index

Hi, beyond scope of your question (as you use 2.1.17) but starting from v3.4 SASI is avaialble, doc is about DSE, but is applicable for free version as well. Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Mon, 19 Jun 2017 14:00:40 -0400 techpyaasa .

Re: Secondary Index

rtunity to > de-normalize your data model OR create composite keys for your primary > index – if that works for you. > > Secondary index are there so you can leverage them they come with cost. > They’re difficult to manage , as you repair data your secondary index will > NOT be

RE: Secondary Index

Hey there – Like other suggested before adding more index , look for opportunity to de-normalize your data model OR create composite keys for your primary index – if that works for you. Secondary index are there so you can leverage them they come with cost. They’re difficult to manage , as you

Re: Secondary Index

id1, id2) >> ) WITH CLUSTERING ORDER BY (id2 ASC) >> >> 'status' will have values of 0/1/2/3/4 (4 possible values) , insertions >> to table(partition) will happen based on id2 i.e values(id1,id2,resp,status) >> >> I want to have a filtering/criteria applied o

Re: Secondary Index

to > table(partition) will happen based on id2 i.e values(id1,id2,resp,status) > > I want to have a filtering/criteria applied on 'status' column too like > select * from ks1.cf1 where id1=123 and status=0; > > How can I achieve this w/o secondary index (on 'status

Re: Secondary Index

oo like select * from ks1.cf1 where id1=123 and status=0; How can I achieve this w/o secondary index (on 'status' column )?? On Tue, Jun 20, 2017 at 12:09 AM, ZAIDI, ASAD A wrote: > If you’re only creating index so that your query work, think again! > You’ll be storing secondary i

RE: Secondary Index

If you’re only creating index so that your query work, think again! You’ll be storing secondary index on each node , queries involving index could create issues (slowness!!) down the road the when index on multiple node Is involved and not maintained! Tables involving a lot of inserts/delete

Secondary Index

Hi, I want to create Index on already existing table which has more than 3 GB/node. We are using c*-2.1.17 with 2 DCs , each DC with 3 groups and each group has 7 nodes.(Total 42 nodes in cluster) So is it ok to create Index on this table now or will it have any problem? If its ok , how much time

Re: results differ on two queries, based on secondary index key and partition key

model. Have you looked >> at DSE Graph as a possibility? >> >> >> >> >> >> Sean Durity >> >> *From:* ferit baver elhuseyni [mailto:feritba...@gmail.com] >> *Sent:* Tuesday, March 14, 2017 11:40 AM >> *To:* user@cassandra.apache.org >>

Re: results differ on two queries, based on secondary index key and partition key

purposes of this problem, I got followers of the most-followed user from > both tables. > > > > A) select * from followers where uid=12345678 > > B) select * from followings where fid=12345678 > > > > using a small script on unix, i could find out this info on sets A

Re: results differ on two queries, based on secondary index key and partition key

graph-based model. Have you looked at > DSE Graph as a possibility? > > > > > > Sean Durity > > *From:* ferit baver elhuseyni [mailto:feritba...@gmail.com] > *Sent:* Tuesday, March 14, 2017 11:40 AM > *To:* user@cassandra.apache.org > *Subject:* results differ

RE: results differ on two queries, based on secondary index key and partition key

secondary index key and partition key Hi all, We are using a C* 2.2.8 cluster in our production system, composed of 5 nodes in 1 DC with RF=3. Our clients mostly write with CL.ALL and read with CL.ONE (both will be switched to quorum soon). We face several problems while trying to persist

results differ on two queries, based on secondary index key and partition key

g than that is, if I query follower table on secondary index, I don't get a row that I normally get with filtering just on partition key. Let me try to visualize it : select uid,ts,fid from followers where fid=X (cannot find uid=12345678) A | BBB | X C | DDD | X E | FFF | X s

Re: secondary index on static column

demo (id2); > > id and id2 match one to one. > > I make one insert: > insert into demo (id, id2, added, source, dest) values ('id1', 22, > '2017-01-28', 'src1', 'dst1'); > > > The "select from demo;" gives the expe

Re: secondary index on static column

rc1', 'dst1'); > > > The "select from demo;" gives the expected answer of the one inserted row. > > But "select from demo where id2=22" gives 70 rows as result (all the same). > > Why? I have read > https://www.datastax.com/dev/blog/cassandra-native-secondary-index-deep-dive > > but I don't get it... > > thanks for answering, > Michael > > >

Re: secondary index on static column

ot;select from demo where id2=22" gives 70 rows as result (all the same). Why? I have read https://www.datastax.com/dev/blog/cassandra-native-secondary-index-deep-dive but I don't get it... thanks for answering, Michael

secondary index on static column

;src1', 'dst1'); The "select from demo;" gives the expected answer of the one inserted row. But "select from demo where id2=22" gives 70 rows as result (all the same). Why? I have read https://www.datastax.com/dev/blog/cassandra-native-secondary-index-deep-dive but I don't get it... thanks for answering, Michael

Re: Secondary index tombstone limit

unsubsribe Sent from Yahoo Mail on Android On Tue, 8 Nov, 2016 at 2:11 pm, Oleg Krayushkin wrote: Hi, could you please clarify: 100k tombstone limit for SE is per CF, cf-node, original sstable or (very unlikely) partition? Thanks!-- Oleg Krayushkin

Secondary index tombstone limit

Hi, could you please clarify: 100k tombstone limit for SE is per CF, cf-node, original sstable or (very unlikely) partition? Thanks! -- Oleg Krayushkin

Re: Secondary Index on Boolean column with TTL

;>> ry-index-deep-dive/ >>> >>> See section E Caveats which applies to your boolean use-case >>> >>> On Mon, Oct 31, 2016 at 2:19 PM, Oleg Krayushkin >>> wrote: >>> >>>> Hi, >>>> >>>> Is it a good approa

Re: Secondary Index on Boolean column with TTL

at 2:19 PM, Oleg Krayushkin >> wrote: >> >>> Hi, >>> >>> Is it a good approach to make a boolean column with TTL and build a >>> secondary index on it? >>> (For example, I want to get rows which need to be updated after a >>> certain

Re: Secondary Index on Boolean column with TTL

log/cassandra-native- > secondary-index-deep-dive/ > > See section E Caveats which applies to your boolean use-case > > On Mon, Oct 31, 2016 at 2:19 PM, Oleg Krayushkin > wrote: > >> Hi, >> >> Is it a good approach to make a boolean column with TTL and build a &g

Re: given partition key and secondary index, still require allow_filtering?

e = 0 > > AND gc_grace_seconds = 864000 > > AND max_index_interval = 2048 > > AND memtable_flush_period_in_ms = 0 > > AND min_index_interval = 128 > > AND read_repair_chance = 0.0 > > AND speculative_retry = '99PERCENTILE'; >

Re: Secondary Index on Boolean column with TTL

http://www.planetcassandra.org/blog/cassandra-native-secondary-index-deep-dive/ See section E Caveats which applies to your boolean use-case On Mon, Oct 31, 2016 at 2:19 PM, Oleg Krayushkin wrote: > Hi, > > Is it a good approach to make a boolean column with TTL and build a > sec

Secondary Index on Boolean column with TTL

Hi, Is it a good approach to make a boolean column with TTL and build a secondary index on it? (For example, I want to get rows which need to be updated after a certain time, but I don't want, say, to add a filed "update_date" as clustering column or to create another table)

given partition key and secondary index, still require allow_filtering?

864000 AND max_index_interval = 2048 AND memtable_flush_period_in_ms = 0 AND min_index_interval = 128 AND read_repair_chance = 0.0 AND speculative_retry = '99PERCENTILE'; CREATE INDEX user_categories_1477899735_score_idx ON profile_new.user_categories_1477899735

Re: OutOfMemoryError when initializing a secondary index

ning Cassandra 3.0.7 we have 3 out of 6 nodes that threw an OOM error > when a developer created a secondary index. I'm trying to repair the > cluster. I stopped all nodes, deleted all traces of the table and secondary > index from disk, removed commit logs and saved caches, and rest

OutOfMemoryError when initializing a secondary index

Running Cassandra 3.0.7 we have 3 out of 6 nodes that threw an OOM error when a developer created a secondary index. I'm trying to repair the cluster. I stopped all nodes, deleted all traces of the table and secondary index from disk, removed commit logs and saved caches, and restarte

Re: Low cardinality secondary index behaviour

Udyog Vihar, > Phase -4, Sector 18, Gurgaon, Haryana 122016, INDIA > > On Thu, May 12, 2016 at 9:18 PM, Tyler Hobbs wrote: > >> >> On Tue, May 10, 2016 at 6:41 AM, Atul Saroha >> wrote: >> >>> I have concern over using secondary index on field

Re: Low cardinality secondary index behaviour

*EXT*: 12369 Plot # 362, ASF Centre - Tower A, Udyog Vihar, Phase -4, Sector 18, Gurgaon, Haryana 122016, INDIA On Thu, May 12, 2016 at 9:18 PM, Tyler Hobbs wrote: > > On Tue, May 10, 2016 at 6:41 AM, Atul Saroha > wrote: > >> I have concern over using secondary index

Re: Low cardinality secondary index behaviour

On Tue, May 10, 2016 at 6:41 AM, Atul Saroha wrote: > I have concern over using secondary index on field with low cardinality. > Lets say I have few billion rows and each row can be classified in 1000 > category. Lets say we have 50 node cluster. > > Now we want to fetch da

Low cardinality secondary index behaviour

I have concern over using secondary index on field with low cardinality. Lets say I have few billion rows and each row can be classified in 1000 category. Lets say we have 50 node cluster. Now we want to fetch data for a single category using secondary index over a category. And query is

Re: Clustering key and secondary index behavior changed between 2.0.11 and 3.3.0

7;,37); > INSERT INTO table1 (name, class, inter, power) VALUES ('R1',4, 'int1',49); > > In version 2.0.11, I used to have a secondary index on inter, that allowed > me to make fast queries on this table: > CREATE INDEX table1_inter ON table1 (inter); > SELECT * F

Clustering key and secondary index behavior changed between 2.0.11 and 3.3.0

class, inter, power) VALUES ('R1',2, 'int1',18); INSERT INTO table1 (name, class, inter, power) VALUES ('R1',3, 'int1',37); INSERT INTO table1 (name, class, inter, power) VALUES ('R1',4, 'int1',49); In version 2.0.11, I used to have a seco

RE: Updating secondary index options

that holds index options but it seems I need to restart Cassandra twice to be able to see the changes. Regards, -- Jacques-Henri Berthemet From: Jack Krupansky [mailto:jack.krupan...@gmail.com] Sent: vendredi 4 mars 2016 18:40 To: user@cassandra.apache.org Subject: Re: Updating secondary index o

Re: Updating secondary index options

s-Henri Berthemet* >> >> >> >> *From:* DuyHai Doan [mailto:doanduy...@gmail.com] >> *Sent:* vendredi 4 mars 2016 14:52 >> *To:* user@cassandra.apache.org >> *Subject:* Re: Updating secondary index options >> >> >> >> DROP and re-create t

Re: Updating secondary index options

t; *Sent:* vendredi 4 mars 2016 14:52 > *To:* user@cassandra.apache.org > *Subject:* Re: Updating secondary index options > > > > DROP and re-create the index with the new options > > > > On Fri, Mar 4, 2016 at 3:45 PM, Jacques-Henri Berthemet < > jacques-henri.berthe...@genes

RE: Updating secondary index options

Subject: Re: Updating secondary index options DROP and re-create the index with the new options On Fri, Mar 4, 2016 at 3:45 PM, Jacques-Henri Berthemet mailto:jacques-henri.berthe...@genesys.com>> wrote: Hi, I’m using Cassandra 2.2.5 with a custom secondary index. It’s created with the below

Re: Updating secondary index options

DROP and re-create the index with the new options On Fri, Mar 4, 2016 at 3:45 PM, Jacques-Henri Berthemet < jacques-henri.berthe...@genesys.com> wrote: > Hi, > > > > I’m using Cassandra 2.2.5 with a custom secondary index. It’s created with > the below syntax: > >

Updating secondary index options

Hi, I'm using Cassandra 2.2.5 with a custom secondary index. It's created with the below syntax: https://docs.datastax.com/en/cql/3.1/cql/cql_reference/create_index_r.html CREATE CUSTOM INDEX ON users (email) USING 'path.to.the.IndexClass' WITH OPTIONS = {'some_settin

Re: Secondary index is causing high CPU load

See https://issues.apache.org/jira/browse/CASSANDRA-10414 for an overview of why vnodes are currently less efficient for secondary index queries. On Tue, Sep 29, 2015 at 12:45 PM, Robert Coli wrote: > On Tue, Sep 15, 2015 at 7:44 AM, Tom van den Berge < > tom.vandenbe...@gmail.c

Re: Secondary index is causing high CPU load

On Tue, Sep 15, 2015 at 7:44 AM, Tom van den Berge < tom.vandenbe...@gmail.com> wrote: > Read queries on a secondary index are somehow causing an excessively high > CPU load on all nodes in my DC. > ... > What really surprised me is that executing a single query on this >

Secondary index is causing high CPU load

Read queries on a secondary index are somehow causing an excessively high CPU load on all nodes in my DC. The table has some 60K records, and the cardinality of the index is very low (~10 distinct values). The returned result set typically contains 10-30K records. The same queries on nodes in

Re: Thrift to cql : mixed static and dynamic columns with secondary index

>> >> I'm trying to migrate from Cassandra 1.1 and Hector to a more up-to-date >> stack like Cassandra 1.2+ and CQL3. >> >> I have read http://www.datastax.com/dev/blog/thrift-to-cql3 >> <https://webmail.one.grp/owa/redir.aspx?C=d70889e7914440b0ad13875bf007

Re: Thrift to cql : mixed static and dynamic columns with secondary index

ssandra 1.2+ and CQL3. > > I have read http://www.datastax.com/dev/blog/thrift-to-cql3 > <https://webmail.one.grp/owa/redir.aspx?C=d70889e7914440b0ad13875bf00770a8&URL=http%3a%2f%2fwww.datastax.com%2fdev%2fblog%2fthrift-to-cql3> > but > my use case adds a complexity whic

Thrift to cql : mixed static and dynamic columns with secondary index

2fdev%2fblog%2fthrift-to-cql3> but my use case adds a complexity which seems not documented : I have a mixed column family with a secondary index. The column family has one explicitly declared column, which is indexed natively. In this column family, I'm also adding columns dynamically :

Re: timeout when using secondary index

Jimmy, The secondary index is getting scanned since you put the column in your query. The behavior you are looking for is a coming feature called Global Indexes slated for 3.0. https://issues.apache.org/jira/browse/CASSANDRA-6477 In the meantime, you could build your own lookup table even with

timeout when using secondary index

Hi, Ran into RPC timeout exception when execution a query that involve secondary index of a Boolean column when for example the company has more than 1k person. select * from company where company_id= and isMale = true; such extreme low cardinality of secondary index like the other docs

Re: Internal pagination in secondary index queries

Thanks. I've opened the following issue to track this: https://issues.apache.org/jira/browse/CASSANDRA-8550 SK On 2014-12-30 11:26, Tyler Hobbs wrote: > > On Mon, Dec 29, 2014 at 5:20 PM, Sam Klock > wrote: > > > Our investigation led us to logic in Cassandra u

Re: Internal pagination in secondary index queries

On Mon, Dec 29, 2014 at 5:20 PM, Sam Klock wrote: > > > Our investigation led us to logic in Cassandra used to paginate scans > of rows in indexes on composites. The issue seems to be the short > algorithm Cassandra uses to select the size of the pages for the scan, > partially given on the follo

Re: Internal pagination in secondary index queries

Secondary indexes are there for convenience, not performance. If you're looking for something performant, you'll need to maintain your own indexes. On Mon Dec 29 2014 at 3:22:58 PM Sam Klock wrote: > Hi folks, > > Perhaps this is a question better addressed to the Cassandra developers > direct

Internal pagination in secondary index queries

Hi folks, Perhaps this is a question better addressed to the Cassandra developers directly, but I thought I'd ask it here first. We've recently been benchmarking certain uses of secondary indexes in Cassandra 2.1.x, and we've noticed that when the number of items in an index reaches beyond so

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

quest to the replica: What's the extra overhead incurred by vnode to process the secondary index request on the replica? In other words, does replica still has to fire individual queries internally for all the token ranges [(max(-9193352069377957523), max(-9136021049555745100), etc.], or it ca

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

27;s a limit on the query, return the first N results when listed in token order). > > With non-vnode, it only queries a particular node only one time..Btw, in > the worst case, I understand secondary index query has to scan all the > nodes in cluster sometime (empty table or high card

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

re sending a lot more requests and waiting for the response than the number of nodes. " Don't understand the restriction though - "don't break the existing API's". With non-vnode, it only queries a particular node only one time..Btw, in the worst case, I understand sec

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

On Fri, Sep 19, 2014 at 2:19 PM, DuyHai Doan wrote: > But does it implies that with vnodes, there are actually "extra work" to > do for scanning indices ? > Vnodes are just nodes, so they have all the problems-associated-with-many-nodes one would get with 256x as many nodes. =Rob

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

we are sending a lot more requests and waiting for the response than the number of nodes. " Don't understand the restriction though - "don't break the existing API's". With non-vnode, it only queries a particular node only one time..Btw, in the worst case, I understan

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

On Fri, Sep 19, 2014 at 4:19 PM, DuyHai Doan wrote: > > But does it implies that with vnodes, there are actually "extra work" to > do for scanning indices ? > Yes. > If yes, is this "extra load" rather I/O bound or CPU bound ? > It doesn't necessarily change what the query is "bound" by, exc

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

, there is no data in the table. Table is empty. Query is fired on the >> empty table. >> > > This is actually the worst case for secondary index lookups. > > >> >> From the tracing ouput, I don't understand why it's doing multiple scans >> on one node.

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

On Fri, Sep 19, 2014 at 12:41 PM, Jay Patel wrote: > > Btw, there is no data in the table. Table is empty. Query is fired on the > empty table. > This is actually the worst case for secondary index lookups. > > From the tracing ouput, I don't understand why it's d

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

gmail.com] On >> Behalf Of Jonathan Haddad >> Sent: Friday, September 19, 2014 4:01 AM >> To: user@cassandra.apache.org >> Subject: Re: Slow down of secondary index query with VNODE (C* version >> 1.2.18, jre6). >> >> Keep in mind secondary indexes in cassandra ar

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

r 19, 2014 4:01 AM > To: user@cassandra.apache.org > Subject: Re: Slow down of secondary index query with VNODE (C* version > 1.2.18, jre6). > > Keep in mind secondary indexes in cassandra are not there to improve > performance, or even really be used in a serious user facing manner. &

RE: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

Of Jonathan Haddad Sent: Friday, September 19, 2014 4:01 AM To: user@cassandra.apache.org Subject: Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6). Keep in mind secondary indexes in cassandra are not there to improve performance, or even really be used in a serious

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

seeing extreme slow down (500ms to 1s) in query on secondary index > with vnode. I'm seeing multiple secondary index scans on a given node in > trace output when vnode is enabled. Without vnode, everything is good. > > Cluster size: 6 nodes > Replication factor: 3 > Consisten

Re: Slow down of secondary index query with VNODE (C* version 1.2.18, jre6).

> We are seeing extreme slow down (500ms to 1s) in query on secondary index > with vnode. I'm seeing multiple secondary index scans on a given node in > trace output when vnode is enabled. Without vnode, everything is good. > > Cluster size: 6 nodes > Replication factor: 3

RE: Secondary index or dedicated CF?

Thanks you for your feedbacks. De : Mark Reddy [mailto:mark.l.re...@gmail.com] Envoyé : vendredi 22 août 2014 17:08 À : user@cassandra.apache.org Objet : Re: Secondary index or dedicated CF? Hi, As a general rule of thumb I would steer clear of secondary indexes, this is also the official

Re: Secondary index or dedicated CF?

x27;s built-in secondary indexes where possible. Instead, it is recommended to denormalize data and manually maintain a dynamic table as a form of an index instead of using a secondary index. If and when secondary indexes are to be used, they should be created only on columns containin

Re: Secondary index or dedicated CF?

Hello Eric "Under the hood what is the difference of the both solutions?" 1. Cassandra secondary index: distributed index, supports better high volume of data, the index itself is distributed so there is no bottleneck. The tradeoff is that depending on the cardinality of data havin

Secondary index or dedicated CF?

ult will be the same. Both will have the rowkey equals to the "bucketname" and the "tenantID". Excepted that the secondary index can have a replication delay... Can you help me on this point? Regards, Eric Ce message et les pi?ces jointes sont

Re: RPC timeout paging secondary index query results

oing to have to rework our data model to avoid them. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/RPC-timeout-paging-secondary-index-query-results-tp7595078p7595486.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.

Re: RPC timeout paging secondary index query results

indexed value with another 100,000 records then we can't > page > through any of the indexed values even though the original 2 that worked > previously have not changed. > > Phil > > > > -- > View this message in context: > http://cassandra-user-in

Re: Cannot query secondary index

r the index item. > > The cost of the "every once in a while" delete may be infrequent enough > for you to do what you were actually trying to do in the first place, use a > secondary index and query the table leveraging the ALLOW FILTERING clause. > > My recommendation

Re: Cannot query secondary index

elps manage the effort of the manual delete. However, you would still have to insert into this separate table per the index item. The cost of the "every once in a while" delete may be infrequent enough for you to do what you were actually trying to do in the first place, use a seco

Re: RPC timeout paging secondary index query results

ven though the original 2 that worked previously have not changed. Phil -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/RPC-timeout-paging-secondary-index-query-results-tp7595078p7595126.html Sent from the cassandra-u...@incubator.apache.org ma

Re: RPC timeout paging secondary index query results

uests in Cassandra are subject to timeouts which default to small numbers of seconds. Secondary index queries are slower than non-secondary index queries. Low cardinality is not a great case for them. If you turn on tracing, it might inform your performance picture. My hunch is that you are not see

Re: RPC timeout paging secondary index query results

The problem appears to be directly related to number of entries in the index. I started with an empty table and added 50,000 entries at a time with the same indexed value. I was able to page through the results of a query that used the secondary index with 250,000 records in the table using a

Re: RPC timeout paging secondary index query results

On Wed, Jun 11, 2014 at 12:43 PM, Phil Luckhurst < phil.luckhu...@powerassure.com> wrote: > It just seems that what we are trying to do here is > such basic functionality of an index that I thought we must be doing > something wrong for it to appear to be this broken. > To be clear, I did not rea

Re: RPC timeout paging secondary index query results

must be doing something wrong for it to appear to be this broken. Phil -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/RPC-timeout-paging-secondary-index-query-results-tp7595078p7595092.html Sent from the cassandra-u...@incubator.apache.org

Re: RPC timeout paging secondary index query results

I like the "- Provides the illusion that you are using a RDBMS." part ;-) On Wed, Jun 11, 2014 at 8:52 PM, Robert Coli wrote: > On Wed, Jun 11, 2014 at 2:24 AM, Phil Luckhurst < > phil.luckhu...@powerassure.com> wrote: > >> Is paging through the results of a

Re: RPC timeout paging secondary index query results

On Wed, Jun 11, 2014 at 2:24 AM, Phil Luckhurst < phil.luckhu...@powerassure.com> wrote: > Is paging through the results of a secondary index query broken in > Cassandra > 2.0.7 or are we doing something wrong? > General feedback on questions of this type : http://mail-a

RPC timeout paging secondary index query results

Is paging through the results of a secondary index query broken in Cassandra 2.0.7 or are we doing something wrong? We have table with a few hundred thousand records and an indexed low-cardinality column. The relevant bits of the table definition are shown below CREATE TABLE measurement

Re: Cannot query secondary index

2:45 PM, Michal Michalski < >>>> michal.michal...@boxever.com> wrote: >>>> >>>>> Secondary indexes internally are just CFs that map the indexed value >>>>> to a row key which that value belongs to, so you can only query these >>>&

Re: Cannot query secondary index

owever, your query does not require index *IF* you provide a row key - >>>> you can use "<" or ">" like you did for the date column, as long as you >>>> refer to a single row. However, if you don't provide it, it's not going to >>&

Re: Frequent secondary index sstable corruption

the process of migrating data over to cassandra for several of our >> apps, and a few of the schemas use secondary indexes. Four times in the >> last couple months I've run into a corrupted sstable belonging to a >> secondary index, but have never seen this on any other sst

Re: Frequent secondary index sstable corruption

On Tue, Jun 10, 2014 at 7:31 AM, Jeremy Jongsma wrote: > I'm in the process of migrating data over to cassandra for several of our > apps, and a few of the schemas use secondary indexes. Four times in the > last couple months I've run into a corrupted sstable belonging to

Frequent secondary index sstable corruption

I'm in the process of migrating data over to cassandra for several of our apps, and a few of the schemas use secondary indexes. Four times in the last couple months I've run into a corrupted sstable belonging to a secondary index, but have never seen this on any other sstables. When

  1   2   3   4   5   >