Re: Java examples for 0.7

Thanks I found the example https://github.com/zznate/hector-examples/blob/master/src/main/java/com/riptano/cassandra/hector/example/GetIndexedSlices.java Lohit 2011/4/1

Re: Java examples for 0.7

Thanks. This was very helpful. I could not find any for examples for query on secondary index. Could you point me to some piece of code I could look at. 2011/4/10 Steven Yen-Liang Su > > > https://github.com/zznate/hector-examples/tree/master/src/main/java/com/riptano/cassandra/hector/example >

Re: Java examples for 0.7

https://github.com/zznate/hector-examples/tree/master/src/main/java/com/riptano/cassandra/hector/example Sincerely Yen-Liang Su http://about.me/xpsteven 2011/4/11 lohit > Hi, > > Is there any java examples for insert/scan for version 0.7. Anythi

Java examples for 0.7

Hi, Is there any java examples for insert/scan for version 0.7. Anything I can find in sources? -- Have a Nice Day! Lohit

Re: Columns values(integer) need frequent updates/ increments

The row index is an index of the columns stored in a particular row: it is only written when a row gets larger than column_index_size_in_kb (see your config file). The sstable index is currently an index of the keys stored in an sstable, but #2319 proposes to merge the sstable and row indexes. On

Re: CLI does not list data after upgrading to 0.7.4

put in an assumption first, so from cassandra-cli, do: assume aCF KEYS as lexicaluuid; then do your list On Sun, Apr 10, 2011 at 10:03 PM, Wenjun Che wrote: > > It is happening on clean 0.7.4 server as well.  Here is how to reproduce: > > 1. create a CF with UUID as row key > 2. add some data >

Re: CLI does not list data after upgrading to 0.7.4

It is happening on clean 0.7.4 server as well. Here is how to reproduce: 1. create a CF with UUID as row key 2. add some data 3. list CF always returns "Input length = 1" I figured out one way to fix this: run 'assume CF keys as lexicaluuid;". This issue does not happen to CLI of 0.7.0 or earli

Re: Columns values(integer) need frequent updates/ increments

What's the difference between a row index and sstable index? -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Columns-values-integer-need-frequent-updates-increments-tp6251464p6259882.html Sent from the cassandra-u...@incubator.apache.org mailing l

Re: unrepairable sstable data rows

The WARN messages are the "emergency pressure valve" kicking in, search for that test in conf/cassandra.yaml. These are settings to reduce the chance of going OOM. It means you should take a look at your memtable and cache settings as you are getting close to running out of memory. Jonathan or

Re: Atomicity Strategies

A Strategy that should Cover at least some use Cases is roughly like this: Given cf A and B should Be in Sync In write 'a' to cf A Add another Column 'Synchronisation_token' and Write a tuuid 'T' (or a timestamp or some Otter Value that Allows (Time based) ordering) As its value. On the related

Re: Reg : unsubscribe

>           Please unsubscribe my email address from user list . http://wiki.apache.org/cassandra/FAQ#unsubscribe -- / Peter Schuller

Reg : unsubscribe

Hi Team , Please unsubscribe my email address from user list . -- Regards, Heerachand G A

Re: Site Not Surviving a Single Cassandra Node Crash

Not sure about that Hector Version, but there was a Hector Bug that Hector did Not stop using a Dead Node As Proxy and that it did not do proper Load balancing in the requests. If you enable trace Logs for Hector you can See which nodes it uses for requests. If there is a newer 0.6 Hector you sh

Re: Columns values(integer) need frequent updates/ increments

It doesn't. It collects the row on each sstables and then merge all the columns of each snapshot of that row, dropping the deleted ones and solving using the timestamp the ones with conflicts Sent from my iPhone On 09/04/2011, at 21:52, mcasandra wrote: > That I understand but my basic quesiton

unrepairable sstable data rows

It appears we have several unserializable or unreadable rows. These were not fixed even after doing a "scrub" on all nodes - even though the scrub seemed to have completed successfully. I trying to fix these by doing a "repair", but these exceptions are thrown exactly when doing a repair.

Re: Heads up: restarting a node with autobootstrap=true after nodetool move will re-bootstrap the node in 0.7.0-0.7.4

> What is de-seeding and why would it cause this problem? Relation of seeding > and auto_bootstrap always confuses me. If and when you have time can you > please explain it to me. I was ad-hoc inventing the term 'de-seeding' to mean reconfiguring all others nodes to not use the node as a seed. And

Re: Flush / Snapshot Triggering Full GCs, Leaving Ring

On Apr 7, 2011, at 23:43 , Jonathan Ellis wrote: > The history is that, way back in the early days, we used to max it out > the other way (MTT=128) but observed behavior is that objects that > survive 1 new gen collection are very likely to survive "forever." Just a quick note: my own tests seem