epaxos would be nice, it's been about 2 years since it was started, and Blake asked for a first review well over a year ago. the benchmarks and thorough test suite look like a huge improvement over the current situation.
https://issues.apache.org/jira/browse/CASSANDRA-6246 On Fri, Nov 4, 2016 at 3:28 AM Edward Capriolo <edlinuxg...@gmail.com> wrote: > I would like to propose features around seeds: > https://issues.apache.org/jira/browse/CASSANDRA-12627 > > I have other follow up issues like getting seeds from Amazon API, or from > JNDI/ DNS, etc. > > I was hoping 12627 was an easy way to grease the wheels. > > > On Fri, Nov 4, 2016 at 8:39 AM, Jason Brown <jasedbr...@gmail.com> wrote: > > > Hey Nate, > > > > I'd like to add CASSANDRA-11559 (Enhance node representation) to the > list, > > including the comment I made on the ticket (different storage ports for > > each node). For us, it's a great "would really like to have" as our group > > will probably need this in production within the next 1 year or less. > > However since it hasn't gotten much attention, I'm not sure if we should > > add it to the list of "must haves" for 4.0. I'm planning on bringing it > up > > internally today, as well. > > > > Also, from the previous 4.0 email thread that Jonathan started back in > July > > ( > > https://mail-archives.apache.org/mod_mbox/cassandra-dev/ > > 201607.mbox/%3CCALdd-zhW3qJ%3DOWida9nMXPj0JOsru7guOYh6- > > 7uTjqEBvacrgQ%40mail.gmail.com%3E > > ) > > > > - CASSANDRA-11115 (thrift removal) - ticket not mentioned explicitly in > the > > email, but the notion of removing thrift was > > - CASSANDRA-10857 (Allow dropping COMPACT STORAGE flag) > > > > Thanks, > > > > -Jason > > > > On Thu, Nov 3, 2016 at 8:43 PM, sankalp kohli <kohlisank...@gmail.com> > > wrote: > > > > > List looks really good. I will let you know if there is something else > we > > > plan to add to this list. > > > > > > On Thu, Nov 3, 2016 at 7:47 PM, Nate McCall <zznat...@gmail.com> > wrote: > > > > > > > It was brought up recently at the PMC level that our goals as a > > > > project are not terribly clear. > > > > > > > > This is a pretty good point as outside of Jira 'Fix Version' > labelling > > > > (which we actually suck less at compared to a lot of other ASF > > > > projects) this really isnt tracked anywhere outside of general tribal > > > > knowledge about who is working on what. > > > > > > > > I would like to see us change this for two reasons: > > > > - it's important we are clear with our community about where we are > > going > > > > - we need to start working more closely together > > > > > > > > To that end, i've put together a list (in no particular order) of the > > > > *major* features in which I know folks are interested, have patches > > > > coming, are awaiting design review, etc.: > > > > > > > > - CASSANDRA-9425 Immutable node-local schema > > > > - CASSANDRA-10699 Strongly consistent schema alterations > > > > - CASSANDRA-12229 NIO streaming > > > > - CASSANDRA-8457 NIO messaging > > > > - CASSANDRA-12345 Gossip 2.0 > > > > - CASSANDRA-9754 Birch trees > > > > > > > > What did I miss? What else would folks like to see? Specifically, > this > > > > should be "new stuff that could/will break things" given we are > upping > > > > the major version. > > > > > > > > To be clear, it's not my intention to set this in stone and then beat > > > > people about the head with it. More to have it there to point it at a > > > > high level and foster better communication with our users from the > > > > perspective of an open source project. > > > > > > > > Please keep in mind that given everything else going on, I think it's > > > > a fantastic idea to keep this list small and spend some time focusing > > > > on stability particularly as we transition to a new release process. > > > > > > > > -Nate > > > > > > > > > >
