Click on Submit Patch then it should get noticed as the committers go through
the patch list. And / Or update the comments to get it back into the activity
stream
If you need a hand with updating the 0.8 patch let me know.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@a
On Apr 27, 2011, at 16:59, Timo Nentwig wrote:
> On Apr 27, 2011, at 16:52, Edward Capriolo wrote:
>
>> The method being private is not a deal-breaker.While not good software
>> engineering practice you can copy and paste the code and renamed the
>> class SSTable2MyJson or whatever.
>
> Sure I
On Apr 27, 2011, at 17:10, Edward Capriolo wrote:
> I would think most people who watch dev watch this list.
>
> http://wiki.apache.org/cassandra/HowToContribute
So, here it is: https://issues.apache.org/jira/browse/CASSANDRA-2582
On Wed, Apr 27, 2011 at 10:59 AM, Timo Nentwig wrote:
>
> On Apr 27, 2011, at 16:52, Edward Capriolo wrote:
>
>> The method being private is not a deal-breaker.While not good software
>> engineering practice you can copy and paste the code and renamed the
>> class SSTable2MyJson or whatever.
>
> S
On Apr 27, 2011, at 16:52, Edward Capriolo wrote:
> The method being private is not a deal-breaker.While not good software
> engineering practice you can copy and paste the code and renamed the
> class SSTable2MyJson or whatever.
Sure I can do this but I'd like to have it just available in the d
On Wed, Apr 27, 2011 at 10:16 AM, Timo Nentwig wrote:
>
> On Apr 27, 2011, at 15:58, Edward Capriolo wrote:
>
>> Hacking a separate copy of SSTable2json is trivial. Just look for the
>> section of the code that writes the data and change what it writes. If
>
> I did. The method's private...
>
>> y
On Apr 27, 2011, at 15:58, Edward Capriolo wrote:
> Hacking a separate copy of SSTable2json is trivial. Just look for the
> section of the code that writes the data and change what it writes. If
I did. The method's private...
> you can make it a knob --nottl then it could be included in Cassand
On Wed, Apr 27, 2011 at 9:40 AM, Timo Nentwig wrote:
> Hi!
>
> What about a simple option for sstable2json to not print out expiration
> TTL+LocalDeletionTime (maybe even ignore isMarkedForDelete)? I want to move
> old data from a live cluster (with TTL) to an archive cluster (->data does
> not
Hi!
What about a simple option for sstable2json to not print out expiration
TTL+LocalDeletionTime (maybe even ignore isMarkedForDelete)? I want to move old
data from a live cluster (with TTL) to an archive cluster (->data does not
expire there).
BTW is there a smarter way to do this? Actually
