for
Spark jobs that operate with a high degree of selectivity; vs. larger bulk scoops. – Scott On Jun
24, 2024, at 1:29 AM, Jon Haddad wrote: I also think it would be a
great contribution, especially since the bulk analytics library can’t be used by the majority of
teams, since it’s hard coded to only
looks promising: https://tinselcity.github.io/SSL_Sendfile/– Scott—MobileOn Apr 19, 2024, at 11:31 AM, Jordan West wrote:If we are considering the main process then we have to do some additional work to ensure that it doesn’t put pressure on the JVM and introduce latency. That’s one thing I like about
n’t downleveled unexpectedly during migration.- ScottOn Apr 8, 2024, at 2:15 PM, C. Scott Andreas wrote:Hi Jon,Thanks for taking the time to read and reply to this proposal. Would encourage you to approach it from an attitude of seeking understanding on the part of the first-time CEP aut
the output of a shell script. I'll yield to Hari to share more, though
today is a public holiday in India. I do see this CEP as solving an important problem. Thanks, – Scott On Apr
8, 2024, at 10:23 AM, Jon Haddad wrote: This seems like a lot of work to create an
rsync alternative. I can't really
, but am not curious enough to learn how they make that work right now. :) I withdraw the proposal. – Scott On
Jan 22, 2024, at 10:56 AM, Brandon Williams wrote: That's right, I'd forgotten about this. I change my +1 to
-1, there's not enough value in this to break signatures. Kind Regards, Brandon
ge footer, I'll file an INFRA ticket with a link to this thread. Thanks, – Scott
control. Any server should have mechanisms to defend itself against any client; official or non–. Jon's also right that an
implementation in the Spark Cassandra Connector may help jobs make progress at the maximum safe pace. Thanks for sharing this
thoughtful document. – Scott On Jan 16, 2024, at 10
— appreciate and enjoying it.– Scott–––MobileOn Dec 20, 2023, at 7:52 AM, Benjamin Lerer wrote:
If we are to address that within the CEP itself then we should discuss
it here, as I would like to fully understand the approach as well as how
it relates to consistency of execution and the idea
for this proposal and discussion so far — appreciate and enjoying it. – Scott On Dec 20, 2023, at 7:52 AM, Benjamin Lerer wrote: If we are to address that
within the CEP itself then we should discuss it here, as I would like to fully understand the approach as well as how it relates to consistency
Congratulations, Francisco!
- Scott
> On Nov 28, 2023, at 10:53 AM, 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!
>
&g
ather than anchored in
values of quality and data integrity. – Scott On Nov 28, 2023, at 9:20 AM, Brandon Williams
wrote: 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
I’d happily be the first to vote -1(nb) on a release containing a known and reproducible bug that can result in data loss or an incorrect response to a query. And I certainly wouldn’t run it.Since we have a programmatic repro within just a few seconds, this should not take long to root-cause.On
Let’s please not change the default at the same time the feature is introduced.Making the capability available will allow users to evaluate and quantify the benefit of the work, as well as to call out any unintended consequences. As users and the project gain confidence in the results, we can
+1 (nb)Accepting this donation would mark a huge milestone for the project.On Oct 3, 2023, at 4:25 AM, Josh McKenzie
wrote:I see now this will likely be instead apache/cassandra-java-driverI was wondering about that. apache/java-driver seemed pretty broad.
:)From the linked page:Check that all
.
- Scott
—
Mobile
> On Sep 6, 2023, at 8:50 AM, Paulo Motta wrote:
>
>
> Hi,
>
> I've been bitten by OOMs with disk_access_mode:auto/mmap that were fixed by
> changing to disk_access_mode:mmap_index_only. In a particular benchmark I got
> 5x more read throughput on 3.11
A snapshot artifact seems more appropriate for early testing to me, rather than a voted / released build issued by the project given how much has yet to land.- ScottOn Aug 25, 2023, at 8:46 AM, Ekaterina Dimitrova wrote:+1On Fri, 25 Aug 2023 at 11:14, Mick Semb Wever
Given how early we are in the cycle with even the branch only recently cut (and how
much is not yet present in the alpha), housecleaning seems like a positive impulse.On
Aug 23, 2023, at 7:28 AM, Ekaterina Dimitrova wrote:Hi
everyone,I wanted to clarify something. I understood dependency
+1nbOn Aug 19, 2023, at 9:50 AM, Blake Eggleston wrote:+1On Aug 17, 2023, at 12:37 AM, Alex Petrov wrote:+1On Thu, Aug 17, 2023, at 4:46 AM, Brandon Williams wrote:+1Kind Regards,BrandonOn Wed, Aug 16, 2023 at 4:34 PM Dinesh Joshi wrote:>> Proposing the test build of in-jvm
, and there is nothing
that would prevent someone from continuing to use a sidecar-based solution in
perpetuity if they preferred.
- Scott
> On Jul 26, 2023, at 3:25 PM, Jon Haddad wrote:
>
> I'm 100% in favor of repair being part of the core DB, not the sidecar. The
> current (and past) state of
I think these concerns are well-intended, but they feel rooted in uncertainty rather than in factual examples of areas where risk is present. I
would appreciate elaboration on the specific areas of risk that folks imagine.I would encourage those who express skepticism to try the patch,
and I
not
able to take this action on others' behalf.More information on the project's mailing lists and how to
join/leave them is here: https://cassandra.apache.org/_/community.htmlCheers,– ScottOn Jul 26, 2023,
at 7:11 AM, C. Scott Andreas wrote:Can you say more about the shape of
your conce
Can you say more about the shape of your concern?JCA/JCE conformance and correctness of the functions implemented are a responsibility of the ACCP/Corretto test suite (link). These are thoroughly exercised by Amazon and bundled into the Corretto JDK distribution Amazon ships as well.With regard to
Jeremiah, that’s my understanding as well. ACCP accelerates a subset of
functions and delegates the rest.
In years of using ACCP with Cassandra, I have yet to see an issue - or any case
in which adopting ACCP was anything other than a strict benefit.
- Scott
> On Jul 26, 2023, at 5:33 AM
Ekaterina, thank you for spearheading JDK17 support for Apache Cassandra! Exciting to get to this point.- ScottOn Jul 24, 2023, at 7:11 PM, Ekaterina Dimitrova wrote:Good news! After run #1638-39 you should not see anything else failing than SSLFactory test class. This known issue will be fixed
is as if
somebody is "greping" it and it is not there, it will break.Do you understand that the same way or am I interpreting that wrong?____From: C. Scott Andreas Sent: Thursday, July 13, 2023 16:35To: dev@cassandra.apache.orgCc: devSubject:
Re: Changing the output of tooli
"From what I see you guys want to condition any change by offering json/yaml as well."I don't think I've seen a proposal to block changes to nodetool output on machine-parseable formats in
this thread.Additions of new delimited fields to nodetool output are mostly straightforward. Changes to
Agreed with Eric’s point here, yes.- ScottOn Jul 12, 2023, at 10:48 AM, Eric Evans wrote:On Wed, Jul 12, 2023 at 1:54 AM Miklosovic, Stefan wrote:I agree with Jackson that having a different output format (JSON/YAML) in order to be able to change the default output
Thanks Patrick. I like the idea of a user survey.Added a handful of comments in the doc. –
ScottOn Jul 11, 2023, at 12:51 AM, Mick Semb Wever wrote:Looks good
to me, thanks Patrick.On Tue, 11 Jul 2023 at 03:11, Patrick McFadin
wrote:For quite a few years, I have done Twitter polls to gather
OT, but would gladly +1(nb) a `nodetool --output-format=json` CEP. :)
[ Some discussion also in:
https://issues.apache.org/jira/browse/CASSANDRA-12698 ]
> On Jul 8, 2023, at 11:26 AM, Josh McKenzie wrote:
>
>> I think they should not parse that output in the first place. Gradually
>>
+1nbOn Jun 28, 2023, at 6:40 PM, Abe Ratnofsky wrote:+1 (nb)On Jun 28, 2023, at 18:38, guo Maxwell wrote:+1 Nate McCall 于2023年6月29日 周四上午9:25写道:+1 On Wed, Jun 28, 2023 at 5:17 AM Shailaja Koppu wrote:Hi Team,(Starting a new thread for VOTE instead of
+1 for ACCP and can attest to its results. ACCP also optimizes for a range of hash
functions and other cryptographic primitives beyond TLS acceleration for Netty.On Jun 22,
2023, at 2:07 PM, Jeff Jirsa wrote:Either would be better than
today. On Thu, Jun 22, 2023 at 1:57 PM Jordan West
+1nbOn Jun 13, 2023, at 10:25 AM, German Eichberger via dev wrote:
+ 1
Great to see this moving forward!
From: Abe Ratnofsky
Sent: Tuesday, June 13, 2023 10:09 AM
To: dev@cassandra.apache.org
Subject: [EXTERNAL] Re: [VOTE] CEP-8 Datastax Drivers Donation
+1 (nb)
On Jun 13,
+1nb
> On May 25, 2023, at 10:12 AM, Mick Semb Wever wrote:
>
> Proposing the test build of Cassandra 4.1.2 for release.
>
> sha1: c5c075f0080f3f499d2b01ffb155f89723076285
> Git: https://github.com/apache/cassandra/tree/4.1.2-tentative
> Maven Artifacts:
>
+1nb
> On May 25, 2023, at 10:14 AM, Brandon Williams wrote:
>
> +1
>
> Kind Regards,
> Brandon
>
> On Thu, May 25, 2023 at 10:13 AM Mick Semb Wever wrote:
>>
>> Proposing the test build of Cassandra 4.0.10 for release.
>>
>> sha1: da77d3f729160e84fbab37666de99550be794265
>> Git:
+1nb.As someone familiar with this work, it's pretty hard to overstate the impact it
has on completing Cassandra's HTAP story. Eliminating the overhead of bulk reads and
writes on production OLTP clusters is transformative.– ScottOn May 4, 2023, at 9:47
AM, Doug Rohrer wrote:Hello all,I’d
If there’s lack of clarity around EOL policy and dates, we should absolutely make this clear.Most releases of the project have been “LTS” in that the release cadence since 2018 has not been rapid but focused on minor enhancements on long-lived branches like 3.0, 3.11, and 4.0.x. But I’d
Done, thanks Doug!On Mar 21, 2023, at 2:22 PM, Doug Rohrer
wrote:Hi folks:I’d like to post a CEP, but given it’s the first time I’m trying to
contribute to the wiki, I don’t have access.If someone with access could please grant
user drohrer access to post, I’d greatly appreciate
I agree with Aleksey's view here.To expand on the final point he makes re: requiring
SSTables be fully rewritten prior to rev'ing from 4.x to 5.x (if the cluster previously ran
3.x) –This would also invalidate incremental backups. Operators would either be required to
perform a full snapshot
is more of an optimization to avoid read repair for queries
over the affected range grinding traffic to a halt, rather than necessary for
safety.
— Scott
> On Mar 8, 2023, at 8:54 AM, C. Scott Andreas wrote:
>
> For this to be safe, my understanding is that:
>
> – A repair of the
For this to be safe, my understanding is that:– A repair of the affected range would
need to be completed among the replicas without such corruption (including paxos
repair).– And we'd need a mechanism to execute repair on the affected node without it
being available to respond to queries,
ack count.
A discuss thread seems fine for this rather than a CEP to me.
— Scott
> On Mar 6, 2023, at 2:51 AM, Miklosovic, Stefan
> wrote:
>
> Hi all,
>
> some time ago we identified an issue with NetworkTopologyStrategy. The
> problem is that when RF > number of ra
Regarding “We should focus on why it took 6 months to go from 4.1 first alpha to GA and what happened inside that time window.” —Speaking solely from my perspective, the single biggest time draw was tracking down and resolving https://issues.apache.org/jira/browse/CASSANDRA-18110.One of the
I realize my feedback on this has been spread across tickets and older mailing list / wiki discussions, so I'll offer a proposal here.Starting with goals -1. Cassandra users must be able to abort and
revert an upgrade to a new version of the database that introduces a new major SSTable
Thanks and congratulations Lorina!
— Scott
> On Feb 16, 2023, at 4:29 PM, Lorina Poland wrote:
>
> Good news! The Open Collective application was accepted! Step one is done.
>
> Lorina
>
>> On 2023/02/13 22:23:35 Lorina Poland wrote:
>> Hi all -
>>
+1 nb
> On Feb 6, 2023, at 9:05 PM, Ariel Weisberg wrote:
>
> +1
>
> On Mon, Feb 6, 2023, at 11:15 AM, Sam Tunnicliffe wrote:
>> Hi everyone,
>>
>> I would like to start a vote on this CEP.
>>
>> Proposal:
>>
Supportive of this as well.
I see testability of trunk against JDK17 as more important than continuous
preservation of support for scripted UDFs *during* that development.
Will be tempted to cherry-pick this and begin kicking the tires as soon as it’s
ready.
- Scott
> On Feb 5, 2023, a
Congratulations, Patrick!On Feb 2, 2023, at 9:46 PM, Berenguer Blasi
wrote:Welcome!On 3/2/23 4:09, Vinay Chella
wrote:Well deserved one, Congratulations, Patrick. On Fri, Feb 3, 2023 at 4:01
AM Josh McKenzie
wrote:Congrats Patrick! Well deserved.On Thu, Feb 2, 2023, at
There are some ideas that development community members have kicked around that may falsify the assumption that "virtual tables are
tiny and will fit in memory."One example is CASSANDRA-14629: Abstract Virtual Table for very large result
Josh and all PMC members, thank you for your work on this!Supportive of the changes
and grateful to have scaffolding in place to accommodate current/incoming
subprojects.– ScottOn Jan 26, 2023, at 1:21 PM, Josh McKenzie
wrote:The Cassandra PMC is pleased to announce that
we're evolving our
Hugely excited to this – thanks to the Program Committee and to the Linux Foundation
for organizing!It's been a long few years away from conferences and I can't wait to
see all of you.Beyond learning about what everyone is doing with Apache Cassandra,
I'm looking forward to the hallway chats
internal systems for unauthorized access from December 21.
Details: https://circleci.com/blog/january-4-2023-security-alert/
— Scott
+1nbOn Dec 19, 2022, at 1:27 PM, Josh McKenzie wrote:+1On Mon, Dec 19, 2022, at 11:54 AM, SAURABH VERMA wrote:+1On Mon, Dec 19, 2022 at 9:36 PM Benjamin Lerer wrote:+1Le lun. 19 déc. 2022
à 16:31, Andrés de la Peña a écrit :+1On Mon, 19 Dec 2022 at 15:11, Aleksey Yeshchenko wrote:+1On 19 Dec
uild with it. One more thing. We need sponsors! If your employer
> can, this is a great opportunity to get your brand out in front of people
> building the future. I’ll be back. Go submit a talk. You’ll be happy you
> did! Patrick*
>
--
Scott Hirleman
scott.hirle...@gmail.com
that users of modern build tools get for free. It also
demands continuous, incremental work to adapt to changes in security and build
tooling in use at many companies that don’t need to be made for projects using
well-supported tools like Maven or Gradle.
– Scott
> On Nov 25, 2022, at 4:56
Jon, thanks for flagging that I didn't get a reply to your question on the thread.My main point in this thread is that I don't
think post-beta is an appropriate time for a major prop change like this in the release cycle. Ideally at this point in the
release cycle, major contributors and large
We have precedent for changing defaults that have near-universal positive
impact in patchlevel releases, yep.
disk_access_mode: auto -> mmap_index_only comes to mind.
- Scott
> On Nov 16, 2022, at 6:49 PM, Derek Chen-Becker wrote:
>
> I'm fine with not including G1 in 4.1,
I share David and Aleksey’s views on this.
We shouldn’t make major defaults changes right before RC. Might be worth adding
a release note recommending users try them, and that they may become default in
a future release though.
— Scott
> On Nov 16, 2022, at 3:38 PM, David Capwell wr
A 2-3% increase in storage volume is roughly equivalent to giving up the gain from LZ4 -> LZ4HC, or a one to two-level bump in Zstandard compression levels. This regression could be very expensive for storage-bound use cases.From the perspective of storage overhead, the unsigned int approach
+1nb
— Scott
> On Oct 21, 2022, at 4:06 AM, Brandon Williams wrote:
>
> +1
>
> Kind Regards,
> Brandon
>
>> On Wed, Oct 19, 2022 at 4:41 AM Mick Semb Wever wrote:
>>
>>
>> Proposing the test build of Cassandra 4.0.7 for release.
>>
+1nb
— Scott
> On Oct 21, 2022, at 4:05 AM, Brandon Williams wrote:
>
> +1
>
> Kind Regards,
> Brandon
>
>> On Wed, Oct 19, 2022 at 4:41 AM Mick Semb Wever wrote:
>>
>>
>> Proposing the test build of Cassandra 3.11.14 for release.
>>
+1nb
— Scott
> On Oct 21, 2022, at 4:04 AM, Brandon Williams wrote:
>
> +1
>
> Kind Regards,
> Brandon
>
>> On Wed, Oct 19, 2022 at 4:41 AM Mick Semb Wever wrote:
>>
>>
>> Proposing the test build of Cassandra 3.0.28 for release.
>>
Hi Jaydeep,Thanks for reaching out and for bumping this thread.This is probably not the answer you’re after, but mentioning as it may address the issue.C* 3.0.14 was released over five years ago, with many hundreds of important bug fixes landing since July 2017. These include fixes for issues that
+1nbOn Aug 22, 2022, at 8:55 AM, Mick Semb Wever 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's.+1Checked- signing
.
- Scott
> On Aug 10, 2022, at 1:00 AM, Claude Warren, Jr via dev
> wrote:
>
>
> At the moment we have 222 open pull requests. Some dating back 4 years. For
> some the repository from which they were pulled from has been deleted. For
> many there are branch conflict
Amit, welcome and thank you for contributing the results from your test and opening this discussion.I don’t think anyone is arguing that the database shouldn’t take advantage of available hardware.A few things important to keep in mind when considering a patch like this:- Where the actual
Congratulations, Jacek!On Jul 6, 2022, at 7:38 AM, Mick Semb Wever
wrote:Congrats Jacek! On Wed, 6 Jul 2022 at 15:00, Ekaterina Dimitrova
wrote:Well deserved, congrats! On Wed, 6 Jul 2022 at 8:56, Brandon Williams
wrote:Congrats!On Wed, Jul 6, 2022, 7:00 AM Benjamin Lerer wrote:The PMC
+1nb
> On May 26, 2022, at 10:21 PM, Berenguer Blasi
> wrote:
>
>
> +1 nb
>
> On 26/5/22 16:25, Ekaterina Dimitrova wrote:
>> +1 (nb)
>>
>> On Tue, 24 May 2022 at 11:37, Andrés de la Peña wrote:
>>> +1 nb
>>>
>>> On Tue, 24 May 2022 at 16:10, Benjamin Lerer wrote:
+1
Le
Yep, supportive of anything that has the potential to increase the number of users evaluating a pre-release build. Alpha sounds great.On May 18,
2022, at 9:29 AM, David Capwell wrote:Works for meOn May 18, 2022, at 7:36 AM, Josh McKenzie
wrote:+1 from me on the grounds that I expect users to
+1nb
> On May 9, 2022, at 5:24 PM, Mick Semb Wever 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
+1nb
> On May 5, 2022, at 9:49 AM, Brandon Williams wrote:
>
> +1
>
> Also passed dependency-check
>
> Kind Regards,
> Brandon
>
>> On Wed, May 4, 2022 at 9:33 AM Mick Semb Wever wrote:
>>
>> Proposing the test build of Cassandra 4.0.4 for release.
>>
>> sha1:
+1, with special attention to CASSANDRA-14752 - didn’t realize we hadn’t
released a build with a resolution for this yet.
> On May 9, 2022, at 5:23 PM, Mick Semb Wever wrote:
>
>
>>
>> > The vote will be open for 72 hours (longer if needed). Everyone who
>> > has tested the build is invited
+1nbOn Mar 31, 2022, at 10:21 AM, Dinesh Joshi wrote:+1On Mar 31, 2022,
at 10:04 AM, David Capwell wrote:+1On Mar 31, 2022, at 9:53 AM, Alex
Petrov wrote:Proposing the test build of in-jvm dtest API 0.0.13 for
want to know about.
Thank you for working to get Cassandra launching on JDK17. Excited for what’s
ahead.
— Scott
> On Mar 23, 2022, at 7:58 AM, Ekaterina Dimitrova
> wrote:
>
>
> Hi everyone,
>
> Looking into our way to Java 17, I wanted to share with the community
+1nbOn Feb 17, 2022, at 2:37 PM, J. D. Jordan wrote:+1 nbOn Feb
17, 2022, at 4:25 PM, Brandon Williams wrote:+1On Thu, Feb 17, 2022 at
4:23 PM Caleb Rackliffe wrote:Hi everyone,I'd like to call a vote
to approve CEP-7.Proposal:
+1nb
> On Feb 16, 2022, at 5:59 AM, Jeremy Hanna wrote:
>
> +1 nb. Thanks for all of the great work on this Branimir. Excited to see
> this moving forward.
>
>> On Feb 16, 2022, at 7:56 AM, J. D. Jordan wrote:
>>
>> +1 nb
>>
On Feb 16, 2022, at 7:30 AM, Josh McKenzie wrote:
+1nb
> On Feb 8, 2022, at 4:18 AM, Brandon Williams wrote:
>
> +1
>
>> On Mon, Feb 7, 2022 at 8:44 AM Alex Petrov wrote:
>>
>> Proposing the test build of cassandra-harry 0.0.1 for release, to start
>> using it in Cassandra tree.
>>
>> Repository:
>>
Hi Dorian,I see that the following download URLs appear to work fine for me and result in the
tarballs being downloaded as expected.–
https://dist.apache.org/repos/dist/dev/cassandra/3.11.12/apache-cassandra-3.11.12-src.tar.gz–
Branimir, thank you for sharing these results.
The numbers are exciting - particularly the UCS test in which compaction keeps
up, and your note mentioning 30% larger L0 flushes due to the more compact
memory representation.
Great work.
— Scott
> On Feb 7, 2022, at 8:39 AM, Branimir Lam
+1nbOn Feb 7, 2022, at 6:14 AM, Mick Semb Wever
wrote:Proposing the test build of Cassandra 3.0.26 for release.sha1:
b18adcba1a808cf77576905dc2ceccd7783bdb18Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.26-tentativeMaven
Artifacts:
+1nbOn Feb 7, 2022, at 6:15 AM, Mick Semb Wever
wrote:Proposing the test build of Cassandra 4.0.2 for release.sha1:
25012d2fec1984cc9c1a352f214eb912ca4f10f5Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.2-tentativeMaven
Artifacts:
I also (+1nb) support a proposal to deprecate JavaScript UDFs; to offer an
interface for those who would like to supply a UDF implementation; and to
extract/remove our current implementation.
JDK17 support seems like a much higher priority than in-tree JS UDFs.
— Scott
> On Jan 18, 2022, a
+1nb, with and without the amendment.Reason for mentioning without: I see the ability to cut a
release to address an urgent security or data loss issue as one of the strongest arguments for
maintaining green CI as a resting state so we are ready in the event of an emergency.Test results
that
gt; >> > > *Pluggability improvements:*> > >> > > * Pluggable schema manager (CEP pending)> > > * Pluggable filesystem (CEP pending)> > > * Pluggable authenticator for CQLSH (CASSANDRA-16456). A CEP> draft> > > can be> > >
+1, this would be great to have fixed. Thanks for talking with Infra about
this, Bowen.
> On Dec 4, 2021, at 9:16 AM, Bowen Song wrote:
>
> Hello,
>
>
> Currently this mailing list has MIME-part filtering turned on, which will
> results in "From:" address munging (appending ".INVALID" to
. I see that the 2016 version adds
a couple round-trip unit tests with a small amount of static data. It would be
good to see randomized tests fleshed out that exercise more of the read/write
path; or which add variants of existing read/write path tests that enable
encryption.
– Scott
> On
Congratulations, Sumanth!
> On Nov 5, 2021, at 11:17 AM, Oleksandr Petrov
> wrote:
>
> The PMC members are pleased to announce that Sumanth Pasupuleti has
> recently accepted the invitation to become committer.
>
> Sumanth, thank you for all your contributions to the project over the years.
>
Re: "I think you all know my feels on JMX." –Super fair - I'd meant to speak in terms of desired outcome ("the feature should be dynamically
configurable at runtime") rather than implementation ("this should be via JMX"). On Nov 1, 2021, at 1:24 PM, David Capwell
wrote:If anyone wants to bite
Thank you for starting discussion on this CEP, Andrés!Can the "Scope" section of the doc be filled out? It currently reads "TBD," but
having a better understanding of the scope of work would help focus discussion: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-3%3A+GuardrailsRe:
+1nb
> On Oct 29, 2021, at 6:17 AM, bened...@apache.org wrote:
>
> +1
>
> From: Mick Semb Wever
> Date: Friday, 29 October 2021 at 13:45
> To: dev@cassandra.apache.org
> Subject: [VOTE] Release dtest-api 0.0.11
> Proposing the test build of in-jvm dtest API 0.0.11 for release.
>
>
that the
CEP does not contain a design for a feature that is a non-goal of the initial
scope proposed by the CEP, and which is also not precluded by the CEP.
- Scott
> On Oct 14, 2021, at 11:27 AM, Aleksey Yeschenko wrote:
>
> +1 on all points
>
>> On 14 Oct 2021, at 17:31, bened..
in collaboration
with other contributors; engage with members of the developer and user community on
feedback, enhancements, and bugs; and intend deliver it to completion at a standard
of readiness suitable for production transactional systems of record.Thanks,– ScottOn
Oct 6, 2021, at 8:25 AM, C. Scott
Adding a few notes from my perspective as well – Re: the UX question, thanks for asking this.I agree that offering a set of example queries and use cases may help make the specific use cases more understandable; perhaps we can prepare these as examples to be included in the CEP.I do think that
+1nb
>
> On Sep 9, 2021, at 2:03 PM, David Capwell wrote:
>
> +1
>
>> On Sep 9, 2021, at 1:52 PM, Mick Semb Wever wrote:
>>
>> +1
>>
>>> On Thu, 2 Sept 2021 at 13:20, Mick Semb Wever wrote:
>>>
>>> Proposing the test build of in-jvm dtest API 0.0.9 for release.
>>>
>>> Repository:
>>>
+1nb
> On Sep 1, 2021, at 6:54 AM, Jeff Jirsa wrote:
>
> +1
>
>
>> On Wed, Sep 1, 2021 at 4:54 AM Sam Tunnicliffe wrote:
>>
>> Proposing the test build of Cassandra 4.0.1 for release.
>>
>> sha1: 6709111ed007a54b3e42884853f89cabd38e4316
>> Git:
>>
+1
> On Aug 27, 2021, at 12:58 PM, Mick Semb Wever wrote:
>
>
>>
>>
>> Proposal:
>> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-14%3A+Paxos+Improvements
>> Discussion:
>>
as returned by the API,
so users upgrading from 8 to 11 who have a dependency on timestamp identity may
want to examine it.
That JDK change was: https://bugs.openjdk.java.net/browse/JDK-8177809
— Scott
---
Mobile
On Aug 26, 2021, at 7:35 AM, Ekaterina Dimitrova wrote:
Hi everyone,
I had a few
out aside from deploying
this patch. We should get a new release out quickly.
– Scott
From: Sam Tunnicliffe
Sent: Monday, August 23, 2021 11:27 AM
To: dev@cassandra.apache.org
Subject: Potential issues during 4.0 upgrade
Hi all,
I just opened a JIRA wh
of linearizability via assurance of the
set of instances voting on a transaction.
– Scott
From: bened...@apache.org
Sent: Wednesday, August 18, 2021 2:31 PM
To: dev@cassandra.apache.org
Subject: [DISCUSS] CEP 14: Paxos Improvements
RE:
https://cwiki.apache.org
Congratulations, Adam!
From: Joseph Lynch
Sent: Tuesday, August 17, 2021 7:44 AM
To: dev@cassandra.apache.org
Subject: Re: Welcome Adam Holmberg as Cassandra committer
Congratulations Adam!
On Tue, Aug 17, 2021 at 10:25 AM Jordan West wrote:
>
>
left in limbo with no
resolution is worse than being told "no", especially for new contributors.
On Fri, Jul 2, 2021 at 1:23 PM Brandon Williams wrote:
> On Tue, Jun 29, 2021 at 5:49 PM Scott Carey wrote:
> >
> > I'd like to discuss the inclusion of the above tickets
1 - 100 of 179 matches
Mail list logo