and have been running it for
>> a bit over a week. Works well, would love to see it get into trunk/0.7
>> proper.
>>
>>
>>
>> From: Ryan Daum [mailto:r...@thimbleware.com]
>> Sent: Wednesday, March 31, 2010 11:49 AM
>> To: user@cassandra.apache.org
>
nk/0.7
> proper.
>
>
>
> *From:* Ryan Daum [mailto:r...@thimbleware.com]
> *Sent:* Wednesday, March 31, 2010 11:49 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: expiring data out of Cassandra/time to live
>
>
>
> I was able to successfully merge this patch into
Thanks a lot Jonathan and everyone else that replied to my thread. This
looks like it will do what I need. I have a colleague that is a Java
wizard and will probably have no problem putting this patch into place
for our production builds.
I'm a C/C++ programmer at heart so the code itself does
out of Cassandra/time to live
I was able to successfully merge this patch into the 0.6 branch a few weeks ago
by doing the following:
* Downloading the patch
* Checking out the trunk of Cassandra from github
* Rolling back (checking out) the git repo to the same date that the patch
I was able to successfully merge this patch into the 0.6 branch a few weeks
ago by doing the following:
- Downloading the patch
- Checking out the trunk of Cassandra from github
- Rolling back (checking out) the git repo to the same date that the
patch was submitted to Jira
- Apply
Sounds like you want to follow
https://issues.apache.org/jira/browse/CASSANDRA-699. There is a patch
there but I wouldn't recommend merging it if Java scares you. :)
On Wed, Mar 31, 2010 at 1:39 PM, Mike Gallamore
wrote:
> Hello everyone,
>
> I saw a thread on the incubator user chat that starte
