---- On Tue, 29 Nov 2016 03:55:15 -0500 Benjamin Lerer <benjamin.le...@datastax.com> wrote ----
>It also seems that the ticket has never been marked as patch available Yes, as it still was under discussion that never was finished. Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting ---- On Tue, 29 Nov 2016 03:55:15 -0500 Benjamin Lerer <benjamin.le...@datastax.com> wrote ---- Hi Vladimir, It also seems that the ticket has never been marked as patch available and that you did not assign yourself to it. Most of us look at those to determine in which state is a ticket. On Tue, Nov 29, 2016 at 9:42 AM, Jeff Jirsa <jji...@gmail.com> wrote: > Hey Vladimir > > Always nice to see patches, and pinging this list is a good way to draw > attention to them if they go idle > > Looks like it stalled because Brandon recommended two changes and you > addressed one but not the other - Brandon may have more feedback, he's very > familiar with that part of the codebase. > > These days, it'd also be nice to see a unit test (or dtest) to demonstrate > that the patch corrects the issue properly - that not only proves > correctness, but better protects us in the future in case someone tries to > alter the schema of system.peers in an incompatible way. > > > > -- > Jeff Jirsa > > > > On Nov 29, 2016, at 12:19 AM, Vladimir Yudovin <vla...@winguzone.com> > wrote: > > > > Hi, > > > > > > > > in the light of broader community involvement I would like to bring > attentions to the https://issues.apache.org/jira/browse/CASSANDRA-8596 I > open with proposed patch. > > > > It's stuck for almost 1.5 years. > > > > > > > > I would like to help with Cassandra development and improvement, and I > have several other fixes, some has JIRA, some not. > > > > > > > > Best regards, Vladimir Yudovin, > > > > Winguzone - Cloud Cassandra Hosting > > > > > > > > > > >
