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

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). > >

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 you by chance have

Re: secondary index use case

Hi, You didn't mention your C* version, but starting from 3.4 SASI indexes are available. You can try it with SPARSE option, as uuid corresponds to only one row. Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Thu, 20 Jul 2017 05:21:31 -0400 Micha

Re: Secondary Index

cs.datastax.com/en/cql/3.1/cql/ddl/ddl_when_use_ind >> ex_c.html >> >> >> >> >> >> >> >> *From:* techpyaasa . [mailto:techpya...@gmail.com] >> *Sent:* Tuesday, June 20, 2017 2:30 AM >> *To:* ZAIDI, ASAD A <az1...@att.com> >>

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

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

om] > *Sent:* Tuesday, June 20, 2017 2:30 AM > *To:* ZAIDI, ASAD A <az1...@att.com> > *Cc:* user@cassandra.apache.org > *Subject:* Re: Secondary Index > > > > Hi ZAIDI, > > Thanks for reply. > Sorry I didn't get your line > "You can get away the potential situation by lev

RE: Secondary Index

gt; Cc: user@cassandra.apache.org Subject: Re: Secondary Index Hi ZAIDI, Thanks for reply. Sorry I didn't get your line "You can get away the potential situation by leveraging composite key, if that is possible for you?" How can I get through it?? Like I have a table as below CREATE TA

Re: Secondary Index

Hi: If you model your table with 'status' as the partitiion key you are limiting your cluster. If status only has 5 posible values, every insert will be assigned only to 5 nodes. So, you will not use your cluster resources correctly. create table ks1.sta1(status int,id1 bigint,id2 binint,resp

Re: Secondary Index

Hi , Better you can go with denormalized the data based on status. create table ks1.sta1(status int,id1 bigint,id2 binint,resp text,primary key(status,id1)); This will allow you to do as you want.. select * from ks1.sta1 where status = 0 and id1 = 123; Please make sure, that (status and id1)

Re: Secondary Index

Hi ZAIDI, Thanks for reply. Sorry I didn't get your line "You can get away the potential situation by leveraging composite key, if that is possible for you?" How can I get through it?? Like I have a table as below CREATE TABLE ks1.cf1 (id1 bigint, id2 bigint, resp text, status int, PRIMARY KEY

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

Re: secondary index on static column

Hi, Sorry for the delay, I created a ticket with steps to reproduce the issue:  https://issues.apache.org/jira/browse/CASSANDRA-13277 Best, Romain Le Jeudi 2 février 2017 16h53, Micha a écrit : Hi, it's a 3.9, installed on a jessie system. For me it's like

Re: secondary index on static column

Hi, it's a 3.9, installed on a jessie system. For me it's like this: I have a three node cluster. When creating the keyspace with replication factor 3 it works. When creating the keyspace with replication factor 2 it doesn't work and shows the weird behavior. This is a fresh install, I also

Re: secondary index on static column

Hi, What's your C* 3.X version?I've just tested it on 3.9 and it works: cqlsh> SELECT * FROM test.idx_static where id2=22;  id  | added                           | id2 | source | dest-+-+-++-- id1 | 2017-01-27 23:00:00.00+ |  22 |  

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

Re: Secondary Index on Boolean column with TTL

Thanks a lot, DuyHai! 2016-10-31 19:53 GMT+03:00 DuyHai Doan : > Technically TTL should be handled properly. However, be careful of expired > data turning into tombstones. For the original table, it may be a tombstone > on a skinny partition but for the 2nd index, it may be

Re: Secondary Index on Boolean column with TTL

Technically TTL should be handled properly. However, be careful of expired data turning into tombstones. For the original table, it may be a tombstone on a skinny partition but for the 2nd index, it may be a tombstone set on a wide partition and you'll start getting into trouble when reading a

Re: Secondary Index on Boolean column with TTL

Hi, DuyHai, thank you. I got the idea of caveat with too low cardinality, but still wondering of possible troubles at the idea to put TTL (months) on indexed column (not bool, say, 100 different values of int). 2016-10-31 16:33 GMT+03:00 DuyHai Doan : >

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

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 makes

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 < >

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 having the same

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 stand that DataStax take (see p5 of their best practices doc: http://www.datastax.com/wp-content/uploads/2014/04/WP-DataStax-Enterprise-Best-Practices.pdf). “It is best to avoid using Cassandra's

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 Question

Yup, there are other types of indexing like that in PlayOrm which do it differently so all nodes are not hit so it works better for instance if you are partitioning your data and you query into just a single partition so it doesn't put load on all the nodes. (of course, you have to have a

RE: Secondary Index Question

Thanks Dean. Any reason why it is sequential ? It is to avoid loading all the nodes and see if one node can return the desired results ? -Original Message- From: Hiller, Dean [mailto:dean.hil...@nrel.gov] Sent: 21 August 2013 07:36 To: user@cassandra.apache.org Subject: Re: Secondary

Re: Secondary Index Question

Message- From: Hiller, Dean [mailto:dean.hil...@nrel.gov] Sent: 21 August 2013 07:36 To: user@cassandra.apache.org Subject: Re: Secondary Index Question Yup, there are other types of indexing like that in PlayOrm which do it differently so all nodes are not hit so it works better for instance

Re: Secondary Index Question

results ? -Original Message- From: Hiller, Dean [mailto:dean.hil...@nrel.gov] Sent: 21 August 2013 07:36 To: user@cassandra.apache.org Subject: Re: Secondary Index Question Yup, there are other types of indexing like that in PlayOrm which do it differently so all nodes are not hit so

Re: Secondary Index Question

On Tue, Aug 20, 2013 at 5:57 PM, Kanwar Sangha kan...@mavenir.com wrote: Hi – I was reading some blogs on implementation of secondary indexes in Cassandra and they say that “the read requests are sent sequentially to all the nodes” ? ** ** So if I have a query to fetch ALL records

Re: Secondary Index on table with a lot of data crashes Cassandra

Hi, this is true for CQL2, it doesn't work for CQL3: cqlsh:c4 SELECT id from some_table WHERE indexed_column='test'; ... cqlsh:c4 SELECT KEY from some_table WHERE indexed_column='test'; Bad Request: Undefined name key in selection clause Perhaps you meant to use CQL 2? Try using the -2 option

Re: Secondary Index on table with a lot of data crashes Cassandra

What are we doing wrong? Can it be that Cassandra is actually trying to read all the CF data rather than just the keys! (actually, it doesn't need to go to the users CF at all - all the data it needs is in the index CF) Data is not stored as a BTree, that's the RDBMS approach. We hit the

Re: Secondary Index on table with a lot of data crashes Cassandra

Hi, if you are able to reproduce the issue, file a ticket on https://issues.apache.org/jira/browse/CASSANDRA - my experience is developers respond quickly on issues that are clearly a bug. regards, ondrej cernos On Thu, Apr 25, 2013 at 10:03 AM, Tamar Rosen ta...@correlor.com wrote: Hi,

RE: Secondary Index on table with a lot of data crashes Cassandra

IMHO: user_name is not a column, it is the row key. Therefore, according to http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/ , the row does not contain a relevant column index, which causes the iterator to read each column (including value) of each row. I believe that instead of

Re: secondary index problem

Seems like when we have updates that are large (10k rows in one mutate) the problem is more likely to occur. 10K rows in one mutate is a very bad idea. It will take the nodes a long time to process them, risking time out, and it will essentially starving other requests. You should also

Re: secondary index problem

We are using CL ONE for mutates. As for the large batches, yes, our use pattern has exceeded the initial understanding. We plan to rewrite this bit, but it has not been a problem so far (or maybe this index thing is the problem that forces the rewrite?). On the rare timeout, we retry... I

Re: secondary index problem

Brett, Do you have some steps to reproduce the problem ? If so please create a ticket on jira. Cheers - Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 16/03/2013, at 11:40 AM, Janne Jalkanen

Re: secondary index problem

Aaron, No recipe yet. It pops up randomly and, i think due to the nature of our app, goes away. Seems like when we have updates that are large (10k rows in one mutate) the problem is more likely to occur. I'll try to workout a repro... -Brett On Mar 18, 2013, at 10:18 AM, aaron morton

Re: secondary index problem

This could be either of the following bugs (which might be the same thing). I get it too every time I recycle a node on 1.1.10. https://issues.apache.org/jira/browse/CASSANDRA-4973 or https://issues.apache.org/jira/browse/CASSANDRA-4785 /Janne On Mar 15, 2013, at 23:24 , Brett Tinling

Re: Secondary index query + 2 Datacenters + Row Cache + Restart = 0 rows

I tried to run with tracing, but it says 'Scanned 0 rows and matched 0'. I found existing issue on this bug https://issues.apache.org/jira/browse/CASSANDRA-4973 I made a d-test for reproducing it and attached to the ticket. Alexei On 2 February 2013 23:00, aaron morton aa...@thelastpickle.com

Re: Secondary index query + 2 Datacenters + Row Cache + Restart = 0 rows

Can you run the select in cqlsh and enabling tracing (see the cqlsh online help). If you can replicate it then place raise a ticket on https://issues.apache.org/jira/browse/CASSANDRA and update email thread. Thanks - Aaron Morton Freelance Cassandra Developer New Zealand

Re: Secondary index loss on node restart

Can you contribute your experience to this ticket https://issues.apache.org/jira/browse/CASSANDRA-4670 ? Thanks - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 24/09/2012, at 6:22 AM, Michael Theroux mthero...@yahoo.com wrote: Hello, We

Re: Secondary index read/write explanation

On 7 September 2012 00:42, aaron morton aa...@thelastpickle.com wrote: 1. When a write request is received, it is written to the base CF and secondary index to secondary (hidden) CF. If this right, will the secondary index be written local the node or will it follow RP/OPP to write to nodes.

Re: Secondary index read/write explanation

1. When a write request is received, it is written to the base CF and secondary index to secondary (hidden) CF. If this right, will the secondary index be written local the node or will it follow RP/OPP to write to nodes. it's local. If an index is to be updated the previous column values

Re: Secondary index partially created

If you are still having problems can you post the query and the output from nodetool cfstats on one of the nodes that fails ? cfstats will tell us if the secondary index was built. Cheers - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On

Re: Secondary index partially created

On Mon, Aug 27, 2012 at 12:59 AM, aaron morton aa...@thelastpickle.com wrote: If you are still having problems can you post the query and the output from nodetool cfstats on one of the nodes that fails ? driftx got me sorted. It escaped me that a rolling restart was necessary to build

Re: Secondary index partially created

On Thu, Aug 23, 2012 at 6:54 PM, Richard Crowley r...@rcrowley.org wrote: I have a three-node cluster running Cassandra 1.0.10. In this cluster is a keyspace with RF=3. I *updated* a column family via Astyanax to add a column definition with an index on that column. Then I ran a backfill to

Re: Secondary index partially created

What does List my_column_family in CLI show on all the nodes? Perhaps the syntax u're using isn't correct? You should be getting the same data on all the nodes irrespective of which node's CLI you use. The replication factor is for redundancy to have copies of the data on different nodes to help

Re: Secondary index and/or row key in the read path ?

- do we need to post-process (filter) the result of the query in our application ? Thats the one :) Right now the code paths don't exist to select a row using a row key *and* apply a column level filter. The RPC API does not work that way and I'm not sure if this is something that is planned

Re: Secondary index and/or row key in the read path ?

Hi Aaron, Thank you for your answer. So, I shall do post-processing for selecting a row using a row key *and* applying a column level filter. Best Regards, Jean-Armel 2012/8/21 aaron morton aa...@thelastpickle.com - do we need to post-process (filter) the result of the query in our

Re: Secondary index impact on write performance

There is a second (system managed) column family for each secondary index, so any write to a field that is indexed causes two writes, one to the main column family, and another to the index column family, where in this index column family the key is the value of the secondary column, and the

Re: Secondary index impact on write performance

Thanks. That was what I expected, but wanted to confirm. On Aug 4, 2012 11:24 AM, Dave Brosius dbros...@mebigfatguy.com wrote: There is a second (system managed) column family for each secondary index, so any write to a field that is indexed causes two writes, one to the main column family,

Re: Secondary Index, performance , data type

select my_cf where columnA = a and columnB = b and columnC = c and columnD = d Cassandra will only use one equality clause to select the candidate rows. The other clauses are applied to the rows using that first clause. The clause to use to select candidate rows is based on statistics that

Re: Secondary Index, performance , data type

Many thx for the explanation Aaron. On Wednesday, July 4, 2012, aaron morton wrote: select my_cf where columnA = a and columnB = b and columnC = c and columnD = d Cassandra will only use one equality clause to select the candidate rows. The other clauses are applied to the rows using that

Re: Secondary index data gone after restart (1.1.1)

CASSANDRA-3954 disabled caches on secondary index CF's in 1.1.0 and CASSANDRA-4197 enabled it in 1.1.1 Can you create a ticket on https://issues.apache.org/jira/browse/CASSANDRA I guessing this has something to do with the local partitioner used for the secondary index Cf. That would explain

Re: Secondary index data gone after restart (1.1.1)

Hi please refer JDK nio package's ByteBuffer, I don't think that ByteBuffer can be cast from the BigInteger directly, it seems you need make some conversion before put it into a ByteBuffer. Thanks Fei On Tue, Jun 26, 2012 at 12:07 AM, Ivo Meißner i...@overtronic.com wrote: Hi, I am

Re: Secondary index data gone after restart (1.1.1)

Hi, but if the data must be converted, this is something that should be fixed inside cassandra… Is this a bug, should I file a bug report? Or is there some kind of setting I can change to make it work for now? Maybe it is related to this issue, but this should have been fixed in 1.1.0:

Re: Secondary Index Validation Type Parse Error

java.lang.RuntimeException: org.apache.cassandra.db.marshal.MarshalException: cannot parse 'subject' as hex bytes This has to do with the create column family statement... and comparator = 'BytesType' Tells Cassandra that all column names in this CF should be interpreted as raw bytes. The

RE: Secondary Index Validation Type Parse Error

Hi me again - sorry i've just read that bytestype will expect hex input so my question now is how to create a column that will accept non-validated text as as input? I think I can maybe get round this by forcing UTF8Encoding regardless if the string is already identified as UTF8 or not

RE: Secondary index issue, unable to query for records that should be there

From: Riyad Kalla [mailto:rka...@gmail.com] Sent: Monday, November 07, 2011 4:31 PM To: user@cassandra.apache.org Subject: Re: Secondary index issue, unable to query for records that should be there Nate, is this all against a single Cassandra server, or do you have a ring setup? If you do have

Re: Secondary index issue, unable to query for records that should be there

] *Sent:* Monday, November 07, 2011 4:31 PM *To:* user@cassandra.apache.org *Subject:* Re: Secondary index issue, unable to query for records that should be there ** ** Nate, is this all against a single Cassandra server, or do you have a ring setup? If you do have a ring setup, what

RE: Secondary index issue, unable to query for records that should be there

should have rows). Thanks, -nate From: Jake Luciani [mailto:jak...@gmail.com] Sent: Tuesday, November 08, 2011 8:56 AM To: user@cassandra.apache.org Subject: Re: Secondary index issue, unable to query for records that should be there Hi Nate, Could you try running it with debug enabled

RE: Secondary index issue, unable to query for records that should be there

ResponseVerbHandler.java (line 44) Processing response on a callback from 463@natebookpro/127.0.1.1 Thanks, -nate From: Jake Luciani [mailto:jak...@gmail.com] Sent: Tuesday, November 08, 2011 8:56 AM To: user@cassandra.apache.org Subject: Re: Secondary index issue, unable to query for records that should

RE: Secondary index issue, unable to query for records that should be there

Note that I had identical behavior using a fresh download of Cassandra 1.0.2 as of today. Thanks, -nate From: Nate Sammons [mailto:nsamm...@ften.com] Sent: Tuesday, November 08, 2011 10:20 AM To: user@cassandra.apache.org Subject: RE: Secondary index issue, unable to query for records

RE: Secondary index issue, unable to query for records that should be there

To: user@cassandra.apache.org Subject: RE: Secondary index issue, unable to query for records that should be there Note that I had identical behavior using a fresh download of Cassandra 1.0.2 as of today. Thanks, -nate From: Nate Sammons [mailto:nsamm...@ften.com]mailto:[mailto:nsamm

Re: Secondary index issue, unable to query for records that should be there

Nate, is this all against a single Cassandra server, or do you have a ring setup? If you do have a ring setup, what is your replicationfactor set to? Also what ConsistencyLevel are you writing with when storing the values? -R On Mon, Nov 7, 2011 at 2:43 PM, Nate Sammons nsamm...@ften.com wrote:

Re: Secondary index update issue

as LongType domain as utf8. When I upload data using above mentioned index type on CF definition then, above queries are working sucessfully. Why? Regards, Thamizhannal P --- On Wed, 7/9/11, Jonathan Ellis jbel...@gmail.com wrote: From: Jonathan Ellis jbel...@gmail.com Subject: Re: Secondary

Re: Secondary index update issue

My guess would be you're querying using a different encoding and there really is no data for your query as given. Hard to say without more details. On Wed, Sep 7, 2011 at 8:13 AM, Thamizh tceg...@yahoo.co.in wrote: Hi All, I have created KS CF using cassandra-0.7.8 and inserted some rows

Re: Secondary index update issue

, Thamizhannal P --- On Wed, 7/9/11, Jonathan Ellis jbel...@gmail.com wrote: From: Jonathan Ellis jbel...@gmail.com Subject: Re: Secondary index update issue To: user@cassandra.apache.org Date: Wednesday, 7 September, 2011, 7:29 PM My guess would be you're querying using a different encoding

Re: Secondary index on composite columns?

Hi Jonathan, AFAIK, you might change the internal implementation of super column family by using the composite column. Does this mean that maybe the secondary index will be supported on super columns in the future? will you use composite column to add more capability to super column family or we

Re: Secondary index on composite columns?

To the best of my ability to predict the future, we would probably enhance native composite columns with those features, but not expose them in the old supercolumn API. So again, if supercolumns work for you, we won't pull the rug out from under you, but don't start using them expecting them to

Re: Secondary index on composite columns?

Sure, but it's still only useful for equality predicates. On Sun, Jul 31, 2011 at 8:50 PM, Boris Yen yulin...@gmail.com wrote: Hi, I was wondering if anyone would know if secondary index can be enabled on composite columns? Regards Boris -- Jonathan Ellis Project Chair, Apache Cassandra

Re: Secondary Index doesn't work with LOCAL_QUORUM

Sounds like https://issues.apache.org/jira/browse/CASSANDRA-2870 to me. You can disable the dynamic snitch as a workaround, or use a different consistencylevel. On Mon, Jul 11, 2011 at 11:38 AM, Hefeng Yuan hfy...@rhapsody.com wrote: Hi, We're using Cassandra with 2 DC - one OLTP Cassandra, 6

Re: secondary index performance

On Jul 3, 2011, at 4:29 PM, Jeremy Hanna wrote: Anyone know if secondary index performance should be in the 100-500 ms range. That's what we're seeing right now when doing lookups on a single value. We've increased keys_cached and rows_cached to 100% for that column family and assume

Re: secondary index performance

On Sun, Jul 3, 2011 at 5:12 PM, Jeremy Hanna jeremy.hanna1...@gmail.com wrote: Trying some other stuff with tools mentioned here: http://spyced.blogspot.com/2010/01/linux-performance-basics.html but not seeing anything particularly disk bound, though await (from iostat -x) seems high on one

Re: Secondary Index keeping track of column names

You could simulate it thoug. Just Add some Meta Column with a boolean Value indicating if the referred Column is in the Row or Not. Then Add an Index in that Meta Column and query for it. I. E. Row a: (c=1234),(has_c=Yes) Quert : List cf where has_c=Yes Am 06.04.2011 um 18:52 schrieb

Re: Secondary Index Updates Break CLI and Client Code Reading :: DebugLog Attached

Addressed on the issue you created, https://issues.apache.org/jira/browse/CASSANDRA-2436. On Thu, Apr 7, 2011 at 12:19 PM, Fryar, Dexter dexter.fr...@hp.com wrote: I have also attached the debug log with each step attached. I've even tried going back and updating the CF with the old index to

Re: Secondary Index keeping track of column names

No, 0.7 indexes handle equality queries; you're basically asking for a IS NOT NULL query. On Wed, Apr 6, 2011 at 11:23 AM, Jeremiah Jordan jeremiah.jor...@morningstar.com wrote:        In 0.7.X is there a way to have an automatic secondary index which keeps track of what keys contain a certain

Re: Secondary Index not working?

https://issues.apache.org/jira/browse/CASSANDRA-2244 On Thu, Mar 10, 2011 at 9:28 PM, Rommel Garcia groups.no...@gmail.com wrote: I tried the tutorial on this site - http://www.datastax.com/docs/0.7/data_model/secondary_indexes and worked on creating an index on a new column. That went good.

Re: Secondary index - keys only.

No. On Sun, Feb 13, 2011 at 8:48 AM, Shay Assulin sh...@il.ibm.com wrote: HI, Is there a way to get only the keys of indexed rows (without getting columns) using get_indexed_slices method? I am using Hector to access Cassandra and I want to count rows with a specific index - so i need to

Re: Secondary Index information

http://www.datastax.com/blog/whats-new-cassandra-07-secondary-indexes On Fri, Jan 28, 2011 at 7:15 AM, Sasha Dolgy sasha.do...@gmail.com wrote: Hi there, Where can I find information regarding secondary indexes? Spent the past 2 days looking for some good details.

Re: Secondary Index information

Thank you. So, after reading, I'm still unsure if this feature will afford me a larger benefit when compared to an inverted index solution. Has anyone done a pros / cons ? -sd On Fri, Jan 28, 2011 at 3:22 PM, Jake Luciani jak...@gmail.com wrote:

Re: Secondary Index information

Hi Victor, In my research and playing around with nosql, specifically cassandra, I see the true benefit in defining search requirements and then creating CF's and the hierarchy based on this. So for me, I see quite a bit of simplicity in defining alternate CF's to allow me to efficiently find a

Re: Secondary Index information

batch_mutate doesn't guarantee consistency. each mutation in the batch is guaranteed to be consistent based on your CL, but if it returns an error it means that it couldn't complete all mutations ... but the converse isn't true. it may have successfully completed some mutations. if you get

Re: Secondary index on SuperColumn Family , Casandra 0.7beta2

Thanks Jonathan Nicolas Santini

Re: Secondary index on SuperColumn Family , Casandra 0.7beta2

Created https://issues.apache.org/jira/browse/CASSANDRA-1813 so this doesn't just silently not work. On Thu, Dec 2, 2010 at 5:28 PM, Tyler Hobbs ty...@riptano.com wrote: Unfortunately, super columns families are not yet supported for secondary indexes. - Tyler On Thu, Dec 2, 2010 at 5:22

Re: Secondary index on SuperColumn Family , Casandra 0.7beta2

Unfortunately, super columns families are not yet supported for secondary indexes. - Tyler On Thu, Dec 2, 2010 at 5:22 PM, Nick Santini nick.sant...@kaseya.comwrote: Hi, Im creating a column family and adding some secondary indexes on the column definition for some columns inside my super

Re: Secondary index on SuperColumn Family , Casandra 0.7beta2

I think you will find secondary indexes are not supported for super columns Sent from my iPhone On Dec 3, 2010, at 10:22, Nick Santini nick.sant...@kaseya.com wrote: Hi, Im creating a column family and adding some secondary indexes on the column definition for some columns inside my super

Re: Secondary index on SuperColumn Family , Casandra 0.7beta2

Thanks for the answers, cant wait for the feature to come :-) I guess Im gonna have to provide my own for a while Nicolas Santini Director of Cloud Computing Auckland - New Zealand (64) 09 914 9426 ext 2629 (64) 021 201 3672 On Fri, Dec 3, 2010 at 12:30 PM, Jason Pell jasonmp...@gmail.com

Re: Secondary index query return row should not return?

https://issues.apache.org/jira/browse/CASSANDRA-1745 On Thu, Nov 11, 2010 at 2:49 PM, Jonathan Ellis jbel...@gmail.com wrote: It's working as written, but I think you're right that it makes more sense to fail the expression when the column doesn't exist. On Thu, Nov 11, 2010 at 7:04 AM,

Re: Secondary index query return row should not return?

It's working as written, but I think you're right that it makes more sense to fail the expression when the column doesn't exist. On Thu, Nov 11, 2010 at 7:04 AM, Ching-Cheng Chen cc...@evidentsoftware.com wrote: Not sure if this the intended behavior of the indexed query. I created a column

Re: Secondary Index Null Pointer Error

Pulled trunk r999443 and applied https://issues.apache.org/jira/browse/CASSANDRA-1415 using jira-apply. Built and ran code that used to fail and now it works. Thanks. CB On Fri, Sep 17, 2010 at 9:49 AM, Jonathan Ellis jbel...@gmail.com wrote: Indexed columns don't have to exist. Try this