3.10 fixver, CHANGES.txt, and the cassandra-3.11 branch

Sam and I fixed up CHANGES.txt and fix versions in JIRA that had 3.11. Since 3.10 has not been released yet,and the cassandra-3.11 branch was created from the 3.10-tentative tag for fixed on top of 3.10, the cassandra-3.11 branch will be used for the 3.10 release, as well as for fixed bugs on top

Re: PgConf US 2017

Hi Josh, What kind of cross pollination are you hoping to see? What would the PG community be interested in hearing about Cassandra? On Mon, Nov 28, 2016 at 11:01 AM, Joshua D. Drake wrote: > Hello folks, > > This is the last week of the PGConf US 2017 CFP. It would be great to see > some inte

Streaming and MVs

I don't know where else to discuss this issue, so I post it here. I am trying to get CS to run stable with MVs since the beginning of july. Normal reads + write do work as expected but when it comes to repairs or bootstrapping it still feels far far away from what I would call fast and stable. The

Re: CASSANDRA-8596

One of the problem is that we have to deal with a huge number of tickets. We could let them open forever or close the ones that we think are not real problems or that we know we will never have time to do. CASSANDRA-8954 has been opened for a year before Aleksey closed it. When those things happen

Re: CASSANDRA-8596

On Tue, 29 Nov 2016 03:55:15 -0500 Benjamin Lerer 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 Cassand

Re: CASSANDRA-8596

Hi guys, thanks for answer! Actually the last activity on this ticket was my question Does this issue exist with other snitches? How can they benefit from my solution? Also before working on ticked or prepare patch it's good to know if it's needed at all. ;-) Look at https://issues.apac

Re: CASSANDRA-8596

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 wrote: > Hey Vladimir > > Always nice to see patches, and

Re: CASSANDRA-8596

I would recommend several things that could help this (and probably many other patches that accidentally went under radar) to get accepted. It's hard to keep an enormous amount of issues in memory, so we try to rely on simple rules that help everyone to see current status and understand what to do

Re: CASSANDRA-8596

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 th

CASSANDRA-8596

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