Praveen,
We are certainly interested. To get things moving we implemented an add-on for
Cassandra to demonstrate the viability (using AOP):
https://github.com/hmsonline/cassandra-triggers
Right now the implementation executes triggers asynchronously, allowing you to
implement a java interface a
I found that Triggers are coming in Cassandra 1.2 (
https://issues.apache.org/jira/browse/CASSANDRA-1311) but no mention of any
StoreProc like pattern.
I know this has been discussed so many times but never met with
any initiative. Even Groovy was staged out of the trunk.
Cassandra is great for l
but after repair all nodes should be in sync regardless of whether new
files were compacted or not.
Do you suggest major compaction after repair? I'd like to avoid it.
On 04/22/2012 11:52 AM, Philippe wrote:
Repairs generate new files that then need to be compacted.
Maybe that's where the temp
Repairs generate new files that then need to be compacted.
Maybe that's where the temporary extra volume comes from?
Le 21 avr. 2012 20:43, "Igor" a écrit :
> Hi
>
> I can't understand the repair behavior in my case. I have 12 nodes ring
> (all 1.0.7):
>
> 10.254.237.2LA ADS-LA-1
