Re: [VOTE] Accept java-driver

+1 (nb) Thank you to everyone involved for making this happen. Regards, On Wed, 4 Oct 2023 at 10:34, Nate McCall wrote: > +1 > > On Tue, Oct 3, 2023 at 5:53 PM Mick Semb Wever wrote: > >> The donation of the java-driver is ready for its IP Clearance vote. >>

Re: [DISCUSS] New data type for vector search

It would be strange for this declaration to look different from other collection types. We may want to reconsider using the collection syntax. I also like the idea of the vector dimensions being declared with the VECTOR keyword. An alternative syntax option to explore is: VECTOR[size] On Fri, 28

Re: Welcome Patrick McFadin as Cassandra Committer

Congratulations, Patrick! Well deserved given all the work you do for the community. Kind regards, On Mon, 6 Feb 2023 at 11:39, Paulo Motta wrote: > Congratulations for this well deserved recognition, Patrick! Thank you for > all the energy you inject into this community! :-) > > On Sun, Feb

Re: Should we change 4.1 to G1 and offheap_objects ?

+1 to switching to G1 as well. Most production clusters I've seen are typically running with a heap size of 16 GB or higher which works well with G1. I agree with Elliott's comment; I think this change should go into 4.1 onwards (i.e. no change to the default JVM settings in 4.0). On Fri, 11 Nov

Re: Thanks to Nate for his service as PMC Chair

Thank you, Nate, for all the work you did! Congratulations Mick; you'll do a great job! On Tue, 12 Jul 2022 at 18:46, Benjamin Lerer wrote: > Thank you Nate for all your work! Congratulations Mick! > > Le mar. 12 juil. 2022 à 06:59, Berenguer Blasi > a écrit : > >> Thanks Nate and congrats

Re: Adding RSS feed to the Apache Cassandra website.

This is a good idea! I think option 2 is the best way to go. Currently, there are manual steps involved to publish a post to the blog. I would like to avoid adding more manual work. We could implement option 2 either by: - Bolting on JavaScript for Anotra to use to generate the RSS XML -

Re: Welcome Aleksandr Sorokoumov as Cassandra committer

Congratulations Aleksandr! Thank you for your work on the project. On Thu, 17 Mar 2022 at 12:33, Erick Ramirez wrote: > Congratulations Aleksandr and welcome aboard!  > > On Thu, 17 Mar 2022 at 00:15, Benjamin Lerer wrote: > >> The PMC members are pleased to announce that Aleksandr Sorokoumov

Re: [FOR REVIEW] Blog post: An Interview with Project Contributor, Lorina Poland

+1 On Wed, 16 Mar 2022 at 21:58, bened...@apache.org wrote: > +1 > > > > *From: *Erick Ramirez > *Date: *Tuesday, 15 March 2022 at 22:08 > *To: *dev@cassandra.apache.org > *Subject: *Re: [FOR REVIEW] Blog post: An Interview with Project > Contributor, Lorina Poland > > Looks good to me!  > >

Re: [DISCUSS] Cleaning up docs, completing CASSANDRA-16763

it (under the same Jira ticket number), we will just > > remove that label and the work is done if there are no tickets with > > such label anymore. > > > > Hence we do not create any additional ticket at all, we may even > > reopen tickets which are resolve

Re: [DISCUSS] Cleaning up docs, completing CASSANDRA-16763

> > > > from reStructedText (rST)to AsciiDoc. [1] > > > > > The conversion required both the docs source files to be converted, > > but > > > > > also the cassandra-website > > > > > source to be updated, to build the docs from AsciiDoc

Re: Supported upgrade path for 4.0

Hi Josh, This is a really good question. I agree with David about making sure this is clearly documented. As far as the supported upgrade path goes, I think we should officially support only 3.11.x. I do understand the idea of giving users the flexibility to upgrade from 3.0.x. However, the

Re: [DISCUSS] Updating the C* website design

Hi Lorina and Mick, I've raised CASSANDRA-16066 to capture the effort required to carry out the work of converting the markdown to asciidoc. As part of the work, I think all content files should be moved to cassandra/doc. This would give a

Re: Committing `CASSANDRA-13701 Lower default num_tokens` and the dtest slowdown…

Hi Mick, No objections from me. It will be good to get this change into the 4.0 release. Whilst the slow down of the dtests is annoying, I am happy to see this change committed. As long as there are no regressions in the number of tests that pass then it should be fine. The proposal to raise a

Re: Proof of concept for Cassandra docs conversion

I agree as well. Nice work, Lorina! This POC is a really good start. It has a bit more of a modern feel to it. The navigation bar on the side makes the information very accessible. This is a must for technical documentation. Would it be possible to have a search bar somewhere on the site? I

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

say "this would clean the master > branch history", would the content directory be removed from past commits > using bfg or similar tools? > > (I'm fine with either way; just curious.) > > On Fri, 1 May 2020, 07:12 Anthony Grasso, > wrote: > > > Hi everyone, >

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

Hi everyone, Thanks to hard work by Mick every push to the cassandra-website *src/* directory in master is now automatically deployed to https://cassandra.staged.apache.org/. The automation is carried out by a Jenkins job at https://ci-cassandra.apache.org/job/cassandra-website/. This is really

Re: [VOTE] Release Apache Cassandra 4.0-alpha3

+1 (non-binding) On Fri, 31 Jan 2020 at 08:48, Joshua McKenzie wrote: > +1 > > On Thu, Jan 30, 2020 at 4:31 PM Brandon Williams wrote: > > > +1 > > > > On Thu, Jan 30, 2020 at 1:47 PM Mick Semb Wever wrote: > > > > > > Proposing the test build of Cassandra 4.0-alpha3 for release. > > > > > >

Re: [Discuss] num_tokens default in Cassandra 4.0

I think lowering the number of tokens is a great idea! Similar to Jon, when I have reduced the number of tokens for clients it has been improvement in repair performance. I am concerned that the proposed default value for num_tokens is too low. If you set up a cluster using the proposed defaults,

Re: moving the site from SVN to git

Hi Jon, Thank you for actioning this! The only trivial things that come to mind for me is to do with documentation: - The README file with the instructions to build the site points to SVN - The website Publication page

Re: TLP tools for stress testing and building test clusters in AWS

helpful as we did. > > Regards > > On Wed, 17 Apr 2019 at 10:08, Anthony Grasso > wrote: > > > > Hi Stefan and devs, > > > > I have set up a zoom link for the TLP tool set intro that will be on in > an > > hours time (17 April 2019 @ 11:00AM AEST):

Re: TLP tools for stress testing and building test clusters in AWS

in his meeting tomorrow. Regards, Anthony On Wed, 17 Apr 2019 at 08:29, Anthony Grasso wrote: > Hi Stefan, > > Thanks for sending the invite out! > > Just wondering what do you think of the idea of having a Zoom meeting that > anyone can join? This way anyone else interested c

Re: TLP tools for stress testing and building test clusters in AWS

< stefan.mikloso...@instaclustr.com> wrote: > Hi Anthony, > > sounds good. I ve sent you Hangouts meeting invitation privately. > > Regards > > On Tue, 16 Apr 2019 at 14:53, Anthony Grasso > wrote: > > > > Hi Stefan, > > > > I have been working with Jo

Re: TLP tools for stress testing and building test clusters in AWS

Hi Stefan, I have been working with Jon on developing the tool set. I can do a Zoom call tomorrow (Wednesday) at 11am AEST if that works for you? We can go through all the same information that Jon is going to go through in his call. Note that I am in the same timezone as you, so if tomorrow

Re: [VOTE] Release Apache Cassandra 2.1.21

d page, and move on. I don't think it's > right to continue telling users we are doing something, if we aren't and > haven't been. > > Michael > > On 2/3/19 5:24 PM, Anthony Grasso wrote: > > +1 non-binding, for the release of 2.1.21 > > > > Regarding EOL of 2.1.x,

Re: [VOTE] Release Apache Cassandra 2.1.21

+1 non-binding, for the release of 2.1.21 Regarding EOL of 2.1.x, did we announce in the past that 2.1.21 would be the final release? According to the download page 2.1 is meant to be supported with critical fixes only until 4.0 is released. I suspect that

Re: [VOTE] Release Apache Cassandra 3.0.18

+1 non-binding On Mon, 4 Feb 2019 at 05:52, Jonathan Haddad wrote: > +1 > > On Sun, Feb 3, 2019 at 9:44 AM Nate McCall wrote: > > > On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler > > wrote: > > > > > > I propose the following artifacts for release as 3.0.18. > > > > > > sha1:

Re: [VOTE] Release Apache Cassandra 3.11.4

+1 non-binding On Mon, 4 Feb 2019 at 06:19, Jonathan Haddad wrote: > +1 > > On Sun, Feb 3, 2019 at 9:35 AM Nate McCall wrote: > > > On Sat, Feb 2, 2019 at 4:38 PM Michael Shuler > > wrote: > > > > > > I propose the following artifacts for release as 3.11.4. > > > > > > sha1:

Re: [VOTE] Release Apache Cassandra 2.2.14

+1 non-binding On Mon, 4 Feb 2019 at 04:39, Nate McCall wrote: > On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler > wrote: > > > > I propose the following artifacts for release as 2.2.14. > > > > sha1: af91658353ba601fc8cd08627e8d36bac62e936a > > Git: > > >

Re: unsubscribe

Hi Yang Su Li, To unsubscribe, simply send an email to dev-unsubscr...@cassandra.apache.org . Note, replying to this email does nothing to remove your email address from the list. For further information, please see http://apache.org/foundation/mailinglists.html. Kind regards, Anthony On 23

Re: splitting CQL parser & spec into separate repo

This is a great idea +1 (non-binding) On 22 March 2017 at 07:04, Edward Capriolo wrote: > On Tue, Mar 21, 2017 at 3:24 PM, Mark Dewey wrote: > > > I can immediately think of a project I would use that in. +1 > > > > On Tue, Mar 21, 2017 at 12:18 PM

Re: Can we kill the wiki?

+1 to killing the wiki as well. If that is not possible, we should at least put a note on there saying it is deprecated and point people to the new docs. On 18 March 2017 at 08:09, Jonathan Haddad wrote: > +1 to killing the wiki. > > On Fri, Mar 17, 2017 at 2:08 PM Blake

Re: Contribute to the Cassandra wiki

On 14 March 2017 at 03:55, Jonathan Haddad wrote: > > I urge you to try giving the in-tree docs a chance. It may not be the way > *you* want it but I have to point out that they're the best we've seen in > Cassandra world. Making them prettier won't help anything. > Agreed

Contribute to the Cassandra wiki

Hi My username is AnthonyGrasso and I would like to contribute to the Cassandra wiki please. Kind regards, Anthony