Re: Welcome Ekaterina Dimitrova as Cassandra PMC member

Congratulations Ekaterina! On Wed, 5 Mar 2025 at 08:18, Josh McKenzie wrote: > Welcome Ekaterina! \o/ > > On Tue, Mar 4, 2025, at 7:07 PM, Francisco Guerrero wrote: > > Congratulations Ekaterina! Well deserved! > > On 2025/03/04 20:25:08 Paulo Motta wrote: > > Aloha, > > > > The Project Managem

Re: Welcome Caleb Rackliffe to the PMC

Congrats Caleb! On Fri, 21 Feb 2025 at 08:54, Jasonstack Zhao Yang < jasonstack.z...@gmail.com> wrote: > Congrats Ceb! > > On Fri, 21 Feb 2025 at 08:20, Jordan West wrote: > >> Congrats Caleb!! >> >> Jordan >> >> On Thu, Feb 20, 2025 at 18:13 Be

Re: Welcome Caleb Rackliffe to the PMC

Congrats Ceb! On Fri, 21 Feb 2025 at 08:20, Jordan West wrote: > Congrats Caleb!! > > Jordan > > On Thu, Feb 20, 2025 at 18:13 Bernardo Botella < > conta...@bernardobotella.com> wrote: > >> So many good news today! Congratulations Caleb! >> >> >> >> On Feb 20, 2025, at 4:07 PM, Ekaterina Dimitro

Re: Welcome Jeremiah Jordan to the PMC

Congrats! On Sat, 15 Feb 2025 at 20:25, Maxim Muzafarov wrote: > Congratulation Jeremiah! > > On Sat, 15 Feb 2025 at 05:01, Paulo Motta wrote: > > > > Congrats JD! > > > > On Fri, 14 Feb 2025 at 18:35 guo Maxwell wrote: > >> > >> Congrats！ > >> Tolbert, Andy 于2025年2月15日 周六上午6:22写道： > >>> > >>>

Re: Welcome Mike Adamson as Cassandra committer

Congrats Mike! On Sat, 9 Dec 2023 at 8:47 PM, Piotr Kołaczkowski wrote: > Congratulations, Mike! Well deserved, working with you has always been a > pleasure! > > > Wiadomość napisana przez Melissa Logan w dniu > 09.12.2023, o godz. 02:35: > >  > > Congratulations, Mike! > > On Fri, Dec 8, 202

Re: [VOTE] CEP-30 ANN Vector Search

+1 On Fri, 26 May 2023 at 8:44 AM, Yifan Cai wrote: > +1 > -- > *From:* Josh McKenzie > *Sent:* Thursday, May 25, 2023 5:37:02 PM > *To:* dev > *Subject:* Re: [VOTE] CEP-30 ANN Vector Search > > +1 > > On Thu, May 25, 2023, at 8:33 PM, Jake Luciani wrote: > > +1 > >

Re: CEP-30: Approximate Nearest Neighbor(ANN) Vector Search via Storage-Attached Indexes

Hi, I have updated the CEP with some details about distributed queries in the *Approach* section. David: > given results have a real ranking, the current 2i logic may yield incorrect results C* internal iterators are all in primary key order. So we need two in-memory top-k filters, one at repli

Re: Welcome our next PMC Chair Josh McKenzie

Congrats Josh! And thank you Mick! On Thu, 23 Mar 2023 at 23:42, Jeremy Hanna wrote: > Thank you Mick for all of your hard work in the project including your > time as the PMC chair! > > Thank you too Josh for all that you do - and for the work that you'll do > as chair! > > On Mar 23, 2023, at

Re: Thanks to Nate for his service as PMC Chair

Thank you, Nate! Congrats Mick! On Fri, 15 Jul 2022 at 02:42, Henrik Ingo wrote: > Thank you Nate for holding the baton for all these years. Even as a > relative newcomer (2+ years already) I wanted to say I do understand and > appreciate your role in carrying the torch to where the project is

Re: Welcome Aleksandr Sorokoumov as Cassandra committer

Congrats Aleks! On Wed, 16 Mar 2022 at 22:01, J. D. Jordan wrote: > Congratulations! > > On Mar 16, 2022, at 8:43 AM, Ekaterina Dimitrova > wrote: > >  > Great news! Well deserved! Congrats and thank you for all your support! > > On Wed, 16 Mar 2022 at 9:41, Paulo Motta wrote: > >> Congratula

Re: [VOTE] CEP-7: Storage Attached Index

+1 On Fri, 18 Feb 2022 at 08:15, Jeremy Hanna wrote: > +1 nb. Thanks Caleb, Mike, Jason, and everyone involved with the effort. > > On Feb 17, 2022, at 4:23 PM, Caleb Rackliffe > wrote: > >  > Hi everyone, > > I'd like to call a vote to approve CEP-7. > > Proposal: > https://cwiki.apache.org/c

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

+1 On Mon, 26 Jul 2021 at 22:02, Michael Shuler wrote: > +1 > > Kind regards, > Michael > > On 7/22/21 5:40 PM, Brandon Williams wrote: > > I am proposing the test build of Cassandra 4.0.0 for release. > > > > sha1: 902b4d31772eaa84f05ffdc1e4f4b7a66d5b17e6 > > Git: > https://gitbox.apache.org/re

Re: Welcome Caleb Rackliffe as Cassandra committer

Congrats, Caleb!

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

+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: 3282f5ecf187ecbb56b8d73ab9a9110c010898b0 > > Git: > > > https://gitbox.apache.org/repos/asf?p=cass

Re: Welcome Berenguer Blasi as Cassandra committer

Congrats Berenguer! On Thu, 25 Mar 2021 at 18:11, Erick Ramirez wrote: > Congratulations, Berenguer! Thanks for all the work you've done. 🍻 > > > On Thu, 25 Mar 2021 at 21:10, Benjamin Lerer wrote: > > > The PMC's members are pleased to announce that Berenguer Blasi has > > accepted the invita

Re: Welcome Paulo Motta as Cassandra PMC member

Congrats Paulo! On Wed, 10 Feb 2021 at 00:03, Ekaterina Dimitrova wrote: > Congrats! Well done! > > On Tue, 9 Feb 2021 at 11:02, J. D. Jordan > wrote: > > > Congrats Paulo! A great addition to the PMC. > > > > > On Feb 9, 2021, at 9:59 AM, Jonathan Ellis wrote: > > > > > > Congratulations, Pa

Re: Regarding Materialized Views

Hi, > 1. When will MVs be enabled for production use again ? at least 4.x, it will be assessed after CASSANDRA-15921 > 2. Is there any plan to support secondary indexes on materialized views ? unless your index query is partition-restricte

Re: [DISCUSS] CEP-7 Storage Attached Index

t is going to change when > row offsets are added, so my concern is that we may have to support two > versions of a format for a smooth migration. > > > > On Thu, Sep 24, 2020 at 6:53 AM Jasonstack Zhao Yang < > jasonstack.z...@gmail.com> wrote: > > > >> I

Re: [DISCUSS] CEP-7 Storage Attached Index

> > > > the most primitive implementation of a B-Tree. Fully-occupied prefix > > > > B-Tree > > > > can have similar properties. There's been a lot of research on > B-Trees > > > > and > > > > opt

Re: [VOTE] Accept the Harry donation

+1 nb On Fri, Sep 18, 2020, 12:26 Oleksandr Petrov wrote: > +1 > > On Thu, Sep 17, 2020 at 6:28 PM Blake Eggleston > wrote: > > > +1 > > > > > On Sep 16, 2020, at 2:45 AM, Mick Semb Wever wrote: > > > > > > This vote is about officially accepting the Harry donation from Alex > > Petrov > > > a

Re: [DISCUSS] CEP-7 Storage Attached Index

Thank you Patrick for hosting Cassandra Contributor Meeting for CEP-7 SAI. The recorded video is available here: https://cwiki.apache.org/confluence/display/CASSANDRA/2020-09-01+Apache+Cassandra+Contributor+Meeting On Tue, 1 Sep 2020 at 14:34, Jasonstack Zhao Yang wrote: > Thank you, Char

Re: [DISCUSS] Change style guide to recommend use of @Override

+1 On Wed, 2 Sep 2020 at 02:45, Dinesh Joshi wrote: > +1 > > > On Sep 1, 2020, at 11:27 AM, David Capwell wrote: > > > > Currently our style guide recommends to avoid using @Override and updates > > intellij's code style to exclude it by default; I would like to propose > we > > change this rec

Re: [DISCUSS] CEP-7 Storage Attached Index

te: > > > > > > > > Meeting scheduled. > > > > > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/2020-08-01+Apache+Cassandra+Contributor+Meeting > > > > > > > > Tuesday September 1st, 11AM PST. I added a basic b

Re: [VOTE] Release Apache Cassandra 4.0-beta2

+1 On Sat, 29 Aug 2020 at 00:28, Joshua McKenzie wrote: > +1 > > On Fri, Aug 28, 2020 at 11:48 AM Brandon Williams > wrote: > > > +1 > > > > On Fri, Aug 28, 2020, 9:19 AM Mick Semb Wever wrote: > > > > > Proposing the test build of Cassandra 4.0-beta2 for release. > > > > > > sha1: 56eadf20043

Re: [DISCUSS] CEP-7 Storage Attached Index

modularization? > > > > > > > > > > > > We probably should have a discussion on the ML or monthly contrib > call > > > > > > about it first to see how aligned the interested contributors are. > > Could > > > > > do > > &

Re: [DISCUSS] CEP-7 Storage Attached Index

ven a few bugs are open against 2i and SASI, can we provide some > overview, or rough indication, of how many of them we could "triage away"? > > And, is it time for the project to start introducing new SPI > implementations as separate sub-modules and jar files that are only lo

Re: [DISCUSS] CEP-7 Storage Attached Index

dex, that's a user > decision for faster queries or more disk space. > > On Tue, Aug 18, 2020 at 6:05 AM DuyHai Doan wrote: > > > > Thank you Zhao Yang for starting this topic > > > > After reading the short design doc, I have a few questions > > > &g

Re: [DISCUSS] CEP-7 Storage Attached Index

DT indexings (at any depth) on the roadmap of SAI ? I strongly believe > that those features are the bare minimum to make SAI an interesting > replacement for the native 2nd index as well as SASI. SASI limited support > for those advanced data structures has hindered its wide adoption (among

Re: [DISCUSS] CEP-7 Storage Attached Index

t still choose afresh 2i or SASI over SAI I'd like SAI to be the only index for users, but this is a decision to be made by the community. > - Who fills the roles involved? Contributors that are still active on C* or related projects: Andres de la Peña Caleb Rackliffe Dan LaRocque Jason

[DISCUSS] CEP-7 Storage Attached Index

explanation about SAI design in the CEP document. To make the technical discussion simpler, we created a slack channel #cassandra-sai. We are looking forward to the community's feedback and suggestions. Regards, Zhao Yang [1] https://docs.google.com/docum

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

sorry, my phone got unlocked accidentally in my pocket. please ignore the empty email. On Tue, 21 Jul 2020 at 18:40, Jasonstack Zhao Yang < jasonstack.z...@gmail.com> wrote: > > Blake Eggleston 于 2020年7月21日周二 01:57写道： > >> Characterizing alternate or conflicting points of

Re: Media coordination (was: [VOTE] Release Apache Cassandra 4.0-beta1)

Blake Eggleston 于 2020年7月21日周二 01:57写道： > Characterizing alternate or conflicting points of view as assuming bad > intentions without justification is both unproductive and unhealthy for the > project. > > > On Jul 20, 2020, at 9:14 AM, Joshua McKenzie > wrote: > > > > This kind of back and fort

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

+1 (nb) On Sun, 19 Jul 2020 at 07:01, Ekaterina Dimitrova wrote: > +1(nb) > > On Sat, 18 Jul 2020 at 18:13, Jeff Jirsa wrote: > > > > > > > +1 > > > > > On Jul 17, 2020, at 4:28 PM, Mick Semb Wever wrote: > > > > > > Proposing the test build of Cassandra 4.0-beta1 for release. > > > > > > sha

Re: [VOTE] Release Apache Cassandra 4.0-beta1

+1 (nb) On Thu, 16 Jul 2020 at 01:28, Brandon Williams wrote: > +1 (binding) > > On Tue, Jul 14, 2020, 6:06 PM Mick Semb Wever wrote: > > > Proposing the test build of Cassandra 4.0-beta1 for release. > > > > sha1: 5e767711360ecc4bc05a7cd219f0e680bfada004 > > Git: > > > > > https://gitbox.apach

Re: [DISCUSS] Future of MVs

> I agree with Jeff that there is some stuff to do to address the current MV > issues and I am willing to focus on making them production ready. +1 On Wed, 1 Jul 2020 at 15:42, Benjamin Lerer wrote: > > > > "Make the scan faster" > > "Make the scan incremental and automatic" > > "Make it not bl

Re: [DISCUSS] Future of MVs

> While at TLP, I helped numerous customers move off of MVs, mostly because > they affected stability of clusters in a horrific way. The most telling > project involved helping someone create new tables to manage 1GB of data > because the views performed so poorly they made the cluster unresponsiv

Re: [VOTE] Project governance wiki doc (take 2)

+1 (nb) On Sat, 20 Jun 2020 at 23:18, Jeff Jirsa wrote: > +1 (and present?) > > > > On Jun 20, 2020, at 8:12 AM, Joshua McKenzie > wrote: > > > > Link to doc: > > > https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Project+Governance > > > > Change since previous cancelled

Re: Keeping test-only changes out of CHANGES.txt

+1 On Thu, Apr 9, 2020, 00:04 Aleksey Yeshchenko wrote: > +1 > > > On 8 Apr 2020, at 15:08, Mick Semb Wever wrote: > > > > Can we agree on keeping such test changes out of CHANGES.txt ? > > > > We already don't put entries into CHANGES.txt if it is not a change > > from any previous release. >

Re: but there are still the same only 3 compile errors left on the 1 line code in abstractRow.java

Hi, It's probably just an Eclipse issue that doesn't properly handle lambda. Intellij should work just fine or you can add a type cast "(Function)" for Eclipse... On Wed, 17 Jul 2019 at 16:32, Nimbus Lin wrote: > To Sir Michael: > > Thank you for your guiding, my steps are: > cd /data/wo

Re: Warn about SASI usage and allow to disable them

+1 on yaml config. +1 on disable by default. On Tue, 15 Jan 2019 at 13:23 Taylor Cressy wrote: > +1 on config. +1 on disabling. > > +1 on applying it to materialized views as well. > > > On Jan 14, 2019, at 17:29, Joshua McKenzie wrote: > > > > +1 on config change, +1 on disabling, and so long

CASSANDRA-14925 DecimalSerializer.toString() can OOM

Hi, Would like to get some feedback for CASSANDRA-14925. In order to avoid potential OOM attack, we propose to change DecimalSerializer.toString() from `BigDecimal.toPlainString()` to `BigDecimal.toString()` on Trunk. This change should not cause any compatibility issues.. Thanks Zhao Yang

DoS attack through PagingState

Hello, Can someone please take a look at https://issues.apache.org/jira/browse/CASSANDRA-14433 to see if it's a valid report? Thanks, Yang -- _CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review

Re: unsubscribe

ibe > > > > > > 2017-04-05 9:45 GMT+01:00 Nitija Patil : > > > > > > > unsubscribe > > > > > > > > On Wed, Apr 5, 2017 at 2:05 PM, 郑蒙家(蒙家) > com > > > > > > > > wrote: > > > > > > > > > unsubscribe > > > > > > > > > > -- Suli Yang Department of Physics University of Wisconsin Madison 4257 Chamberlin Hall Madison WI 53703

Re: thread architecture of Cassandra

hould have posted this request to other, more appropriate list instead of this one. Thanks a lot. Suli On Thu, Mar 23, 2017 at 1:04 PM, 杨苏立 Yang Su Li wrote: > Hi, > > Sorry the original email is missing attachement. You can find attachment > in the following URL: http://pages.

Re: thread architecture of Cassandra

Hey Suli, > > > > You forgot to attach the document. > > > > *Thanks,* > > *Christopher Licata* > > Senior Software Engineer > > Game Changers > > Card Rewards > > 718.916.8940 <(718)%20916-8940> > > > > *From: *杨苏立 Yang Su Li > *R

Re: thread architecture of Cassandra

(attached). I am wondering if the developers of Cassandra could take a look at it and let me know if anything is incorrect or inaccurate, or if I have missed anything. Thanks a lot for your help! On Wed, Mar 22, 2017 at 3:10 PM, 杨苏立 Yang Su Li wrote: > Hi, > > I am a graduate student w

Re: thread architecture of Cassandra

send a link? > > - Jeff > > > On Wed, Mar 22, 2017 at 1:10 PM, 杨苏立 Yang Su Li > wrote: > > > Hi, > > > > I am a graduate student working on scheduling on storage systems, and we > > are interested in how different threads in Cassandra intera

thread architecture of Cassandra

(attached). I am wondering if the developers of Cassandra could take a look at it and let me know if anything is incorrect or inaccurate, or if I have missed anything. Thanks a lot for your help! Suli -- Suli Yang Department of Physics University of Wisconsin Madison 4257 Chamberlin Hall Madison

Re: [VOTE] Ask Infra to move github notification emails to pr@

+1 On Tue, 21 Mar 2017 at 9:36 AM, Jonathan Haddad wrote: > +1 > On Mon, Mar 20, 2017 at 6:33 PM Jason Brown wrote: > > > +1 > > On Mon, Mar 20, 2017 at 18:21 Anthony Grasso > > wrote: > > > > > +1 > > > > > > On 21 March 2017 at 09:32, Jeff Jirsa wrote: > > > > > > > There's no reason for the

Re: Rough roadmap for 4.0

Hi, Will we still use tick-tock release for 4.x and 4.0.x ? Stefan Podkowinski 于2016年11月16日周三 下午4:52写道： > From my understanding, this will also effect EOL dates of other branches. > > "We will maintain the 2.2 stability series until 4.0 is released, and 3.0 > for six months after that.". > > > O

Re: Support Multi-Tenant in Cassandra

quest(eg. insert a blo to collection column), it will be awful. Thank you. jason zhao yang 于2016年8月6日周六 下午12:33写道： > We consider splitting by Keypspace or tables before, but Cassandra's table > is a costly structure(more cpu, flush, memory..). > > In our use case, it's

Re: Support Multi-Tenant in Cassandra

paces. This will also help with server resource isolation and > most of the issues you've raised. > > > On Fri, Jul 15, 2016 at 10:10 AM Romain Hardouin > wrote: > > > I don't use C* in such a context but out of curiosity did you set > > the request_schedu

Support Multi-Tenant in Cassandra

Hi, May I ask is there any plan of extending functionalities related to Multi-Tenant? Our current approach is to define an extra PartitionKey called "tenant_id". In my use cases, all tenants will have the same table schemas. * For security isolation: we customized GRANT statement to be able to r

About MergeColumnFamilies when creating table

Hi, Recently I am checking the performance of creating tables. I found that MigrationStage thread spent most of the time in " mergeColumnFamilies(oldColumnFamilies, newColumnFamilies);" method. Can someone explain the purpose of merging oldCFs and newCFs to find the diff between old and new whe

Re: cassandra-3.1 branch and new merge order

> What is the difference between 3.0.x series and 3.1? > - trunk represents the upcoming cassandra-3.2 release (fixes from 3.1 and > new features) > > -- > AY -- Thanks, Phil Yang

Re: Proposal: release 2.2 (based on current trunk) before 3.0 (based on 8099)

> > > > > > > > > * - Extend 2.1.x series and 2.2.x until 4.0, but skip 3.0.x > stabilization > > > series in favor of tick-tock 3.x- Extend 2.1.x series until 4.0, but > stop > > > 2.2.x when 3.0 ships in favor of developing 3.0.x insteadThoughts?* > > > > > > -- > > > Jonathan Ellis > > > Project Chair, Apache Cassandra > > > co-founder, http://www.datastax.com > > > @spyced > -- Thanks, Phil Yang

Re: 3.0 and the Cassandra release process

tained for at least a year > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder, http://www.datastax.com > @spyced > -- Thanks, Phil Yang

Re: 3.0 and the Cassandra release process

at > > >>>>> once. > > >>>>>> We > > >>>>>>> can do something similar here: > > >>>>>>> > > >>>>>>> One month releases. Period. If it’s not done, it can wait. > > >>>>>>> *Every other release only accepts bug fixes.* > > >>>>>>> > > >>>>>>> By itself, one-month releases are going to dramatically reduce > the > > >>>>>>> complexity of testing and debugging new releases -- and bugs that > > do > > >>>>> slip > > >>>>>>> past us will only affect a smaller percentage of users, avoiding > > the > > >>>>> “big > > >>>>>>> release has a bunch of bugs no one has seen before and pretty > much > > >>>>>> everyone > > >>>>>>> is hit by something” scenario. But by adding in the second > rule, I > > >>>>> think > > >>>>>>> we have a real chance to make a quantum leap here: stable, > > >>>>>> production-ready > > >>>>>>> releases every two months. > > >>>>>>> > > >>>>>>> So here is my proposal for 3.0: > > >>>>>>> > > >>>>>>> We’re just about ready to start serious review of 8099. When > > that’s > > >>>>>> done, > > >>>>>>> we branch 3.0 and cut a beta and then release candidates. > Whatever > > >>>>> isn’t > > >>>>>>> done by then, has to wait; unlike prior betas, we will only > accept > > >>>>> bug > > >>>>>>> fixes into 3.0 after branching. > > >>>>>>> > > >>>>>>> One month after 3.0, we will ship 3.1 (with new features). At > the > > >>>>> same > > >>>>>>> time, we will branch 3.2. New features in trunk will go into > 3.3. > > >>>>> The > > >>>>>> 3.2 > > >>>>>>> branch will only get bug fixes. We will maintain backwards > > >>>>> compatibility > > >>>>>>> for all of 3.x; eventually (no less than a year) we will pick a > > >>>>> release > > >>>>>> to > > >>>>>>> be 4.0, and drop deprecated features and old backwards > > >>>>> compatibilities. > > >>>>>>> Otherwise there will be nothing special about the 4.0 > designation. > > >>>>> (Note > > >>>>>>> that with an “odd releases have new features, even releases only > > have > > >>>>> bug > > >>>>>>> fixes” policy, 4.0 will actually be *more* stable than 3.11.) > > >>>>>>> > > >>>>>>> Larger features can continue to be developed in separate > branches, > > >>>>> the > > >>>>>> way > > >>>>>>> 8099 is being worked on today, and committed to trunk when ready. > > So > > >>>>>> this > > >>>>>>> is not saying that we are limited only to features we can build > in > > a > > >>>>>> single > > >>>>>>> month. > > >>>>>>> > > >>>>>>> Some things will have to change with our dev process, for the > > better. > > >>>>> In > > >>>>>>> particular, with one month to commit new features, we don’t have > > room > > >>>>> for > > >>>>>>> committing sloppy work and stabilizing it later. Trunk has to be > > >>>>> stable > > >>>>>> at > > >>>>>>> all times. I asked Ariel Weisberg to put together his thoughts > > >>>>>> separately > > >>>>>>> on what worked for his team at VoltDB, and how we can apply that > to > > >>>>>>> Cassandra -- see his email from Friday <http://bit.ly/1MHaOKX>. > > >>>>> (TLDR: > > >>>>>>> Redefine “done” to include automated tests. Infrastructure to > run > > >>>>> tests > > >>>>>>> against github branches before merging to trunk. A new test > > harness > > >>>>> for > > >>>>>>> long-running regression tests.) > > >>>>>>> > > >>>>>>> I’m optimistic that as we improve our process this way, our even > > >>>>> releases > > >>>>>>> will become increasingly stable. If so, we can skip sub-minor > > >>>>> releases > > >>>>>>> (3.2.x) entirely, and focus on keeping the release train moving. > > In > > >>>>> the > > >>>>>>> meantime, we will continue delivering 2.1.x stability releases. > > >>>>>>> > > >>>>>>> This won’t be an entirely smooth transition. In particular, you > > will > > >>>>>> have > > >>>>>>> noticed that 3.1 will get more than a month’s worth of new > features > > >>>>> while > > >>>>>>> we stabilize 3.0 as the last of the old way of doing things, so > > some > > >>>>>>> patience is in order as we try this out. By 3.4 and 3.6 later > this > > >>>>> year > > >>>>>> we > > >>>>>>> should have a good idea if this is working, and we can make > > >>>>> adjustments > > >>>>>> as > > >>>>>>> warranted. > > >>>>>>> > > >>>>>>> -- > > >>>>>>> Jonathan Ellis > > >>>>>>> Project Chair, Apache Cassandra > > >>>>>>> co-founder, http://www.datastax.com > > >>>>>>> @spyced > > >>>>> > > >>>> > > >>> > > > > > > > > -- Thanks, Phil Yang

What are the factors that affect the release time of each minor version?

ld we make each release more frequently? Or we may make a rule to decide if we need release a new version? For example: "If the latest version was released two weeks ago, or after the latest version we have already resolved 20 issues, we should release a new minor version". -- Thanks, Phil Yang

Re: why bloom filter is only for row key?

loom filter's property between row keys and row keys+column names automatically or by user's config? Thanks, Philo Yang 2014-09-15 2:45 GMT+08:00 DuyHai Doan : > Hello Philo > > Building bloom filter for column names (what you call column key) is > technically possible but

why bloom filter is only for row key?

on? Thanks, Philo Yang

apply for the access to contribute Cassandra Wiki

Hi, all I think I can improve some pages in Cassandra Wiki and I see in https://wiki.apache.org/cassandra/FrontPage I should send a mail to this list. Please give me the access to contribute the wiki. My nickname is PhiloYang. Thank you. -- Regards, Philo Yang

Dynamic columns in a column family?

Hi everyone, I am wondering whether it is possible to not to define the column metadata when creating a column family, but to specify the column when client updates data, for example: CREATE COLUMN FAMILY products WITH default_validation_class= UTF8Type AND key_validation_class=UTF8Type AND compa

Re: wiki updates

Thanks Aaron for the hard work. The new front page gives a much clear image on Cassandra. However I would also like to present some of my thoughts - based on my own learning path: 1) The first part should present a clear image on what Cassandra is, and what's inside Cassandra - thus we'd better

Re: Hadoop over Cassandra

interesting that I just came up with the same question this morning and found https://issues.apache.org/jira/browse/CASSANDRA-342 http://mail-archives.apache.org/mod_mbox/incubator-cassandra-dev/200907.mbox/ these give u some perspective into the thinking behind the implementation On Mon, Ma