+1
Kind Regards,
Brandon
On Tue, May 21, 2024 at 5:59 PM Bret McGuire wrote:
>
>Greetings all! We're going to give this another go.
>
>Apologies for the confusion that sprang out of our last attempt. It
> appears that the Nexus staging repository for the 4.18.1 release was
>
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0.13.
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
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.1.5.
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
With five +1 (3 binding including my own) and no -1, the vote passes.
I'll get the artifacts published.
Kind Regards,
Brandon
On Thu, May 2, 2024 at 10:16 AM Brandon Williams wrote:
>
> Proposing the test build of Cassandra 4.0.13 for release.
>
> sha1: a6fb3b76feb8467d314b116f9373
With five +1 (4 binding including my own) and no -1, the vote passes.
I'll get the artifacts published.
On Thu, May 2, 2024 at 11:36 AM Brandon Williams
wrote:
>
> Proposing the test build of Cassandra 4.1.5 for release.
>
> sha1: 6b134265620d6b39f9771d92edd29abdfd27de6a
Friendly reminder that this vote is still open and lacks one binding
vote to pass.
On Thu, May 2, 2024 at 11:36 AM Brandon Williams
wrote:
>
> Proposing the test build of Cassandra 4.1.5 for release.
>
> sha1: 6b134265620d6b39f9771d92edd29abdfd27de6a
> Git: https://github.com/a
Friendly reminder that this vote is still open and needs two more binding votes.
Kind Regards,
Brandon
On Thu, May 2, 2024 at 10:16 AM Brandon Williams wrote:
>
> Proposing the test build of Cassandra 4.0.13 for release.
>
> sha1: a6fb3b76feb8467d314b116f937322e1989b42e1
+1
On Thu, May 2, 2024 at 11:36 AM Brandon Williams
wrote:
>
> Proposing the test build of Cassandra 4.1.5 for release.
>
> sha1: 6b134265620d6b39f9771d92edd29abdfd27de6a
> Git: https://github.com/apache/cassandra/tree/4.1.5-tentative
> Maven Artifacts:
> https://reposito
+1
Kind Regards,
Brandon
On Thu, May 2, 2024 at 10:16 AM Brandon Williams wrote:
>
> Proposing the test build of Cassandra 4.0.13 for release.
>
> sha1: a6fb3b76feb8467d314b116f937322e1989b42e1
> Git: https://github.com/apache/cassandra/tree/4.0.13-tentative
> Maven
Hi Raymond,
I've sent you an invite.
Kind Regards,
Brandon
On Tue, May 7, 2024 at 1:41 PM Raymond Welgosh wrote:
>
> Hi,
>
> My name is Raymond Welgosh. I previously emailed the owner so if this was
> resolved please ignore. I am interested in joining the AFS slack. Please let
> me know what
Proposing the test build of Cassandra 4.1.5 for release.
sha1: 6b134265620d6b39f9771d92edd29abdfd27de6a
Git: https://github.com/apache/cassandra/tree/4.1.5-tentative
Maven Artifacts:
Proposing the test build of Cassandra 4.0.13 for release.
sha1: a6fb3b76feb8467d314b116f937322e1989b42e1
Git: https://github.com/apache/cassandra/tree/4.0.13-tentative
Maven Artifacts:
I want to begin by saying I am generally +1 on this because I have
become a fan of easy-cass-stress after using it, but I am curious if
this is intended to be a subproject, or replace cassandra-stress? If
the latter, we are going to have to reconcile the build systems
somehow. I don't really
Congrats everyone!
Kind Regards,
Brandon
On Wed, Apr 17, 2024 at 12:11 PM Benjamin Lerer wrote:
>
> The Apache Cassandra PMC is pleased to announce that Alexandre Dutra, Andrew
> Tolbert, Bret McGuire and Olivier Michallat have accepted the invitation to
> become committers on the java driver
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.17.
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
Minor correction, three votes were binding.
On Tue, Apr 16, 2024 at 7:08 AM Brandon Williams
wrote:
>
> On Fri, Apr 12, 2024 at 1:52 PM Brandon Williams
> wrote:
> > The vote will be open for 72 hours (longer if needed). Everyone who
> > has tested the build is invited
On Fri, Apr 12, 2024 at 1:52 PM Brandon Williams
wrote:
> The vote will be open for 72 hours (longer if needed). Everyone who
> has tested the build is invited to vote. Votes by PMC members are
> considered binding. A vote passes if there are at least three binding
> +1s and no -1'
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.30.
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
On Thu, Apr 11, 2024 at 1:48 PM Brandon Williams
wrote:
> The vote will be open for 72 hours (longer if needed). Everyone who
> has tested the build is invited to vote. Votes by PMC members are
> considered binding. A vote passes if there are at least three binding
> +1s and no -1'
Proposing the test build of Cassandra 3.11.17 for release.
sha1: d079952c50019c3c8c96e341a01f7bc0554e1733
Git: https://github.com/apache/cassandra/tree/3.11.17-tentative
Maven Artifacts:
Proposing the test build of Cassandra 3.0.30 for release.
sha1: 657e595b78227c28a6b8808ef9bf62f646029f3b
Git: https://github.com/apache/cassandra/tree/3.0.30-tentative
Maven Artifacts:
I am +1 on separate projects as well, but to Abe's point I don't think
it matters now, we had 21 binding votes for CEP-8 which spells this
out.
Kind Regards,
Brandon
On Tue, Apr 9, 2024 at 9:24 AM Josh McKenzie wrote:
>
> +1 to separate JIRA projects per subproject. Having workflows distinct to
Given that 3.6 has been EOL for 2+ years[1], I don't think it makes
sense to add support for it back.
Kind Regards,
Brandon
[1] https://devguide.python.org/versions/
On Mon, Mar 11, 2024 at 12:08 PM David Capwell wrote:
>
> Originally we had planned to support RHEL 7 but in testing 5.0 we
Congrats Brad!
Kind Regards,
Brandon
On Wed, Feb 21, 2024 at 2:46 PM Josh McKenzie wrote:
>
> The Apache Cassandra PMC is pleased to announce that Brad Schoening has
> accepted
> the invitation to become a committer.
>
> Your work on the integrated python driver, launch script environment, and
lect only those tests which do not support vnodes. Do you know about such
> in-jvm dtests as well?
>
> - - -- --- - -
> Jacek Lewandowski
>
>
> czw., 15 lut 2024 o 18:21 Brandon Williams napisał(a):
>>
>> On Thu, Feb 15, 2024 at 1:10 AM Jacek
On Thu, Feb 15, 2024 at 1:10 AM Jacek Lewandowski
wrote:
> For dtests we have vnodes/no-vnodes, offheap/onheap, and nothing about other
> stuff. To me running no-vnodes makes no sense because no-vnodes is just a
> special case of vnodes=1. On the other hand offheap/onheap buffers could be
>
On Tue, Feb 13, 2024 at 6:17 AM Sam Tunnicliffe wrote:
> Also, if CASSANDRA-16999 is only going to trunk, why can't we just deprecate
> dual ports in 5.0 (as it isn't at -rc stage yet) and remove it from trunk?
> That seems preferable to shoehorning something into the new
> system_views.peers
I think we lost track of this one over some concern about
CASSANDRA-19097, but that turned out to be a test problem. +1
Kind Regards,
Brandon
On Fri, Jan 26, 2024 at 4:31 AM Štefan Miklošovič
wrote:
>
> Proposing the test build of Cassandra 4.1.4 for release.
>
> sha1:
e:
>
> I think we used to have this and removed them because it was breaking
> the encryption signature on messages or something which meant they were
> very likely to be treated as spam?
>
> Not saying we can’t put it back on, but it was removed for good reasons
> from wha
+1
Kind Regards,
Brandon
On Mon, Jan 22, 2024 at 12:10 PM C. Scott Andreas wrote:
>
> Hi all,
>
> I'd like to propose appending the following two footers to messages sent to
> the user@ and dev@ lists. The proposed postscript including line breaks is
> between the "X" blocks below.
>
>
+1
Kind Regards,
Brandon
On Thu, Jan 18, 2024 at 5:56 AM Štefan Miklošovič
wrote:
>
> Proposing the test build of Cassandra 4.0.12 for release.
>
> sha1: af752fcd535ccdac69b9fed88047b2dd7625801e
> Git: https://github.com/apache/cassandra/tree/4.0.12-tentative
> Maven Artifacts:
>
A configuration option for a cosmetic feature seems like overkill to me, I
don't think which side we align text on is enough to justify (heh) the
overhead. I agree with how Excel and Postgres do it and think we should
follow suit.
Kind Regards,
Brandon
On Tue, Jan 9, 2024 at 9:19 AM Brad
Congrats Maxim!
Kind Regards,
Brandon
On Mon, Jan 8, 2024 at 12:20 PM Josh McKenzie wrote:
>
> The Apache Cassandra PMC is pleased to announce that Maxim Muzafarov has
> accepted
> the invitation to become a committer.
>
> Thanks for all the hard work and collaboration on the project thus far,
+1
Kind Regards,
Brandon
On Sat, Dec 9, 2023 at 1:43 AM Mick Semb Wever wrote:
>
> Proposing the test build of Cassandra Java Driver 4.18.0 for release.
>
> sha1: 105d378fce16804a8af4c26cf732340a0c63b3c9
> Git: https://github.com/apache/cassandra-java-driver/tree/4.18.0
> Maven Artifacts:
>
Congratulations Mike!
Kind Regards,
Brandon
On Fri, Dec 8, 2023 at 8:41 AM Benjamin Lerer wrote:
>
> The PMC members are pleased to announce that Mike Adamson has accepted
> the invitation to become committer.
>
> Thanks a lot, Mike, for everything you have done for the project.
>
>
On Thu, Dec 7, 2023 at 8:50 AM Alex Petrov wrote:
> > I've noticed many "sleeps" in the tests - is it possible with simulation
> > tests to artificially move the clock forward by, say, 5 seconds instead of
> > sleeping just to test, for example whether TTL works?)
>
> Yes, simulator will skip
Given how fundamental disk space is to operational competence, it's
hard to imagine anyone actually parsing this output instead of using
at least something like the machine readable option. The switch is
rather simple if they need to make it, and they will be better for it,
so I support tidying
+1
Kind Regards,
Brandon
On Fri, Dec 1, 2023 at 7:32 AM Mick Semb Wever wrote:
>
>
> Proposing the test build of Cassandra 5.0-beta1 for release.
>
> sha1: 87fd1fa88a0c859cc32d9f569ad09ad0b345e465
> Git: https://github.com/apache/cassandra/tree/5.0-beta1-tentative
> Maven Artifacts:
>
+1
Kind Regards,
Brandon
On Wed, Nov 29, 2023 at 5:15 AM Alex Petrov wrote:
>
> Even though we would like to bring harry in-tree, this is not an immediate
> priority. Meanwhile, we need to unblock RPM builds for trunk, which means no
> custom jars. We will have at least one more Harry release
So then cutting an alpha2 is possible.
Kind Regards,
Brandon
On Tue, Nov 28, 2023 at 2:59 PM Mick Semb Wever wrote:
>
>
> You can't change bits in a signed and checksummed artefact. You have to cut
> from scratch.
>
> On Tue, 28 Nov 2023 at 20:28, Brandon Williams wr
I think the last time I looked into it there was nothing in the
scripts that forced anything, but if that's not true I think we should
be fixing that, not having it drive our release decisions.
Kind Regards,
Brandon
On Tue, Nov 28, 2023 at 12:54 PM Mick Semb Wever wrote:
>
>
>
> On Tue, 28 Nov
Congrats Francisco!
Kind Regards,
Brandon
On Tue, Nov 28, 2023 at 12:53 PM Dinesh Joshi wrote:
>
> The PMC members are pleased to announce that Francisco Guerrero Hernandez has
> accepted
> the invitation to become committer today.
>
> Congratulations and welcome!
>
> The Apache Cassandra PMC
If we are going to commit to beta2 before the summit because "putting
a beta w/ SAI in this state into users’ hands at summit would be very,
very bad" I don't see why we need to have a subpar beta1 at all?
Kind Regards,
Brandon
On Tue, Nov 28, 2023 at 11:16 AM Mick Semb Wever wrote:
>
>
>
> On
You should hopefully have your account now, welcome to Apache
Cassandra, Rajneesh!
Kind Regards,
Brandon
On Mon, Nov 27, 2023 at 4:30 PM Rajneesh wrote:
>
> Thank you, Brandon!
>
> -Regards
>
>
> On Mon, Nov 27, 2023 at 1:34 PM Brandon Williams wrote:
>>
>&g
Please request one here: https://selfserve.apache.org/jira-account.html
Kind Regards,
Brandon
On Mon, Nov 27, 2023 at 3:29 PM Rajneesh wrote:
>
> Hi,
>
> I am looking to contribute to Cassandra.
>
> I am going through the How-To here -
> https://cassandra.apache.org/_/development/index.html
>
I am +1 on including Harry in-tree.
Kind Regards,
Brandon
On Fri, Nov 24, 2023 at 9:44 AM Alex Petrov wrote:
>
> Hi everyone,
>
> With TCM landed, there will be way more Harry tests in-tree: we are using it
> for many coordination tests, and there's now a simulator test that uses
> Harry.
On Mon, Nov 27, 2023 at 9:25 AM Mick Semb Wever wrote:
>
> It was agreed to move them to 5.0-rc
Where?
As long as it's disabled by default that's an easy +1 from me.
Kind Regards,
Brandon
On Mon, Nov 27, 2023 at 7:03 AM Jacek Lewandowski
wrote:
>
> Hey,
>
> I'd like to ask if we can include
> https://issues.apache.org/jira/browse/CASSANDRA-18464 in the 5.0-beta1
> release. This introduces the
I agree and just now opened it for 5.0-beta (among others.)
Kind Regards,
Brandon
On Sat, Nov 4, 2023 at 11:08 AM Benedict wrote:
>
> I think before we cut a beta we need to have diagnosed and fixed 18993
> (assuming it is a bug).
>
> > On 4 Nov 2023, at 16:04, Mick Semb Wever wrote:
> >
> >
+1
Kind Regards,
Brandon
On Mon, Oct 30, 2023 at 4:47 PM Mick Semb Wever wrote:
>
> Proposing the test build of Cassandra 5.0-alpha2 for release.
>
> DISCLAIMER, this alpha release does not contain the features:
> Transactional Cluster Metadata (CEP-21) and Accord Transactions
> (CEP-15).
ing to primarily annual calendar-based
>>
>> > releases was to avoid precisely this situation, where something that
>>
>> > *feels* right at the cusp of merging leads us to delay a release
>>
>> > repeatedly. We discussed this a couple times this year:
>
+1
Kind Regards,
Brandon
On Mon, Oct 23, 2023 at 6:22 PM Yifan Cai wrote:
>
> Hi,
>
> I want to propose merging the patch in CASSANDRA-18941 to 4.0 and up to trunk
> and hope we are all OK with it.
>
> In CASSANDRA-18941, I am adding the capability to produce size-bounded
> SSTables in
On Tue, Oct 24, 2023 at 7:48 AM Claude Warren, Jr via dev
wrote:
>
> Is there someplace I can stash the tgz that others can download it from? The
> file info is : 6269066 okt 24 12:46 compare_oshi_sigar.tgz
Is posting a github branch not sufficient?
The concern I have with this is that is a big slippery 'if' that
involves development time estimation, and if it tends to take longer
than we estimate (as these things tend to do), then I can see a future
where 5.0 is delayed until the middle of 2024, and I really don't want
that to happen. Maybe
As noted on CASSANDRA-16565 we don't actually need sigar for anything,
so I don't see a reason to keep any of it, especially if that is going
to force us to specify OSes.
Kind Regards,
Brandon
On Fri, Oct 20, 2023 at 9:04 AM Claude Warren, Jr via dev
wrote:
>
> I am looking at
I've added you, you should have access now.
Kind Regards,
Brandon
On Tue, Oct 10, 2023 at 1:24 AM Jaydeep Chovatia
wrote:
>
> Hi,
>
> I want to create a new CEP request but do not see the "Create" page
> permission on Confluent. Could someone permit me?
> Here is the CEP draft: [DRAFT] CEP -
On Fri, Oct 6, 2023 at 5:50 PM David Capwell wrote:
> Lets say you now need to host replace node1
Won't the replacement have a newer generation?
> avoid peers mutating endpoint states they don’t own
This sounds reasonable to me.
> This would be a protocol change, so would need to make sure
+1
Kind Regards,
Brandon
On Mon, Oct 2, 2023 at 11:53 PM Mick Semb Wever wrote:
>
> The donation of the java-driver is ready for its IP Clearance vote.
> https://incubator.apache.org/ip-clearance/cassandra-java-driver.html
>
> The SGA has been sent to the ASF. This does not require
I think it could be argued that not retrying messages is a bug, I am
+1 on including this in 5.0.
Kind Regards,
Brandon
On Tue, Sep 19, 2023 at 1:16 PM David Capwell wrote:
>
> To try to get repair more stable, I added optional retry logic (patch is
> still in review) to a handful of critical
On Wed, Sep 13, 2023 at 11:37 AM Jeff Jirsa wrote:
> You can open a legal JIRA to confirm, but based on my understanding (and
> re-confirming reading
> https://www.apache.org/legal/resolved.html#category-a ):
>
>
We should probably get clarification here regardless, iirc this came up
when we
I don't see any problem with this, +1.
Kind Regards,
Brandon
On Wed, Sep 13, 2023 at 11:09 AM Mike Adamson wrote:
> CEP-30: [Approximate Nearest Neighbor(ANN) Vector Search via
> Storage-Attached Indexes] uses the smile-nlp library
> (com.github.haifengl.smile-nlp) in its testing to allow the
+1
Kind Regards,
Brandon
On Mon, Sep 4, 2023 at 3:26 PM Mick Semb Wever wrote:
>
>
> Proposing the test build of Cassandra 5.0-alpha1 for release.
>
> DISCLAIMER, this alpha release does not contain the expected 5.0
> features: Vector Search (CEP-30), Transactional Cluster Metadata
> (CEP-21)
Given https://issues.apache.org/jira/browse/CASSANDRA-17237 I think it
makes sense. At the least I think we should restore disk_access_mode
so that users are more aware of the options available.
Kind Regards,
Brandon
On Wed, Sep 6, 2023 at 10:50 AM Paulo Motta wrote:
>
> Hi,
>
> I've been
I would prefer to have one standard way to do it, and given the
options I would prefer it be proper JMX instead of mocking.
Kind Regards,
Brandon
On Fri, Aug 25, 2023 at 4:20 AM Miklosovic, Stefan
wrote:
>
> Hi list,
>
> I want to gather a feedback for this comment (1).
>
> Long story short,
:
>>
>> Thanks, I thought I had updated against trunk but apparently missed it. It's
>> working now.
>>
>> On Tue, Aug 15, 2023 at 7:27 AM Brandon Williams wrote:
>>>
>>> On Tue, Aug 15, 2023 at 8:13 AM Derek Chen-Becker
>>> wrote:
>>>
s you recognize the sender and know
>> >> >>> the content is safe.
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> With or without outputting JavaDoc to HTML, there are some errors
>> >> >>
+1
Kind Regards,
Brandon
On Wed, Aug 16, 2023 at 4:34 PM Dinesh Joshi wrote:
>
> Proposing the test build of in-jvm dtest API 0.0.16 for release.
>
> Repository:
> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
>
> Candidate SHA:
>
+1
Kind Regards,
Brandon
On Tue, Aug 15, 2023 at 12:53 PM Miklosovic, Stefan
wrote:
>
> This is the second attempt to pass the vote after [1] is fixed.
>
> Proposing the test build of Cassandra 3.11.16 for release.
>
> sha1: 681b6ca103d91d940a9fecb8cd812f58dd2490d0
> Git:
On Tue, Aug 15, 2023 at 8:13 AM Derek Chen-Becker wrote:
>
> Also, I noticed that the instructions on
> https://cassandra.apache.org/_/development/how_to_commit.html mention "ant
> jar check" as a recommended step, but there's not "check" target. Does it
> mean "checkstyle"?
It exists in the
I think most of those use InMemoryAuditLogger so it's not a problem,
but we can call DatabaseDescriptor.setAuditLoggingOptions to change
the dir, the same way the AuditLoggerTest.testJMXArchive method does.
Kind Regards,
Brandon
On Mon, Aug 14, 2023 at 11:23 PM Derek Chen-Becker
wrote:
>
> I
+1
Kind Regards,
Brandon
On Thu, Aug 10, 2023 at 1:43 AM Miklosovic, Stefan
wrote:
>
> Proposing the test build of Cassandra 3.11.16 for release.
>
> sha1: f86929eae086aa108cf58ee0164c3d12a59ad4af
> Git: https://github.com/apache/cassandra/tree/3.11.16-tentative
> Maven Artifacts:
>
On Fri, Aug 11, 2023 at 2:13 AM Miklosovic, Stefan
wrote:
>
> If we had an official PIP package, I can imagine that we would not ship CQLSH
> in RPM at all (maybe not in DEB either?) so we would decouple this. A PIP
> package is installable almost anywhere (if it is Python 3, that is the way
>
+1
Kind Regards,
Brandon
On Fri, Aug 11, 2023 at 8:08 AM Ekaterina Dimitrova
wrote:
>
>
> “ The rationale for this proposed deprecation is that the upcoming 5.0
> release is a good time to evaluate dependencies that are no longer receiving
> updates and will become risks in the future.”
>
>
On Wed, Aug 9, 2023 at 8:48 AM Ekaterina Dimitrova
wrote:
>
> Just thinking it might be easier to do the releases all together, from
> operational perspective
I personally think, if anything, it's more overhead having multiple
releases in flight simultaneously.
On Wed, Aug 9, 2023 at 3:58 AM Miklosovic, Stefan
wrote:
> There is a user on Slack asking for a release of 3.11.16 because of 16555.
If people are showing interest, I think it's time.
> If we release right now, we might potentially do one more release before 5.0
> is GA.
I think 5.0 is
ng run, see CASSANDRA-18705
>
>
>
> On Sat, 29 Jul 2023 at 00:00, Brandon Williams wrote:
>>
>> +1 to everything stated here.
>>
>> Kind Regards,
>> Brandon
>>
>> On Wed, Jul 26, 2023 at 5:28 PM Mick Semb Wever wrote:
>> >
>> >
I don't think even if it works anyone is going to use the output, so
I'm good with removal.
Kind Regards,
Brandon
On Wed, Aug 2, 2023 at 11:50 AM Ekaterina Dimitrova
wrote:
>
> Hi everyone,
> We were looking into a user report around our ant javadoc task recently.
> That made us realize it is
+1 to everything stated here.
Kind Regards,
Brandon
On Wed, Jul 26, 2023 at 5:28 PM Mick Semb Wever wrote:
>
>
> The previous thread¹ on when to freeze 5.0 landed on freezing the first week
> of August, with a waiver in place for TCM and Accord to land later (but
> before October).
>
> With
+1
Kind Regards,
Brandon
On Fri, Jul 21, 2023 at 11:58 AM Jyothsna Konisa wrote:
>
> Hi Everyone!
>
> I would like to start a vote thread for CEP-34.
>
> Proposal:
>
I think we could special-case and default to 'auto' but allow other
more explicit options.
Kind Regards,
Brandon
On Thu, Jul 20, 2023 at 4:18 PM German Eichberger via dev
wrote:
>
> In general I agree with Joey -- but I would prefer if this behavior is
> configurable, e.g. there is an option
+1
Kind Regards,
Brandon
On Wed, Jul 19, 2023 at 1:28 AM Miklosovic, Stefan
wrote:
>
> Proposing the test build of Cassandra 4.1.3 for release.
>
> sha1: 2a4cd36475de3eb47207cd88d2d472b876c6816d
> Git: https://github.com/apache/cassandra/tree/4.1.3-tentative
> Maven Artifacts:
>
On Sun, Jul 16, 2023 at 11:47 PM Berenguer Blasi
wrote:
> one q that came up during the review: What should we do if we find a
> markForDeleteAt (mfda) usging the MSByte? That is a mfda beyond year 4254:
>
> A. That is a mistake/bug. I makes no sense when localDeletionTime can't
> already go
You forgot to link references,
https://issues.apache.org/jira/browse/CASSANDRA-18666 has it all
though I think
I think it's too late to align versions, that cat is out of the bag.
What we can do though is what I last suggested there: keep the C*
version somewhere in cqlsh and warn when it doesn't
+1
On Thu, Jul 13, 2023, 2:13 AM Miklosovic, Stefan <
stefan.mikloso...@netapp.com> wrote:
> Proposing the test build of Cassandra 4.0.11 for release.
>
> sha1: f8584b943e7cd62ed4cb66ead2c9b4a8f1c7f8b5
> Git: https://github.com/apache/cassandra/tree/4.0.11-tentative
> Maven Artifacts:
>
+1
Checked debian and boolean redhat installs
Kind Regards,
Brandon
On Wed, Jul 12, 2023 at 3:08 PM Miklosovic, Stefan
wrote:
>
> The test build of Cassandra 4.0.11 is available.
>
> sha1: f8584b943e7cd62ed4cb66ead2c9b4a8f1c7f8b5
> Git: https://github.com/apache/cassandra/tree/4.0.11-tentative
I agree with Ekaterina, but also want to point out that snitches are
pluggable, so whatever we do should be pretty safe. If someone
discovers after the removal that they need it, they can just plug it
back in.
Kind Regards,
Brandon
On Mon, Jul 10, 2023 at 8:54 AM Ekaterina Dimitrova
wrote:
>
>
On Mon, Jul 10, 2023 at 6:07 AM Jacek Lewandowski
wrote:
> Remove the checkstyle dependency from "jar" and "test"
> Create a single "check" target that includes all the checks we expect to pass
> in the CI (currently Checkstyle, RAT, and Eclipse-Warnings), making this task
> the default.
I
On Fri, Jul 7, 2023 at 2:20 PM Miklosovic, Stefan
wrote:
>
> Great thanks. That might work.
>
> So we do not change the default output unless there is json / yaml equivalent.
>
> Once there is, we are free to change the default output however we want.
Yes, exactly. Then we have the best of both
On Fri, Jul 7, 2023 at 2:11 PM Miklosovic, Stefan
wrote:
>
> Yes, that is true, but the original, unfixed, output, is still there. Are we
> OK with that?
When we have a serialized output available, we do whatever we like to
the display output.
On Fri, Jul 7, 2023 at 2:02 PM Miklosovic, Stefan
wrote:
>
> There is just no clear path how to improve that over time and exposing the
> same output via different format is not really solving it ... the
> discrepancies are still there.
I'm not sure what you mean, can you explain? In my mind,
On Fri, Jul 7, 2023 at 10:21 AM Miklosovic, Stefan
wrote:
>
> Anyway, the main question here is if we are OK to change the output in majors.
I think we always want to strive for compatibility whenever possible.
My personal litmus test is "can this information be obtained
elsewhere?" and if the
On Fri, Jul 7, 2023 at 10:21 AM Miklosovic, Stefan
wrote:
> If that is the case, we should start to treat this problem completely
> differently and we should not rely on the output of tooling at all and we
> should either provide corresponding JMX method to retrieve it or we should
> offer
On Fri, Jul 7, 2023 at 10:09 AM Josh McKenzie wrote:
> 3. Multiplexed tests (changed, added) run against all JDK's and a broader
> range of configs (no-vnode, vnode default, compression, etc)
I think this is going to be too heavy...we're taking 500 iterations
and multiplying that by like 4 or
On Thu, Jun 29, 2023 at 11:42 AM Jeff Jirsa wrote:
> 3-4% reduction on disk ... for what exactly?
>
> It seems exceptionally uncommon to have 3% of your data SIZE be tombstones.
If the data is TTL'd I think it's not entirely uncommon.
Kind Regards,
Brandon
This sounds good to me. Can we shorten 'build-project' to just 'build'?
Kind Regards,
Brandon
On Thu, Jun 29, 2023 at 3:22 AM Jacek Lewandowski
wrote:
>
> So given all the feedback, I'm going to do the following:
>
> "jar" will depend on "check" target
> "build-project", "build-test" and
+1
Kind Regards,
Brandon
On Tue, Jun 27, 2023 at 12:17 PM Shailaja Koppu wrote:
>
> Hi Team,
>
> (Starting a new thread for VOTE instead of reusing the DISCUSS thread, to
> follow usual procedure).
>
> Please vote on CEP 33 - CIDR filtering authorizer
>
The "artifacts" task is not quite the same since it builds other things
like docs, which significantly contributes to longer build time. I don't
see why we couldn't add a new task that preserves the old behavior though,
"fulljar" or something like that.
Kind Regards,
Brandon
On Mon, Jun 26,
On Fri, Jun 23, 2023 at 8:36 AM Josh McKenzie wrote:
> How frequently do we see failures in tests (straight failure, flakes, etc)
> that are due to the versions of dependencies (JDK or python) that we're
> running the tests with?
>
> Regardless of 1, if the answer to 2 is "almost never", then
On Thu, Jun 22, 2023 at 4:23 PM Josh McKenzie wrote:
>
> 2. Anyone concerned about us being specific about versions in
> requirements.txt in the dtest repo?
My concern with this is atrophy; we'll set the version once and when
finally forced to update, find that a lot of other things must also
I was concerned about 'jre8' being in the dependency name and looked
into which java versions were supported, and it looks like 17 is, so
we should verify but I am +1 if that is the case.
https://github.com/wiremock/wiremock/issues/1655
Kind Regards,
Brandon
On Tue, Jun 20, 2023 at 6:35 AM
1 - 100 of 714 matches
Mail list logo
