Talk:Apache Cassandra
It is of interest to the following WikiProjects:
.svg){kind=link}
Revisions succeeding this version of this article is substantially duplicated in one or more external publications. Since these publication(s) copied Wikipedia, rather than the reverse, please do not flag this article as a copyright violation of the following source:
|
On 6/11/17 I changed the header "decentralized" to "distributed" since Cassandra allows for a distributed database system . In addition, the word decentralized has been popularized by the blockchain community and this might lead to confusion. Shahaed (talk) 13:13, 11 June 2018 (UTC) Reply
Removing the worded like an advert banner. Whilst I can see that the content is a bit weak in places I don't see that it's not neutral — Preceding unsigned comment added by 185.69.144.191 (talk) 10:50, 11 July 2017 (UTC) Reply
I corrected the link to the better explanation Elcidia (talk) 18:57, 10 March 2010 (UTC) Reply
June 2009
[edit ]I've expanded the article a little, including a brief description of column families. I carefully skated over the difference between ordinary columns and supercolumns. (At the moment, the Google Code wiki has a better explanation of the data model than the wiki at apache.org.) Another important thing I left out is the Read Repair feature.
Given the lack of detail in the article, I've marked the article as a {{database-stub }}.
Corrections and expansions are very welcome. I suspect this will become a very significant project. 18:57, 10 March 2010 User:Elcidia
- The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.
The result of the move request was: page moved. Vegaswikian (talk) 18:33, 30 March 2010 (UTC) Reply
Cassandra (database) → Apache Cassandra
- On February 17th, 2010 it graduated to a top-level Apache Project and it is the official name User:109.82.236.134 05:16, 23 March 2010 (UTC) Reply
- Support Might as well. Better to disambiguate this way. Ham Pastrami (talk) 06:21, 24 March 2010 (UTC) Reply
- The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.
Small text
The link to IBM's research on using it for an email system links to Google Doc's PDF viewer rather than directly to the PDF. That seems odd. -- Ralph Corderoy (talk) 16:23, 18 January 2011 (UTC) Reply
The intro to this article is a mess. It says Cassandra enables low latency operations and then includes a quote saying latencies are high and that this somehow enables high throughput. It's not consistent and doesn't make sense. Telanis (talk) 05:00, 6 April 2016 (UTC) Reply
- I agree. The reality as I see it is this: Historically, as a result of its Log-structured_merge-tree, it has always had very low latency writes, potentially at the cost of higher read latency. However, there have been a number of optimizations over the intervening years that have brought read latency down to within accepted norms, so I'm not sure it's worth drawing any special attention to it at all. I believe the reference to latency in the first paragraph (which has probably been there since the early days of this article), was using low latency as a way of indicating Cassandra's suitability for transactional work loads (that used to be the way that language was used). I believe the reference to latency in the second paragraph is some combination of Wrong, and outdated. It should be relatively easy to find citations to support all of these assertions, and rewrite the entirely of the intro. I'd be willing to take a crack at this, but I might be too close to the project to be objective (though I do not think I could make it sound any more like a sales pitch if I tried :/ ). Jericevans (talk) 13:30, 6 April 2016 (UTC) Reply
Hello fellow Wikipedians,
I have just modified 2 external links on Apache Cassandra. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive https://web.archive.org/web/20120307033743/http://about.digg.com/node/564 to http://about.digg.com/node/564
- Added archive https://web.archive.org/web/20140528110238/http://www.networkworld.com/news/tech/2012/102212-nosql-263595.html to http://www.networkworld.com/news/tech/2012/102212-nosql-263595.html
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck }}).
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check }} (last update: 5 June 2024).
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot (Report bug) 07:56, 16 October 2016 (UTC) Reply
The stable release is mentioned twice with different values (3.0 and 3.9). It needs to be fixed. — Preceding unsigned comment added by 98.234.159.92 (talk) 01:56, 12 January 2017 (UTC) Reply
Hello fellow Wikipedians,
I have just modified 6 external links on Apache Cassandra. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Corrected formatting/usage for http://www.mail-archive.com/cassandra-dev%40incubator.apache.org/msg00004.html
- Corrected formatting/usage for http://www.mail-archive.com/cassandra-dev%40incubator.apache.org/msg01518.html
- Corrected formatting/usage for http://www.mail-archive.com/cassandra-dev%40incubator.apache.org/msg01163.html
- Added archive https://web.archive.org/web/20110511204551/https://www.cloudkick.com/blog/2010/mar/02/4_months_with_cassandra/ to https://www.cloudkick.com/blog/2010/mar/02/4_months_with_cassandra/
- Added archive https://web.archive.org/web/20111210143921/http://blip.tv/datastax/cassandra-at-mahalo-com-4030941 to http://blip.tv/datastax/cassandra-at-mahalo-com-4030941
- Added archive https://web.archive.org/web/20111007063645/http://openx.com/publisher/technology to http://openx.com/publisher/technology
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check }} (last update: 5 June 2024).
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot (Report bug) 21:44, 7 July 2017 (UTC) Reply
This should be a sub-section of the main article as Tombstones are inherent to Cassandra and not other NoSQLs Devopam (talk) 08:32, 18 June 2019 (UTC) Reply
- Disagree, this is untrue. To provide just a few counterexamples, Couchbase ref and OpenStack Swift ref also use tombstones; it's a broader distributed systems topic and not inherent to Cassandra. ␄ –Nucleosynth (t c) 13:55, 14 July 2019 (UTC) Reply
The description of the data model is confusing partly, I imagine, because it seems the terminology is not consistent with other types of database. A diagram would help a lot here. FreeFlow99 (talk) 14:05, 17 December 2023 (UTC) Reply
- I reworked this section. i think its a bit more clear now. the old section had been written a long time ago, using terminology that isn't as widely used anymore. Cononsense (talk) 16:01, 9 December 2024 (UTC) Reply
I believe that Cassandra can run on AWS and on-prem, so guess it could run on GCP too. Is this right? What is the mechanism for scaling, ie how/what causes more containers/processors to spin up as necessary? FreeFlow99 (talk) 08:20, 3 September 2024 (UTC) Reply
Concerns were raised previously via tag about AI-generated content in this article, which is prohibited per WP:NEWLLM. This is a procedural talk page section to discuss it. There is no need to ping me in response. Read WP:AISIGNS for more information for why this is tagged; however, note that fixing the issue requires more than just changing the superficial signs.
Rationale: this 2024 rewrite; note WP:AISIGNS in superficial analyses, vocab distro typical of LLM output etc Gnomingstuff (talk) 04:43, 26 June 2026 (UTC) Reply
- C-Class Computing articles
- High-importance Computing articles
- C-Class software articles
- High-importance software articles
- C-Class software articles of High-importance
- All Software articles
- C-Class Free and open-source software articles
- High-importance Free and open-source software articles
- C-Class Free and open-source software articles of High-importance
- All Free and open-source software articles
- All Computing articles