Re: [VOTE] Release Apache Cassandra 3.6

+1 On Wed, May 11, 2016 at 9:51 AM, Aleksey Yeschenko wrote: > +1 > > -- > AY > > On 11 May 2016 at 02:55:10, Jake Luciani (j...@apache.org) wrote: > > I propose the following artifacts for release as 3.6. > > sha1: c17cbe1875a974a00822ffbfad716abde363c8da > Git: > > http://git-wip-us.apache.org

Re: Error running 'ant test'

CassandraIndexTest is intermittently failing on trunk & 3.0 at the moment: http://cassci.datastax.com/view/trunk/job/trunk_utest/1378/testReport/ http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_utest/747/testReport/ On Thu, May 19, 2016 at 3:24 PM, Oleksandr Petrov < oleksandr.pet

Re: [VOTE] Release Apache Cassandra 3.6 (Attempt #2)

+1 On Wed, Jun 1, 2016 at 6:30 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.6. > > sha1: 8d22d9fd1842c59ea65a3793aceb5a78c5852351 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative > Artifacts: > > https://reposi

Re: [VOTE] Release Apache Cassandra 3.0.8

+1 On Fri, Jul 1, 2016 at 4:40 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.0.8. > > sha1: 8b21d9e9e975ea07023ae6ec4c04d997006c1a0a > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.8-tentative > Artifacts: > > https://re

Re: [VOTE] Release Apache Cassandra 2.1.15

+1 On Fri, Jul 1, 2016 at 4:44 PM, Jonathan Ellis wrote: > +1 on the release, but let's get those fixed for next time. > > On Thu, Jun 30, 2016 at 6:02 PM, Dave Brosius > wrote: > > > nits > > > > snappy-java and thrift-server's license files have the wrong version > > numbers. > > > > > > > >

Re: [VOTE] Release Apache Cassandra 2.2.7

+1 On Fri, Jul 1, 2016 at 3:58 PM, Jake Luciani wrote: > I propose the following artifacts for release as 2.2.7. > > sha1: 092054170ec3daf92ec494a0db295037d3563229 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.7-tentative > Artifacts: > > https://re

Re: Failing tests 2016-08-22 [cassandra-3.9]

I've opened https://issues.apache.org/jira/browse/CASSANDRA-12523 for the new flaky failure. Thanks, Sam On Tue, Aug 23, 2016 at 6:44 AM, Joel Knighton wrote: > === > testall:

Re: [VOTE] Release Apache Cassandra 3.0.9

+1 On 15 Sep 2016 19:58, "Jake Luciani" wrote: > I propose the following artifacts for release as 3.0.9. > > sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.9-tentative > Artifacts: > https://repository.

Re: [VOTE] Release Apache Cassandra 3.9

+1 On Mon, Sep 26, 2016 at 4:12 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.9. > > sha1: c1fa21458777b51a9b21795330ed6f298103b436 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.9-tentative > Artifacts: > https://repo

Re: [VOTE] Release Apache Cassandra 3.8

+1 On Mon, Sep 26, 2016 at 3:52 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.8-tentative > Artifacts: > https://repo

Re: [VOTE] Release Apache Cassandra 3.10 (Take 2)

-1 from me too due to #12877. I also agree with Alex's suggestion of reverting #11990 and re-rolling. On Wed, Nov 9, 2016 at 1:20 PM, Oleksandr Petrov wrote: > -1 > > Sorry but I have to -1 that one, with the following explanation > > One of the features in 3.10 breaks SASI in quite a significan

Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

I'll register another (non-binding) -1 due to the failing tests. In particular, CASSANDRA-12651 is due to a legit bug with potential corruption and data loss (albeit in indexes only). The same bug is also the likely cause of CASSANDRA-12590, so it'd be good to include the fix in 3.10. On Mon, Nov

tracing improvements

sues.apache.org/jira/browse/CASSANDRA-13156 Thanks for reading! Regards, Sam [1] https://issues.apache.org/jira/browse/CASSANDRA-9193 Facility to write dynamic code to selectively trigger trace or log for queries [2] https://issues.apache.org/jira/browse/CASSANDRA-11012 Allow tracing CQL of a

Re: [VOTE] Release Apache Cassandra 3.0.13

> > One dtest failed on the standard and "novnode" jobs, which we > have an existing JIRA for, CASSANDRA-13113 The initial dtest failure that 13113 was opened for is not worth blocking the release for IMO. In the comments of that ticket, Alex has identified a more pressing, user facing regression

Re: oracle goldengate to cassandra

s sink. Sam > On Oct 10, 2017, at 4:24 AM, neslişah demirci > wrote: > > Hi all , > > Is there anyone to know how can i configure oracle goldengate for data > streaming to cassandra database ? > > Any comments , links, any help appreciated. > > Kind regards , > Nesli.

Re: Flakey Dtests

ID is ‘sasrira’, and I don’t see an Assign action / button to self-assign. Thanks, Sam > On Nov 15, 2017, at 8:44 PM, Jeff Jirsa wrote: > > In lieu of a weekly wrap-up, here's a pre-Thanksgiving call for help. > > If you haven't been paying attention to JIRA, you likely

Optimizing queries for partition keys

Cassandra devs, We use workflows in some of our clusters (running 3.0.15) that involve "SELECT DISTINCT key FROM..."-style queries. For some tables, we observed extremely poor performance under light load (i.e., a small number of rows per second and frequent timeouts), which we eventually traced

Re: Optimizing queries for partition keys

redicate with a count of 1, to make sure we do have a live column before including the partition key. " By using ColumnFilter.selectionBuilder(); you do not select all the columns. By consequence, some partitions might be returned while they should not. On Thu, Mar 22, 2018 at 6:24 PM

Re: [DISCUSS] Backport CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0

Sorry to derail the discussion but just on a point of order, there is actually precedent for requiring a minimum patch level before a major upgrade. For instance, from NEWS.txt: Upgrade to 3.0 is supported from Cassandra 2.1 versions greater or equal to 2.1.9, or Cassandra 2.2 version

Re: [VOTE] Release test-api 0.0.17

+1 > On 10 Sep 2024, at 15:34, Doug Rohrer wrote: > > Proposing the test build of in-jvm dtest API 0.0.17 for release > > Repository: > https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git > > Candidate SHA: > https://github.com/apache/cassandra-in-jvm-dtest-api/commit/85b538ca

Re: Update: Cassandra Virtual Nodes

comfortable committing 4121, 4122, 4125, 4127, 4123 as a group. > From what I've seen, review should proceed fairly quickly, so > hopefully floating the earlier ones a bit longer won't add much pain. Agreed, that makes sense. -- Sam Overton Acunu | http://www.acunu.com | @acunu

Re: Virtual nodes & order preserving partitioning

rg/jira/browse/CASSANDRA-4445 -- Sam Overton Acunu | http://www.acunu.com | @acunu

Re: Download source release / binary files in source release

I agree with Jeff. The inclusion of binary dependencies to assist developers building from a source release doesn't seem like a deal breaker to me personally as long as these are purely a convenience and not a requirement. That said, the stance of the ASF as recorded in the incubator thread is

Re: [DISCUSS] Releases after 4.0

+1 > On 29 Mar 2021, at 15:41, Joseph Lynch wrote: > > I am slightly concerned about removing support for critical bug fixes > in 3.0 on a short time-frame (<1 year). I know of at least a few major > installations, including ours, who are just now able to finish > upgrades to 3.0 in production d

Re: [VOTE] Release Apache Cassandra 4.0-rc1 (take2)

+1 > On 23 Apr 2021, at 04:19, Jasonstack Zhao Yang > wrote: > > +1 > > On Fri, 23 Apr 2021 at 08:16, Nate McCall wrote: > >> +1 >> >> >> On Thu, Apr 22, 2021 at 6:59 AM Mick Semb Wever wrote: >> >>> Proposing the test build of Cassandra 4.0-rc1 for release. >>> >>> sha1: 3282f5ecf187ec

Re: Obfuscation of passwords in audit loging, in or not in 4.0?

> On 4 Jun 2021, at 03:44, Jonathan Koppenhofer wrote: > > +1 to this being a serious bug. As a large user, if we used internal > passwords, this would completely prevent me from using Cassandra native > audit log capabilities. Disabling DCL is not a great option, as DCL is > probably the most

Re: Additions to Cassandra ecosystem page?

+1 > On 23 Jun 2021, at 22:31, Jeff Jirsa wrote: > > This would be my preference. > > > On Wed, Jun 23, 2021 at 2:22 PM Ben Bromhead wrote: > >> I'm also comfortable with a strict approach where we just list actual >> Apache Cassandra offerings, that also provides good solid clarity to users

Re: [VOTE] Release Apache Cassandra 4.0-rc2

+1 > On 29 Jun 2021, at 05:30, Jeff Jirsa wrote: > > +1 > > >> On Jun 28, 2021, at 9:00 PM, Jeremy Hanna wrote: >> >> +1 (nb) nice to see all of the fixes and the use of newer TLS by default >> and obfuscation of passwords in the audit log for the 4.0 release. >> >>> On Jun 29, 2021, at 6

Re: [DISCUSS] CEP-10: Cluster and Code Simulations

. Thanks, Sam > On 13 Jul 2021, at 09:20, bened...@apache.org wrote: > > Did anyone have any thoughts on this CEP, or shall I bring it forward for a > vote also? > > From: bened...@apache.org > Date: Thursday, 3 June 2021 at 20:19 > To: dev@cassandra.apache.org >

Re: [VOTE] Release Apache Cassandra 4.0.0 (take2)

+1 > On 13 Jul 2021, at 23:13, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.0 for release. > > sha1: 924bf92fab1820942137138c779004acaf834187 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.0-tentative > Maven Artifacts: > https:/

Re: [VOTE] Release Apache Cassandra 4.0.0 (third time is the charm)

+1 > On 22 Jul 2021, at 23:40, Brandon Williams wrote: > > I am proposing the test build of Cassandra 4.0.0 for release. > > sha1: 902b4d31772eaa84f05ffdc1e4f4b7a66d5b17e6 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.0-tentative > Maven Artifacts: > h

Re: [VOTE] Release Apache Cassandra 3.11.11

+1 > On 25 Jul 2021, at 20:06, Brandon Williams wrote: > > I am proposing the test build of Cassandra 3.11.11 for release. > > sha1: 4cafe2288e56e1135d65e76adbcd6c2de9306d6b > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.11-tentative > Maven Artifacts:

Re: [VOTE] Release Apache Cassandra 3.0.25

+1 > On 25 Jul 2021, at 18:40, Brandon Williams wrote: > > I am proposing the test build of Cassandra 3.0.25 for release. > > sha1: 06235e93e16d1f483a3b03ba02f8fb29e33305fa > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.25-tentative > Maven Artifacts: >

Re: [VOTE] CEP-10: Cluster and Code Simulations

+1 > On 26 Jul 2021, at 11:51, bened...@apache.org wrote: > > Proposing the CEP-10 (Cluster and Code Simulations) for adoption > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-10%3A+Cluster+and+Code+Simulations > Discussion: > https://lists.apache.org/thread.html/rc908

Re: [VOTE] CEP-11: Pluggable memtable implementations

+1 > On 19 Aug 2021, at 17:10, Branimir Lambov wrote: > > Hello everyone, > > I am proposing the CEP-11 (Pluggable memtable implementations) for adoption > > Discussion thread: > https://lists.apache.org/thread.html/rb5e950f882196764744c31bc3c13dfbf0603cb9f8bc2f6cfb976d285%40%3Cdev.cassandra.a

Potential issues during 4.0 upgrade

that operators of large clusters hold off on any planned 4.0 upgrades. Thanks, Sam

Re: [VOTE] CEP-14: Paxos Improvements

+1 > On 27 Aug 2021, at 20:48, bened...@apache.org wrote: > > Hi everyone, I’m proposing this CEP for approval. > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements > Discussion: > https://lists.apache.org/thread.html/r1af3da2d875ef93479e3874072ee6

[ANNOUNCE] Apache Cassandra 4.0.1 test artifact available

The test build of Cassandra 4.0.1 is available. sha1: 6709111ed007a54b3e42884853f89cabd38e4316 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1247/org/apache/ca

[VOTE] Release Apache Cassandra 4.0.1

Proposing the test build of Cassandra 4.0.1 for release. sha1: 6709111ed007a54b3e42884853f89cabd38e4316 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1247/org/

Re: [VOTE] Release Apache Cassandra 4.0.1

This vote has passed with 16 +1 votes (10 binding) and no -1 votes. > On 1 Sep 2021, at 12:54, Sam Tunnicliffe wrote: > > Proposing the test build of Cassandra 4.0.1 for release. > > sha1: 6709111ed007a54b3e42884853f89cabd38e4316 > Git: > https://gitbox.apache.org/repos/

[RELEASE] Apache Cassandra 4.0.1 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 4.0.1. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of sourc

[DISCUSS] CASSANDRA-16922 CEP-10: Major Prerequisites (Phase 1)

rtunity to contribute before we start moving this forward. Notwithstanding that, there are some failing tests still to address, mostly due to changes made in trunk since this work was started and subsequently encountered during rebase. Th

Re: [VOTE] CEP-15: General Purpose Transactions

1. +1 2. +1 3. +1 Thanks, Sam > On 14 Oct 2021, at 17:31, bened...@apache.org wrote: > > Hi everyone, > > I would like to start a vote on this CEP, split into three sub-decisions, as > discussion has been circular for some time. > > 1. Do you support adopting this

Re: [VOTE] CEP-17: SSTable format API

+1 > On 15 Nov 2021, at 19:42, Branimir Lambov wrote: > > Hi everyone, > > I would like to start a vote on this CEP. > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-17%3A+SSTable+format+API > > Discussion: > https://lists.apache.org/thread.html/r636bebcab4e678dbee042

Re: [VOTE] Formalizing our CI process

+1 with/without amendment > On 13 Jan 2022, at 05:26, Berenguer Blasi wrote: > > Oh I completely agree with you. I was just trying to explain that > getting to 2/3 failures is a realistic target. > > +1 also on the amendment. > > On 12/1/22 17:39, Joseph Lynch wrote: >> On Wed, Jan 12, 2022 at

Re: [VOTE] CEP-19: Trie memtable implementation

+1 > On 16 Feb 2022, at 08:57, Branimir Lambov wrote: > > Hi everyone, > > I'd like to propose CEP-19 for approval. > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-19%3A+Trie+memtable+implementation > >

Re: Code freeze starts 1st May. Anything to be addressed?

27;m not completely convinced about encoding metadata into host ids, but even if that is something we want to do, I don't think it's wise to completely remove control over the identifiers from Cassandra itself. Thanks, Sam > On 25 Apr 2022, at 16:17, Ekaterina Dimitrova wrote: >

Re: Code freeze starts 1st May. Anything to be addressed?

sers > which normally know what they're doing. We have tons of potentially dangerous > knobs and I don't get why this particular one is any different. > > Em qua., 27 de abr. de 2022 às 14:05, Sam Tunnicliffe <mailto:s...@beobal.com>> escreveu: > CASSANDR

Re: [VOTE] Release Apache Cassandra 3.0.27

+1 > On 7 May 2022, at 07:37, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 3.0.27 for release. > > sha1: 205366131484967a3a8a749f1d1d841c952127e8 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.27-tentative > Maven Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 3.11.13

+1 > On 7 May 2022, at 07:38, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 3.11.13 for release. > > sha1: 836ab2802521a685efe84382cb48db56caf4478d > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.13-tentative > Maven Artifacts: > http

Re: [VOTE] Release Apache Cassandra 4.0.4 (take2)

+1 > On 7 May 2022, at 07:39, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.4 for release. > This is from the (take4) test artifact. > > sha1: 052125f2c6ed308f1473355dfe43470f0da44364 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0

[DISCUSS] CEP-21: Transactional Cluster Metadata

Hi, I'd like to open discussion about this CEP: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21%3A+Transactional+Cluster+Metadata Cluster metadata in Cassandra comprises a number

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

h something(s) > that allow us to externalize some of the complexity of maintaining > consistency. I need to digest the proposal you've made, but I don't see the > two ideas being at odds on my first read. > > Cheers, > > Derek > > On Mon, Aug 22, 2022

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

improving modularity in Cassandra and one of >> the ideas I'm discussing is pluggably (?) replacing gossip with something(s) >> that allow us to externalize some of the complexity of maintaining >> consistency. I need to digest the proposal you've made, but I don&#x

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

Good catch, I'll update the doc. Thanks, Sam > On 24 Aug 2022, at 10:24, Claude Warren, Jr via dev > wrote: > > Should > > (**) It may seem counterintuitive, that A is being written to even after > we've stopped reading from it. This is done in order to g

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

> On 5 Sep 2022, at 22:02, Henrik Ingo wrote: > > Mostly I just wanted to ack that at least someone read the doc (somewhat > superficially sure, but some parts with thought...) > Thanks, it's a lot to digest, so we appreciate that people are working through it. > One pre-feature that we wo

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

log history, just a snapshot plus subsequent entries). > On 6 Sep 2022, at 15:24, Jacek Lewandowski > wrote: > > Hi Sam, this is a great idea and a really well described CEP! > > I have some questions, perhaps they reflect my weak understanding, but maybe > you can a

Re: Shall 4.2 become 5.0 ?

> do we want to drop support in trunk for upgrading from 3.x ? This is a bit premature as it hasn't even gone to a vote yet, but if accepted, CEP-21 might make this something we want to do. https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21:+Transactional+Cluster+Metadata#CEP21:Transac

Re: CEP-21 and complete cluster replacement.

I'm not sure I 100% understand the question, but the things covered in CEP-21 won't enable you to as an operator to bootstrap all your new nodes without fully joining, then perform an atomic CAS to replace the existing members. CEP-21 alone also won't solve all cross-version streaming issues, wh

Re: CEP-21 and complete cluster replacement.

be performed in sequence. My > understanding is that you can't add more than one node at a time. What we > would like to do is do this is 3 steps: > Add A', B', C' to the cluster. > Wait for all 3 to be accepted and functioning. > Remove A, B, C from the cluster.

Re: CEP-21 and complete cluster replacement.

ting StartJoin for all nodes, > while the range is locked, but block execution of `MidJoin` for any of the > nodes until StartJoin for all of them is executed and, similarly, throttling > FinishJoin before MidJoin is executed for all the nodes. In other words, I > think there

Re: [VOTE] Release Apache Cassandra 4.1.0 (take2)

+1 > On 7 Dec 2022, at 21:40, Mick Semb Wever wrote: > > > Proposing the (second) test build of Cassandra 4.1.0 for release. > > sha1: f9e033f519c14596da4dc954875756a69aea4e78 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.0-tentative > Maven Artifacts

RFC: Cassandra Virtual Nodes

orward to your input, ideas and recommendations. Best Regards, Sam Overton [1] Staggering repair: https://issues.apache.org/jira/browse/CASSANDRA-3721 [2] Project Voldemort, Design: http://project-voldemort.com/design.php [3] Dynamo: http://www.allthingsdistributed.com/files/amazon-dynamo-sos

Re: RFC: Cassandra Virtual Nodes

is is how we anticipate support for heterogeneity in cluster hardware. Sam -- Sam Overton Acunu | http://www.acunu.com | @acunu

Re: RFC: Cassandra Virtual Nodes

ith more than two replicas increases with declustering [Xin et al. 2004]" ("declustering" meaning increasing DF towards N) Regards, -- Sam Overton Acunu | http://www.acunu.com | @acunu

Re: RFC: Cassandra Virtual Nodes

tokens into hot ranges. It makes sense that this would not be a manual process, but there would certainly be more control than just increasing or decreasing the number of tokens assigned to a node. -- Sam Overton Acunu | http://www.acunu.com | @acunu

Re: RFC: Cassandra Virtual Nodes

> For OPP the problem of load balancing is more profound. Now you need > vnodes per keyspace because you can not expect each keyspace to have > the same distribution. With three keyspaces you are not unsure as to > which was is causing the hotness. I think OPP should just go away. That's a good po

Re: RFC: Cassandra Virtual Nodes

described previously is then fairly trivial. The only additional change needed is to assign the tokens in some other way which does not restrict the ranges to being contiguous. -- Sam Overton Acunu | http://www.acunu.com | @acunu

Re: RFC: Cassandra Virtual Nodes

On 20 March 2012 13:37, Eric Evans wrote: > On Tue, Mar 20, 2012 at 6:40 AM, Sam Overton wrote: >> On 20 March 2012 04:35, Vijay wrote: >>> May be, what i mean is little more simple than that... We can consider >>> every node having a multiple conservative ranges and

Re: RFC: Cassandra Virtual Nodes

sale replacing the entire distribution logic in Cassandra with CRUSH. I'm not sure if that's exactly what your design is suggesting? -- Sam Overton Acunu | http://www.acunu.com | @acunu

Re: RFC: Cassandra Virtual Nodes

There is now a parent ticket for this issue in JIRA: https://issues.apache.org/jira/browse/CASSANDRA-4119 Comments and contributions are still welcome! Cheers, Sam On 16 March 2012 23:38, Sam Overton wrote: > Hello cassandra-dev, > > This is a long email. It concerns a significant

PerRowSecondaryIndex

I'm looking at https://issues.apache.org/jira/browse/CASSANDRA-2897 and poking around in the secondary indexes code, I see PerRowSecondaryIndex. I found some relevant JIRAs [1][2][3] but can anyone point me towards implementations which extend this abstract class? Cheers, Sam [1]

Update: Cassandra Virtual Nodes

suites but we will also be writing new tests in addition. I look forward to your questions and comments! -- Sam Overton Acunu | http://www.acunu.com | @acunu

[DISCUSS] Deprecation of IEndpointSnitch (CASSANDRA-19488)

Since CEP-21, the source of truth for topology info (a node's datacenter & rack) is ClusterMetadata. Each node provides its dc/rack when it registers itself with the cluster prior to joining and this information is effectively immutable (for now). This significantly reduces the scope of IEndpoin

Re: 【DISCUSS】What is the current status of triggers in Cassandra ?

This is really a bug with the current implementation of CreateTriggerStatement and I've filed CASSANDRA-20287 to address it. Thanks, Sam > On 3 Feb 2025, at 21:06, Štefan Miklošovič wrote: > > Correct, snapshotting is the way to go here via nodetool cms snapshot > > Bu

Re: [VOTE] Release Apache Cassandra 3.11.19

+1 > On 6 Feb 2025, at 07:02, Štefan Miklošovič wrote: > > Proposing the test build of Cassandra 3.11.19 for release. > > sha1: ecbafb52750f1a2ab8523cbd7cc88c760dd3632b > Git: https://github.com/apache/cassandra/tree/3.11.19-tentative > Maven Artifacts: > https://repository.apache.org/content/

Re: [VOTE] Release Apache Cassandra 3.0.32

+1 > On 6 Feb 2025, at 07:00, Štefan Miklošovič wrote: > > Proposing the test build of Cassandra 3.0.32 for release. > > sha1: c559cf89624802fdb770e6ea962b45f102e48224 > Git: https://github.com/apache/cassandra/tree/3.0.32-tentative > Maven Artifacts: > https://repository.apache.org/content/re

Re: [VOTE] Release Apache Cassandra 4.0.17

+1 > On 6 Feb 2025, at 10:31, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.17 for release. > > sha1: 0354c915a9f8be6ab671af5ff93b8178e6f2e76f > Git: https://github.com/apache/cassandra/tree/4.0.17-tentative > Maven Artifacts: > https://repository.apache.org/content/repos

Re: [DISCUSS] 5.1 should be 6.0

for going off topic re: the actual number we give to the next release, I really don't feel strongly about 5.1 vs 6.0. Thanks, Sam > On 11 Dec 2024, at 11:02, Rahul Singh (ANANT) wrote: > > +1 for calling it 6, even if just to bring up to people on 2.x,3.x that they > are

Re: [DISCUSS] 5.1 should be 6.0

arcus Eriksson wrote: >> >> Staying slightly off topic - we'd also have to run upgrade tests for all >> these upgrade combinations, including different storage compatibility mode >> settings, that is going to be very expensive. >> >> /Marcus &g

Re: [DISCUSS] 5.1 should be 6.0

ow long a bake time is tolerable. This specific issue could probably be fixed by revisiting the SCM implementation in 5.1/6.0, so we should certainly do that but the fact remains that we don't have great test coverage to indicate how clusters behave when running in SCM for a prolonged peri

Re: [DISCUSS] Deprecation of IEndpointSnitch (CASSANDRA-19488)

ne using a custom snitch implementation is able to check it out and help verify that. > On 31 Oct 2024, at 16:53, Sam Tunnicliffe wrote: > > Since CEP-21, the source of truth for topology info (a node's datacenter & > rack) is ClusterMetadata. Each node provides its dc/rack w

Re: [DISCUSS] 5.1 should be 6.0

reads/writes so the consistency guarantees are weakened. Thanks, Sam > On 12 Dec 2024, at 16:17, Jeremiah Jordan wrote: > > My expectation is that in trunk SCM CASSANDRA_4 would change to SCM > CASSANDRA_5. I think we should be striving to support full > downgrade/rollback ab

Re: [VOTE] Simplifying our release versioning process

+1 > On 17 Apr 2025, at 16:58, Josh McKenzie wrote: > > [DISCUSS] thread: > https://lists.apache.org/thread/jy6vodbkh64plhdfwqz3l3364gsmh2lq > > The proposed new versioning mechanism: > • We no longer use semver .MINOR > • Online upgrades are supported for all GA supported releases at

Re: [DISCUSS] Virtualise system_schema (CASSANDRA-19129)

In trunk that durability comes from the metadata log, the system_schema tables are only maintained for backwards compatibility (i.e. downgrades) and for drivers. > On 21 Feb 2025, at 00:29, Jeff Jirsa wrote: > > The schema has to be durable on disk for cold start > > You could put a virtua

<    1   2