at 00:31
To: dev@cassandra.apache.org
Cc: Miklosovic, Stefan
Subject: Re: [DISCUSS] CEP-42: Constraints Framework
You don't often get email from conta...@bernardobotella.com. Learn why this is
important<https://aka.ms/LearnAboutSenderIdentification>
EXTERNAL EMAIL - USE CAUTION when clicking
You wrote in the CEP:
As we mentioned in the motivation section, we currently have some guardrails
for columns size in place which can be extended for other data types.
Those guardrails will take preference over the defined constraints in the
schema, and a SCHEMA ALTER adding constraints that
s in (2).
(1) https://issues.apache.org/jira/browse/CASSANDRA-19593
(2) https://github.com/instaclustr/cassandra/tree/CEP-24-with-generator-tcm
________
From: Miklosovic, Stefan
Sent: Monday, December 19, 2022 14:24
To: dev@cassandra.apache.org
Subject: Re: [Discuss] CEP-24
My personal bet is that from the very beginning, Cassandra was more
"number-centric" and right alignment just made more sense back then,
considering strings as an afterthought. Another explanation is that nobody
actually put any work to it to distinguish strings and numbers and it stayed
like
I would like to know whose idea was it to align it like it is currently done in
the first place. Maybe we are missing something important like why it was done
like that? If there is no reason, we might just start to align it as other DB
offerings do. My initial proposal to support both is more
Great news! Congratulations.
From: Josh McKenzie
Sent: Monday, January 8, 2024 19:19
To: dev
Subject: Welcome Maxim Muzafarov as Cassandra Committer
EXTERNAL EMAIL - USE CAUTION when clicking links or attachments
The Apache Cassandra PMC is pleased to
For completeness, there is this thread (1) where we already decided that sigar
is OK to be removed completely.
I think that OSHI is way better lib to have, I am +1 on this proposal.
Currently the deal seems to be that this will go just to trunk.
(1)
Wow, great news! Congratulations on your committership, Mike.
From: Benjamin Lerer
Sent: Friday, December 8, 2023 15:41
To: dev@cassandra.apache.org
Subject: Welcome Mike Adamson as Cassandra committer
EXTERNAL EMAIL - USE CAUTION when clicking links or
Hi Claude,
while technically possible, I do not see a lot of people would use this. I am
for straightforward -H option instead of introducing -Hn which seems to bring
almost no value and brings discrepancy into the nodetool flags. I think there
are other -H outputs for other commands, are not
//github.com/apache/cassandra/pull/2853/files#diff-4e5b9f6d0d76ab9ace1bd805efe5788bb5d23c84c25ccf75b9896f20b46a1879
Thanks and regards
________
From: Miklosovic, Stefan via dev
Sent: Monday, October 30, 2023 23:07
To: dev@cassandra.apache.org
Cc: Miklosovic, Stefan
Subject: Re: Removal of deprecatio
The link is fixed. Thanks!
From: Miklosovic, Stefan
Sent: Monday, November 6, 2023 11:42
To: dev@cassandra.apache.org
Subject: Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)
I can't view it either
I can't view it either.
From: guo Maxwell
Sent: Monday, November 6, 2023 11:40
To: dev@cassandra.apache.org
Subject: Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)
NetApp Security WARNING: This is an external email. Do not click
for them as well :-)
[1] https://issues.apache.org/jira/browse/CASSANDRA-18773
On Fri, 3 Nov 2023 at 22:55, Miklosovic, Stefan via dev
wrote:
>
> Hi list,
>
> is anybody against cutting some 3.x and 4.x releases? I think that is nice to
> do before summit. The last 4.x were rel
Hi list,
is anybody against cutting some 3.x and 4.x releases? I think that is nice to
do before summit. The last 4.x were released late July, 3.0 in the middle of
May. There is quite a lot of changes in these branches.
I can release it all.
What is your opinion?
Regards
Do I understand it correctly that this is basically the case of "deprecated on
introduction" as we know that it will not be necessary the very next version?
I think that not everybody is upgrading from version to version as they appear.
If somebody upgrades from 4.0 to 5.1 (which we seem to
Sure we can do that just for trunk. No problem with that. Hence, I am parking
this effort for a while.
From: Mick Semb Wever
Sent: Monday, October 30, 2023 22:56
To: dev@cassandra.apache.org
Subject: Re: Removal of deprecations added in Cassandra 3.x
Hi,
similarly as for Cassandra 1.x and 2.x deprecations removal done in
CASSANDRA-18959, you are welcome to comment on the removal of all stuff
deprecated in 3.x (1).
If nobody objects after couple days I would like to proceed to the actual
removal. Please tell me if you want something to
OK fair enough, I am taking that part back.
From: Alex Petrov
Sent: Monday, October 30, 2023 11:45
To: dev
Cc: Miklosovic, Stefan
Subject: Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate
5.1-alpha1)
NetApp Security WARNING
ortant feature for me to win some internal company bet
My 2 cents,
German
From: Miklosovic, Stefan via dev
mailto:dev@cassandra.apache.org>>
Sent: Thursday, October 26, 2023 4:23 AM
To: dev@cassandra.apache.org<mailto:dev@cassandra.
What Maxim proposes in the last paragraph would be definitely helpful. Not for
the project only but for a broader audience, companies etc., too.
Until this thread was started, my assumption was that "there will be 5.0 on
summit with TCM and Accord and it somehow just happens". More transparent
Hi list,
this is the follow-up thread after we discussed the addition of Deprecated
annotations with "since" in the code. It was merged to 5.0 and trunk under
18912.
I have added all the mappings under (1). There are tables for each major
version of Cassandra with links to all places where we
To double check the reasoning behind this proposal:
1) is 5.1 going to contain only TCM / Accord when it comes to new features? In
other words, 5.1, except these two, will only ever contain bugfixes from older
branches (merging them up) or fixes for TCM / Accord itself (which will be
ent: Friday, October 13, 2023 15:36
To: dev
Cc: Miklosovic, Stefan
Subject: Re: [DISCUSS] putting versions into Deprecated annotations
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.
I
your next release will not contain any stuff which
should not be there. E.g. when we release 6.0, all 4.0 stuff can go away etc ...
____
From: Miklosovic, Stefan via dev
Sent: Friday, October 13, 2023 15:00
To: dev@cassandra.apache.org
Cc: Miklosovic, Stefan
S
13 oct. 2023 à 14:11, Miklosovic, Stefan via dev
mailto:dev@cassandra.apache.org>> a écrit :
Maybe for better understanding what we talk about, there is the PR which
implements the changes suggested here (1)
It is clear that @Deprecated is not used exclusively on JMX / Configuration
Maybe for better understanding what we talk about, there is the PR which
implements the changes suggested here (1)
It is clear that @Deprecated is not used exclusively on JMX / Configuration but
we use it internally as well. This is a very delicate topic and we need to go,
basically, one by
ge and require a deep archaeology.
Not aiming for 100% accuracy, but more on code style agreement.
> All of the above led me to the following which is pretty easy to
> achieve and improves the code quality:
>
> /** @deprecated See CASSANDRA-6504 */
> @Deprecated(since = &qu
code quality:
>
> /** @deprecated See CASSANDRA-6504 */
> @Deprecated(since = "2.1")
> public Integer concurrent_replicates = null;
>
> On Wed, 11 Oct 2023 at 09:51, Miklosovic, Stefan
> mailto:stefan.mikloso...@netapp.com>> wrote:
> >
> > Here (1) it sup
uld make it a lot easier to grep for things to pull before a
> > > major)
> > > If it's being replaced by something, you should {@link #} the javadoc for
> > > it so people know where to bounce over to
> > >
> > > I've been leaning pretty heavily on the functional
's being replaced by something, you should {@link #} the javadoc for
> > it so people know where to bounce over to
> >
> > I've been leaning pretty heavily on the functionality of point 3 for
> > documenting cross-module implicit dependencies as I come across them lat
OK.
Let's go with in-built java.lang.Deprecated annotation. If somebody wants to
document that in more detail, there are Javadocs as mentioned. Let's just stick
with the standard stuff.
I will try to implement this for 5.0 (versions since it was deprecated) with my
take on what should be
-N", link to a dev ML thread on pony mail, etc. That way if
> someone comes across it in the codebase they have some context to follow up
> on if it's the shape of a thing they need w/out having to go full-bore w/git
> blame and JQL.
>
> On Fri, Oct 6, 2023, at 4:43 AM, Miklos
Hi list,
I have a ticket to discuss (1).
When we deprecate APIs / methods etc, what I want to suggest is that we might
start to explicitly add the version when that happened. For example, if you
deprecated something which goes to 5.0, would you be so nice to do this?
@Deprecated(since =
Would it be possible to make Jimfs integration production-ready then? I see we
are using it in the tests already.
It might be one of the reference implementations of this CEP. If there is a
type of workload / type of nodes with plenty of RAM but no disk, some kind of
compute nodes, it would
Hi list,
there is CASSANDRA-18773 we want to merge to 4.0 up to trunk (hence it will be
in 5.0 (alpha2)) and I want to be sure we are all OK with that (especially for
that 5.0 alpha release).
The patch is significantly speeding up the compaction throughput for cases when
you have a lot of
:20 PM, Miklosovic, Stefan wrote:
Hi list,
Currently, we are skipping the usage of native libraries in Netty as part of
testing here (1).
In 5.0 branch, we upgraded Netty to 4.1.96 and we brought all native
dependencies to the class path so they are there in runtime (x86, arm, mac).
I conducted
I wonder why disk_access_mode property is not in cassandra.yaml (looking into
trunk right now). Do you all think we can add it there with brief explanation
what each option does?
From: Caleb Rackliffe
Sent: Wednesday, September 6, 2023 21:08
To:
Hi list,
Currently, we are skipping the usage of native libraries in Netty as part of
testing here (1).
In 5.0 branch, we upgraded Netty to 4.1.96 and we brought all native
dependencies to the class path so they are there in runtime (x86, arm, mac).
I conducted few CI tests for 5.0+ and not
nstead 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, until JMX feature was introduced, we kind of hacked / mocked
the calls to MBeans from IInstance, like this (2). If you
Hi list,
I want to gather a feedback for this comment (1).
Long story short, until JMX feature was introduced, we kind of hacked / mocked
the calls to MBeans from IInstance, like this (2). If you notice, there is a
lot of methods throwing UnsupportedOperationException because we had no proper
he broken ant task which generates html files from
> >> >> > them.
> >> >> >
> >> >> > +1 from me on removing the ant task. If someone feels the task is
> >> >> > useful they can always implement one that does not crash and add
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.11.16.
Apache Cassandra is a fully distributed database. It is the right choice when
you need scalability and high availability without compromising performance.
https://cassandra.apache.org/
Downloads of
The vote passed with 3 binding and 2 non-binding +1s.
I would remove it all in 5.0 but that's just me. I do not think that the
deprecation is a must and it is just unnecessary exercise and we are just red
taping here.
Major releases are good for dropping the "baggage" like this. Do we really want
to wait until 6.0 is out to cut off the dead
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: https://github.com/apache/cassandra/tree/3.11.16-tentative
Maven Artifacts:
The vote has not passed successfully because of (1) not being done.
(1) https://issues.apache.org/jira/browse/CASSANDRA-18751
-1 as we can not pull Java 11 as a dependency for RPM package when 3.11 is
being installed.
We need to fix this, stage and vote once again.
Ticket for tracking this work is here
https://issues.apache.org/jira/browse/CASSANDRA-18751
From: Mick Semb
One nice benefit of a CQLSH PIP package which was omitted in this discussion is
that it is "Python-version-agnostic". What I mean by that is that the way how
we currently package CQLSH in RPM is that the container it is produced in is
using Python 3.6 so the produced RPM will run, believe or
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:
The test build of Cassandra 3.11.16 is available.
sha1: f86929eae086aa108cf58ee0164c3d12a59ad4af
Git: https://github.com/apache/cassandra/tree/3.11.16-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1305/org/apache/cassandra/cassandra-all/3.11.16/
Hi,
with 5.0 getting closer, when do we plan to release the last releases of 3.0.x
and 3.11.x?
There is a user on Slack asking for a release of 3.11.16 because of 16555.
If we release right now, we might potentially do one more release before 5.0 is
GA.
Do you think it makes sense to
Since there is no response / nobody seems to see this as an issue, I am going
to remove it (will be removed in 5.0).
From: Miklosovic, Stefan
Sent: Wednesday, August 2, 2023 21:57
To: dev@cassandra.apache.org
Subject: Removal
That is a good idea. I would like to have Javadocs valid when going through
them in IDE. To enforce it, we would have to fix it first. If we find a way how
to validate Javadocs without actually rendering them, that would be cool.
There is a lot of legacy and rewriting of some custom-crafted
Hello list,
I want to double check this one (1) on ML.
It is relatively an innocent low-hanger however the caveat is that it might
potentially break the upgrade to 5.0. The deprecation happened in (2) (in 4.0).
I think it is just eligible for deletion now. This property was commented out
and
gt; >> big change like the import order [1] a really straightforward matter
> >> (by pressing Crtl + Opt + O in their local branch to organize
> >> imports).
> >>
> >> See:
> >>
> >> Move the IntelliJ Idea code style and inspections confi
I plan to run few builds with Corretto etc and do few manual tests, I will try
to push that as soon as possible but it might happen it will leak to the next
week.
From: Mick Semb Wever
Sent: Thursday, July 27, 2023 0:27
To: dev
Subject: August 5.0
k so I would be fine for someone to
figure it out post merge if there is a concern. What JCE provider you use
should have no upgrade concerns.
-Jeremiah
> On Jul 26, 2023, at 1:07 PM, Miklosovic, Stefan
> mailto:stefan.mikloso...@netapp.com>> wrote:
>
> Am I understanding it
Am I understanding it correctly that tests you are talking about are only
required in case we make ACCP to be default provider?
I can live with not making it default and still deliver it if tests are not
required. I do not think that these kind of tests were required couple mails
ago when
Yes, you are right. I know the providers have their preference and we are
installing Corretto as the first one.
So if a service is not there it will just search where it is next. I completely
forgot this aspect of it ... Folks from Corretto forgot to mention this
behavior as well, interesting.
) https://github.com/corretto/amazon-corretto-crypto-provider/issues/315
(2) https://issues.apache.org/jira/browse/CASSANDRA-18624
________
From: Miklosovic, Stefan
Sent: Friday, July 21, 2023 18:17
To: dev@cassandra.apache.org
Subject: Re: [DISCUSS] Using ACCP or
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.1.3.
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 vote passes with three binding and one non-binding +1s.
https://lists.apache.org/thread/8ot3wjc88k0rhx1m9m58k0bp4msbjw6w
We gave it the second look and I came up with this (1)
In a nutshell, we download both arch libs to libs/corretto and then
cassandra.in.sh will dynamically resolve the architecture and OS. Based on
that, it will add respective jar to the class path. If it went wrong and it is
not added to CP,
;>> Maybe we could start providing Dockerfile’s and/or make arch specific
>>> rpm/deb packages that have everything setup correctly per architecture?
>>> We could also download them all and have the startup scripts put stuff in
>>> the right places depending on the arc
Hi,
as I was reviewing the patch for this feature (1), we realized that it is not
quite easy to bundle this directly into Cassandra.
The problem is that this was supposed to be introduced as a new dependency:
software.amazon.cryptools
AmazonCorrettoCryptoProvider
2.2.0
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:
The test build of Cassandra 4.1.3 is available.
sha1: 2a4cd36475de3eb47207cd88d2d472b876c6816d
Git: https://github.com/apache/cassandra/tree/4.1.3-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1304/org/apache/cassandra/cassandra-all/4.1.3/
The
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0.11.
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
The vote passes with three binding +1s.
https://lists.apache.org/thread/hd4lncvnqz8f5c0f2wfv9o2flk02loq2
ARNING: This is an external email. Do not click links or open
attachments unless you recognize the sender and know the content is safe.
On Thu, Jul 13, 2023 at 9:44 AM Miklosovic, Stefan
mailto:stefan.mikloso...@netapp.com>> wrote:
For example Dinesh said this:
"Until nodetool
epresentation, though.
What are some changes that you'd like to make?
– Scott
On Jul 13, 2023, at 7:44 AM, "Miklosovic, Stefan"
wrote:
For example Dinesh said this:
"Until nodetool can support JSON as output format for all interaction and there
is a significant a
o is pretty small,
and the cost for everyone downstream is not. This is why we should spellcheck
things in API's before we release them. :)
On Wed, Jul 12, 2023, at 2:45 PM, Miklosovic, Stefan wrote:
Eric,
I appreciate your feedback on this, especially more background about where you
are comming from i
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:
The test build of Cassandra 4.0.11 is available.
sha1: f8584b943e7cd62ed4cb66ead2c9b4a8f1c7f8b5
Git: https://github.com/apache/cassandra/tree/4.0.11-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1303/org/apache/cassandra/cassandra-all/4.0.11/
ments unless you recognize the sender and know the content is safe.
On Wed, Jul 12, 2023 at 1:54 AM Miklosovic, Stefan
mailto:stefan.mikloso...@netapp.com>> wrote:
I agree with Jackson that having a different output format (JSON/YAML) in order
to be able to change the default output resolves
CEP is a great idea. The devil is in details and while this looks cool, it will
definitely not hurt to have the nuances ironed out.
From: Patrick McFadin
Sent: Tuesday, July 11, 2023 2:24
To: dev@cassandra.apache.org; German Eichberger
Subject: Re:
tps://aka.ms/LearnAboutSenderIdentification>
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.
On Sun, Jul 9, 2023 at 9:10 PM Dinesh Joshi
mailto:djo...@apache.org>> w
for the users,
> just in case someone somewhere uses it and did not follow the user mailing
> list?
>
> Thank you
> Ekaterina
>
> On Mon, 10 Jul 2023 at 9:47, Miklosovic, Stefan
> mailto:stefan.mikloso...@netapp.com>> wrote:
>>
>> Hi list,
>>
>&g
On Mon, 10 Jul 2023 at 9:47, Miklosovic, Stefan
mailto:stefan.mikloso...@netapp.com>> wrote:
Hi list,
I want to ask about the future of CloudstackSnitch.
This snitch was added 9 years ago (1). I contacted the original author of that
snitch, Pierre-Yves Ritschard, who is currently CEO of a comp
Hi list,
I want to ask about the future of CloudstackSnitch.
This snitch was added 9 years ago (1). I contacted the original author of that
snitch, Pierre-Yves Ritschard, who is currently CEO of a company he coded that
snitch for.
In a nutshell, Pierre answered that he does not think this
lated to that if it is changed"
in this particular case.
____
From: Miklosovic, Stefan
Sent: Saturday, July 8, 2023 17:43
To: dev
Subject: Re: Changing the output of tooling between majors
Thank you, Josh, for your insight.
I think they should not parse t
change things here for the record, just want
to call this out for anyone that might not have been thinking about things this
way.
On Fri, Jul 7, 2023, at 3:23 PM, Brandon Williams wrote:
On Fri, Jul 7, 2023 at 2:20 PM Miklosovic, Stefan
mailto:stefan.mikloso...@netapp.com>> wrote:
@cassandra.apache.org
Subject: Re: Changing the output of tooling between majors
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.
On Fri, Jul 7, 2023 at 2:11 PM Miklosovic, Stefan
wrote:
>
&g
ject: Re: Changing the output of tooling between majors
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.
On Fri, Jul 7, 2023 at 2:02 PM Miklosovic, Stefan
wrote:
>
> There is just no clear p
nts unless you recognize the sender and know the content is safe.
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 pers
Hi list,
I want to clarify the policy we have when we want to / going to change the
output of the tooling (nodetool or tools/bin etc.).
I am not sure it is written somewhere explicitly, but how I get it from the
gossip over years is that we should not change the output (e.g. changing the
name
Hi Maxim,
I went through the PR and added my comments. I think David also reviewed it.
All points you mentioned make sense to me but I humbly think it is necessary to
have at least one additional pair of eyes on this as the patch is relatively
impactful.
I would like to see additional column
Great stuff, Josh! This is what I was talking about when I was mentioning that
I am super curious about the workflows of other people. Any chance you share
your setup somewhere so I may try it? Too soon to tell if we indeed want to go
that direction but trying it out would be great
ment that
can be explored (not part of what Jacek does here, though). Maxim, do you mind
creating a ticket, please?
Best regards,
Ekaterina
On Mon, 26 Jun 2023 at 17:04, Miklosovic, Stefan
mailto:stefan.mikloso...@netapp.com>> wrote:
Yes, in this case, opting-out is better than opting-in
Yes, in this case, opting-out is better than opting-in. I feel like the build
process is quite versatile and one just picks what is necessary. I never build
docs, there is a flag for that. I turned off checkstyle because I was fed up
with that until Berenguer cached it and now I get ant jar
retty much imagine that
the testing efforts might be expanded to all other snitches as well.
____
From: Miklosovic, Stefan
Sent: Tuesday, June 20, 2023 13:35
To: dev@cassandra.apache.org
Subject: Adding wiremock to test dependencies
Hi,
we want to introduce wiremo
Hi,
we want to introduce wiremock library (1) into the project as a test dependency
to test CASSANDRA-16555.
In that patch, (wip here (2)), we want to test how would such snitch behave
based on what Amazon EC2 Identity Service of version 2 returned to that snitch.
AWS Identity service of
can lead down a rabbit hole of sparse documentation trying to
figure out what the simplenative option is, and is better than cql3?
On Wed, May 31, 2023 at 1:58 AM Miklosovic, Stefan
mailto:stefan.mikloso...@netapp.com>> wrote:
Interesting point about the debuggability.
Yes, I agree that Sim
Interesting point about the debuggability.
Yes, I agree that SimpleClient (as class) should not be removed because we are
using it in tests. I have already mentioned in my original e-mail that for this
reason that class is not going anywhere and we still need to use it.
The cost of keeping it
I am doing some fixes for cassandra-stress and I stumbled upon this
https://issues.apache.org/jira/browse/CASSANDRA-18529
There is
Usage: -mode native [unprepared] cql3 [compression=?] [port=?] [user=?]
[password=?] [auth-provider=?] [maxPending=?] [connectionsPerHost=?]
[protocolVersion=?]
001c1f4R70
On Fri, 31 Mar 2023 at 07:08, Jacek Lewandowski
wrote:
>
> I'll do
>
> - - -- --- - -
> Jacek Lewandowski
>
>
> czw., 30 mar 2023 o 22:09 Miklosovic, Stefan
> napisał(a):
>>
>> Hi list,
>>
>> we are look
I don't want to hijack this thread, I just want to say that the point 4) seems
to be recurring. I second Caleb in saying that transactional metadata would
probably fix this. Because of the problem of not being sure that all config is
same, cluster-wide, I basically dropped the effort on CEP-24
Great stuff, Lapo!
I was looking into FreeBSD ports few days ago to see what Cassandra version it
supports as I have BSDs as a hobby ...
Can't wait until I see 4.1!
BTW I noticed there is quite a lot of patches to make Cassandra run on FreeBSD
(1). Would you be maybe interesting in submitting
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.29.
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
The vote passed with 3 binding +1's and 0 binding -1's.
https://lists.apache.org/thread/39s345w5fv2r4z7p0jjslc2vf6rqdjk1
1 - 100 of 220 matches
Mail list logo
