3.11.3
We probably need to release 3.11.3 at some point soon because there's some pretty major bug fixes in there and interest has been expressed multiple times now for a release. Currently the only tickets marked for 3.11.3 that aren't complete are: https://issues.apache.org/jira/browse/CASSANDRA-14355 - No work has started on this yet. https://issues.apache.org/jira/browse/CASSANDRA-13929 - A lot of work has been done here... just need a final review However we've got quite a few tickets with patches that should probably be considered - can't say all are necessary to get into 3.11.3 but seeing as they all have patch available and have been around : for a while they are worth considering for anyone who could kindly review: https://issues.apache.org/jira/browse/CASSANDRA-14242 - Inconsistent indexing on static columns :(. needs review https://issues.apache.org/jira/browse/CASSANDRA-14415 - performance regression fix for DISTINCT https://issues.apache.org/jira/browse/CASSANDRA-14204 - Straightforward fix for nodetool garbagecollect https://issues.apache.org/jira/browse/CASSANDRA-14167 - Pretty much ready for commit - has been given +1 by Sylvain https://issues.apache.org/jira/browse/CASSANDRA-14099 - Needs only a unit test https://issues.apache.org/jira/browse/CASSANDRA-14085 - performance fix, small patch needs review https://issues.apache.org/jira/browse/CASSANDRA-13935 - Simple fix to CQL output for indexes when dumping schema https://issues.apache.org/jira/browse/CASSANDRA-13917 - Needs review, fix for compact storage inserts. https://issues.apache.org/jira/browse/CASSANDRA-13843 - Needs review. Small debian packaging fix for heapdump location. https://issues.apache.org/jira/browse/CASSANDRA-13834 - Needs an "official" reviewer and probably a test. https://issues.apache.org/jira/browse/CASSANDRA-13618 - Can likely be committed. Jeff has already done all the work for it just need to verify tests. https://issues.apache.org/jira/browse/CASSANDRA-11479 - Waiting for review for quite a long time.. unit test fix but seems to include changes to the server Handy JQL: project = CASSANDRA AND ((fixVersion = 3.11.x and status = "Patch Available" ) OR (fixVersion = 3.11.3 AND status != Resolved)) and Type = Bug
Re: 3.11.3
wrt releasing 3.11, +1 to this ... and additionally, 3.0 and 2.2. I'd propose we cut early next week (Monday) and anything that can get reviewed/committed from Kurt's list would be great. On Wed, Jun 6, 2018 at 5:22 AM, kurt greaves wrote: > We probably need to release 3.11.3 at some point soon because there's some > pretty major bug fixes in there and interest has been expressed multiple > times now for a release. > > Currently the only tickets marked for 3.11.3 that aren't complete are: > https://issues.apache.org/jira/browse/CASSANDRA-14355 - No work has > started > on this yet. > https://issues.apache.org/jira/browse/CASSANDRA-13929 - A lot of work has > been done here... just need a final review > > However we've got quite a few tickets with patches that should probably be > considered - can't say all are necessary to get into 3.11.3 but seeing as > they all have patch available and have been around : > for a while they are worth considering for anyone who could kindly review: > https://issues.apache.org/jira/browse/CASSANDRA-14242 - Inconsistent > indexing on static columns :(. needs review > https://issues.apache.org/jira/browse/CASSANDRA-14415 - performance > regression fix for DISTINCT > https://issues.apache.org/jira/browse/CASSANDRA-14204 - Straightforward > fix > for nodetool garbagecollect > https://issues.apache.org/jira/browse/CASSANDRA-14167 - Pretty much ready > for commit - has been given +1 by Sylvain > https://issues.apache.org/jira/browse/CASSANDRA-14099 - Needs only a unit > test > https://issues.apache.org/jira/browse/CASSANDRA-14085 - performance fix, > small patch needs review > https://issues.apache.org/jira/browse/CASSANDRA-13935 - Simple fix to CQL > output for indexes when dumping schema > https://issues.apache.org/jira/browse/CASSANDRA-13917 - Needs review, fix > for compact storage inserts. > https://issues.apache.org/jira/browse/CASSANDRA-13843 - Needs review. > Small > debian packaging fix for heapdump location. > https://issues.apache.org/jira/browse/CASSANDRA-13834 - Needs an > "official" > reviewer and probably a test. > https://issues.apache.org/jira/browse/CASSANDRA-13618 - Can likely be > committed. Jeff has already done all the work for it just need to verify > tests. > https://issues.apache.org/jira/browse/CASSANDRA-11479 - Waiting for review > for quite a long time.. unit test fix but seems to include changes to the > server > > Handy JQL: > project = CASSANDRA AND ((fixVersion = 3.11.x and status = "Patch > Available" ) OR (fixVersion = 3.11.3 AND status != Resolved)) and Type = > Bug >
Re: 3.11.3
+1 for all the active branches. It will also be a good chance to review the release doc addition Mick so graciously wrote up. https://github.com/apache/cassandra/pull/230 -- Michael On 06/06/2018 07:30 AM, Jason Brown wrote: wrt releasing 3.11, +1 to this ... and additionally, 3.0 and 2.2. I'd propose we cut early next week (Monday) and anything that can get reviewed/committed from Kurt's list would be great. On Wed, Jun 6, 2018 at 5:22 AM, kurt greaves wrote: We probably need to release 3.11.3 at some point soon because there's some pretty major bug fixes in there and interest has been expressed multiple times now for a release. Currently the only tickets marked for 3.11.3 that aren't complete are: https://issues.apache.org/jira/browse/CASSANDRA-14355 - No work has started on this yet. https://issues.apache.org/jira/browse/CASSANDRA-13929 - A lot of work has been done here... just need a final review However we've got quite a few tickets with patches that should probably be considered - can't say all are necessary to get into 3.11.3 but seeing as they all have patch available and have been around : for a while they are worth considering for anyone who could kindly review: https://issues.apache.org/jira/browse/CASSANDRA-14242 - Inconsistent indexing on static columns :(. needs review https://issues.apache.org/jira/browse/CASSANDRA-14415 - performance regression fix for DISTINCT https://issues.apache.org/jira/browse/CASSANDRA-14204 - Straightforward fix for nodetool garbagecollect https://issues.apache.org/jira/browse/CASSANDRA-14167 - Pretty much ready for commit - has been given +1 by Sylvain https://issues.apache.org/jira/browse/CASSANDRA-14099 - Needs only a unit test https://issues.apache.org/jira/browse/CASSANDRA-14085 - performance fix, small patch needs review https://issues.apache.org/jira/browse/CASSANDRA-13935 - Simple fix to CQL output for indexes when dumping schema https://issues.apache.org/jira/browse/CASSANDRA-13917 - Needs review, fix for compact storage inserts. https://issues.apache.org/jira/browse/CASSANDRA-13843 - Needs review. Small debian packaging fix for heapdump location. https://issues.apache.org/jira/browse/CASSANDRA-13834 - Needs an "official" reviewer and probably a test. https://issues.apache.org/jira/browse/CASSANDRA-13618 - Can likely be committed. Jeff has already done all the work for it just need to verify tests. https://issues.apache.org/jira/browse/CASSANDRA-11479 - Waiting for review for quite a long time.. unit test fix but seems to include changes to the server Handy JQL: project = CASSANDRA AND ((fixVersion = 3.11.x and status = "Patch Available" ) OR (fixVersion = 3.11.3 AND status != Resolved)) and Type = Bug - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: TWCS - Disabling Tombstone Compactions for TWCS
That's helpful background, thanks Lerh! It does seem intentional. I'd suggest that this violates principal of least surprise (unset defaults should have the same effect as setting same to default values), and should be worth calling out as a separate option for both DTCS and TWCS. On Mon, Jun 4, 2018 at 6:02 PM Lerh Chuan Low wrote: > Hi Eric, > > I think it has something to do with the same reason it is disabled in DTCS: > https://issues.apache.org/jira/browse/CASSANDRA-9234 can shed more light. > > > > On 5 June 2018 at 09:02, Eric Stevens wrote: > > > I'm trying to understand the reasoning behind this stanza in Time > Windowed > > Compaction Strategy's init: > > https://github.com/apache/cassandra/blob/cassandra-3.0. > > 15/src/java/org/apache/cassandra/db/compaction/ > > TimeWindowCompactionStrategy.java#L63-L69 > > > > Reposted (and slightly reformatted) here for convenience: > > if ( > > > > !options.containsKey(AbstractCompactionStrategy. > > TOMBSTONE_COMPACTION_INTERVAL_OPTION) > > && > > > > !options.containsKey(AbstractCompactionStrategy. > > TOMBSTONE_THRESHOLD_OPTION) > > ) > > { > > disableTombstoneCompactions = true; > > logger.debug("Disabling tombstone compactions for TWCS"); > > } > > else > > logger.debug("Enabling tombstone compactions for TWCS"); > > > > If you have left both tombstone compaction interval, and tombstone > > threshold at default values, you are *opting out* of tombstone > compactions? > > > > This was certainly a surprising side effect to us, as we expected unset > > values to have the same exact effect as setting those values to their > > defaults. > > > > I'm wondering if someone can shed some more light on this, or if this > > should be considered a bug (it seems really intentional). > > >
FINAL REMINDER: Apache EU Roadshow 2018 in Berlin next week!
Hello Apache Supporters and Enthusiasts This is a final reminder that our Apache EU Roadshow will be held in Berlin next week on 13th and 14th June 2018. We will have 28 different sessions running over 2 days that cover some great topics. So if you are interested in Microservices, Internet of Things (IoT), Cloud, Apache Tomcat or Apache Http Server then we have something for you. https://foss-backstage.de/sessions/apache-roadshow We will be co-located with FOSS Backstage, so if you are interested in topics such as incubator, the Apache Way, open source governance, legal, trademarks or simply open source communities then there will be something there for you too. You can attend any of talks, presentations and workshops from the Apache EU Roadshow or FOSS Backstage. You can find details of the combined Apache EU Roadshow and FOSS Backstage conference schedule below: https://foss-backstage.de/schedule?day=2018-06-13 Ticket prices go up on 8th June 2018 and we have a last minute discount code that anyone can use before the deadline: 15% discount code: ASF15_discount valid until June 7, 23:55 CET You can register at the following link: https://foss-backstage.de/tickets Our Apache booth and lounge will be open from 11th - 14th June for meetups, hacking or to simply relax between sessions. And we will be posting regular updates on social media throughout next week so please follow us on Twitter @ApacheCon Thank you for your continued support and we look forward to seeing you in Berlin! Thanks Sharan Foga, VP Apache Community Development http://apachecon.com/ PLEASE NOTE: You are receiving this message because you are subscribed to a user@ or dev@ list of one or more Apache Software Foundation projects. - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: TWCS - Disabling Tombstone Compactions for TWCS
Hi Eric, Np, I was curious as to why it did that as well. As it turns out, there's actually a JIRA where it has taken another person by surprise: https://issues.apache.org/jira/browse/CASSANDRA-14496. You could maybe bump it too :) On 7 June 2018 at 03:39, Eric Stevens wrote: > That's helpful background, thanks Lerh! It does seem intentional. > > I'd suggest that this violates principal of least surprise (unset defaults > should have the same effect as setting same to default values), and should > be worth calling out as a separate option for both DTCS and TWCS. > > On Mon, Jun 4, 2018 at 6:02 PM Lerh Chuan Low > wrote: > > > Hi Eric, > > > > I think it has something to do with the same reason it is disabled in > DTCS: > > https://issues.apache.org/jira/browse/CASSANDRA-9234 can shed more > light. > > > > > > > > On 5 June 2018 at 09:02, Eric Stevens wrote: > > > > > I'm trying to understand the reasoning behind this stanza in Time > > Windowed > > > Compaction Strategy's init: > > > https://github.com/apache/cassandra/blob/cassandra-3.0. > > > 15/src/java/org/apache/cassandra/db/compaction/ > > > TimeWindowCompactionStrategy.java#L63-L69 > > > > > > Reposted (and slightly reformatted) here for convenience: > > > if ( > > > > > > !options.containsKey(AbstractCompactionStrategy. > > > TOMBSTONE_COMPACTION_INTERVAL_OPTION) > > > && > > > > > > !options.containsKey(AbstractCompactionStrategy. > > > TOMBSTONE_THRESHOLD_OPTION) > > > ) > > > { > > > disableTombstoneCompactions = true; > > > logger.debug("Disabling tombstone compactions for TWCS"); > > > } > > > else > > > logger.debug("Enabling tombstone compactions for TWCS"); > > > > > > If you have left both tombstone compaction interval, and tombstone > > > threshold at default values, you are *opting out* of tombstone > > compactions? > > > > > > This was certainly a surprising side effect to us, as we expected unset > > > values to have the same exact effect as setting those values to their > > > defaults. > > > > > > I'm wondering if someone can shed some more light on this, or if this > > > should be considered a bug (it seems really intentional). > > > > > >
Re: 3.11.3
Oh yeah forgot about those branches, but yes definitely +1 to those. On 6 June 2018 at 14:55, Michael Shuler wrote: > +1 for all the active branches. It will also be a good chance to review > the release doc addition Mick so graciously wrote up. > https://github.com/apache/cassandra/pull/230 > > -- > Michael > > > On 06/06/2018 07:30 AM, Jason Brown wrote: > >> wrt releasing 3.11, +1 to this ... and additionally, 3.0 and 2.2. >> >> I'd propose we cut early next week (Monday) and anything that can get >> reviewed/committed from Kurt's list would be great. >> >> On Wed, Jun 6, 2018 at 5:22 AM, kurt greaves >> wrote: >> >> We probably need to release 3.11.3 at some point soon because there's some >>> pretty major bug fixes in there and interest has been expressed multiple >>> times now for a release. >>> >>> Currently the only tickets marked for 3.11.3 that aren't complete are: >>> https://issues.apache.org/jira/browse/CASSANDRA-14355 - No work has >>> started >>> on this yet. >>> https://issues.apache.org/jira/browse/CASSANDRA-13929 - A lot of work >>> has >>> been done here... just need a final review >>> >>> However we've got quite a few tickets with patches that should probably >>> be >>> considered - can't say all are necessary to get into 3.11.3 but seeing as >>> they all have patch available and have been around : >>> for a while they are worth considering for anyone who could kindly >>> review: >>> https://issues.apache.org/jira/browse/CASSANDRA-14242 - Inconsistent >>> indexing on static columns :(. needs review >>> https://issues.apache.org/jira/browse/CASSANDRA-14415 - performance >>> regression fix for DISTINCT >>> https://issues.apache.org/jira/browse/CASSANDRA-14204 - Straightforward >>> fix >>> for nodetool garbagecollect >>> https://issues.apache.org/jira/browse/CASSANDRA-14167 - Pretty much >>> ready >>> for commit - has been given +1 by Sylvain >>> https://issues.apache.org/jira/browse/CASSANDRA-14099 - Needs only a >>> unit >>> test >>> https://issues.apache.org/jira/browse/CASSANDRA-14085 - performance fix, >>> small patch needs review >>> https://issues.apache.org/jira/browse/CASSANDRA-13935 - Simple fix to >>> CQL >>> output for indexes when dumping schema >>> https://issues.apache.org/jira/browse/CASSANDRA-13917 - Needs review, >>> fix >>> for compact storage inserts. >>> https://issues.apache.org/jira/browse/CASSANDRA-13843 - Needs review. >>> Small >>> debian packaging fix for heapdump location. >>> https://issues.apache.org/jira/browse/CASSANDRA-13834 - Needs an >>> "official" >>> reviewer and probably a test. >>> https://issues.apache.org/jira/browse/CASSANDRA-13618 - Can likely be >>> committed. Jeff has already done all the work for it just need to verify >>> tests. >>> https://issues.apache.org/jira/browse/CASSANDRA-11479 - Waiting for >>> review >>> for quite a long time.. unit test fix but seems to include changes to the >>> server >>> >>> Handy JQL: >>> project = CASSANDRA AND ((fixVersion = 3.11.x and status = "Patch >>> Available" ) OR (fixVersion = 3.11.3 AND status != Resolved)) and Type = >>> Bug >>> >>> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
3.11 currently not building
Hi guys, I saw your message on IRC Jason, Kurt forwarded it to me. Thanks for the heads up! 3.11 presently doesn't build, I think it may have been due to an accidental merge gone bad. The original JIRA https://issues.apache.org/jira/browse/CASSANDRA-13698 has been updated with a patch and the tests are running (runs locally for me as well), do please have a look when possible, thanks! Lerh