Re: Planet Cassandra meetup organizer opportunity

[Aaron]

Melissa,

I would be happy to help, as well.

Thanks,

Aaron


On Fri, Dec 6, 2024 at 11:56 PM Soheil Rahsaz 
wrote:

> Hello Mellisa
>
> I am also eager to volunteer and excited to help. I have previously given
> talks about Cassandra.
>
> Regards,
> Soheil
>
> On Sat, Dec 7, 2024 at 1:11 AM Melissa Logan 
> wrote:
>
>> Wonderful, thank you Rahul! I'll connect with you to discuss.
>>
>>
>>
>> On Fri, Dec 6, 2024 at 1:28 PM Rahul Singh (ANANT) 
>> wrote:
>>
>>> Melissa, Bernardo, am happy to help and volunteer some of our resources
>>> as well. We've done many Cassandra Lunches over the years and would love to
>>> support and continue the Planet Cassandra meetups.
>>>
>>>
>>> Sent via Superhuman <https://sprh.mn/?vip=rahul.si...@anant.us>
>>>
>>>
>>> On Fri, Dec 06, 2024 at 2:56 PM, Melissa Logan 
>>> wrote:
>>>
>>>> Bernardo, I would be delighted for you to do this.
>>>>
>>>> Let me know a good time to chat: https://cal.com/mklogan
>>>>
>>>>
>>>>
>>>> On Fri, Dec 6, 2024 at 10:22 AM Bernardo Botella <
>>>> conta...@bernardobotella.com> wrote:
>>>>
>>>>> Hi Melissa,
>>>>>
>>>>> I’ll be happy to jump in to keep this going. Let’s sync about this
>>>>> when you have a chance.
>>>>>
>>>>> Regards,
>>>>> Bernardo
>>>>>
>>>>> On Dec 6, 2024, at 10:17 AM, Melissa Logan 
>>>>> wrote:
>>>>>
>>>>> Hi folks:
>>>>>
>>>>> My team and I created and managed the Planet Cassandra Meetup - a
>>>>> virtual monthly meetup to share Cassandra use cases, best practices, case
>>>>> studies, community updates, and other similar topics:
>>>>> https://www.meetup.com/cassandra-global/
>>>>>
>>>>> As we have stepped back from organizing this, we're looking for one
>>>>> or more individuals who are interested in stepping up. In short, it would
>>>>> mean finding speakers and hosting the event virtually each month. You can
>>>>> see a detailed list of activities here:
>>>>>
>>>>>
>>>>> https://cwiki.apache.org/confluence/display/CASSANDRA/Planet+Cassandra+Meetup
>>>>>
>>>>> It's a fun way to stay up-to-date on Cassandra and connected with the
>>>>> community. I'm happy to share more details if anyone is interested. In an
>>>>> ideal world, a couple people would collaborate to draw ideas from multiple
>>>>> sources and share the workload.
>>>>>
>>>>> Note: Meetup.com <http://meetup.com/> does incur a monthly fee of
>>>>> about $15/mo which I believe will remain at this legacy/lower fee.
>>>>>
>>>>> If we don't hear from anyone by Friday, Jan. 3 we plan to close the
>>>>> group.
>>>>>
>>>>> Any questions, just let me know. Thanks!
>>>>>
>>>>> Melissa
>>>>>
>>>>>
>>>

Re: Patrick McFadin joins the PMC

[Aaron]

Woohoo! Congrats Patrick!

On Wed, Jan 22, 2025 at 10:05 AM Jordan West  wrote:

> The PMC's members are pleased to announce that Patrick McFadin has accepted
> an invitation to become a PMC member.
>
> Thanks a lot, Patrick, for everything you have done for the project all
> these years.
>
> Congratulations and welcome!!
>
> The Apache Cassandra PMC
>

Re: Welcome Jeremiah Jordan to the PMC

[Aaron]

Congratulations, JD!

On Sat, Feb 15, 2025 at 7:05 AM Jasonstack Zhao Yang <
jasonstack.z...@gmail.com> wrote:

> 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写道：
>> >>>
>> >>> Congrats JD!
>> >>>
>> >>> On Fri, Feb 14, 2025 at 4:13 PM  wrote:
>> 
>>  Congratulations, well deserved!
>> 
>>  El 14 feb 2025, a las 20:40, Alex Petrov 
>> escribió:
>> 
>>  
>>  Congratulations!
>> 
>>  On Fri, Feb 14, 2025, at 7:33 PM, Josh McKenzie wrote:
>> 
>>  Congrats Jeremiah!
>> 
>>  I know you're excited to have yet another email list to attend to,
>> aren't you? :D
>> 
>>  On Fri, Feb 14, 2025, at 1:29 PM, Jeremiah Jordan wrote:
>> 
>>  Thanks all!  Excited to continue being a part of the project in this
>> new role.
>> 
>>  -Jeremiah Jordan
>> 
>>  On Feb 14, 2025 at 12:23:17 PM, Francisco Guerrero <
>> fran...@apache.org> wrote:
>> 
>>  Congrats!
>> 
>>  On 2025/02/14 18:20:02 Yifan Cai wrote:
>> 
>>  Congrats!
>> 
>> 
>>  On Fri, Feb 14, 2025 at 10:16 AM Jordan West 
>> wrote:
>> 
>> 
>>  > Congrats, JD! Welcome aboard!
>> 
>>  >
>> 
>>  > Jordan
>> 
>>  >
>> 
>>  > On Fri, Feb 14, 2025 at 11:01 Mick Semb Wever 
>> wrote:
>> 
>>  >
>> 
>>  >>.
>> 
>>  >>
>> 
>>  >> > I hope you will join me in welcoming him to the committee.
>> 
>>  >>
>> 
>>  >>
>> 
>>  >> Welcome JD!
>> 
>>  >>
>> 
>>  >
>> 
>> 
>> 
>> 
>>
>

Re: Welcome Caleb Rackliffe to the PMC

[Aaron]

Congratulations, Caleb! Well-deserved!

On Fri, Feb 21, 2025 at 8:56 AM Jeremy Hanna 
wrote:

> Congratulations Caleb.  Thank you for all of your contribution and work on
> the project.
>
> > On Feb 20, 2025, at 4:06 PM, Jon Haddad  wrote:
> >
> > The PMC for Apache Cassandra is delighted to announce that Caleb
> Rackliffe has joined it's membership!
> >
> > Caleb has been a member of the community for 10 years and is one of the
> most active committers on the project.
> >
> > Please join us in welcoming Caleb to his new role!
> >
> > Jon
> > On behalf of the Cassandra PMC
> >
> >
>
>

Re: New committers: Maxwell Guo and Dmitry Konstantinov

[Aaron]

Congratulations Maxwell and Dmitry! That's awesome!

On Thu, Feb 20, 2025 at 1:12 PM Maxim Muzafarov  wrote:

> Congratulations!
>
> On Thu, 20 Feb 2025 at 19:17, Abe Ratnofsky  wrote:
> >
> > Congrats Maxwell and Dmitry!
>

Re: Welcome Aaron Ploetz as Cassandra Committer

[Aaron]

Thank you everyone!

Aaron


On Tue, Mar 4, 2025 at 7:02 AM J. D. Jordan 
wrote:

> 🎉
>
> On Mar 4, 2025, at 5:49 AM, Ekaterina Dimitrova 
> wrote:
>
> 
> Congrats!!! 🎉
>
> On Tue, 4 Mar 2025 at 6:11, Josh McKenzie  wrote:
>
>> Congrats Aaron!
>>
>> On Tue, Mar 4, 2025, at 4:08 AM, Soheil Rahsaz wrote:
>>
>> Congratulations Aaron!
>>
>> On Tue, Mar 4, 2025 at 12:09 PM Paulo Motta  wrote:
>>
>> Congratulations Aaron, happy to see you recognized as a committer!
>>
>> Cheers,
>>
>> Paulo
>>
>> On Tue, 4 Mar 2025 at 03:26 Bernardo Botella <
>> conta...@bernardobotella.com> wrote:
>>
>> That’s awesome!!
>>
>> Congratulations Aaron!! Long overdue for sure!
>>
>>
>> On Mon, Mar 3, 2025 at 16:25 Patrick McFadin  wrote:
>>
>> The Apache Cassandra PMC is very happy to announce that Aaron Ploetz has
>> accepted the invitation to become a committer!
>>
>> Aaron has been tireless in his mission to help every single Cassandra
>> operator on planet Earth. If you don't believe me, check out his Stack
>> Overflow profile page: https://stackoverflow.com/users/1054558/aaron
>> He's been a continuous speaker on Cassandra topics and is one of the
>> coordinators for the Planet Cassandra meetup. Those are just the
>> recent highlights.
>>
>> Please join us in congratulating and welcoming Aaron.
>>
>> The Apache Cassandra PMC members
>>
>>

Re: Welcome Ekaterina Dimitrova as Cassandra PMC member

[Aaron]

Welcome Ekaterina! Congratulations!!!

On Tue, Mar 4, 2025 at 2:50 PM Yifan Cai  wrote:

> Congratulations!
> --
> *From:* Dmitry Konstantinov 
> *Sent:* Tuesday, March 4, 2025 12:40:48 PM
> *To:* dev@cassandra.apache.org 
> *Subject:* Re: Welcome Ekaterina Dimitrova as Cassandra PMC member
>
> Congrats Ekaterina!!
>
> On Tue, 4 Mar 2025 at 23:25, Paulo Motta  wrote:
>
> Aloha,
>
> The Project Management Committee (PMC) for Apache Cassandra is delighted
> to announce that Ekaterina Dimitrova has joined the PMC!
>
> Thanks a lot, Ekaterina, for everything you have done for the project all
> these years.
>
> The PMC - Project Management Committee - manages and guides the direction
> of the project, and is responsible for inviting new committers and PMC
> members to steward the longevity of the project.
>
> See https://community.apache.org/pmc/responsibilities.html if you're
> interested in learning more about the rights and responsibilities of PMC
> members.
>
> Please join us in welcoming Ekaterina Dimitrova to her new role in our
> project!
>
> Paulo, on behalf of the Apache Cassandra PMC
>
>
>
> --
> Dmitry Konstantinov
>

Re: Welcome Bernardo Botella as Cassandra Committer

[Aaron]

Congratulations Bernardo! Glad to see this happen!


On Tue, Mar 4, 2025 at 7:12 AM J. D. Jordan 
wrote:

> Congrats!
>
> On Mar 4, 2025, at 5:48 AM, Ekaterina Dimitrova 
> wrote:
>
> 
> Congratulations!! 🎉
>
> On Tue, 4 Mar 2025 at 6:15, Josh McKenzie  wrote:
>
>> Congrats Bernardo - it's been great collaborating with you thus far and
>> looking forward to more!
>>
>> On Tue, Mar 4, 2025, at 4:13 AM, Paulo Motta wrote:
>>
>> ¡Felicitaciones Bernardo! Well deserved!
>>
>> Cheers,
>>
>> Paulo
>>
>> On Tue, 4 Mar 2025 at 06:10 Soheil Rahsaz 
>> wrote:
>>
>> Congrats, Bernardo! Well deserved! 🎉 Looking forward to seeing your
>> continued impact on the project.
>>
>>
>>
>> On Tue, Mar 4, 2025 at 12:03 PM Dmitry Konstantinov 
>> wrote:
>>
>> Congrats Bernardo!!
>>
>> On Tue, 4 Mar 2025 at 10:58, Berenguer Blasi 
>> wrote:
>>
>> Congrats!
>>
>> On 4/3/25 8:30, Štefan Miklošovič wrote:
>> > The Project Management Committee (PMC) for Apache Cassandra has
>> > invited Bernardo Botella to become a committer and we are pleased to
>> > announce that he has accepted.
>> >
>> > Please join us in welcoming Bernardo Botella to his new role and
>> > responsibility in our project community.
>> >
>> > Stefan Miklosovic
>> >
>> > On behalf of the Apache Cassandra PMC
>>
>>
>>
>> --
>> Dmitry Konstantinov
>>
>>
>>

Re: [DISCUSS] 5.1 should be 6.0

[Aaron]

+1 to 6.0

And David makes a good point about making sure that we support 4.x to 6.0
upgrades.

Thanks,

Aaron

On Fri, Apr 11, 2025 at 1:03 AM guo Maxwell  wrote:

> +1 to 6.0
>
> Berenguer Blasi  于2025年4月11日周五 13:53写道：
>
>> +1 6.0
>> On 10/4/25 23:57, David Capwell wrote:
>>
>> +1 to 6.0
>> Strong +1 to T-3, we should support 4.0/4.1 to 6.0 upgrades.
>>
>> On Apr 10, 2025, at 2:18 PM, C. Scott Andreas 
>>  wrote:
>>
>> +1 6.0
>>
>> - Scott
>>
>> —
>> Mobile
>>
>> On Apr 10, 2025, at 1:34 PM, Jeremy Hanna 
>>  wrote:
>>
>>  +1 for 6.0 for TCM/Accord changes, making it easier to make a case to
>> upgrade dependencies like the Java/Python versions.
>>
>> On Apr 10, 2025, at 3:24 PM, Bernardo Botella
>>   wrote:
>>
>> +1 on 6.0
>>
>> On Apr 10, 2025, at 1:07 PM, Josh McKenzie 
>>  wrote:
>>
>> Let's keep this thread to just +1's on 6.0; I'll see about a proper
>> isolated [DISCUSS] thread for my proposal above hopefully tomorrow,
>> schedule permitting.
>>
>> On Thu, Apr 10, 2025, at 3:46 PM, Jeremiah Jordan wrote:
>>
>> +1 to 6.0
>>
>> On Thu, Apr 10, 2025 at 1:38 PM Josh McKenzie 
>> wrote:
>>
>>
>> +1 to 6.0.
>>
>> On Thu, Apr 10, 2025, at 2:28 PM, Jon Haddad wrote:
>>
>> Bringing this back up.
>>
>> I don't think we have any reason to hold up renaming the version.  We can
>> have a separate discussion about what upgrade paths are supported, but
>> let's at least address this one issue of version number so we can have
>> consistent messaging.  When i talk to people about the next release, I'd
>> like to be consistent with what I call it, and have a unified voice as a
>> project.
>>
>> Jon
>>
>> On Thu, Jan 30, 2025 at 1:41 AM Mick Semb Wever  wrote:
>>
>> .
>>
>>
>> If you mean only 4.1 and 5.0 would be online upgrade targets, I would
>> suggest we change that to T-3 so you encompass all “currently supported”
>> releases at the time the new branch is GAed.
>>
>> I think that's better actually, yeah. I was originally thinking T-2 from
>> the "what calendar time frame is reasonable" perspective, but saying "if
>> you're on a currently supported branch you can upgrade to a release that
>> comes out" makes clean intuitive sense. That'd mean:
>>
>> 6.0: 5.0, 4.1, 4.0 online upgrades supported. Drop support for 4.0. API
>> compatible guaranteed w/5.0.
>> 7.0: 6.0, 5.0, 4.1 online upgrades supported. Drop support for 4.1. API
>> compatible guaranteed w/6.0.
>> 8.0: 7.0, 6.0, 5.0 online upgrades supported. Drop support for 5.0. API
>> compatible guaranteed w/7.0.
>>
>>
>>
>>
>> I like this.
>>
>>
>>
>>
>>

Re: Welcome David Capwell as Cassandra PMC Member!

[Aaron]

Congratulations David!

On Tue, Apr 29, 2025 at 9:16 AM Paulo Motta  wrote:

> Congrats David!
>
> On Tue, 29 Apr 2025 at 07:47 Ariel Weisberg  wrote:
>
>> Huzzah!
>>
>> On Mon, Apr 28, 2025, at 3:09 PM, Jon Haddad wrote:
>>
>> Hey everyone!
>>
>> The Project Management Committee (PMC) for Apache Cassandra is delighted
>> to announce that David Capwell has joined the PMC!
>>
>> Thank you David for all your contributions to the project over the years.
>>
>> The PMC - Project Management Committee - manages and guides the
>> direction of the project, and is responsible for inviting new committers
>> and PMC members to steward the longevity of the project.
>>
>> See https://community.apache.org/pmc/responsibilities.html if you're
>> interested in learning more about the rights and responsibilities of PMC
>> members.
>>
>> Please join us on welcoming David Capwell to his new role in our project!
>>
>> Jon, on behalf of the Apache Cassandra PMC
>>
>>
>>

Re: [VOTE][IP CLEARANCE] easy-cass-stress

[Aaron]

+1

On Thu, May 1, 2025 at 4:27 PM Dave Herrington 
wrote:

> +1 (nb)
>
> -Dave
>
> On Wed, Apr 30, 2025 at 8:16 AM Jordan West  wrote:
>
>> (general@incubator cc'd)
>>
>> Please vote on the acceptance of the easy-cass-stress (to be renamed
>> cassandra-stress) and its IP Clearance:
>>
>> https://incubator.apache.org/ip-clearance/cassandra-easy-cass-stress.html
>>
>> All consent from original authors of the donation, and tracking of
>> collected CLAs, is found in
>>
>> https://github.com/rustyrazorblade/easy-cass-stress/pull/41/files and
>> 
>> https://delicate-tail-8c0.notion.site/easy-cass-stress-submission-141ac849cc9d80a4972cc8623aa54667
>>
>> These do not all require acknowledgement before the vote.
>>
>> The code is prepared for donation at
>> https://github.com/rustyrazorblade/easy-cass-stress
>>
>> Once this vote passes we will request ASF Infra to move the
>> rustyrazorblade/easy-cass-stress as-is to apache/cassandra-stress. The main
>> branch and gh-pages branches, all tags, and all history, will be kept.  The
>> main branch will continue to be named main.
>>
>> PMC members, please check carefully the IP Clearance requirements before
>> voting.
>>
>> The vote will be open for 72 hours (or longer). Votes by PMC members
>>
>> are considered binding. A vote passes if there are at least three binding
>> +1s and no -1's.
>>
>> Thanks,
>>
>> Jordan
>>
>
>
> --
> -Dave
>
> David A. Herrington II
> President and Chief Engineer
> RhinoSource, Inc.
>
> *Data Lake Architecture, Cloud Computing and Advanced Analytics.*
>
> www.rhinosource.com
>

Re: Welcome Patrick McFadin as Cassandra Committer

[Aaron Ploetz]

Patrick FTW!!!

On Thu, Feb 2, 2023 at 12:32 PM Joseph Lynch  wrote:

> W! Congratulations Patrick!!
>
> -Joey
>
> On Thu, Feb 2, 2023 at 9:58 AM Benjamin Lerer  wrote:
>
>> The PMC members are pleased to announce that Patrick McFadin has accepted
>> the invitation to become committer today.
>>
>> Thanks a lot, Patrick, for everything you have done for this project and
>> its community through the years.
>>
>> Congratulations and welcome!
>>
>> The Apache Cassandra PMC members
>>
>

New episode of The Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to the next episode:
https://drive.google.com/file/d/1nvHs7o4JJC2P18mtR5MrbnNoeW5f44j1/view?usp=sharing

s2Ep1 - Patrick McFadin

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
by Saturday, March 4th (19:00 UTC).

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

For my guest pipeline, I have recording sessions scheduled with:
- Aaron Morton
- Loren Sands-Ramshaw (Temporal)

And I'm currently trying to nail down a time with Valeri:
- Valeri Karpov (MeanIT Software)

Thanks, everyone!

Aaron Ploetz

Re: Degradation of availability when using NTS and RF > number of racks

[Aaron Ploetz]

> I think it would be a worse experience to not warn and let the user
discover later when they can't write at QUORUM.

Agree.

Should we add a note in the cassandra.yaml comments as well?  Maybe in the
spot where default_keyspace_rf is defined?  On the other hand, that section
is pretty "wordy" already.  But calling it out in the yaml might not be a
bad idea.

Thanks,

Aaron


On Tue, Mar 7, 2023 at 11:12 AM Derek Chen-Becker 
wrote:

> I think that the warning would only be thrown in the case where a
> potentially QUORUM-busting configuration is used. I think it would be a
> worse experience to not warn and let the user discover later when they
> can't write at QUORUM.
>
> Cheers,
>
> Derek
>
> On Tue, Mar 7, 2023 at 9:32 AM Jeremiah D Jordan <
> jeremiah.jor...@gmail.com> wrote:
>
>> I agree with Paulo, it would be nice if we could figure out some way to
>> make new NTS work correctly, with a parameter to fall back to the “bad”
>> behavior, so that people restoring backups to a new cluster can get the
>> right behavior to match their backups.
>> The problem with only fixing this in a new strategy is we have a ton of
>> tutorials and docs out there which tell people to use NTS, so it would be
>> great if we could keep “use NTS” as the recommendation.  Throwing a warning
>> when someone uses NTS is kind of user hostile.  If someone just read some
>> tutorial or doc which told them “make your key space this way” and then
>> when they do that the database yells at them telling them they did it
>> wrong, it is not a great experience.
>>
>> -Jeremiah
>>
>> > On Mar 7, 2023, at 10:16 AM, Benedict  wrote:
>> >
>> > My view is that if this is a pretty serious bug. I wonder if
>> transactional metadata will make it possible to safely fix this for users
>> without rebuilding (only via opt-in, of course).
>> >
>> >> On 7 Mar 2023, at 15:54, Miklosovic, Stefan <
>> stefan.mikloso...@netapp.com> wrote:
>> >>
>> >> Thanks everybody for the feedback.
>> >>
>> >> I think that emitting a warning upon keyspace creation (and
>> alteration) should be enough for starters. If somebody can not live without
>> 100% bullet proof solution over time we might choose some approach from the
>> offered ones. As the saying goes there is no silver bullet. If we decide to
>> implement that new strategy, we would probably emit warnings anyway on NTS
>> but it would be already done so just new strategy would be provided.
>> >>
>> >> 
>> >> From: Paulo Motta 
>> >> Sent: Monday, March 6, 2023 17:48
>> >> To: dev@cassandra.apache.org
>> >> Subject: Re: Degradation of availability when using NTS and RF >
>> number of racks
>> >>
>> >> NetApp Security WARNING: This is an external email. Do not click links
>> or open attachments unless you recognize the sender and know the content is
>> safe.
>> >>
>> >>
>> >>
>> >> It's a bit unfortunate that NTS does not maintain the ability to lose
>> a rack without loss of quorum for RF > #racks > 2, since this can be easily
>> achieved by evenly placing replicas across all racks.
>> >>
>> >> Since RackAwareTopologyStrategy is a superset of
>> NetworkTopologyStrategy, can't we just use the new correct placement logic
>> for newly created keyspaces instead of having a new strategy?
>> >>
>> >> The placement logic would be backwards-compatible for RF <= #racks. On
>> upgrade, we could mark existing keyspaces with RF > #racks with
>> use_legacy_replica_placement=true to maintain backwards compatibility and
>> log a warning that the rack loss guarantee is not maintained for keyspaces
>> created before the fix. Old keyspaces with RF <=#racks would still work
>> with the new replica placement. The downside is that we would need to keep
>> the old NTS logic around, or we could eventually deprecate it and require
>> users to migrate keyspaces using the legacy placement strategy.
>> >>
>> >> Alternatively we could have RackAwareTopologyStrategy and fail NTS
>> keyspace creation for RF > #racks and indicate users to use
>> RackAwareTopologyStrategy to maintain the quorum guarantee on rack loss or
>> set an override flag "support_quorum_on_rack_loss=false". This feels a bit
>> iffy though since it could potentially confuse users about when to use each
>> strategy.
>> >>
>> >> On Mon, Mar 6, 

New episode of The Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to the next episode:
https://drive.google.com/file/d/1_EOBpG3yiuptDJ-PU-3a7amSVvi7pgM8/view?usp=sharing

s2Ep2 - Aaron Morton

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
by Saturday, March 11th (22:00 UTC).

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

I have also recorded a session with Loren Sands-Ramshaw (Temporal), and
expect to submit that for approval tomorrow.  It will be the last one to
come out before Cassandra Forward.

For my guest pipeline, I have recording sessions scheduled with:
- Valeri Karpov (MeanIT Software)

Thanks, everyone!

Aaron Ploetz

New episode of The Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to the next episode:
https://drive.google.com/file/d/1IePasf681bU-7xRNl4tBzWvVG28y4tQK/view?usp=share_link

s2Ep3 - Loren Sands-Ramshaw
(You may have to download it to play)

FYI - Experimenting with a video podcast on this one.

It will remain in staging for 72 hours, going live (assuming no objections)
by Sunday, March 12th (17:00 UTC).

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

For my guest pipeline, I have recording sessions scheduled with:
- Valeri Karpov (MeanIT Software)

Looking for additional guests, so if you know someone who has a great use
case, let me know!

Thanks, everyone!

Aaron Ploetz

Re: Welcome our next PMC Chair Josh McKenzie

[Aaron Ploetz]

Congratulations, Josh!

And of course, thank you Mick for all you've done for the project while in
the PMC Chair role!

On Thu, Mar 23, 2023 at 7:44 AM Derek Chen-Becker 
wrote:

> Congratulations, Josh!
>
> On Thu, Mar 23, 2023, 4:23 AM Mick Semb Wever  wrote:
>
>> It is time to pass the baton on, and on behalf of the Apache Cassandra
>> Project Management Committee (PMC) I would like to welcome and congratulate
>> our next PMC Chair Josh McKenzie (jmckenzie).
>>
>> Most of you already know Josh, especially through his regular and
>> valuable project oversight and status emails, always presenting a balance
>> and understanding to the various views and concerns incoming.
>>
>> Repeating Paulo's words from last year: The chair is an administrative
>> position that interfaces with the Apache Software Foundation Board, by
>> submitting regular reports about project status and health. Read more about
>> the PMC chair role on Apache projects:
>> - https://www.apache.org/foundation/how-it-works.html#pmc
>> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
>> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>>
>> The PMC as a whole is the entity that oversees and leads the project and
>> any PMC member can be approached as a representative of the committee. A
>> list of Apache Cassandra PMC members can be found on:
>> https://cassandra.apache.org/_/community.html
>>
>

New episode of The Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to the next episode:
https://drive.google.com/file/d/1YoHbFwADEESdBgzhFgm43XVYTGatTBsU/view?usp=sharing

s2e4 - Val Karpov (Mongoose)
(You may have to download it to play)

It will remain in staging for 72 hours, going live (assuming no objections)
by Monday, April 3rd.

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

For my guest pipeline, I'm trying to coordinate with Rahul Singh.  But I am
looking for additional guests.  So if you know someone who has a great use
case, let me know!

Thanks, everyone!

Aaron Ploetz

New episode of The Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to the next episode:
https://drive.google.com/file/d/1E9HTuwkRf9W6W-9tM6PB0da8SRAd3g5j/view?usp=sharing

s2e5 - Rahul Singh (Anant)
(You may have to download it to play)

It will remain in staging for 72 hours, going live (assuming no objections)
by Sunday, April 16th.

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

For my guest pipeline, I'm trying to coordinate with Rahul Singh.  But I am
looking for additional guests.  So if you know someone who has a great use
case, let me know!

Thanks, everyone!

Aaron Ploetz

New episode of The Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to the next episode:
https://drive.google.com/file/d/1E9HTuwkRf9W6W-9tM6PB0da8SRAd3g5j/view?usp=sharing

s2e5 - Rahul Singh (Anant)
(You may have to download it to play)

It will remain in staging for 72 hours, going live (assuming no objections)
by Sunday, April 16th.

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

For my guest pipeline, I'm trying to coordinate with Charna Parkey and Mary
Grygleski.  But I am looking for additional guests.  So if you know someone
who has a great use case, let me know!

Thanks, everyone!

Aaron Ploetz

New episode of The Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to the next episode:
https://drive.google.com/file/d/1Rzmvj3db_chj6ZLvQ5G2bBLxIF_QaPCV/view?usp=sharing

s2e6 - Mary Grygleski (DataStax)
(You may have to download it to play)

It will remain in staging for 72 hours, going live (assuming no objections)
by Saturday, June 17th.

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

For my guest pipeline, I'm working on coordinating with Charna Parkey and
Josh McKenzie.  But I am looking for additional guests.  So if you know
someone who has a great use case, let me know!

Thanks, everyone!

Aaron Ploetz

New episode of The Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to the next episode (audio only):
https://drive.google.com/file/d/1HmhtR1stWmtD8gJTFh3gKIye7lQKXN1y/view?usp=sharing

s2e7 - German Eighberger and Theo van Kraay (Microsoft)
(You may have to download it to play)

It will remain in staging for 72 hours, going live (assuming no objections)
by Monday, July 10th.

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

For my guest pipeline, I'm still coordinating with Josh McKenzie.  But I am
looking for additional guests.  So if you know someone who would be a
great guest, let me know!

Thanks, everyone!

Aaron

New episode of The Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to the next episode (video):
https://drive.google.com/file/d/1nu_h8JczmAI59GhnDunTI9Oew-TxmzNU/view?usp=sharing

s2e8 - Otavio Santana
(You may have to download it to play)

It will remain in staging for 72 hours, going live (assuming no objections)
by Monday, August 28th.

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

I am looking for additional guests.  So if you know someone who would be a
great guest, please let me know!

Thanks, everyone!

Aaron

New episode of The Apache Cassandra(R) Corner podcast!

[Aaron Ploetz]

Link to the next episode (video):
https://drive.google.com/file/d/1tm96RLPUesm3dXZYSVzzrIGKlSQsfag8/view?usp=sharing

s2e9 - Aaron Morton
(You may have to download it to play)

It will remain in staging for 72 hours, going live (assuming no objections)
by Monday, September 11th.

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

I am looking for additional guests.  So if you know someone who would be a
great guest, please let me know!

Thanks, everyone!

Aaron

New episode of the Apache Cassandra(R) Corner podcast

[Aaron Ploetz]

s2e10 - Dr. Charna Parkey
(You may have to download it to play)

https://drive.google.com/file/d/1L8gw--kRLDEit1Vmk51u32LQVIKOT6yr/view?usp=drive_link

It will remain in staging for 72 hours, going live (assuming no objections)
by Thursday, September 21st.

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

I am looking for additional guests.  So if you know someone who would be a
great guest, please let me know!

Thanks, everyone!

Aaron

New episode of the Apache Cassandra(R) Corner podcast

[Aaron Ploetz]

s2e11 - Sarma Pydipally
(You may have to download it to play)

https://drive.google.com/file/d/1X98HjR0G3wnRaUUuUUvsDyvx05QZYXXN/view?usp=drive_link

It will remain in staging for 72 hours, going live (assuming no objections)
by Thursday, October 19th.

If anyone should have any questions or comments, or if you want to be a
guest, please reach out to me.

I am looking for additional guests.  So if you know someone who would be a
great guest, please let me know!

Thanks, everyone!

Aaron

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

[Aaron Ploetz]

>
> If I had to pick a month of the year to release software used by large
> enterprises, it probably would be something like March instead of December.
> I have no good research to back that up, of course...
>

Can confirm. Many large enterprises (especially retailers) have been in
"holiday code freeze" for a few weeks already. Infrastructure teams will be
freezing all changes shortly (they get a few "buffer" weeks to scale-out
for holiday traffic). Everything is basically locked-down until the week
after New Years.

Once infra teams can push changes again, they'll likely have a backlog of
findings from their security team, indicating a list of things that need to
be patched/updated across all of their server instances. At Target, we
usually had to spend all of January playing "catch-up" to make the security
scans happy again.

Maybe by mid-February, they'll be ready to entertain doing a database
update. So the February/March timeframe is a good choice.

Aaron


On Mon, Oct 23, 2023 at 1:12 PM Josh McKenzie  wrote:

> If I had to pick a month of the year to release software used by large
> enterprises, it probably would be something like March instead of December.
>
> That's... a good point. If we end up on a cadence of major's in December
> (since we slipped to then for 4.1 and inherit that from that calendar year
> "pressure") we're setting ourselves up to release right in the largest
> consistent change-freeze window I know of for most users.
>
> It will be another 2.2 release.
>
> Let me live on with the stories I tell myself about the hordes of Windows
> users that appreciated Windows support before the Storage Engine rewrite,
> thank you very much. :D
>
> On Mon, Oct 23, 2023, at 1:57 PM, Caleb Rackliffe wrote:
>
> ...or like the end of January. Either way, feel free to ignore the "aside"
> :)
>
> On Mon, Oct 23, 2023 at 12:53 PM Caleb Rackliffe 
> wrote:
>
> Kind of in the same place as Benedict/Aleksey.
>
> If we release a 5.1 in, let's say...March of next year, the number of 5.0
> users is going to be very minimal. Nobody is going to upgrade anything
> important from now through the first half of January anyway, right? They're
> going to be making sure their existing clusters aren't exploding.
>
> (We still want TCM/Accord to be available to people to test by Summit, but
> that feels unrelated to whether we cut a 5.1 branch...)
>
> Aside: If I had to pick a month of the year to release software used by
> large enterprises, it probably would be something like March instead of
> December. I have no good research to back that up, of course...
>
> On Mon, Oct 23, 2023 at 12:19 PM Benedict  wrote:
>
>
> To be clear, I’m not making an argument either way about the path forwards
> we should take, just concurring about a likely downside of this proposal. I
> don’t have a strong opinion about how we should proceed.
>
>
> On 23 Oct 2023, at 18:16, Benedict  wrote:
>
> 
>
> I agree. If we go this route we should essentially announce an immediate
> 5.1 alpha at the same time as 5.0 GA, and I can’t see almost anybody
> rolling out 5.0 with 5.1 so close on its heels.
>
>
> On 23 Oct 2023, at 18:11, Aleksey Yeshchenko  wrote:
>
> I’m not so sure that many folks will choose to go 4.0->5.0->5.1 path
> instead of just waiting longer for TCM+Accord to be in, and go 4.0->5.1 in
> one hop.
>
> Nobody likes going through these upgrades. So I personally expect 5.0 to
> be a largely ghost release if we go this route, adopted by few, just a
> permanent burden on the merge path to trunk.
>
> Not to say that there isn’t valuable stuff in 5.0 without TCM and Accord -
> there most certainly is - but with the expectation that 5.1 will follow up
> reasonably shortly after with all that *and* two highly anticipated
> features on top, I just don’t see the point. It will be another 2.2 release.
>
>
> On 23 Oct 2023, at 17:43, Josh McKenzie  wrote:
>
> We discussed that at length in various other mailing threads Jeff - kind
> of settled on "we're committing to cutting a major (semver MAJOR or MINOR)
> every 12 months but want to remain flexible for exceptions when
> appropriate".
>
> And then we discussed our timeline for 5.0 this year and settled on the
> "let's try and get it out this calendar year so it's 12 months after 4.1,
> but we'll grandfather in TCM and Accord past freeze date if they can make
> it by October".
>
> So that's the history for how we landed here.
>
> 2) Do we drop the support of 3.0 and 3.11 after 5.0.0 is out or after
> 5.1.0 is?
>
> This is my understanding, yes. Deprecation and support d

Re: [VOTE] Release Apache Cassandra 5.0-beta1

[Aaron Ploetz]

Even though my opinion doesn't really count here, I do feel compelled to
mention that:

 - No one expects a "beta" release to be perfect, but it does signal that
it is "close" to being ready.
 - An "alpha" release is in fact a LOT scarier than a "beta" release.

>From a user perspective, if I was coaching dev teams on selecting a build
based on newly available features, I would help them build up a dev/stage
cluster based on a beta (and make the "beta" part very clear to them).
However an alpha version just doesn't convey the same level of confidence.
When I test out an "alpha" of anything, I fully expect some things to just
be broken.

As for cutting a beta for the Summit; it makes sense that we'd want to get
some things fixed up before that. But it would also be great to be at the
point where we have a beta ready for folks to take a look at. We absolutely
could tell everyone to download the alpha and give it a spin. But more
people will be likely to do that for a beta than for an alpha.

Take that however you will.

Thanks,

Aaron


On Wed, Nov 29, 2023 at 9:54 AM Aleksey Yeshchenko 
wrote:

> -1 on cutting a beta1 in this state. An alpha2 would be acceptable now,
> but I’m not sure there is significant value to be had from it. Merge the
> fixes for outstanding issues listed above, then cut beta1.
>
> With TCM and Accord pushed into 5.1, SAI is the headliner user-visible
> feature. It is what we want users to test. If we are to drive more people
> to test SAI, we should resolve the issues that we ourselves know of first.
> Respect our users’ time and effort - don’t make them bump into known bugs.
>
> P.S. I don’t believe that ‘alpha' vs. ‘beta' really makes a significant
> difference to people’s willingness to try out the build. For most folks
> both feel too raw to play with, and most of the rest would be equally
> adventurous enough for an alpha *or* a beta. This is just my gut feeling
> vs. your gut feeling, in absence of hard data.
>
> On 28 Nov 2023, at 21:17, Mick Semb Wever  wrote:
>
>
>
> So then cutting an alpha2 is possible.
>>
>
>
> Possible, but still leaves alpha1 as our mitigation plan and alpha2 as our
> best plan.  Doesn't seem worth it IMHO.
>
>
>

New episode of the Apache Cassandra(R) Corner podcast

[Aaron Ploetz]

s2e13 - Jonathan Ellis
(You may have to download it to play)

https://drive.google.com/file/d/1XNfVyIrTM1AIdqzrSDeww7Xe05f8pIdD/view?usp=sharing

It will remain in staging for 72 hours, going live (assuming no objections)
by Monday, December 4th.

If anyone should have any questions or comments, please reach out to me.

Barring any additional sessions recorded live at the Cassandra Summit, this
is likely to be the last episode of 2023.

Thanks, everyone!

Aaron

Re: Voice of Apache (Feathercast) at summit?

[Aaron Ploetz]

Rich,

I'm happy to sit down for a session with you, as well!

Thanks,

Aaron


On Fri, Dec 8, 2023 at 8:05 AM Rahul Xavier Singh <
rahul.xavier.si...@gmail.com> wrote:

> I’m sure you have other people interested but would love to speak about
> the community aspect, how we’ve seen customers use it and how it continues
> to grow into what we need as technologists to help people build scalable
> platforms.
>
>
>
> On Tue, Dec 5, 2023 at 8:35 AM Rich Bowen  wrote:
>
>> Hey, folks. I'll be at Cassandra Summit next week, and was wondering if
>> any of you who might be there would be interested in doing a podcast
>> interview with me for Voice Of Apache (the podcast formerly known as
>> Feathercast - see https://feathercast.apache.org for context). Topics
>> might include something about 5.0, retrospectives on the last 13 years, or
>> whatever you think might be of interest.
>>
>> Let me know soon of anyone's interested/available, so I know to pack my
>> gear.
>>
>> Thanks!
>>
>> --Rich
>>
>

New episode of the Apache Cassandra(R) Corner!

[Aaron Ploetz]

s3e1 - Jon Haddad
(You may have to download it to play)

https://drive.google.com/file/d/1zZn8DSLvHiym3gx3V4IMlG8bkwnifP2F/view?usp=sharing

It will remain in staging for 72 hours, going live (assuming no objections)
by Thursday, February 29th.

If anyone should have any questions or comments, or if you or someone you
know wants to be a guest, please let me know!

Thanks, everyone!

Aaron

New episode of the Apache Cassandra(R) Corner!

[Aaron Ploetz]

s3e2 - Otavio Santana
(You may have to download it to play)

https://drive.google.com/file/d/1RZLP-mpq01LtYBbQPiYS0YbP4WKf0nKG/view?usp=drive_link

It will remain in staging for 72 hours, going live (assuming no objections)
by Thursday, April 11th.

If anyone should have any questions or comments, or if you or someone you
know wants to be a guest, please let me know!

Thanks, everyone!

Aaron

Re: Cassandra PMC Chair Rotation, 2024 Edition

[Aaron Ploetz]

Congratulations, Dinesh!

On Thu, Jun 20, 2024 at 10:51 AM Josh McKenzie  wrote:

> Another PMC Chair baton pass incoming! On behalf of the Apache Cassandra
> Project Management Committee (PMC) I would like to welcome and congratulate
> our next PMC Chair Dinesh Joshi (djoshi).
>
> Dinesh has been a member of the PMC for a few years now and many of you
> likely know him from his thoughtful, measured presence on many of our
> collective discussions as we've grown and evolved over the past few years.
>
> I appreciate the project trusting me as liaison with the board over the
> past year and look forward to supporting Dinesh in the role in the future.
>
> Repeating Mick (repeating Paulo's) words from last year: The chair is an
> administrative position that interfaces with the Apache Software Foundation
> Board, by submitting regular reports about project status and health. Read
> more about the PMC chair role on Apache projects:
> - https://www.apache.org/foundation/how-it-works.html#pmc
> - https://www.apache.org/foundation/how-it-works.html#pmc-chair
> - https://www.apache.org/foundation/faq.html#why-are-PMC-chairs-officers
>
> The PMC as a whole is the entity that oversees and leads the project and
> any PMC member can be approached as a representative of the committee. A
> list of Apache Cassandra PMC members can be found on:
> https://cassandra.apache.org/_/community.html
>

Re: EOL 2.1 series?

[Aaron Ploetz]

Speaking as a user with a few large clusters still running on 2.1, I think a 
final release of it with some additional fixes would be welcomed.  That being 
said, I thought we were holding off on EOLing 2.1 until 4.0 is released.  
Although, the timings probably don’t need to coincide.

In short, a (non-binding) final release of 2.1 is a good idea.

Thanks,

Aaron


> On Jan 7, 2019, at 8:01 PM, Michael Shuler  wrote:
> 
> It came to my attention on IRC a week or so ago, and following up on the
> ticket that someone asked if they should commit to 2.1, that developers
> have been actively ignoring the 2.1 branch. If we're not committing
> critical fixes there, even when we know they exist, I think it's time to
> just call it EOL an do one last release of the few fixes that did get
> committed. Comments?
> 
> Michael
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Google Season of Docs 2019 for Apache Cassandra

[Aaron Ploetz]

I’m willing to help as well.  Feel free to reach out!

Aaron Ploetz

> On Mar 12, 2019, at 8:37 PM, Rahul Singh  wrote:
> 
> Cool. I’m willing to help by taking sub sections of the overall effort. The 
> docs need a lot of TLC. Thanks ,
> 
> Rahul Singh
> Principal Architect | 1.202.390.9200 | rahul.si...@datastax.com
>> On Mar 12, 2019, 8:58 PM -0400, Ben Slater , 
>> wrote:
>> Hi Dinesh
>> 
>> Great idea. We should be able to find some Instaclustr people to help with
>> technical input (Stefan has already put his hand up).
>> 
>> I’m also happy to help with the application if that’s useful.
>> 
>> Cheers
>> Ben
>> 
>> ---
>> 
>> 
>> *Ben Slater*
>> *Chief Product Officer*
>> 
>> 
>> <https://www.facebook.com/instaclustr> <https://twitter.com/instaclustr>
>> <https://www.linkedin.com/company/instaclustr>
>> 
>> Read our latest technical blog posts here
>> <https://www.instaclustr.com/blog/>.
>> 
>> This email has been sent on behalf of Instaclustr Pty. Limited (Australia)
>> and Instaclustr Inc (USA).
>> 
>> This email and any attachments may contain confidential and legally
>> privileged information. If you are not the intended recipient, do not copy
>> or disclose its content, but please reply to this email immediately and
>> highlight the error to the sender and then immediately delete the message.
>> 
>> 
>> On Wed, 13 Mar 2019 at 08:12, Dinesh Joshi 
>> wrote:
>> 
>>> Hi all,
>>> 
>>> I came across GSoD 2019[1]. This is different from GSoC and focuses on
>>> improving documentation for Open Source projects. I think this would be
>>> beneficial for Cassandra especially with 4.0 coming up. However, working
>>> with a technical writer will require a substantial time commitment from us
>>> to bring them up to speed.
>>> 
>>> Are there any volunteers to help guide the technical writer if Cassandra
>>> is picked as a project?
>>> 
>>> On a side note, we can put together the application on the Confluence
>>> wiki. I will create a page and if anybody is interested in helping out with
>>> putting together the application, please feel free to collaborate on it.
>>> 
>>> Thanks,
>>> 
>>> Dinesh
>>> 
>>> [1] https://developers.google.com/season-of-docs/docs/timeline
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>> 
>>> 

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Staging website at cassandra.staged.apache.org

[Aaron Morton]

Thanks Mick, if there documentation somewhere on how we update the website
?

A

-
Aaron Morton
New Zealand
@aaronmorton

CEO
Apache Cassandra Consulting
http://www.thelastpickle.com


On Tue, 21 Apr 2020 at 18:40, Mick Semb Wever  wrote:

> For our cassandra-website repository, any changes to our website can now
> first be staged at https://cassandra.staged.apache.org/
>
> The staged website comes from the content/ directory on the `asf-staging`
> branch.
>
> regards,
> Mick
>

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

[Aaron Morton]

+1

-
Aaron Morton
New Zealand
@aaronmorton

CEO
Apache Cassandra Consulting
http://www.thelastpickle.com


On Thu, 25 Jun 2020 at 19:46, Benedict Elliott Smith 
wrote:

> The purpose of this document is to define only how the project makes
> decisions, and it lists "tenets" of conduct only as a preamble for
> interpreting the rules on decision-making.  The authors' intent was to lean
> on this to minimise the rigidity and prescriptiveness in the formulation of
> the rules (so that we could e.g. use "reasonable" repeatedly, instead of
> specifying precise expectations), in part because this is our first attempt
> to codify such rules, and in part because rigidity can cause unnecessary
> friction to a project that mostly runs smoothly.
>
> The document provides an avenue for resolving disputes in decision-making
> when these assumptions on behaviour breakdown. However its scope definitely
> isn't, at least in my opinion, addressing misbehaviour by individuals (i.e.
> one of the serious breaches listed in part 5 of the Apache CoC), which it
> seems to me you are addressing here?
>
> Since we reference the ASF CoC, and the ASF provides its own guide for
> handling CoC complaints (including within projects), that applies to that
> very CoC (and which you referenced), it's unclear to me what you're looking
> for.  Are you looking for a more project-specific CoC with different
> guidelines for reporting?  This is something you would be welcome to
> undertake, and seek consensus for.
>
>
>
>
> On 25/06/2020, 02:38, "Dinesh Joshi"  wrote:
>
> > On Jun 24, 2020, at 6:01 PM, Brandon Williams 
> wrote:
> >
> > On Wed, Jun 24, 2020 at 5:43 PM Dinesh Joshi 
> wrote:
> >> 1. How/Who/Where are we planning to deal with Code of Conduct
> violations? I assume this should be private@ but the document does not
> call it out as such. We should call it out explicitly as part of the PMC
> responsibilities. We should also clarify how and where are CoC violations
> against PMC members reported and handled? Should they go to ASF?
> >
> > I think if we assume good intent, this will be a non-issue.  People
> > may make mistakes, but I try to have faith they will realize them and
> > act accordingly when told so without any need to escalate.
>
> We need to spell out in the document how and where the CoC violations
> are reported irrespective of the role of the person in the community. This
> is a critical point to address. ASF spells this out very clearly[1]. We
> should have a similar statement in the Project Governance document,
> otherwise it feels incomplete to me.
>
> Dinesh
>
> [1]
> http://www.apache.org/foundation/policies/conduct.html#reporting-guidelines
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: Monthly community blog - thoughts?

[Aaron Ploetz]

I think this is an awesome idea, and I'm happy to help in any way that I
can.

Possible post topics:
-(new/existing) features
-common modeling practices
-community member "spotlight"
-tooling (Reaper, Medusa, K8s operator, etc...)

Thanks,

Aaron


On Fri, Oct 16, 2020 at 5:30 AM Horia Mocioi  wrote:

> Sounds good.
>
> How should we send suggestions? Via email or we can do it ourselves?
>
> Regards,
> Horia
>
> On Thu, Oct 15, 2020 at 11:58 PM Erick Ramirez  >
> wrote:
>
> > What a great idea! This is a good signal on how active the community is.
> >
> > I'm happy to help with proof-reading/reviews.
> >
> > P.S. The section on Harry contains HTML code. :)
> >
>

Re: New Cassandra website for review

[Aaron Ploetz]

Nice work, looks great!

Thanks,

Aaron


> On Feb 26, 2021, at 3:36 PM, Melissa Logan  wrote:
> 
> Hi all,
> 
> We are excited to share the almost-complete Cassandra website design
> (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony Grosso, Mick Semb
> Weaver, Josh Levy, Chris Thornett, Diogenese Topper, and a few others who
> contributed to this effort.
> 
> Note: There are a few updates to be made prior to launch, but we wanted to
> share to get initial input and signoff to begin the final port to Antora.
> 
> To be completed:
> 
>   - *Homepage: *The logos are placeholders -- they're being updated and
>   resized (pulled from case studies page).
>   - *Docs* will be added once 4.0 documentation is complete. Design
>   will match new site.
>   - *Case Studies * logos are being updated and resized, so ignore broken
>   links.
> 
> If you have case studies or resources -- or community photos --
> please reply to me and we'll add.
> 
> Site for review: https://cassandra.staged.apache.org/
> 
> https://issues.apache.org/jira/browse/CASSANDRA-16115
> 
> Melissa Logan

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 2.1.8

[Aaron Morton]

> 2.1.8 release vote right on top of 2.1.6 and 2.1.7.
I havent dug into the specific issues, but given the small list of changes
and release velocity, those two older releases should probably be
considered an "upgrade now" trigger with clients.

​Thanks for the heads up.

Guess we should keep a list of this sort of thing somewhere.

A​


-----
Aaron Morton
New Zealand
@aaronmorton

Co-Founder & Principal Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

On Mon, Jul 6, 2015 at 12:52 PM, Gary Dusbabek  wrote:

> +1
>
> On Mon, Jul 6, 2015 at 12:04 PM, Jake Luciani  wrote:
>
> > I propose the following artifacts for release as 2.1.8.
> >
> > sha1: db39257c34152f6ccf8d53784cea580dbfe1edad
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.8-tentative
> > Artifacts:
> >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1063/org/apache/cassandra/apache-cassandra/2.1.8/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1063/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~jake
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/BFYiEO (CHANGES.txt)
> > [2]: http://goo.gl/24XaPp (NEWS.txt)
> >
>

Re: Problem while configuring key and row cache?

[aaron morton]

Use info….

$ bin/nodetool -h localhost info
…
Key Cache: size 672 (bytes), capacity 52428768 (bytes), 12 hits, 17 
requests, 0.706 recent hit rate, 14400 save period in seconds
Row Cache: size 0 (bytes), capacity 0 (bytes), 0 hits, 0 requests, NaN 
recent hit rate, 0 save period in seconds

Cheers

-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com

On 22/08/2012, at 5:18 PM, Amit Handa  wrote:

> Hi,
> 
> Thanks Jonathan for your reply.
> I modified key_cache_size_in_mb and row_cache_size_in_mb values inside
> cassandra.yaml. but not able to see it's effect using command " *./nodetool
> -h 107.108.189.212 cfstats*". Can u let me know how to verify that the
> setting for key_cache_size and row_chache_size has taken place.
> 
> With Regards,
> Amit
> 
> 
> On Tue, Aug 21, 2012 at 8:19 PM, Jonathan Ellis  wrote:
> 
>> setcachecapacity is obsolete in 1.1+.  Looks like we missed removing
>> it from nodetool.  See
>> http://www.datastax.com/dev/blog/caching-in-cassandra-1-1 for
>> background.
>> 
>> (Moving to users@.)
>> 
>> On Tue, Aug 21, 2012 at 8:19 AM, Amit Handa  wrote:
>>> I started exploring apache cassandra 1.1.3. I am facing problem with how
>> to
>>> improve performance of cassandra using caching configurations.
>>> I tried setting following configurations:
>>> 
>>> ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 25 0
>>> ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 0 25
>>> ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 25
>> 25
>>> ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 444 444
>>> 
>>> 
>>> But when i am checking that this particula configuration are really been
>>> configured using command:
>>> ./nodetool -h 107.108.189.212 cfstats
>>> 
>>> it's showing following results for keySpace DemoUser and column Family
>>> Users:
>>> *Keyspace: DemoUser
>>>Read Count: 21914
>>>Read Latency: 0.08268495026010769 ms.
>>>Write Count: 87656
>>>Write Latency: 0.06009481381765082 ms.
>>>Pending Tasks: 0
>>>Column Family: Users
>>>SSTable count: 1
>>>Space used (live): 1573335
>>>Space used (total): 1573335
>>>Number of Keys (estimate): 22016
>>>Memtable Columns Count: 0
>>>Memtable Data Size: 0
>>>Memtable Switch Count: 1
>>>Read Count: 21914
>>>Read Latency: 0.083 ms.
>>>Write Count: 87656
>>>Write Latency: 0.060 ms.
>>>Pending Tasks: 0
>>>Bloom Filter False Postives: 0
>>>Bloom Filter False Ratio: 0.0
>>>Bloom Filter Space Used: 41104
>>>Compacted row minimum size: 150
>>>Compacted row maximum size: 179
>>>Compacted row mean size: 179 *
>>> 
>>> I am unable to see the effect of above setcachecapacity command. Let me
>>> know how i can configure the cache capacity, and check it's effect.
>>> 
>>> With Regards,
>>> Amit
>> 
>> 
>> 
>> --
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder of DataStax, the source for professional Cassandra support
>> http://www.datastax.com
>> 

Re: Batch Truncate using Hector 1.0-5

[aaron morton]

The hector user list is the best place this question 
https://groups.google.com/forum/?fromgroups#!forum/hector-users

Cheers

-
Aaron Morton
Freelance Cassandra Developer
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 22/11/2012, at 8:53 AM, Amitabha Karmakar  
wrote:

> Hi,
> 
> Is there any way I could do a batch truncate using hector 1.0-5 ?
> 
> Thanks !

Re: Proposal: require Java7 for Cassandra 2.0

[aaron morton]

+1
-
Aaron Morton
Freelance Cassandra Developer
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 7/02/2013, at 11:21 AM, Jonathan Ellis  wrote:

> Java 6 EOL is this month.  Java 7 will be two years old when C* 2.0
> comes out (July).  Anecdotally, a bunch of people are running C* on
> Java7 with no issues, except for the Snappy-on-OS-X problem (which
> will be moot if LZ4 becomes our default, as looks likely).
> 
> Upgrading to Java7 lets us take advantage of new (two year old)
> features as well as simplifying interoperability with other
> dependencies, e.g., Jetty's BlockingArrayQueue requires java7.
> 
> Thoughts?
> 
> -- 
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder, http://www.datastax.com
> @spyced

Re: ApacheCon North America

[aaron morton]

I'll be there from the evening on the Wednesday 27th to Friday 1st midday.

Talking on Thursday afternoon about C* internals. 
  
Cheers

-
Aaron Morton
Freelance Cassandra Developer
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 12/02/2013, at 4:26 AM, Eric Evans  wrote:

> Hi All
> 
> It's now about 2 weeks until ApacheCon North America, which is taking
> place Sunday 24th Feb - Thursday 28th in Portland. Quite a few people
> from our project will be there, and we'd love to see you all!
> 
> If you haven't already registered for the conference, then we've some
> good news - we've managed to snag a 20% discount for you! To register
> with the 20% off, use code PMC or the link
> http://acna13.eventbrite.com/?discount=PMC
> 
> To see what the talks are, including the ones relating to Cassandra,
> please see the schedule -http://na.apachecon.com/schedule/
> 
> Would you like to get more involved in the project?  A number of
> people will be at the (Free!) Hackathon on the Monday. Ours will focus
> on CQL drivers, but if you would like to learn more about
> contributing, get some mentoring on a patch, or help collaborate on
> some fixes, then by all means come join us.  If you'd like to come,
> whether you can make it to the main conference or not, the details are
> on the ApacheCon wiki: http://wiki.apache.org/apachecon/HackathonNA13
> 
> Also talking of free, there will be a BarCamp on the Sunday. This is
> open to everyone, Portland natives and conference-goers alike, and
> should be a great chance to share new ideas and learn about existing +
> upcoming projects. To sign up to come to that, or learn more, it's
> http://wiki.apache.org/apachecon/BarCampApachePortland
> 
> Hopefully see some of you in Portland in a few weeks!
> ---
> 
> Thanks
> 
> --
> Eric Evans
> Acunu | http://www.acunu.com | @acunu

Re: Rename failed while cassandra is starting up

[aaron morton]

Replying on the user group.

-
Aaron Morton
Freelance Cassandra Consultant
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 14/04/2013, at 3:50 PM, Boris Yen  wrote:

> Hi All,
> 
> Recently, we encountered an error on 1.0.12 that prevented cassandra from
> starting up. From the log messages, it looked like the table/keyspace was
> opened before the scrubDataDirectories was executed. This created a race
> condition between two threads. One was trying to rename files while the
> other was trying to remove tmp files. I was wondering if anyone could
> provide us some information or workaround for this.
> 
> INFO [MemoryMeter:1] 2013-04-09 02:49:39,868 Memtable.java (line 186)
> CFS(Keyspace='fmzd', ColumnFamily='alarm.fmzd_alarm_category') liveRatio is
> 3.7553409423470883 (just-counted was 3.1413828689370487).  calculation took
> 2ms for 265 columns
> INFO [SSTableBatchOpen:1] 2013-04-09 02:49:39,868 SSTableReader.java (line
> 153) Opening /test/db/data/fmzd/ap.fmzd_ap_meshRole-hd-2 (83 bytes)
> INFO [SSTableBatchOpen:2] 2013-04-09 02:49:39,868 SSTableReader.java (line
> 153) Opening /test/db/data/fmzd/ap.fmzd_ap_meshRole-hd-1 (123 bytes)
> INFO [Creating index: alarm.fmzd_alarm_category] 2013-04-09 02:49:39,874
> ColumnFamilyStore.java (line 705) Enqueuing flush of
> Memtable-alarm.fmzd_alarm_category@413535513(14025/65835 serialized/live
> bytes, 275 ops)
> INFO [OptionalTasks:1] 2013-04-09 02:49:39,877 SecondaryIndexManager.java
> (line 184) Creating new index : ColumnDefinition{name=6d65736853534944,
> validator=org.apache.cassandra.db.marshal.UTF8Type, index_type=KEYS,
> index_name='fmzd_ap_meshSSID'}
> INFO [SSTableBatchOpen:1] 2013-04-09 02:49:39,895 SSTableReader.java (line
> 153) Opening /test/db/data/fmzd/ap.fmzd_ap_meshSSID-hd-1 (122 bytes)
> INFO [SSTableBatchOpen:2] 2013-04-09 02:49:39,896 SSTableReader.java (line
> 153) Opening /test/db/data/fmzd/ap.fmzd_ap_meshSSID-hd-2 (82 bytes)
> INFO [OptionalTasks:1] 2013-04-09 02:49:39,900 SecondaryIndexManager.java
> (line 184) Creating new index :
> ColumnDefinition{name=6d6f62696c6974795a6f6e654944,
> validator=org.apache.cassandra.db.marshal.UTF8Type, index_type=KEYS,
> index_name='fmzd_ap_mobilityZoneUUID'}
> ERROR [FlushWriter:1] 2013-04-09 02:49:39,916 AbstractCassandraDaemon.java
> (line 139) Fatal exception in thread Thread[FlushWriter:1,5,main]
> java.io.IOError: java.io.IOException: rename failed of
> /test/db/data/fmzd/alarm.fmzd_alarm_alarmCode-hd-21-Data.db
> at
> org.apache.cassandra.io.sstable.SSTableWriter.rename(SSTableWriter.java:375)
> at
> org.apache.cassandra.io.sstable.SSTableWriter.closeAndOpenReader(SSTableWriter.java:319)
> at
> org.apache.cassandra.io.sstable.SSTableWriter.closeAndOpenReader(SSTableWriter.java:302)
> at org.apache.cassandra.db.Memtable.writeSortedContents(Memtable.java:276)
> at org.apache.cassandra.db.Memtable.access$400(Memtable.java:49)
> at org.apache.cassandra.db.Memtable$4.runMayThrow(Memtable.java:299)
> at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: java.io.IOException: rename failed of
> /test/db/data/fmzd/alarm.fmzd_alarm_alarmCode-hd-21-Data.db
> at
> org.apache.cassandra.utils.FBUtilities.renameWithConfirm(FBUtilities.java:355)
> at
> org.apache.cassandra.io.sstable.SSTableWriter.rename(SSTableWriter.java:371)
> ... 9 more
> INFO [SSTableBatchOpen:1] 2013-04-09 02:49:39,917 SSTableReader.java (line
> 153) Opening /test/db/data/fmzd/ap.fmzd_ap_mobilityZoneUUID-hd-1 (312 bytes)
> INFO [FlushWriter:2] 2013-04-09 02:49:39,916 Memtable.java (line 246)
> Writing Memtable-alarm.fmzd_alarm_alarmCode@402202831(2958/22542
> serialized/live bytes, 58 ops)
> ERROR [main] 2013-04-09 02:49:39,916 AbstractCassandraDaemon.java (line
> 373) Exception encountered during startup
> java.io.IOError: java.io.IOException: Failed to delete
> /test/db/data/fmzd/alarm.fmzd_alarm_alarmCode-tmp-hd-21-Statistics.db
> at
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:372)
> at
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:415)
> at
> org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:193)
> at
> org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:356)
> at
> org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:107)
> Caused by: java.io.IOException: Failed to delete
> /test/db/data/fmzd/alarm.fmzd_ala

wiki access

[Aaron Morton]

Hi my wiki access has somehow died, my user name is aaronmorton. 

Could you please reset my password or generate a new account.

Thanks
Aaron

-
Aaron Morton
New Zealand
@aaronmorton

Co-Founder & Principal Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

Re: wiki access

[Aaron Morton]

It was the case sensitivity. 

Weird because I was in 1Password. 

In now, thanks. 

Cheers
Aaron

-
Aaron Morton
New Zealand
@aaronmorton

Co-Founder & Principal Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

On 30/05/2014, at 6:58 pm, Jonathan Ellis  wrote:

> Is it case sensitive?  We have you as AaronMorton.
> 
> We can whitelist a new account if you create one.
> 
> On Fri, May 30, 2014 at 5:25 AM, Aaron Morton  wrote:
>> Hi my wiki access has somehow died, my user name is aaronmorton.
>> 
>> Could you please reset my password or generate a new account.
>> 
>> Thanks
>> Aaron
>> 
>> -
>> Aaron Morton
>> New Zealand
>> @aaronmorton
>> 
>> Co-Founder & Principal Consultant
>> Apache Cassandra Consulting
>> http://www.thelastpickle.com
>> 
> 
> 
> 
> -- 
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder, http://www.datastax.com
> @spyced

Re: [RELEASE] Apache Cassandra 4.0.0 released

[Aaron Ploetz]

So awesome.  Nice work, everyone!

Aaron


> On Jul 27, 2021, at 7:05 AM, Jean-Armel Luce  wrote:
> 
> Congrats all !!!
> 
>> Le mar. 27 juil. 2021 à 13:23, Benjamin Lerer  a écrit :
>> 
>> Thank you to all of those that contributed and helped out :-)
>> 
>> Le mar. 27 juil. 2021 à 07:05, Berenguer Blasi 
>> a
>> écrit :
>> 
>>> Congrats all! Amazing :-)
>>> 
>>> On 27/7/21 0:23, DuyHai Doan wrote:
>>>> Congrats !!!
>>>> 
>>>> 3 years worth of waiting and finally released !!!
>>>> 
>>>> 
>>>> 
>>>> On Tue, Jul 27, 2021 at 12:02 AM Ben Slater <
>> ben.sla...@instaclustr.com>
>>>> wrote:
>>>> 
>>>>> Congratulations and thank you to everyone involved in getting 4.0
>>> released!
>>>>> It has been a very impressive community effort.
>>>>> 
>>>>> ---
>>>>> 
>>>>> 
>>>>> *Ben Slater**Chief Product Officer*
>>>>> 
>>>>> 
>>>>> <https://www.facebook.com/instaclustr>   <
>>> https://twitter.com/instaclustr>
>>>>> <https://www.linkedin.com/company/instaclustr>
>>>>> 
>>>>> Read our latest technical blog posts here
>>>>> <https://www.instaclustr.com/blog/>.
>>>>> 
>>>>> This email has been sent on behalf of Instaclustr Pty. Limited
>>> (Australia)
>>>>> and Instaclustr Inc (USA).
>>>>> 
>>>>> This email and any attachments may contain confidential and legally
>>>>> privileged information.  If you are not the intended recipient, do not
>>> copy
>>>>> or disclose its content, but please reply to this email immediately
>> and
>>>>> highlight the error to the sender and then immediately delete the
>>> message.
>>>>> 
>>>>> 
>>>>> On Tue, 27 Jul 2021 at 07:34, Stefan Miklosovic <
>>>>> stefan.mikloso...@instaclustr.com> wrote:
>>>>> 
>>>>>> Super exciting, congratulations everybody. Great times ahead!
>>>>>> 
>>>>>> On Mon, 26 Jul 2021 at 22:19, Patrick McFadin 
>>>>> wrote:
>>>>>>> Wow. Just wow. Congratulations to everyone involved in this huge
>>>>>> milestone.
>>>>>>> On Mon, Jul 26, 2021 at 1:04 PM Brandon Williams 
>>>>>> wrote:
>>>>>>>> The Cassandra team is pleased to announce the release of Apache
>>>>>>>> Cassandra version 4.0.0.
>>>>>>>> 
>>>>>>>> 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 source and binary distributions are available in our
>>>>>>>> download section:
>>>>>>>> 
>>>>>>>> http://cassandra.apache.org/download/
>>>>>>>> 
>>>>>>>> This version is the initial release in the 4.0 series. As always,
>>>>>>>> please pay attention to the release notes[2] and Let us know[3] if
>>>>> you
>>>>>>>> were to encounter any problem.
>>>>>>>> 
>>>>>>>> Enjoy!
>>>>>>>> 
>>>>>>>> [1]: CHANGES.txt
>>>>>>>> 
>>>>>>>> 
>>>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.0
>>>>>>>> [2]: NEWS.txt
>>>>>>>> 
>>>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.0
>>>>>>>> [3]: https://issues.apache.org/jira/browse/CASSANDRA
>>>>>>>> 
>>>>>>>> 
>> -
>>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>>>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>>>>>>> 
>>>>>>>> 
>>>>>> -
>>>>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>>>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>>>>> 
>>>>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>> 
>>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Podcast Interviews for Feathercast

[Aaron Ploetz]

Sharan,

FWIW - Patrick and I are also working on putting together a Cassandra
podcast in the near future.  Perhaps we could work together?  Drop me a
message at aaron.plo...@datastax.com, and I'd be happy to set up some time
to discuss.

Thanks,

Aaron


On Wed, Apr 6, 2022 at 10:07 AM Sharan Foga  wrote:

> Hi All
>
> A quick update - I am working with someone on a potential first Cassandra
> related podcast. We are just looking at the questions and interview format
> etc to see how that could work.
>
> Thanks
> Sharan
>
> On 2022/04/02 11:43:32 Mick Semb Wever wrote:
> > >
> > >
> > > For those who are not familiar with FeatherCast
> > > <https://feathercast.apache.org/> -  its the ASF's podcast channel
> that
> > > we generally use to help promote projects.
> > >
> > > Looking through the list of published content I see that there are a
> few
> > > interviews about Cassandra <
> https://feathercast.apache.org/?s=cassandra>
> > > but they are a few years old - so if anyone is interested in being
> > > interviewed then please let me know and we can set something up.
> > >
> > >
> >
> > This is an awesome opportunity. I recommend any and all committers to
> take
> > advantage of it.
> >
> > Chris / Melissa, when we do an 'inside cassandra … interview' for the
> > website, we should offer the contributor the opportunity to follow it up
> > with one of these podcasts.
> >
>

Re: CEP-15 multi key transaction syntax

[Aaron Ploetz]

Benedict,

I'm really excited about this feature.  I've been observing this
conversation for a while now, and I"m happy to add some thoughts.

We must balance the fact we cannot afford to do everything (yet), against
> the need to make sure what we do is reasonably intuitive (to both CQL and
> SQL users) and consistent – including with whatever we do in future.


I think taking small steps forward, to build a few complete features as
close to SQL as possible is a good approach.

question we are currently asking: do we want to have a more LWT-like
> approach... or do we want a more SQL-like approach
>

For years now we've been fighting this notion that Cassandra is difficult
to use.  Coming up with specialized syntax isn't going to bridge that
divide.  From a (new?) user perspective, the best plan is to stay as
consistent with SQL as possible.

I believe that is a MySQL specific concept. This is one problem with
> mimicking SQL – it’s not one thing!


Right?!?!  As if this needed to be more complex.

I think we have evidence that it is fine to interpret NULL as “false” for
> the evaluation of IF conditions.
>

Agree.  Null == false isn't too much of a leap.

Thanks for taking up the charge on this one.  Glad to see it moving forward!

Thanks,

Aaron



On Sun, Jun 12, 2022 at 10:33 AM bened...@apache.org 
wrote:

> Welcome Li, and thanks for your input
>
>
>
> > When I first saw the syntax, I took it for granted that the condition
> was evaluated against the state AFTER the updates
>
>
>
> Depending what you mean, I think this is one of the options being
> considered. At least, it seems this syntax is most likely to be evaluated
> against the values written by preceding statements in the batch, but not
> the statement itself (or later ones), as this could lead to nonsensical
> statements like
>
>
>
> BEGIN TRANSACTION
>
> UPDATE tbl SET v = 1 WHERE key = 1 AS tbl
>
> COMMIT TRANSACTION IF tbl.v = 0
>
>
>
> Where y is never 0 afterwards, so this never succeeds. I take it in this
> simple case you would expect the condition to be evaluated against the
> state prior to the statement (i.e. the initial state)?
>
>
>
> But we have a blank slate, so every option is available to us! We just
> need to make sure it makes sense to the user, even in uncommon cases.
>
>
>
> > The IF (Boolean expr) ABORT TRANSACTION would suffer less because users
> may tend to put the condition closer to the related SELECT statement.
>
>
>
> This is probably not going to matter in practice. The SELECTs all happen
> upfront no matter what the CQL might look like, and the UPDATE all happen
> only after the IF conditions are evaluated. This is all just a question of
> how the user expresses things.
>
>
>
> In future we may offer interactive transactions, or transactions that are
> multi-step, in which case this would be more relevant and could have an
> efficiency impact.
>
>
>
> > Would you consider allowing users to start a read-only transaction
> explicitly like BEGIN TRANSACTION READONLY?
>
>
>
> Good question. I would be OK with this, for sure, and will defer to the
> opinions of others here. There won’t be any optimisation impact, as we
> simply check if the transaction contains any updates, but some validation
> could be helpful for the user.
>
>
>
> > Finally, I wonder if the community would be interested in idempotency
> support.
>
>
>
> This is something that has been considered, and that Accord is able to
> support (in a couple of ways), but as an end-to-end feature this requires
> client support and other scaffolding that is not currently
> planned/scheduled. The simplest (least robust) approach is for the server
> to include the transaction’s identifier in its timeout, so that it be
> queried by the client to establish if it has been made durable. This should
> be quite easy to deliver on the server-side, but would require some
> application or client integration, and is unreliable in the face of
> coordinator failure (so the transaction id is unknown to the client). The
> more complete approach is for the client to include an idempotency token in
> its submission to the server, and for C* to record this alongside the
> transaction id, and for some bounded time window to either reject
> re-submissions of this token or to evaluate it as a no-op. This requires
> much tighter integration from the clients, and more work server-side.
>
>
>
> Which is simply to say, this is on our radar but I can’t make promises
> about what form it will take, or when it will arrive, only that it has been
> planned for enough to ensure we can achieve it when resources permit.
>
>
>
> *From: *Li Boxuan 

The Apache Cassandra(R) Corner Podcast

[Aaron Ploetz]

After some recent discussions and ultimately guidance from Mick, I have
made some adjustments to bring the Apache Cassandra® Corner (formerly known
as the "Cassandra Corner") podcast more into alignment with the Apache
Cassandra® project guidelines and standards.  I have sent the credentials
for Anchor (the central location for the podcast) to Mick, and I will post
all future episodes with a 72 hour staging period for approval.

Link to next episode:

Ep5 - Melissa Logan (Constantia)
https://drive.google.com/file/d/1E4zQmHK4eU635JFjqEDEjVrth14eeVBK/view?usp=sharing

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
on Thursday June 30th.

If anyone should have any questions, comments, or if you want to be a
guest, please reach out to me.

Thanks everyone!

Aaron Ploetz

New episode of the Apache Cassandra(R) Corner Podcast

[Aaron Ploetz]

Link to next episode:

Ep6 - Jeff Beck (SmartThings)
https://drive.google.com/file/d/1_dhnMUlSF_8qByHdcoWQc0GD0rhsZjVf/view?usp=sharing

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
on Thursday, July 28th.

If anyone should have any questions, comments, or if you want to be a
guest, please reach out to me.

Thanks everyone!

Aaron Ploetz

New episode of the Apache Cassandra(R) Corner Podcast!

[Aaron Ploetz]

Link to next episode:

Ep7 - Ekaterina Dimitrova (Apache Cassandra committer)
https://drive.google.com/file/d/1xgwHOdufJAEwjlAluJZP2XwfbGpFWEwv/view?usp=sharing

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
by Monday, August 22nd.

If anyone should have any questions, comments, or if you want to be a
guest, please reach out to me.

For my guest pipeline, I have recording sessions scheduled with:
- Otavio Santana (Java Champion and Open Source Committer w/ the Eclipse
Foundation)
- Sarma Pydipally (Udemy Instructor, Principal Engineer w/ Verizon)

So I should have a good flow of episodes for the next couple of weeks.

Thanks everyone!

Aaron Ploetz

Re: [DISCUSS] CEP-20: Dynamic Data Masking

[Aaron Ploetz]

Some thoughts on this one:

In a prior job, we'd give app teams access to a single keyspace, and two
roles: a read-write role and a read-only role.  In some cases, a
"privileged" application role was also requested.  Depending on the
requirements, I could see the UNMASK permission being applied to the RW or
privileged roles.  But if there's a problem on the table and the operators
go in to investigate, they will likely use a SUPERUSER account, and they'll
see that data.

How hard would it be for SUPERUSERs to *not* automatically get the UNMASK
permission?

I'll also echo the concerns around masking primary key components.  It's
highly likely that certain personal data properties would be used as a
partition or clustering key (ex: range query for people born within a
certain timeframe).  In addition to the "breaks existing" concern, I'm
curious about the challenges around getting that to work with the current
primary key implementation.

Does this first implementation only apply to payload (non-key) columns?
The examples in the CEP currently do not show primary key components being
masked.

Thanks,

Aaron


On Tue, Aug 23, 2022 at 6:44 AM Henrik Ingo 
wrote:

> On Tue, Aug 23, 2022 at 1:10 PM Andrés de la Peña 
> wrote:
>
>> One thought: The way the CEP is currently written, it is only possible to
>>> mask a column one way. You can only define one masking function for a
>>> column, and since you use the original column name, you could only return
>>> one version of it in the result set, even if you had a way to define
>>> several functions.
>>>
>>
>> Right, it's one single type of mapping per the column, declared on
>> CREATE/ALTER TABLE statements. Also, users can manually specify their own
>> masking function in SELECT statements if they have permissions for seeing
>> the clear data.
>>
>> For those cases where the data is automatically masked for an
>> unprivileged user, I don't see the use of including different types of
>> masking for the same column into the same result set. Instead, we might be
>> interested on having different types of masking associated to different
>> roles. We could do so with dedicated CREATE/DROP/LIST MASK statements,
>> instead of using the CREATE/ALTER/DESCRIBE TABLE statements. That CREATE
>> MASK statement would associate a masking function to a column and role.
>> However, I'm not sure we need that type of granularity instead of the
>> simplicity of attaching the masking to the column declaration. wdyt?
>>
>>
>>
> My gut feeling likewise is that this adds complexity but little value.
>
>>
>>>
>
> --
>
> Henrik Ingo
>
> +358 40 569 7354 <358405697354>
>
> [image: Visit us online.] <https://www.datastax.com/>  [image: Visit us
> on Twitter.] <https://twitter.com/DataStaxEng>  [image: Visit us on
> YouTube.]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_channel_UCqA6zOSMpQ55vvguq4Y0jAg&d=DwMFaQ&c=adz96Xi0w1RHqtPMowiL2g&r=IFj3MdIKYLLXIUhYdUGB0cTzTlxyCb7_VUmICBaYilU&m=bmIfaie9O3fWJAu6lESvWj3HajV4VFwgwgVuKmxKZmE&s=16sY48_kvIb7sRQORknZrr3V8iLTfemFKbMVNZhdwgw&e=>
>   [image: Visit my LinkedIn profile.]
> <https://www.linkedin.com/in/heingo/>
>

Re: [DISCUSS] CEP-20: Dynamic Data Masking

[Aaron Ploetz]

>
> Applying this should prevent querying on a field, else you could leak its
> contents, surely?
>

In theory, yes.  Although I could see folks doing something like this:

SELECT COUNT(*) FROM patients
WHERE year_of_birth = 2002
AND date_of_birth >= '2002-04-01'
AND date_of_birth < '2002-11-01';

In this case, the rows containing the masked key column(s) could be
filtered on without revealing the actual data.  But again, that's probably
better for a "phase 2" of the implementation.

Agreed on not being a queryable field. That would also preclude secondary
> indexing, right?


Yes, that's my thought as well.

On Tue, Aug 23, 2022 at 12:42 PM Derek Chen-Becker 
wrote:

> Agreed on not being a queryable field. That would also preclude secondary
> indexing, right?
>
> On Tue, Aug 23, 2022 at 11:20 AM Benedict  wrote:
>
>> Applying this should prevent querying on a field, else you could leak its
>> contents, surely? This pretty much prohibits using it in a clustering key,
>> and a partition key with the ordered partitioner - but probably also a
>> hashed partitioner since we do not use a cryptographic hash and the hash
>> function is well defined.
>>
>> We probably also need to ensure that any ALLOW FILTERING queries on such
>> a field are disabled.
>>
>> Plausibly the data could be cryptographically jumbled before using it in
>> a primary key component (or permitting filtering), but it is probably
>> easier and safer to exclude for now…
>>
>> On 23 Aug 2022, at 18:13, Aaron Ploetz  wrote:
>>
>> 
>> Some thoughts on this one:
>>
>> In a prior job, we'd give app teams access to a single keyspace, and two
>> roles: a read-write role and a read-only role.  In some cases, a
>> "privileged" application role was also requested.  Depending on the
>> requirements, I could see the UNMASK permission being applied to the RW or
>> privileged roles.  But if there's a problem on the table and the operators
>> go in to investigate, they will likely use a SUPERUSER account, and they'll
>> see that data.
>>
>> How hard would it be for SUPERUSERs to *not* automatically get the UNMASK
>> permission?
>>
>> I'll also echo the concerns around masking primary key components.  It's
>> highly likely that certain personal data properties would be used as a
>> partition or clustering key (ex: range query for people born within a
>> certain timeframe).  In addition to the "breaks existing" concern, I'm
>> curious about the challenges around getting that to work with the current
>> primary key implementation.
>>
>> Does this first implementation only apply to payload (non-key) columns?
>> The examples in the CEP currently do not show primary key components being
>> masked.
>>
>> Thanks,
>>
>> Aaron
>>
>>
>> On Tue, Aug 23, 2022 at 6:44 AM Henrik Ingo 
>> wrote:
>>
>>> On Tue, Aug 23, 2022 at 1:10 PM Andrés de la Peña 
>>> wrote:
>>>
>>>> One thought: The way the CEP is currently written, it is only possible
>>>>> to mask a column one way. You can only define one masking function for a
>>>>> column, and since you use the original column name, you could only return
>>>>> one version of it in the result set, even if you had a way to define
>>>>> several functions.
>>>>>
>>>>
>>>> Right, it's one single type of mapping per the column, declared on
>>>> CREATE/ALTER TABLE statements. Also, users can manually specify their own
>>>> masking function in SELECT statements if they have permissions for seeing
>>>> the clear data.
>>>>
>>>> For those cases where the data is automatically masked for an
>>>> unprivileged user, I don't see the use of including different types of
>>>> masking for the same column into the same result set. Instead, we might be
>>>> interested on having different types of masking associated to different
>>>> roles. We could do so with dedicated CREATE/DROP/LIST MASK statements,
>>>> instead of using the CREATE/ALTER/DESCRIBE TABLE statements. That CREATE
>>>> MASK statement would associate a masking function to a column and role.
>>>> However, I'm not sure we need that type of granularity instead of the
>>>> simplicity of attaching the masking to the column declaration. wdyt?
>>>>
>>>>
>>>>
>>> My gut feeling likewise i

New episode of the Apache Cassandra (R) Corner podcast!

[Aaron Ploetz]

Link to next episode:

Ep8 - Sarma Pydipally (Udemy instructor, open source dev)
https://drive.google.com/file/d/15-qRcWOyLwQi5lsY06rUYBdLViXGk_xs/view?usp=sharing

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
by Wednesday, August 31st.

If anyone should have any questions, comments, or if you want to be a
guest, please reach out to me.

For my guest pipeline, I have recording sessions scheduled with:
- Otavio Santana (Java Champion and Open Source Committer w/ the Eclipse
Foundation)


Thanks everyone!

Aaron Ploetz

New episode of The Apache Cassandra Corner(R)

[Aaron Ploetz]

Link to next episode:

Ep9 - Otavio Santana (Java Champion, open source dev)
https://drive.google.com/file/d/1NYk1zCyyHErkuyrJsFGannBx0NAYreea/view?usp=sharing

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
by Monday, September 12th.

If anyone should have any questions, comments, or if you want to be a
guest, please reach out to me.

As for my guest pipeline, I do have a gap coming up.  So if you or someone
you know would be a great guest, please let me know!

Thanks, everyone!

Aaron Ploetz

New episode of The Apache Cassandra Corner(R)

[Aaron Ploetz]

Link to next episode:

Ep10 - Cheng Wang and Jordan West (Netflix)

https://drive.google.com/file/d/1_f-0vTv-ZDZEcLSgqW8b8NQbAjmlQM2Q/view?usp=sharing

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
by Friday (night), October 14th.

If anyone should have any questions, comments, or if you want to be a
guest, please reach out to me.

Thanks, everyone!

Aaron

New episode of The Apache Cassandra(R) Corner

[Aaron Ploetz]

Link to next episode:

Ep11 - Mick Semb Weaver (Apache Cassandra PMC Chair)

https://drive.google.com/file/d/16bSw-hJVVOkIzTEg86KYUMT9g9Nm-X5B/view?usp=sharing

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
by Friday (night), October 14th.

If anyone should have any questions, comments, or if you want to be a
guest, please reach out to me.

Thanks, everyone!

Aaron

New episode of The Apache Cassandra(R) Corner

[Aaron Ploetz]

Link to next episode:

Ep12 - Derek Chen-Becker (AWS Sr. Engineer & open source dev)

https://drive.google.com/file/d/1JH7oQCtvVFUqH1Lhlo66dvW2Fzodif5H/view?usp=sharing

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
by Wednesday (evening), November 2nd.  I'm giving this one a little extra
time, as Amazon's PR folks would like to give it a listen, as well.

If anyone should have any questions, comments, or if you want to be a
guest, please reach out to me.

Thanks, everyone!

Aaron

New episode of The Apache Cassandra(R) Corner

[Aaron Ploetz]

Link to next episode:

Ep13 - Alexa Simon (Realeyes Sr. Data Engineer)

https://drive.google.com/file/d/17vVbAirAJABH4ZbNS-4Yk-eeUbQCyTWd/view?usp=share_link

(You may have to download it to listen)

It will remain in staging for 72 hours, going live (assuming no objections)
by Friday (afternoon), November 11th.

If anyone should have any questions, comments, or if you want to be a
guest, please reach out to me.

Thanks, everyone!

Aaron

Re: Hadoop package exposed through thrift

[aaron morton]

I'm not up to speed with Hadoop in Cassandra, but regular Hadoop provides a IO 
stream interface so it can be used with non Java languages. 

http://hadoop.apache.org/common/docs/r0.15.2/streaming.html

That may be of help. 
Aaron

On 9 Jun 2010, at 09:53, Jeremy Hanna wrote:

> I just didn't know if there were any way to make it easier for the non-java 
> crowd to take advantage of it.  I'll give it some more thought.
> 
> On Jun 8, 2010, at 4:05 PM, Jonathan Ellis wrote:
> 
>> exposing it through thrift would mean the path would be
>> 
>> client
>> to cassandra [processing thrift command]
>> to hadoop [giving it a job]
>> to cassandra [fetching the data]
>> to hadoop [m/r]
>> to cassandra [handing result back]
>> to client
>> 
>> it just doesn't seem like a good design to me.
>> 
>> additionally, thrift is meant more for "stuff your app is doing
>> constantly" while hadoop handles analytics queries.  this separation
>> of duties makes a lot of sense to me.
>> 
>> On Tue, Jun 8, 2010 at 1:45 PM, Jeremy Hanna  
>> wrote:
>>> When I gave a presentation on cassandra+hadoop, some ruby folks were 
>>> wondering about the possibility of using the MapReduce functionality in a 
>>> language other than Java.
>>> 
>>> I was just wondering if any thought was given to exposing the 
>>> org.apache.cassandra.hadoop functionality through thrift.  That way the 
>>> MapReduce code could be used by several languages and secondarily by client 
>>> authors.
>>> 
>>> I'm just trying to see if there is any reason why it wasn't exposed through 
>>> thrift or if more needs to be done before it could be exposed to languages 
>>> other than Java.
>>> 
>>> Thanks,
>>> 
>>> Jeremy
>> 
>> 
>> 
>> -- 
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder of Riptano, the source for professional Cassandra support
>> http://riptano.com
> 

Re: Secondary indexing and 0.6/0.7 integration with Datanucleus

[aaron morton]

I've not read up on the secondary indexes, but am doing some thing similar. I 
got some inspiration from the Lucandra project. You will probably need to make 
multiple calls to the cassandra for each clause of your query.

The design I used had two CF's rough idea was; in the TermDocIndex the key term 
(e.g. lastName=Smith) and the column names are the keys for the object / 
document the term is from e.g. key1. The DocTermIndex uses the object/doc id as 
the key and has columns for each term the document contains, e.g. 
"lastname=Smith"). I also maintained some stats on how many objects/documents 
had the term (using redis, will move to cassandra counters in 0.7 perhaps). 

The query process then becomes.
1.  Determine the most selective term in the query using the stats
2.  Do a get_slice to get the first X (1000 perhaps) column values from the 
TermDocIndex using the term key.
3.  Use the keys from step 2 in a multi_get_slice against the DocTermIndex, 
passing the list of keys from 2 and listing the remaining terms as the column 
names you want to get back. 
4.  From the result of 3 filter all keys that returned less columns that we 
asked for. 
5.  Repeat from 3 if needed. 

I was hoping the limit in step 2 would bound the queries into the cluster, and 
the multiget in step 3 would be better at distributing the most of the work 
around the cluster. E.g. rather than reading 1000 columns from, say, 3 keys. It 
reads 3 columns from 1000 keys.

Aaron


On 16 Jun 2010, at 16:57, Todd Nine wrote:

> No problem,
>  I didn't want to implement my own solution if an existing one could
> easily be applied.  Since I'll be creating CF that represent secondary
> indexes, I'll need to perform range scans over the keys of those
> secondary index CFs.  The column names within the CF's are the row keys
> of the primary table.  Is there a way I can get the intersection of all
> of the column names from multiple ranges scans over different column
> families in one result set?  Otherwise I'll need to make multiple trips
> and create the intersection myself in my plugin.  Here is an example of
> what I'm trying to do.
> 
> CF: Person
> 
> key1: {
>   firstName: John
>   lastName: Smith
>   email: smi...@foo.com
> }
> 
> key2: {
>  firstName: Jane
>  lastName: Smith
>  email: smi...@foo.com
> }
> 
> key3: {
>  firstName: Jane
>  lastName: Doe
>  email: smi...@foo.com
> }
> 
> 
> My secondary index tables would be the following
> 
> CF: Person_LastName
> 
> Smith:{
>  key1: 0x00
>  key2: 0x00
> }
> 
> Doe: {
>  key3:0x00
> }
> 
> CF: Person_Email
>  smi...@foo.com:{
>key1:0x00
>key2:0x00 
>key3:0x00
> }
> 
> If my input is something similar to lastName == 'Smith' && email ==
> "smi...@foo.com", I would return all columns from key "Smith" in CF
> Person_LastName, and all columns from key "smi...@foo.com" in CF
> Person_Email.  The intersection of the two sets is key1, and key2, and
> have cassandra only return those rows.
> 
> Thanks,
> Todd
> 
> 
> 
> 
> 
> On Tue, 2010-06-15 at 23:38 -0500, Jonathan Ellis wrote:
> 
>> No chance that 749 can be backported to 0.6, sorry.
>> 
>> On Tue, Jun 15, 2010 at 10:35 PM, Todd Nine  wrote:
>> 
>>> Lets try that again.
>>> 
>>> This is the intended issue.
>>> 
>>> https://issues.apache.org/jira/browse/CASSANDRA-749
>>> 
>>> thanks,
>>> Todd
>>> 
>>> 
>>> 
>>>  On Tue, 2010-06-15 at 20:02 -0500, Jonathan Ellis wrote:
>>> 
>>> What issue were you trying to link? :)
>>> 
>>> On Tue, Jun 15, 2010 at 6:56 PM, Todd Nine  wrote:
>>>> Hi all,
>>>> I'm implementing a Datanucleus plugin for Cassandra.  I'm finished
>>>> with the basic functionality, and everything seems to work pretty well.
>>>> Now my issue is performing secondary indexing on fields within my data.
>>>> I have outlined some of the issues I'm facing in this post.
>>>> 
>>>> http://www.datanucleus.org/servlet/forum/viewthread_thread,6087_lastpage,yes#32610
>>>> 
>>>> Essentially, for each operand the user specifies, I will need to make a
>>>> trip to Cassandra, load the key columns, then perform an intersection
>>>> with the result from my previous read.  Eventually at the end of all the
>>>> intersections, I will have a list of keys I will then load.  This
>>>> obviously requires several trips to Cassandra, where from my
>>>> understanding of secondary indexing, I would only need to make one trip
>>>> for multiple operands over a column family.I've read over this
>>>> issue.
>>>> 
>>>> http://issues.apache.org/jira/browse/CASSANDRA-32610
>>>> 
>>>> And it seems to solve a lot of my woes.  Is it possible/recommended to
>>>> patch the current code base of 0.6.2 to perform this functionality?
>>>> 
>>>> Thanks,
>>>> Todd
>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 

Re: Atomic Compare and Swap

[aaron morton]

I've been playing with something like CAS, it's not the same but it  
may be of interest.


I write some data into Cassandra with quorum or better consistency,  
that allows me to assert what it should look like when read back. If  
the assertion holds I can then go ahead.


For example, in a CF with Time uuid ordering the client writes a  
column against the key of the thing we want to update. This write does  
not store the value. Then read back the first ordered column, if it's  
name is my uuid then I can proceed. Otherwise delete the column. If  
you know the uuid of the last update you can read back two columns.  
Then assert your the first and the previous is the second.


Perhaps if you were doing a CAS you could then write then actual value  
you want to update and somehow store the uuid from above with it. Say  
as col in another col family with  name as the uuid and value as the  
value. To read get the first colum from both CFs as a multi get, the  
col names must match from both cols for the value to be correct.


(could just use two diff keys in same CF)

Hope that makes sense.
Aaron






On 23/06/2010, at 4:27 PM, Mike Malone  wrote:

I'd be interested in what the folks who want CAS implementations  
think about
vector clocks. Can you use them to fulfill your use cases? If not,  
why not?


I ask because I have found myself wanting CAS in Cassandra too, but  
I think
that's only because I'm pretty familiar with HTTP. I think vector  
clocks
with client merge give you essentially the same functionality, but  
in a way
that fits much more nicely with the rest of the Cassandra  
architecture. CAS

really exacerbates Cassandra's weaknesses.

Mike

On Tue, Jun 22, 2010 at 4:52 PM, Rishi Bhardwaj  
wrote:





S>: An *atomic* CAS is another beast and I see at least two  
difficulties:


S>: 1) making it atomic locally: Cassandra's implementation is very  
much

multi-threaded. On a given node, while you're

reading-comparing-and-swapping

on some column c, no other thread should be allowed to write c (even

'normal'
write). You would probably need to have specific column families  
where CAS

is
allowed and for which all writes would be slower (since some  
locking would

be
involved). Even then, making such locking efficient and right is  
not easy.

But

in the end, local atomicity is quite probably the easy part.


R: I am curious as to how does Cassandra handle two concurrent  
writes to

the same column right now? Is there any locking on the write path to
serialize two writes to the same column? If there is any locking  
then CAS
can build on that. If there is no such locking then we could  
exclude normal
writes from the synchronization/locking required for CAS. So the  
normal
write path remains the same, and we let the client know that atomic  
CAS
wouldn't work if normal writes are also happening on the same  
column values.
In short a client should not mix normal writes with Atomic CAS for  
writing

some column value. This will hopefully make things simpler.

S:>2) making it atomic cluster-wide: data is replicated and an  
atomic CAS

would
need to apply on the exact same column version in every node.  
Which, with

eventual consistency especially, is pretty hard to accomplish unless

you're

locking the cluster (but that's what Cages/ZK do).


R: For starters it would be great if atomic CAS could work for  
consistency
level Quorum and ALL and not be supported for other consistency  
levels. Even
for other consistency levels what would stop CAS to work? Why would  
one
require cluster wide locking? I might be mistaken here but the  
atomic CAS

operation would happen individually at all the replica nodes (either
directly or through hinted writes) and would succeed or fail  
depending on
the timestamp/version of the column at the replica. If we do Quorum  
reads

and CAS writes then we can also be sure about consistency.

S:>That being said, if you have a neat solution for efficient and
distributed
atomic CAS that doesn't require rewriting 80% of Cassandra, I'm  
sure there

will be interest in that.



R: That sounds great. I am definitely going to look into this and  
report

back if I have a good solution.


Thanks,
Rishi





From: Sylvain Lebresne 
To: dev@cassandra.apache.org
Sent: Tue, June 22, 2010 1:21:51 AM
Subject: Re: Atomic Compare and Swap

On Mon, Jun 21, 2010 at 11:19 PM, Rishi Bhardwaj >

wrote:
I have read the post on cages and it is definitely very  
interesting. But
cages seems to be too coarse grained compared to an Atomic Compare  
and

Swap
on Cassandra column value. Cages would makes sense when one wants  
to do
multiple atomic row, column updates. Also, I am not so sure about  
the

scalability when it comes to using zookeeper for keeping locks on

Cassandra

columns... there would also be performance hit with an added RPC for

every

Re: Cassandra and Lucene

[Aaron Morton]

You may need to provide a some more information. What's the cluster configuration, what version, what's in the logs etc. AaronOn 24 Jul, 2010,at 03:40 AM, Michelan Arendse  wrote:Hi

I have recently started working on Cassandra as I need to make a distribute
Lucene index and found that Lucandra was the best for this. Since then I
have configured everything and it's working ok.

Now the problem comes in when I need to write this Lucene index to Cassandra
or convert it so that Cassandra can read it. The test index is 32 gigs and i
find that Cassandra times out alot.

What happens can't Cassandra take that load? Please any help will be great.

Kind Regards,

Re: Cassandra and Lucene

[Aaron Morton]

Sorry, also moving to User list. AaronOn 26 Jul, 2010,at 12:14 PM, Aaron Morton  wrote:You may need to provide a some more information. What's the cluster configuration, what version, what's in the logs etc. AaronOn 24 Jul, 2010,at 03:40 AM, Michelan Arendse  wrote:Hi

I have recently started working on Cassandra as I need to make a distribute
Lucene index and found that Lucandra was the best for this. Since then I
have configured everything and it's working ok.

Now the problem comes in when I need to write this Lucene index to Cassandra
or convert it so that Cassandra can read it. The test index is 32 gigs and i
find that Cassandra times out alot.

What happens can't Cassandra take that load? Please any help will be great

Kind Regards,

Re: Having Problems installing Chiton

[Aaron Morton]

You need to have the python thrift client and the generated cassandra thrift library in the python path. To get the thrift library I followed this guide http://wiki.apache.org/cassandra/InstallThrift There may be an easier way though. It looks like the Telephus client includes the cassandra package but not the thrift package. AaronOn 24 Aug, 2010,at 05:42 PM, durga devi  wrote:Sir/Madam,

I am new to Ubuntu.
I am getting the following Problem when insatlling the chiton in ubuntu
10.4

From this link http://tinyurl.com/24gdgkv
I set the PYHTONPATH as  export
   PYTHONPATH=/home/durga/driftx-
   Telephus-fb32fc7/:/home/durga/driftx-chiton-bd91965/:/usr/bin/python/
   And i run the  /driftx-chiton-bd91965/bin/./chiton-client

   I had the following Problem http://pastebin.com/29T12wef

   I am unble to sort out where this problem is occurring while in
   installation.

Thanks & Regards,
B.Durgadevi

Re: Build an index to join two CFs

[aaron morton]

I cannot tell you where in the code to make these changes. But it sounds like 
you want to fork cassandra and turn it into a RDBMS. It would undoubtedly be 
easier to just use a RDBMS.

Rather than have two CF's, address and name, just have one for the person using 
a super CF. Pull back the entire row for the id. Denormalise your data so the 
query is answered by one slice request to one CF, then you do not need  joins. 

If you want some advice on the data model, move the discussion to the user 
list. 

Aaron



On 11 Sep 2010, at 09:01, Alvin UW wrote:

> Hello,
> 
> I am going to build an index to join two CFs.
> First, we see this index as a CF/SCF. The difference is I don't materialise
> it.
> Assume we have two tables:
> ID_Address(*Id*, address) ,  Name_ID(*name*, id)
> Then,the index is: Name_Address(*name*, address)
> 
> When the application tries to query on Name_Address, the value of "name" is
> given by the application.
> I want to direct the read operation  to Name_ID to get "Id" value, then go
> to ID_Address to
> get the "address" value by the "Id" value. So far, I consider only the read
> operation.
> By this way, the join query is transparent to the user.
> 
> So I think I should find out which methods or classes are in charge of the
> read operation in the above operation.
> For example, the operation in cassandra CLI "get
> Keyspace1.Standard2['jsmith']" calls exactly which methods
> in the server side?
> 
> I noted CassandraServer is used to listen to clients, and there are some
> methods such as get(), get_slice().
> Is it the right place I can modify to implement my idea?
> 
> Thanks.
> 
> Alvin

system tests on osx

[Aaron Morton]

Anyone had trouble running the test/system/test_thrift_server.py tests on a mac book ? I was trying last night and they would sometimes work, sometimes not, without me making any changes They were failing with errors such as  connection reset, TSocket read 0 bytes errors at different times. I've been able to run them at work (Ubuntu 0.4) OK. Just wanted to check if there were any known issues before I spend more time digging into it. ThanksAaron 

Re: Help on dynamic creation of CF

[aaron morton]

Moving to the User List 
Aaron

On 13 Oct 2010, at 18:44, gagandip Singh wrote:

> I am also new to the Cassandra world but I think that is not possible on 0.6
> version. This is feature is provided in 0.7 version which is in beta right
> now. You can download it from Cassandra site.
> 
> Thanks,
> Gagan
> 
> On Wed, Oct 13, 2010 at 11:05 AM, Wicked J  wrote:
> 
>> Hi,
>> I'm using Cassandra v0.6.4 and wondering how can my app. dynamically create
>> Column Families?
>> 
>> Thanks!
>> 

/var/tmp in FailureDetector

[aaron morton]

I was reading through some code and noticed the following in 
FailureDetector.dumpInterArrivealTimes()

FileOutputStream fos = new FileOutputStream("/var/tmp/output-" + 
System.currentTimeMillis() + ".dat", true);

If this is meant to be cross platform I'm happy to create a bug and change it 
to use File.createTempFile() . 

Also I could not find any use of the  dumpInterArrivalTimes(InetAddress ep) 
overload. Anyone know if it should be kept?

thanks
Aaron

Re: /var/tmp in FailureDetector

[aaron morton]

I should have mentioned the FailureDetectorMBean only has the parameterless 
dumpInterArrivalTimes(). 

The overload that takes InetAddress is not available through JMX. 

A
On 21 Oct 2010, at 01:55, Gary Dusbabek wrote:

> Yes, we should generate it in the right temp directory.  That method
> is an implementation of an interface method (FailureDetectorMBean),
> meant to be invoked by JMX, which is why no other code calls it.
> 
> Gary.
> 
> On Wed, Oct 20, 2010 at 03:48, aaron morton  wrote:
>> I was reading through some code and noticed the following in 
>> FailureDetector.dumpInterArrivealTimes()
>> 
>>FileOutputStream fos = new FileOutputStream("/var/tmp/output-" + 
>> System.currentTimeMillis() + ".dat", true);
>> 
>> If this is meant to be cross platform I'm happy to create a bug and change 
>> it to use File.createTempFile() .
>> 
>> Also I could not find any use of the  dumpInterArrivalTimes(InetAddress ep) 
>> overload. Anyone know if it should be kept?
>> 
>> thanks
>> Aaron
>> 
>> 

Question about ColumnFamily Id's

[Aaron Morton]

I was helping a guy who in the end had a mixed beta1 and beta2 cluster http://www.mail-archive.com/u...@cassandra.apache.org/msg06661.htmlI had a look around the code and have a couple of questions, just for my understanding. When ReadResponseSerialize is called to deserialize the response from a node, it calls the RowSerializer which uses the ColumnFamilySerializer. If the CfId in the row is not known on the node a UnserializableColumnFamilyException is thrown. It's an IOException sub class and the error is treated as an Internal Error by the thrift generated Cassandra server. The read message sent to the node contains the Keyspace+CF names, and it returns it's CfID in the response. It looks like if a node somehow has a different/bad schema it can cause reads to fail. Is this correct? Could it's response be ignored if the read still meets the CL?Next question was how nodes could ever get to have a different CfId for the same Keyspace+CF pair?  It looks like the the CfId is never changed, so it would only happen if two node were each given a schema update and could not communicate it with each other.Am guessing the whole scenario is "unsupported" just trying to understand whats happening. ThanksAaron  

Re: /var/tmp in FailureDetector

[Aaron Morton]

To quick for me :)
Aaron


On 21 Oct 2010, at 17:52, Jonathan Ellis  wrote:

> Done in r1025822
> 
> On Wed, Oct 20, 2010 at 12:54 PM, Gary Dusbabek  wrote:
>> You're right!  It looks like dead code that should be removed.
>> 
>> Gary.
>> 
>> On Wed, Oct 20, 2010 at 12:50, aaron morton  wrote:
>>> I should have mentioned the FailureDetectorMBean only has the parameterless 
>>> dumpInterArrivalTimes().
>>> 
>>> The overload that takes InetAddress is not available through JMX.
>>> 
>>> A
>>> On 21 Oct 2010, at 01:55, Gary Dusbabek wrote:
>>> 
>>>> Yes, we should generate it in the right temp directory.  That method
>>>> is an implementation of an interface method (FailureDetectorMBean),
>>>> meant to be invoked by JMX, which is why no other code calls it.
>>>> 
>>>> Gary.
>>>> 
>>>> On Wed, Oct 20, 2010 at 03:48, aaron morton  
>>>> wrote:
>>>>> I was reading through some code and noticed the following in 
>>>>> FailureDetector.dumpInterArrivealTimes()
>>>>> 
>>>>>FileOutputStream fos = new FileOutputStream("/var/tmp/output-" 
>>>>> + System.currentTimeMillis() + ".dat", true);
>>>>> 
>>>>> If this is meant to be cross platform I'm happy to create a bug and 
>>>>> change it to use File.createTempFile() .
>>>>> 
>>>>> Also I could not find any use of the  dumpInterArrivalTimes(InetAddress 
>>>>> ep) overload. Anyone know if it should be kept?
>>>>> 
>>>>> thanks
>>>>> Aaron
>>>>> 
>>>>> 
>>> 
>>> 
>> 
> 
> 
> 
> -- 
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of Riptano, the source for professional Cassandra support
> http://riptano.com

questions about SSTableExport/Import

[aaron morton]

I was trying to help this guy 
http://www.mail-archive.com/u...@cassandra.apache.org/msg07297.html who seemed 
to have troubles loading a json file. And I started taking a look at 
SSTableExport and SSTableImport.

SSTableExport does not encode any information about the Column sub type 
(ExpiringColumn or DeletedColumn). It records isMarkedForDelete(), the 
timestamp and the localDeletionTime as the col value if its a DeletedColumn. 
SSTableImport then calls either cf.addColumn() or cf.addTombstone() based on 
the deleted flag. 

First question is is the code in SSTableImport.addToStandardCF() correct to 
call cf.addColumn() if when the column was serialised it was 
isMarkedForDelete() ?

Next is it OK to lose the fact that a column is an ExpiringColumn (and its ttl) 
when it's exported to json? 

On my local machine I modified the unit test for SSTableExport as below and the 
assertion that the col was not returned failed.

Thanks
Aaron

diff --git a/test/unit/org/apache/cassandra/tools/SSTableExportTest.java 
b/test/unit/org/apache/cassandra/tools/SSTableExportTest.java
index 6f79f62..53d2a9c 100644
--- a/test/unit/org/apache/cassandra/tools/SSTableExportTest.java
+++ b/test/unit/org/apache/cassandra/tools/SSTableExportTest.java
@@ -179,6 +179,7 @@ public class SSTableExportTest extends SchemaLoader
 
 // Add rowA
 cfamily.addColumn(new QueryPath("Standard1", null, 
ByteBufferUtil.bytes("name")), ByteBufferUtil.bytes("val"), 1);
+cfamily.addColumn(new QueryPath("Standard1", null, 
ByteBufferUtil.bytes("ttl")), ByteBufferUtil.bytes("val"), 1, 1);
 writer.append(Util.dk("rowA"), cfamily);
 cfamily.clear();
 
@@ -187,6 +188,15 @@ public class SSTableExportTest extends SchemaLoader
 writer.append(Util.dk("rowExclude"), cfamily);
 cfamily.clear();
 
+//make sure the ttl col has expired
+try
+{
+Thread.sleep(1500);
+}
+catch (InterruptedException e)
+{
+throw new AssertionError(e);
+}
 SSTableReader reader = writer.closeAndOpenReader();
 
 // Export to JSON and verify
@@ -203,6 +213,11 @@ public class SSTableExportTest extends SchemaLoader
 assertTrue(cf != null);
 
assertTrue(cf.getColumn(ByteBufferUtil.bytes("name")).value().equals(ByteBuffer.wrap(hexToBytes("76616c";
 
+qf = QueryFilter.getNamesFilter(Util.dk("rowA"), new 
QueryPath("Standard1", null, null), ByteBufferUtil.bytes("ttl"));
+cf = qf.getSSTableColumnIterator(reader).getColumnFamily();
+assertTrue(cf != null);
+assertTrue(cf.getColumn(ByteBufferUtil.bytes("ttl")) == null);
+

Re: Reducing confusion around client libraries

[Aaron Morton]

I agree with the importance of the Thrift API. When I starting using Cassandra I found the idiomatic API's hid the true nature of what Cassandra does. It felt like trying to learn how a RDBMS works by learning how something like (java) hibernate or (ms) LINQ works. IMHO Cassandra *is* the thrift/avro API just like any RDBMS *is* the SQL language. Thanks AaronOn 07 Dec, 2010,at 07:15 AM, Hannes Schmidt  wrote:Probably chiming in a little late here, but I liked having the Thrift API
documentation in a prominent place. It is a canonical reference that
describes on a logical level what the system can and can't do. Without that
information it would have been much harder to understand how to use the
Hector client. And without that information I wouldn't have been able to
pinpoint bugs in libcassandra.

Having a language- and platform-independent interface specification is worth
gold in my opinion. Moving the clients under the umbrella of the project
would increase the danger that the vetted client source becomes the de-facto
reference because it would be temptingly easy to modify server and client in
lock-step for changes of the on-the-wire format without bothering to
document the change.

I also like seeing the competition of ideas in the client world. I think it
will take some time for the API to mature and settle and a wider variety of
client architectures needs to be evaluated before a set of vetted clients
should be chosen.

On Sun, Dec 5, 2010 at 6:48 AM, Simon Reavely wrote:

> Maybe there needs to be a "listing criteria" for a client library, that
> includes things like examples for what is considered enough to get folks
> started (connections, reads, writes, etc) in addition to what Ran
> suggested "[maintainer, last release, next release, support
> forum, number of committers, number of users, spring support, jpa support
> etc]." I would also have a "who's using us" column as well.
>
> If the library maintainer does not satisfy the listing criteria they can't
> get listed. Then we just need to decide what the criteria is ;-)
>
> Other than understanding how up to date and frequently maintained a library
> is I think that (full) good examples are essential.
>
> Having said that, I am not actually against some hierarchical organization
> in which there is some form of "tested/verified" client library list, then
> "others". To keep things fair the question would then be how something gets
> to be "tested/verified". In an opensource community I expect the library
> developers could take some of this on themselves even if the
> testing/verification is part of the main builds by way of some form of
> plugin/test suite but my level of thinking on this is shallow.
>
> Just my 2 cents/pennies on this topic!
>
> Cheers,
> Simon
>
> On Fri, Dec 3, 2010 at 4:07 PM, Ran Tavory  wrote:
>
> > As developer of one of the client libraries I can say that competition
> > keeps
> > us the library maintainers healthy and in the long run creates more value
> > to
> > the users so we should keep competition fair.
> > I can certainly see Jonathan's point regarding the level of confusion b/w
> > newcomers and I'm all for reducing it, but only as long as there's a fair
> > chance for all clients to evolve.
> > To the points that the server can provide a better interface (avro or CQL
> > and what have you), I think this can improve overall client development
> but
> > will not eliminate the need for clients, there will always be a higher
> > level
> > and nicer interface a client can provide or plugins to 3rd party (spring
> > and
> > such) so it does not solve the confusion problem, there will always be
> more
> > clients as long as cassandra keeps evolving.
> >
> > I like transparency and I think that if you present users enough data
> they
> > will be able to decide mind, even new comers. It would be correct to say
> > that generally folks who'd been involved with cassandra for a few years
> are
> > better informed than newcomers however it is sometimes hard to make an
> > objective decision and it's also hard to make a one-size-fits-all
> decision,
> > for example some clients implement feature x and not y and for most users
> > it
> > makes a lot of sense only that for some users they need y and not x. We
> > need
> > to be transparent and list the features and tradeoffs and let the users
> > decide.
> > I like Paul's idea of a table with a list of libraries and for each
> library
> > a set of columns such as [maintainer, last release, next release, support
> > forum, number of committers, number of users, spring support, jpa support
> > etc]. There's a challenge of keeping this table up to date but on the
> other
> > hand if a library maintainer does not keep his row up to date then it's a
> > signal. If voting can be made easily then I'm all for it as well as part
> of
> > this table. I don't think the table would be huge, it's probably 2-3 per
> > language.
> >
> >
> > On Fri, Dec 3, 2010 at 10:25 PM, Paul Brown 
> wrote:

Re: Multi-tenancy, and authentication and authorization

[Aaron Morton]

Have a read about JVM heap sizing here 
http://wiki.apache.org/cassandra/MemtableThresholds

If you let people create keyspaces with a mouse click you will soon run out of 
memory.

I use Cassandra to provide a self service "storage service" at my organisation. 
All virtual databases operate in the same Cassandra keyspace (which does not 
change), and I use namespaces in the keys to separate things. Take a look at 
how amazon S3 works, it may give you some ideas.

If you want to continue to discussion let's move this to the user list.

A
 

On 17/01/2011, at 7:44 PM, indika kumara  wrote:

> Hi Stu,
> 
> In our app,  we would like to offer cassandra 'as-is' to tenants. It that
> case, each tenant should be able to create Keyspaces as needed. Based on the
> authorization, I expect to implement it. In my view, the implementation
> options are as follows.
> 
> 1) The name of a keyspace would be 'the actual keyspace name' + 'tenant ID'
> 
> 2) The name of a keyspace would not be changed, but the name of a column
> family would be the 'the actual column family name' + 'tenant ID'.  It is
> needed to keep a separate mapping for keyspace vs tenants.
> 
> 3) The name of a keypace or a column family would not be changed, but the
> name of a column would be 'the actual column name' + 'tenant ID'. It is
> needed to keep separate mappings for keyspace vs tenants and column family
> vs tenants
> 
> Could you please give your opinions on the above three options?  if there
> are any issue regarding above approaches and if those issues can be solved,
> I would love to contribute on that.
> 
> Thanks,
> 
> Indika
> 
> 
> On Fri, Jan 7, 2011 at 11:22 AM, Stu Hood  wrote:
> 
>>> (1) has the problem of multiple memtables (a large amount just isn't
>> viable
>> There are some very straightforward solutions to this particular problem: I
>> wouldn't rule out running with a very large number of
>> keyspace/columnfamilies given some minor changes.
>> 
>> As Brandon said, some of the folks that were working on multi-tenancy for
>> Cassandra are no longer focused on it. But the code that was generated
>> during our efforts is very much available, and is unlikely to have gone
>> stale. Would love to talk about this with you.
>> 
>> Thanks,
>> Stu
>> 
>> On Thu, Jan 6, 2011 at 8:08 PM, indika kumara 
>> wrote:
>> 
>>> Thank you very much Brandon!
>>> 
>>> On Fri, Jan 7, 2011 at 12:40 AM, Brandon Williams 
>>> wrote:
>>> 
 On Thu, Jan 6, 2011 at 12:33 PM, indika kumara  wrote:
 
> Hi Brandon,
> 
> I would like you feedback on my two ideas for implementing mufti
>>> tenancy
> with the existing implementation.  Would those be possible to
>>> implement?
> 
> Thanks,
> 
> Indika
> 
>> Two vague ideas: (1) qualified keyspaces (by the tenet domain)
>>> (2)
> multiple Cassandra storage configurations in a single node (one per
> tenant).
> For both options, the resource hierarchy would be /cassandra/
> //keyspaces//
> 
 
 (1) has the problem of multiple memtables (a large amount just isn't
>>> viable
 right now.)  (2) more or less has the same problem, but in JVM
>> instances.
 
 I would suggest a) not trying to offer cassandra itself, and instead
>>> build
 a
 service that uses cassandra under the hood, and b) splitting up tenants
>>> in
 this layer.
 
 -Brandon
 
>>> 
>> 

Looking for Cassandra work.

[aaron morton]

I've decided to leave Weta Digital so I can spend more time working on and with 
Cassandra. If you would like to hire me from mid March please contact me 
directly on aa...@thelastpickle.com

I'm an Australian based in New Zealand and have skills in Python, Java, C#, 
Cassandra and other No Sql's , RDBMS, web and fat client development. 


Cheers
Aaron 

Re: [VOTE] 0.7.1 (3 times the charm?)

[aaron morton]

I just re-opened CASSANDRA-2081 
https://issues.apache.org/jira/browse/CASSANDRA-2081 there was a bug in 
StorageProxy.scan() that may need to be included. 

I listed another possible Message problem in the ticket, may pay to get someone 
else to give the StorageProxy a good going over. 

Aaron

On 5/02/2011, at 3:06 PM, Jeremy Hanna wrote:

> Just wondering - how does the distributed test framework fit into votes?  
> Does it get run each time a vote happens to check for bugs/regressions?
> 
> On Feb 4, 2011, at 1:40 PM, Eric Evans wrote:
> 
>> 
>> Lather. Rinse. Repeat.  Ya'll know the drill.
>> 
>> SVN:
>> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1067260
>> 0.7.1 artifacts: http://people.apache.org/~eevans
>> 
>> The vote will be open for 72 hours.
>> 
>> 
>> [1]: http://goo.gl/axEK0 (CHANGES.txt)
>> [2]: http://goo.gl/66yGY (NEWS.txt)
>> 
>> -- 
>> Eric Evans
>> eev...@rackspace.com
>> 
> 

Re: Using Cassandra-cli

[Aaron Morton]

There is also extensive online help in cassandra-clihelp;AaronOn 08 Feb, 2011,at 07:24 AM, Vishal Gupta  wrote:Hi,

there is a README.txt file in CASSANDRA_HOME which presents clear steps to
use get and set command Also i guess you need to first use Keyspace and
then fire set command.

Regards,
vishal

On Mon, Feb 7, 2011 at 11:43 PM, Eranda Sooriyabandara <0704...@gmail.com>wrote:

> Hi all,
> I tried Cassandra cli option in my machine. Here are my cli commands and
> the
> outputs.
>
> >>./cassandra-cli -host localhost -port 9160 -username eranda -keyspace
> keyspace1 -password eranda
> Keyspace 'keyspace1' not found.
>
> >>./cassandra-cli -host localhost -port 9160
> Connected to: "Test Cluster" on localhost/9160
> Welcome to cassandra CLI.
>
> [default@unknown] set keyspace1.standard['emahesh']['first']='eranda';
> Syntax error at position 13: mismatched input '.' expecting '['
>
> As the output say my commands did not work well. Here I used the commands
> which is in http://wiki.apache.org/cassandra/CassandraCli. I couldn't find
> the error of mine. Can anyone please help me to figure out the error.
>
> thanks
> Eranda
>

Re: How do secondary indices work

[Aaron Morton]

Moving to the user group.On 08 Feb, 2011,at 11:39 PM, alta...@ceid.upatras.gr wrote:Hello,

I'd like some information about how secondary indices work under the hood.

1) Is data stored in some external data structure, or is it stored in an
actual Cassandra table, as columns within column families?
2) Is data stored sorted or not? How is it partitioned?
3) How can I access index data?

Thanks in a advance,

Alexander Altanis

Re: Monitoring Cluster with JMX

[Aaron Morton]

Can't you get the length of the list on the monitoring side of things ?aaronOn 08 Feb, 2011,at 10:25 PM, Roland Gude  wrote:Hello,

we are trying to monitor our cassandra cluster with Nagios JMX checks. While there are JMX attributes which expose the list of reachable/unreachable hosts, it would be very helpful to have additional numeric attributes exposing the size of these lists. This could be used to set thresholds (in Nagios monitoring) i.e. at least 3 hosts must be reachable before Nagios issues a warning.
This is probably not hard to do and we are willing to implement/supply patches if someone could point us in the right direction on where to implement it.

Greetings,
roland

--
YOOCHOOSE GmbH

Roland Gude
Software Engineer

Im Mediapark 8, 50670 Köln

+49 221 4544151 (Tel)
+49 221 4544159 (Fax)
+49 171 7894057 (Mobil)


Email: roland.g...@yoochoose.com
WWW: www.yoochoose.com>

YOOCHOOSE GmbH
Geschäftsführer: Dr. Uwe Alkemper, Michael Friedmann
Handelsregister: Amtsgericht Köln HRB 65275
Ust-Ident-Nr: DE 264 773 520
Sitz der Gesellschaft: Köln

Gossip messages at DEBUG

[Aaron Morton]

I've just put the latest 0.7 build on a node and it's logging gossip messages at DEBUG and making the logs really hard to use. Anyone object to moving these to TRACE level ? e.g.here's 6 in a second for a machine doing nothing. DEBUG [GossipStage:1] 2011-02-09 15:56:04,259 MessagingService.java (line org.apache.cassandra.net.MessagingService.sendOneWay(MessagingService.java:302)) jb04/192.168.114.63 sending GOSSIP_DIGEST_ACK to 9815@/192.168.114.67DEBUG [ScheduledTasks:1] 2011-02-09 15:56:04,424 MessagingService.java (line org.apache.cassandra.net.MessagingService.sendOneWay(MessagingService.java:302)) jb04/192.168.114.63 sending GOSSIP_DIGEST_SYN to 9816@/192.168.114.67DEBUG [ScheduledTasks:1] 2011-02-09 15:56:04,424 MessagingService.java (line org.apache.cassandra.net.MessagingService.sendOneWay(MessagingService.java:302)) jb04/192.168.114.63 sending GOSSIP_DIGEST_SYN to 9817@/192.168.114.65DEBUG [GossipStage:1] 2011-02-09 15:56:04,424 MessagingService.java (line org.apache.cassandra.net.MessagingService.sendOneWay(MessagingService.java:302)) jb04/192.168.114.63 sending GOSSIP_DIGEST_ACK2 to 9818@/192.168.114.67DEBUG [GossipStage:1] 2011-02-09 15:56:04,424 MessagingService.java (line org.apache.cassandra.net.MessagingService.sendOneWay(MessagingService.java:302)) jb04/192.168.114.63 sending GOSSIP_DIGEST_ACK2 to 9819@/192.168.114.65DEBUG [GossipStage:1] 2011-02-09 15:56:04,483 MessagingService.java (line org.apache.cassandra.net.MessagingService.sendOneWay(MessagingService.java:302)) jb04/192.168.114.63 sending GOSSIP_DIGEST_ACK to 9820@/192.168.114.66Aaron

Re: Gossip messages at DEBUG

[Aaron Morton]

thanks.AOn 10 Feb, 2011,at 08:21 AM, Brandon Williams  wrote:On Tue, Feb 8, 2011 at 9:01 PM, Aaron Morton <aa...@thelastpickle.com>wrote:

> I've just put the latest 0.7 build on a node and it's logging gossip
> messages at DEBUG and making the logs really hard to use. Anyone object to
> moving these to TRACE level ?
>

Moved to TRACE.  I think when this was moved from sendRR to sendOneWay
gossip wasn't considered.

-Brandon

Re: RE: SEVERE Data Corruption Problems

[Aaron Morton]

Looks like the bloom filter for the row is corrupted, does it happen for all reads or just for reads on one row ? After the upgrade to 0.7 (assuming an 0.7 nightly build) did you run anything like nodetool repair ? Have you tried asking on the #cassandra IRC room to see if their are any comitters around ? AaronOn 11 Feb, 2011,at 01:18 PM, Dan Hendry  wrote:Upgraded one node to 0.7. Its logging exceptions like mad (thousands per
minute). All like below (which is fairly new to me):

ERROR [ReadStage:721] 2011-02-10 18:13:56,190 AbstractCassandraDaemon.java
(line 114) Fatal exception in thread Threa
d[ReadStage:721,5,main]
java.io.IOError: java.io.EOFException
at
org.apache.cassandra.db.columniterator.SSTableNamesIterator.(SSTableNa
mesIterator.java:75)
at
org.apache.cassandra.db.filter.NamesQueryFilter.getSSTableColumnIterator(Nam
esQueryFilter.java:59)
at
org.apache.cassandra.db.filter.QueryFilter.getSSTableColumnIterator(QueryFil
ter.java:80)
at
org.apache.cassandra.db.ColumnFamilyStore.getTopLevelColumns(ColumnFamilySto
re.java:1275)
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.
java:1167)
at
org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.
java:1095)
at org.apache.cassandra.db.Table.getRow(Table.java:384)
at
org.apache.cassandra.db.SliceByNamesReadCommand.getRow(SliceByNamesReadComma
nd.java:60)
at
org.apache.cassandra.service.StorageProxy$LocalReadRunnable.runMayThrow(Stor
ageProxy.java:473)
at
org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
va:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
08)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:375)
at
org.apache.cassandra.utils.BloomFilterSerializer.deserialize(BloomFilterSeri
alizer.java:48)
at
org.apache.cassandra.utils.BloomFilterSerializer.deserialize(BloomFilterSeri
alizer.java:30)
at
org.apache.cassandra.io.sstable.IndexHelper.defreezeBloomFilter(IndexHelper.
java:108)
at
org.apache.cassandra.db.columniterator.SSTableNamesIterator.read(SSTableName
sIterator.java:106)
at
org.apache.cassandra.db.columniterator.SSTableNamesIterator.(SSTableNa
mesIterator.java:71)
... 12 more

Dan


-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com] 
Sent: February-09-11 18:14
To: dev
Subject: Re: SEVERE Data Corruption Problems

Hi Dan,

it would be very useful to test with 0.7 branch instead of 0.7.0 so at
least you're not chasing known and fixed bugs like CASSANDRA-1992.

As you say, there's a lot of people who aren't seeing this, so it
would also be useful if you can provide some kind of test harness
where you can say "point this at a cluster and within a few hours

On Wed, Feb 9, 2011 at 4:31 PM, Dan Hendry 
wrote:
> I have been having SEVERE data corruption issues with SSTables in my
> cluster, for one CF it was happening almost daily (I have since shut down
> the service using that CF as it was too much work to manage the Cassandra
> errors). At this point, I can’t see how it is anything but a Cassandra bug
> yet it’s somewhat strange and very scary that I am the only one who seems
to
> be having such serious issues. Most of my data is indexed in two ways so I
> have been able to write a validator which goes through and back fills
> missing data but it’s kind of defeating the whole point of Cassandra. The
> only way I have found to deal with issues when they crop up to prevent
nodes
> crashing from repeated failed compactions is delete the SSTable. My
cluster
> is running a slightly modified 0.7.0 version which logs what files errors
> for so that I can stop the node and delete them.
>
>
>
> The problem:
>
> -  Reads, compactions and hinted handoff fail with various
> exceptions (samples shown at the end of this email) which seem to indicate
> sstable corruption.
>
> -  I have seen failed reads/compactions/hinted handoff on 4 out of
4
> nodes (RF=2) for 3 different super column families and 1 standard column
> family (4 out of 11) and just now, the Hints system CF. (if it matters the
> ring has not changed since one CF which has been giving me trouble was
> created). I have check SMART disk info and run various diagnostics and
there
> does not seem to be any hardware issues, plus what are the chances of all
> four nodes having the same hardware problems at the same time when for all
> other purposes, they appear fine?
>
> -  I have added logging which outputs what sstable are causing
> exceptions to be thrown. The corrupt sstables have been both freshly
flushed
> memtables and the output of compaction (ie, 4 sstables which all seem to
be
> fine get comp

6.12 release?

[Aaron Morton]

A guy on the user list has asked about getting a 6.12 release out that includes the fix for CASSANDRA-2081. Without it get_range_slice where CL > ONE will timeout as the message id's are reused. Jonathan has back ported the relevant parts of the second patch (which concerned get_indexed_slices) from the ticket. Can we get this one released?Aaron

rewriting cli help

[Aaron Morton]

I'm working on moving the cli online help into a yaml file for ease of maintenance and am now trying to merge the existing cli help with whats in cassandra.yaml and the wiki. If you have any desires for how it should look please comment on the https://issues.apache.org/jira/browse/CASSANDRA-2008ThanksAaron

Re: Data model

[aaron morton]

Will answer on the user list. 

Aaron

On 8/03/2011, at 1:11 AM, Baskar wrote:

> Does Cassandra allow nesting of column families?
> 
> Here is the use case
> - we need to store calls made by employees
> - employees are associated with an account
> - accounts have phone numbers
> - many calls are made by employees for a given account and phone 
> 
> If possible, would like to store call related data against employee. 
> 
> Thanks
> Baskar

Fwd: batch inserts in cassandra 0.7

[aaron morton]

batch_insert was depricated in 0.6, you should have been using batch_mutate 
http://wiki.apache.org/cassandra/API

Aaron

Begin forwarded message:

> From: Anurag Gujral 
> Date: 16 March 2011 10:04:56 GMT+13:00
> To: dev@cassandra.apache.org
> Subject: batch inserts in cassandra 0.7
> Reply-To: dev@cassandra.apache.org
> 
> Hi All,
>  I am moving from cassandra 0.6 to 0.7  I was using  function
> send_batch_inserts to do batch inserts in cassandra 0.6 when I moved to 0.7
> I dont see the function send_batch_insert
> is there a way to do batch inserts in cassandra 0.7 using thrift-0.0.5.
> 
> Thanks
> Anurag

Re: Limitations on number of secondary indexes

[aaron morton]

Moving to user.
Aaron

On 20 Apr 2011, at 10:45, Jason Kolb wrote:

> I apologize if this has been answered before, I've tried to do some pretty
> exhaustive searching of the archives and haven't been able to see if this
> question has been answered before.
> 
> I was wondering if anyone knows if there is a practical upper limit on the
> number of secondary indexes used, if they're sparsely populated (say, 10,000
> secondary indexes only 2 of which are populated per row).  My understanding
> is that Cassandra creates another column family for each secondary index in
> the background, so the real limitation would appear to be the number of
> column families.
> 
> Is this correct?  And if so (or even if not), does anyone know the answer to
> the question about the upper limit on the number of secondary indexes?
> 
> Thanks!
> Jason

Re: Compacting single file forever

[aaron morton]

Moving to the user list. 

Aaron

On 20 Apr 2011, at 21:25, Shotaro Kamio wrote:

> Hi,
> 
> I found that our cluster repeats compacting a single file forever
> (cassandra 0.7.5). We are wondering if compaction logic is wrong. I'd
> like to have comments from you guys.
> 
> Situation:
> - After trying to repair a column family, our cluster's disk usage is
> quite high. Cassandra cannot compact all sstables at once. I think it
> repeats compacting single file at the end. (you can check the attached
> log below)
> - Our data doesn't have deletes. So, the compaction of single file
> doesn't make free disk space.
> 
> We are approaching to full-disk. But I believe that the repair
> operation made a lot of duplicate data on the disk and it requires
> compaction. However, most of nodes stuck on compacting a single file.
> The only thing we can do is to restart the nodes.
> 
> My question is why the compaction doesn't stop.
> 
> I looked at the logic in CompactionManager.java:
> -
>String compactionFileLocation =
> table.getDataFileLocation(cfs.getExpectedCompactedFileSize(sstables));
>// If the compaction file path is null that means we have no
> space left for this compaction.
>// try again w/o the largest one.
>List smallerSSTables = new
> ArrayList(sstables);
>while (compactionFileLocation == null && smallerSSTables.size() > 1)
>{
>logger.warn("insufficient space to compact all requested
> files " + StringUtils.join(smallerSSTables, ", "));
>smallerSSTables.remove(cfs.getMaxSizeFile(smallerSSTables));
>compactionFileLocation =
> table.getDataFileLocation(cfs.getExpectedCompactedFileSize(smallerSSTables));
>}
>if (compactionFileLocation == null)
>{
>logger.error("insufficient space to compact even the two
> smallest files, aborting");
>return 0;
>}
> -
> 
> The while condition: smallerSSTables.size() > 1
> Is this should be "smallerSSTables.size() > 2" ?
> 
> In my understanding, compaction of single file makes free disk space
> only when the sstable has a lot of tombstone and only if the tombstone
> is removed in the compaction. If cassandra knows the sstable has
> tombstones to be removed, it's worth to compact it. Otherwise, it
> might makes free space if you are lucky. In worst case, it leads to
> infinite loop like our case.
> 
> What do you think the code change?
> 
> 
> Best regards,
> Shotaro
> 
> 
> * Cassandra compaction log
> -
> WARN [CompactionExecutor:1] 2011-04-20 01:03:14,446
> CompactionManager.java (line 405) insufficient space to compact all
> requested files SSTableReader(
> path='foobar-f-3020-Data.db'), SSTableReader(path='foobar-f-3034-Data.db')
> INFO [CompactionExecutor:1] 2011-04-20 03:47:29,833
> CompactionManager.java (line 482) Compacted to
> foobar-tmp-f-3035-Data.db.  260,646,760,319 to 260,646,760,319 (~100%
> of original) bytes for 6,893,896 keys.  Time: 9,855,385ms.
> 
> WARN [CompactionExecutor:1] 2011-04-20 03:48:11,308
> CompactionManager.java (line 405) insufficient space to compact all
> requested files SSTableReader(path='foobar-f-3020-Data.db'),
> SSTableReader(path='foobar-f-3035-Data.db')
> INFO [CompactionExecutor:1] 2011-04-20 06:31:41,193
> CompactionManager.java (line 482) Compacted to
> foobar-tmp-f-3036-Data.db.  260,646,760,319 to 260,646,760,319 (~100%
> of original) bytes for 6,893,896 keys.  Time: 9,809,882ms.
> 
> WARN [CompactionExecutor:1] 2011-04-20 06:32:22,476
> CompactionManager.java (line 405) insufficient space to compact all
> requested files SSTableReader(path='foobar-f-3020-Data.db'),
> SSTableReader(path='foobar-f-3036-Data.db')
> INFO [CompactionExecutor:1] 2011-04-20 09:20:29,903
> CompactionManager.java (line 482) Compacted to
> foobar-tmp-f-3037-Data.db.  260,646,760,319 to 260,646,760,319 (~100%
> of original) bytes for 6,893,896 keys.  Time: 10,087,424ms.
> -
> You can see that compacted size is always the same. It repeats
> compacting the same single sstable.

Fwd: Error trying to move a node - 0.7

[aaron morton]

Will answer on the user list. 

-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com

Begin forwarded message:

> From: Ben Frank 
> Date: 17 June 2011 07:42:07 GMT+12:00
> To: dev@cassandra.apache.org
> Subject: Error trying to move a node - 0.7
> Reply-To: dev@cassandra.apache.org
> 
> Hi All,
>   I'm getting the following error when trying to move a nodes token:
> 
> nodetool -h 145.6.92.82 -p 18080 move 56713727820156410577229101238628035242
> cassandra.in.sh executing for environment DEV1
> Exception in thread "main" java.lang.AssertionError
>at
> org.apache.cassandra.locator.TokenMetadata.firstTokenIndex(TokenMetadata.java:393)
>at
> org.apache.cassandra.locator.TokenMetadata.ringIterator(TokenMetadata.java:418)
>at
> org.apache.cassandra.locator.NetworkTopologyStrategy.calculateNaturalEndpoints(NetworkTopologyStrategy.java:94)
>at
> org.apache.cassandra.service.StorageService.calculatePendingRanges(StorageService.java:807)
>at
> org.apache.cassandra.service.StorageService.calculatePendingRanges(StorageService.java:773)
>at
> org.apache.cassandra.service.StorageService.startLeaving(StorageService.java:1468)
>at
> org.apache.cassandra.service.StorageService.move(StorageService.java:1605)
>at
> org.apache.cassandra.service.StorageService.move(StorageService.java:1580)
> .
> .
> .
> 
> my ring looks like this:
> 
> Address Status State   LoadOwnsToken
> 
> 113427455640312821154458202477256070484
> 145.6.99.80  Up Normal  1.63 GB 36.05%
> 4629135223504085509237477504287125589
> 145.6.92.82  Up Normal  2.86 GB 1.09%
> 6479163079760931522618457053473150444
> 145.6.99.81  Up Normal  2.01 GB 62.86%
> 113427455640312821154458202477256070484
> 
> 
> '80' and '81' are configured to be in the East coast data center and '82' is
> in the West
> 
> Anyone shed any light as to what might be going on here?
> 
> -Ben

Re: Reoganizing drivers

[aaron morton]

I can see the drivers have moved to
http://svn.apache.org/repos/asf/cassandra/drivers/

Just wondering where that path is available on 
git://git.apache.org/cassandra.git

These are the remote branches I can find 

$ git ls-remote  | grep drivers
From git://git.apache.org/cassandra.git
20635cec24389d83b146af51fa902fcf2d21491brefs/remotes/tags/drivers
dd06878fa6b143dbff1e1e338087041b1b230d48refs/tags/drivers
20635cec24389d83b146af51fa902fcf2d21491brefs/tags/drivers^{}

Thanks
A

-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com

On 8 Jun 2011, at 05:01, Eric Evans wrote:

> On Tue, 2011-06-07 at 18:40 +0200, Sylvain Lebresne wrote:
>> On Tue, Jun 7, 2011 at 3:18 PM, Jonathan Ellis 
>> wrote:
>>> Sounds fine as far as it goes, but don't we want some concept of
>>> branches/tags for driver releases too?
>> 
>> Our idea so far (Eric can correct me if I'm wrong :)) was to consider
>> the drivers directory as the 'trunk' for drivers, and create branches
>> and tags for them alongside the cassandra ones.
> 
> Yup.  In fact, I already tagged the Python and Java drivers as
> tags/drivers// during the last release (neither of those
> driver artifacts corresponded to the same SVN rev, nor did they
> correspond to the rev for 0.8.0).
>> 
>> Truth is, I even think that consider the drivers as a whole is not
>> granular enough. It's unlikely the different drivers will move at the
>> same pace.
> 
> As far as I know, there is no reason that a tag (say
> tags/drivers/py/1.1.1) can't point to a subdirectory of drivers/ (i.e.
> drivers/py).  In fact, that's how the tags mentioned above were done
> (except those pointed to branches/cassandra-0.8.0/drivers/).  I
> think it just boils down to a matter convention.
>> 
>> *But*, we believe that moving the drivers up one level is at least a
>> first step towards something better than the status quo.
> 
> Yeah, even if we decide to do something different later on, this is an
> improvement over what we have now. 
> 
> -- 
> Eric Evans
> eev...@rackspace.com
> 

Re: Reoganizing drivers

[aaron morton]

Asked on #asfinfra and was told the only things mirrored on git are trunk / 
tags / branches . 

git-svn it is. 

Cheers

-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com

On 20 Jun 2011, at 16:28, Jonathan Ellis wrote:

> Maybe the non-standard path is giving the git mirror fits.
> 
> On Sun, Jun 19, 2011 at 11:26 PM, aaron morton  
> wrote:
>> I can see the drivers have moved to
>> http://svn.apache.org/repos/asf/cassandra/drivers/
>> 
>> Just wondering where that path is available on 
>> git://git.apache.org/cassandra.git
>> 
>> These are the remote branches I can find
>> 
>> $ git ls-remote  | grep drivers
>> From git://git.apache.org/cassandra.git
>> 20635cec24389d83b146af51fa902fcf2d21491brefs/remotes/tags/drivers
>> dd06878fa6b143dbff1e1e338087041b1b230d48refs/tags/drivers
>> 20635cec24389d83b146af51fa902fcf2d21491brefs/tags/drivers^{}
>> 
>> Thanks
>> A
>> 
>> -
>> Aaron Morton
>> Freelance Cassandra Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>> 
>> On 8 Jun 2011, at 05:01, Eric Evans wrote:
>> 
>>> On Tue, 2011-06-07 at 18:40 +0200, Sylvain Lebresne wrote:
>>>> On Tue, Jun 7, 2011 at 3:18 PM, Jonathan Ellis 
>>>> wrote:
>>>>> Sounds fine as far as it goes, but don't we want some concept of
>>>>> branches/tags for driver releases too?
>>>> 
>>>> Our idea so far (Eric can correct me if I'm wrong :)) was to consider
>>>> the drivers directory as the 'trunk' for drivers, and create branches
>>>> and tags for them alongside the cassandra ones.
>>> 
>>> Yup.  In fact, I already tagged the Python and Java drivers as
>>> tags/drivers// during the last release (neither of those
>>> driver artifacts corresponded to the same SVN rev, nor did they
>>> correspond to the rev for 0.8.0).
>>>> 
>>>> Truth is, I even think that consider the drivers as a whole is not
>>>> granular enough. It's unlikely the different drivers will move at the
>>>> same pace.
>>> 
>>> As far as I know, there is no reason that a tag (say
>>> tags/drivers/py/1.1.1) can't point to a subdirectory of drivers/ (i.e.
>>> drivers/py).  In fact, that's how the tags mentioned above were done
>>> (except those pointed to branches/cassandra-0.8.0/drivers/).  I
>>> think it just boils down to a matter convention.
>>>> 
>>>> *But*, we believe that moving the drivers up one level is at least a
>>>> first step towards something better than the status quo.
>>> 
>>> Yeah, even if we decide to do something different later on, this is an
>>> improvement over what we have now.
>>> 
>>> --
>>> Eric Evans
>>> eev...@rackspace.com
>>> 
>> 
>> 
> 
> 
> 
> -- 
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com

Re: Cassandra Pig with network topology and data centers.

[Aaron Griffith]

Ryan King  twitter.com> writes:

> 
> It'd be great if we had different settings for inter- and intra-DC read 
> repair.
> 
> -ryan
> 


Is there a formula or standard for lowering read repair chance to running
analytics on one DC doesn't hammer the other datacenter?

How low can you set the read repair chance?

CASSANDRA-2249 not in CHANGES.txt for 1.0

[aaron morton]

It's in NEWS should it also be in CHANGES?

https://issues.apache.org/jira/browse/CASSANDRA-2449

Cheers


-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com

wiki updates

[aaron morton]

With 1.0 almost here I was going to try and spruce up the wiki a bit to make 
things a little more welcoming for new users. 

I've created a copy of the home page here 
http://wiki.apache.org/cassandra/FrontPage_draft_aaron as a working draft. 

I've re-aranged things a little, and added some links to pages that do not yet 
exist. I was going to use it as a planning tool by working through all the 
pages linked there to see if they needed updated examples, or were yet to be 
written, that sort of thing. 

Thoughts ? 

I'll probably ask for some volunteers on the user list. 

Cheers

-----
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com

Re: wiki updates

[aaron morton]

Ok, I'll go ahead and work out a way for people to contribute.

@Nick, yes to include CQL examples, and to give them first, but I would also 
keep the rpc call for now. As the RPC interface is still officially supported. 

@Yang, Happy to re-arrange things once we have some content. For better or 
worse I used the Hive wiki as guide 
https://cwiki.apache.org/confluence/display/Hive/Home  . Creating new content 
takes time, first I'd like to improve what we have and make sure it is correct. 


Thanks

-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com

On 7/10/2011, at 1:24 AM, Yi Yang wrote:

> 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 include the Data Model section in
> it - people will easily get to know what's the difference between Cassandra
> and other key based databases like HBase, MangoDB etc., therefore make wise
> choices.
> 
> 2) The second part could give a glance at how to make Cassandra running on a
> small to moderate level application - aka the a small development platform.
>  Including how to create a cluster and also running on Windows / Amazon
> EC2. Here StorageConfiguration is not so important because the target of
> this section is to help users build up a usable Cassandra Cluster.
> 
> 3) The third part can help the administrators of large scale application,
> and also introducing management strategies like storage configuration and
> also other monitoring, node operations techniques.
> 
> The rest parts are perfect. I hope we can match the list with a typical
> users' learning experience, so that for users at different level they can
> focus on their own section. It's just my own idea - and it might different
> from others' experiences, hopefully it could help. Thanks again for the
> great work.
> 
> Best,
> Yi
> 
> On Thu, Oct 6, 2011 at 7:29 PM, aaron morton wrote:
> 
>> With 1.0 almost here I was going to try and spruce up the wiki a bit to
>> make things a little more welcoming for new users.
>> 
>> I've created a copy of the home page here
>> http://wiki.apache.org/cassandra/FrontPage_draft_aaron as a working draft.
>> 
>> I've re-aranged things a little, and added some links to pages that do not
>> yet exist. I was going to use it as a planning tool by working through all
>> the pages linked there to see if they needed updated examples, or were yet
>> to be written, that sort of thing.
>> 
>> Thoughts ?
>> 
>> I'll probably ask for some volunteers on the user list.
>> 
>> Cheers
>> 
>> -
>> Aaron Morton
>> Freelance Cassandra Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>> 
>> 

Re: cassandra node is not starting

[aaron morton]

What version of cassandra and what OS ? 

It sort of looks like it tried to delete a secondary in CF that was defined in 
the system KS. 

Turn the logging up to DEBUG and see what happens. 

Hope that helps. 
Aaron

-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com

On 1/01/2012, at 11:20 PM, Michael Vaknine wrote:

> Hi,
> 
> 
> 
> During restart cassandra not is failing to start
> 
> The error is
> 
> ERROR [main] 2012-01-01 05:03:42,903 AbstractCassandraDaemon.java (line 354)
> Exception encountered during startup
> 
> java.lang.AssertionError: attempted to delete non-existing file
> AttractionUserIdx.AttractionUserIdx_09partition_idx-h-1-Data.db
> 
>at
> org.apache.cassandra.io.util.FileUtils.deleteWithConfirm(FileUtils.java:49)
> 
>at
> org.apache.cassandra.io.util.FileUtils.deleteWithConfirm(FileUtils.java:44)
> 
>at org.apache.cassandra.io.sstable.SSTable.delete(SSTable.java:133)
> 
>at
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyS
> tore.java:355)
> 
>at
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyS
> tore.java:402)
> 
>at
> org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandra
> Daemon.java:174)
> 
>at
> org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassan
> draDaemon.java:337)
> 
>at
> org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:107)
> 
> 
> 
> can someone tell me how to recover from that
> 
> thanks
> 
> 
> 
> Michael 
> 

Re: Welcome committer Aaron Morton!

[aaron morton]

Thanks Jonathan and the other committers.

Cheers :)
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com

On 19/01/2012, at 7:19 AM, Jonathan Ellis wrote:

> The Apache Cassandra PMC has voted to add Aaron as a committer.
> Thanks for helping make Cassandra what it is today!
> 
> -- 
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com