Just wanted to let people who follow the user list know that if there is
interest in something like plugins, triggers, or coprocessors on the
server-side with Cassandra, the ticket to follow or get involved with (code,
comments, etc) is CASSANDRA-1311:
https://issues.apache.org/jira/browse/CASSA
So from here I guess it's a matter of working out the comments/concerns
presented on 1311 and any future discussion sounds like it belongs there.
Like I said, I just wanted to initiate discussion since it had been a while and
the dust from 0.7 had settled. It seems like an incredibly useful con
As the dude that worked on the 1016 prototype, I agree with this.
On Fri, Feb 11, 2011 at 10:53 AM, Stu Hood wrote:
> Honestly, I think we should just mark 1016 a dupe and move forward with
> 1311: we won't be hurting anyone's feelings, and the implementation from
> 1016 is: 1. much, much less co
Honestly, I think we should just mark 1016 a dupe and move forward with
1311: we won't be hurting anyone's feelings, and the implementation from
1016 is: 1. much, much less complete, 2. abandoned.
On Fri, Feb 11, 2011 at 9:23 AM, Jeremy Hanna wrote:
> Thanks Maxim - I'll just go ahead and BCC yo
Thanks Maxim - I'll just go ahead and BCC you and Hentschel and move the
discussion to the dev list.
Based on the comments on 1311 - did you have anything else to add to that -
could we unify around 1016 or 1311 and work on getting that to a general state
of acceptance? Were there any that wer
