2024 at 20:53, Maxim Muzafarov wrote:
>
> Hello everyone,
>
>
> I want to continue the discussion that was originally started here
> [2], however, it's better to move it to a new thread with an
> appropriate title, so that everyone is aware of the replacement
> lib
Hey,
I've prepared a python script that generates the same docs (no go
dependency). I use the jinja2 dependency, not sure if it's optimal
because I had to google how to use it though (also not sure if it has
to be run in docker).
I haven't tested the generated files with the website, but I've
comp
Congratulations, David!
On Mon, 28 Apr 2025 at 21:25, Ekaterina Dimitrova wrote:
>
> Congrats!! 🍾 And thank you for everything you do for the project!
>
> On Mon, 28 Apr 2025 at 15:20, Yifan Cai wrote:
>>
>> Congrats David!
>>
>>
>> From: Abe Ratnofsky
>> Sent:
Also +1
On Tue, 22 Apr 2025 at 07:57, guo Maxwell wrote:
>>
>> We have already agreed some time ago that any incompatible API change
>> requires a DISCUSS thread. I’m fairly sure it’s documented on the wiki.
>
>
> Yes, I remembered that we already have a thread to reach consensus on this.
>
> +1
This is extremely useful, I am the one who completely relies on the
ci-cassandra ;-)
Thank you!
On Thu, 20 Mar 2025 at 11:52, Jacek Lewandowski
wrote:
>
> Awesome, thank you!!!
>
>
> On Thu, Mar 20, 2025, 08:05 guo Maxwell wrote:
>>
>> Thanks so much!!!
>>
>> Berenguer Blasi 于2025年3月20日周四 1
+1 (nb)
On Sun, 9 Mar 2025 at 18:13, Jon Haddad wrote:
>
> +1
>
>
> On Sun, Mar 9, 2025 at 9:52 AM wrote:
>>
>> +1
>>
>>
>> On Mar 9, 2025, at 7:50 AM, Jeremiah Jordan
>> wrote:
>>
>> +1
>>
>> On Sun, Mar 9, 2025 at 8:03 AM Brandon Williams wrote:
>>>
>>> +1
>>>
>>> Kind Regards,
>>> Brandon
If we do swap, we may run into the same issues with third-party
metrics libraries in the next 10-15 years that we are discussing now
with the Codahale we added ~10-15 years ago, and given the fact that a
proposed new API is quite small my personal feeling is that it would
be our best choice for the
Congratulations Ekaterina!
On Wed, 5 Mar 2025 at 15:00, Mick Semb Wever wrote:
>
>.
>
>
> > The Project Management Committee (PMC) for Apache Cassandra is delighted to
> > announce that Ekaterina Dimitrova has joined the PMC!
> >
> > Thanks a lot, Ekaterina, for everything you have done for
Congratulations Caleb!
On Fri, 21 Feb 2025 at 07:45, guo Maxwell wrote:
>
> Congratulations Caleb!
>
> Berenguer Blasi 于2025年2月21日周五 14:37写道：
>>
>> Congrats Sir :-)
>>
>> On 21/2/25 2:04, Brandon Williams wrote:
>> > Congratulations Caleb!
>> >
>> > Kind Regards,
>> > Brandon
>> >
>> > On Thu, F
Congratulations!
On Thu, 20 Feb 2025 at 19:17, Abe Ratnofsky wrote:
>
> Congrats Maxwell and Dmitry!
Congratulation Jeremiah!
On Sat, 15 Feb 2025 at 05:01, Paulo Motta wrote:
>
> Congrats JD!
>
> On Fri, 14 Feb 2025 at 18:35 guo Maxwell wrote:
>>
>> Congrats！
>> Tolbert, Andy 于2025年2月15日 周六上午6:22写道：
>>>
>>> Congrats JD!
>>>
>>> On Fri, Feb 14, 2025 at 4:13 PM wrote:
Congratulations,
+1 (nb)
On Thu, 6 Feb 2025 at 05:34, Patrick McFadin wrote:
>
> +1
>
> On Wed, Feb 5, 2025 at 8:15 PM C. Scott Andreas wrote:
> >
> > +1
> >
> > On Feb 5, 2025, at 2:50 PM, Alex Petrov wrote:
> >
> >
> > +1
> >
> > On Wed, Feb 5, 2025, at 11:03 PM, Blake Eggleston wrote:
> >
> > Ok ok, I've jum
Hello community, Patrick,
I can also prepare some PP slides (status, design, and progress) and a
short talk for:
- CQL Management API
If you can help, option 2 sounds good to me.
On Thu, 30 Jan 2025 at 11:30, Rolo, Carlos via dev
wrote:
>
> Hello Patrick,
>
> Count me in!
>
> I would like to p
+1 (nb)
On Thu, 23 Jan 2025 at 16:35, Josh McKenzie wrote:
>
> +1
>
> On Thu, Jan 23, 2025, at 9:58 AM, Štefan Miklošovič wrote:
>
> +1
>
> On Sat, Jan 18, 2025 at 10:54 PM Bret McGuire wrote:
>
> Greetings all!
>
>
>I’m proposing the Cassandra Java Driver 3.12.1 for release.
>
>
> sha1: 873
Congratulations, Patrick!
I’m surprised because I thought you were already a member! :-)
On Wed, 22 Jan 2025 at 18:36, Francisco Guerrero wrote:
>
> Congrats, Patrick! It is well deserved.
>
> On 2025/01/22 16:05:09 Jordan West wrote:
> > The PMC's members are pleased to announce that Patrick McF
I'm leaning toward not changing the bracing style we already have
unless there's a powerful reason (hard to imagine what it could be).
So currently -1. I would rather focus on enabling lints we all agree
on, and/or the consensus is easy to achieve. There are many such
lints, and much work to be don
As a personal feeling from reading the thread:
Am I right in thinking that we are forcing new contributors to read
long contribution guides (in addition to spending time writing them)
in favour of just pressing Option+Cmd+L (or other hotkeys in the IDE
they like) to format the code before committi
To me, this sounds like the style consistency throughout the project,
so if we just allowed having the "var" keyword we would have a mix of
new and old styles without any distant prospect of a unified style.
We should evolve the code style from one unified form to another, thus
either we use it ev
Hello,
I wanted to throw some ideas and a vision in terms of metrics,
trancing and the adoption of new integrations, particularly
OpenTelemetry. I personally feel that the more integrations we have,
the better the adoption of Cassandra as a database will be. With
OpenTelemetry, users could have a
org/jira/browse/CASSANDRA-19760
[2] https://github.com/apache/cassandra/pull/3412/files
On Mon, 15 Jul 2024 at 21:06, Maxim Muzafarov wrote:
>
> Hello everyone,
>
> I would like to gently ask for help in reviewing the following issue
> that we've been facing for a while:
> https://i
+1
On Mon, 23 Sept 2024 at 01:59, Jordan West wrote:
>
> +1. Validated by starting and creating a 3 node cluster using easy-cass-lab.
>
> Jordan
>
> On Fri, Sep 20, 2024 at 7:36 AM Mick Semb Wever wrote:
>>
>>
>> Proposing the test build of Cassandra 4.1.7 for release.
>>
>> sha1: ca494526025a48
+1
On Fri, 20 Sept 2024 at 16:36, Mick Semb Wever wrote:
>
>
> Proposing the test build of Cassandra 5.0.1 for release.
>
> sha1: c206e4509003ac4cd99147d821bd4b5d23bdf5e8
> Git: https://github.com/apache/cassandra/tree/5.0.1-tentative
> Maven Artifacts:
> https://repository.apache.org/content/re
Сongrats Jordan and Stefan.
Great work!
On Sun, 1 Sept 2024 at 12:46, guo Maxwell wrote:
>
> Congrats Stefan and Jordan!!!
>
> Jacek Lewandowski 于2024年9月1日 周日下午4:39写道：
>>
>> Congrats Stefan and Jordan!!! This is great!
>>
>>
>> sob., 31 sie 2024, 22:21 użytkownik Jordan West napisał:
>>>
>>> Tha
My congratulations Joseph Lynch!
On Thu, 25 Jul 2024 at 18:15, Paulo Motta wrote:
>
> Congratulations Joey!
>
> On Thu, 25 Jul 2024 at 00:55 Venkata Hari Krishna Nukala
> wrote:
>>
>> Congratulations Joey!!
>>
>> On Thu, 25 Jul 2024 at 7:20 AM, Joseph Lynch wrote:
>>>
>>> Thank you all for the
> Apache is close to my heart and I have no intention to switch to another
>>> > license.
>>> >
>>> > The picocli documentation mentions it is possible to incorporate picocli
>>> > in one’s project by copying a single source file. This is not meant
Hello everyone,
I would like to gently ask for help in reviewing the following issue
that we've been facing for a while:
https://issues.apache.org/jira/browse/CASSANDRA-19760
When a cleanup command is called, the compaction process under the
hood is triggered accordingly. However, if there is not
Hello everyone,
I want to continue the discussion that was originally started here
[2], however, it's better to move it to a new thread with an
appropriate title, so that everyone is aware of the replacement
library we're trying to agree on.
The question is:
Does everyone agree with using Picocl
the burden on
> operators / integrations that rely on the nodetool output. As I have earlier
> indicated in the past, relying on human readable output for CLI tools like
> nodetool is fragile and providing a JSON output as an alternative is a great
> first step in eliminating th
ting that dependency. I'm just curious about the level
> of effort. If it is too much or too invasive, we can consider producing JSON
> output for inclusion in the next major release.
>
> On Fri, Jun 28, 2024 at 6:47 AM Maxim Muzafarov wrote:
>>
>> Hello everyone,
&
Hello everyone,
The nodetool relies on the airlift/airline library to mark up the CLI
commands used to manage Cassandra, which are part of our public API.
This library is no longer maintained, so we need to update it anyway,
and the good news is that we already have several good alternatives:
air
Congratulations Dinesh!
On Fri, 21 Jun 2024 at 05:12, Abhijeet Dubey wrote:
>
> Thank you Josh for the amazing work.
>
> Congrats, Dinesh. Welcome to the new role :)
>
> Regards,
> Abhijeet
>
> On Fri, Jun 21, 2024 at 4:09 AM Dinesh Joshi wrote:
>>
>> Thank you everybody. I hope to do my best in
Hello everyone,
I like the idea of highlighting some of the experimental virtual
tables whose model might be changed in future releases.
As another option, we could add an @Experimetal annotation (or another
name) and a configuration parameter
experimental_virtula_tables_enabled (default is false
+1 (nb)
Build from the release branch, and run locally a few tests.
On Fri, 17 May 2024 at 23:06, 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 v
Hello everyone,
During the implementation, many valid design comments were made about
making the virtual table SettingTable [1] updatable. So, I've
rethought the whole concept once again, and I want to take another
step forward to make this problem feasible with less effort on our
part.
I want to
Congratulations!
On Thu, 22 Feb 2024 at 10:23, Berenguer Blasi wrote:
>
> Congrats!
>
> On 22/2/24 9:57, Jacek Lewandowski wrote:
>
> Congrats Brad!
>
>
> - - -- --- - -
> Jacek Lewandowski
>
>
> czw., 22 lut 2024 o 01:29 Štefan Miklošovič
> napisał(a):
>>
>> Congrats B
a-cql-in-ap
On Fri, 22 Dec 2023 at 12:38, Maxim Muzafarov wrote:
>
> Hello everyone and happy holidays,
>
> The changes below are ready for review!
> Benchmarks are also inside.
>
> Expose all table metrics in virtual tables
> https://issues.apache.org/jira/browse/CASSAND
;>>
>>>> On 2024/01/08 18:19:04 Josh McKenzie wrote:
>>>> > The Apache Cassandra PMC is pleased to announce that Maxim Muzafarov has
>>>> > accepted
>>>> > the invitation to become a committer.
>>>> >
>>
tation. I propose we start simple, see if any of the reasons you've
> listed are actually a real problem, then if they are, address the issue in a
> follow up.
>
> If I'm wrong, it sounds like it's fairly easy to add `exec` for changing
> configs. If I'm
solvable problem, and I think the benefits of having a
>>> single, elegant way of interacting with a cluster and configuring it
>>> justifies the investment for us as a project. Assuming someone has the
>>> cycles to, you know, actually do the work. :D
>>>
>
Happy New Year to everyone! I'd like to thank everyone for their
questions, because answering them forces us to move towards the right
solution, and I also like the ML discussions for the time they give to
investigate the code :-)
I'm deliberately trying to limit the scope of the initial solution
like
> > the following
> >
> > registerWithJMX(jmxName, query(“SELECT * FROM system_views.streaming”));
> >
> >
> > So if we want to have a JMX view that matches the table then that’s cool by
> > me, but one thing that has been brought up in reviews is
Hello Raymond,
Do you have draft changes to look at?
I'd suggest a more general approach, as some interfaces seem to
overlap each other. There is the FSErrorHandler, and the
JVMStabilityInspector both of which are currently not configurable via
user configuration. I think it would be possible to
Ariel,
thank you for bringing this topic to the ML.
I may be missing something, so correct me if I'm wrong somewhere in
the management of the Cassandra ecosystem. As I see it, the problem
right now is that if we fork the ohc and put it under its own root,
the use of that row cache is still not we
Hello Benjamin,
Can you share the reasons why Apache Calcite is not suitable for this
case and why it was rejected? It has custom syntax support, CBO, so I
am interested to see some technical details in the "Rejected
Alternatives" section, I'm pretty sure they exist, but they weren't
mentioned the
same picture from various of Dropwizard's metrics exporters
>
> If this is a real problem people are hitting, we can always add the ability
> to push metrics to common systems with a pluggable way to add non-standard
> solutions. Dropwizard already support this so would be low
+1 (nb)
run locally, executed some queries over vts
On Mon, 4 Dec 2023 at 15:15, Brandon Williams wrote:
>
> +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: 87fd1fa88a
I'm gonna take a moment to outline the question. Here we have a point
in time where a time-driven release process clashes with the
alpha/beta release naming convention: we want to have a beta ready
_before_ the Summit.
Here's the Cassandra release lifecycle document [1] that I found
(still under d
My congratulations, Francisco! :-)
On Wed, 29 Nov 2023 at 13:30, Andrés de la Peña wrote:
>
> Congrats Francisco!
>
> On Wed, 29 Nov 2023 at 11:37, Benjamin Lerer wrote:
>>
>> Congratulations!!! Well deserved!
>>
>> Le mer. 29 nov. 2023 à 07:31, Berenguer Blasi a
>> écrit :
>>>
>>> Welcome!
>>
decides to use a dedicated port.
> >
> > More importantly, I think having this functionality exposed over the
> > storage ports may be even better. The storage ports are typically
> > firewalled off from the end users. Operators and tooling, however, usually
> >
a
> either through your CEP or other means but I can also see this as an adjacent
> sub project - let's discuss 🙂
>
> German
>
>
> From: Maxim Muzafarov
> Sent: Monday, November 13, 2023 10:08 AM
> To: dev@cassandra.apache.org
&
Hello everyone,
While we are still waiting for the review to make the settings virtual
table updatable (CASSANDRA-15254), which will improve the
configuration management experience for users, I'd like to take
another step forward and improve the C* management approach we have as
a whole. This appr
+1
you've mentioned some important fixes earlier [1], and we are waiting
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 t
+1 (nb)
On Wed, 1 Nov 2023 at 03:26, guo Maxwell wrote:
>
> +1
>
> German Eichberger via dev 于2023年11月1日周三 04:58写道：
>>
>> +1
>>
>> Heck, yeah, we already tested the branch (build ourselves) and it works
>> great so far.
>>
>> From: Mick Semb Wever
>> Sent: Tues
tter
> reviewer Maxim? And / or making the review process simpler / cleaner for
> someone?
>
> On Wed, Oct 18, 2023, at 5:06 PM, Maxim Muzafarov wrote:
>
> Hello everyone,
>
> It has been a long time since the last update on this thread, so I
> wanted to share some
Personally, I think frequent releases (2-3 per year) are better than
infrequent big releases. I can understand all the concerns from a
marketing perspective, as smaller major releases may not shine as
brightly as a single "game changer" release. However, smaller
releases, especially if they don't h
and potentially will draw some
attention to the community;
- Presenting and discussing slides at one of the Cassandra Town Halls;
I tend to the 1-st and/or 2-nd points. What are the best practices we
have here for such cases though? Any thoughts?
On Tue, 11 Jul 2023 at 15:51, Maxim Muzafarov
I think the source code can describe the intention better than words :-)
The link to our Code Style with a discussion "summary":
https://github.com/apache/cassandra-website/pull/245/files
The link to the pull request with the proposed changes (only "since"
added and description):
https://github.c
force the above, so the mechanisms to
> enforce it would still need to be laid out, unless we can easily support
> something like the above with checkstyle rules.
>
> On 2023/10/10 20:34:27 Maxim Muzafarov wrote:
> > Hello everyone,
> >
> >
> > I&#
Hello everyone,
I've discussed with Stefan some steps we can take to improve the final
solution, so the final version might look like this:
/** @deprecated See CASSANDRA-6504 */
@Deprecated(since = "2.1")
public Integer concurrent_replicates = null;
The issue number will be taken from the git b
some room to do
> the housekeeping like this after these patches lend. It is not like Accord
> will be in trunk on Monday and we release Tuesday ...
>
> ________
> From: Maxim Muzafarov
> Sent: Monday, July 31, 2023 23:05
> To: dev@cassandra.apache.
Hello everyone,
This message is both a review request and my attempt to share with you
some of the benchmark results related to replacing the CRC32 algorithm
for the internode messaging protocol.
When a new connection is initiated between nodes, the corresponding
connection channel is configured
ithub.com/apache/cassandra/pull/2238/files
>
> On Thu, Jul 27, 2023, at 7:59 AM, Maxim Muzafarov wrote:
>
> Bump this topic up for visibility as the code freeze is coming soon.
>
> This seems like a good change to include in 5.0 as this kind of
> library upgrade is more natural wh
+1 (nb)
On Tue, 3 Oct 2023 at 19:48, Vinay Chella wrote:
>
> +1 (nb)
>
> Thanks,
> Vinay Chella
>
>
> On Tue, Oct 3, 2023 at 10:44 AM Yifan Cai wrote:
>>
>> +1
>>
>> From: David Capwell
>> Sent: Tuesday, October 3, 2023 9:45:02 AM
>> To: dev
>> Subject: Re: [VO
Hello everyone,
The problem that I'm struggling with is not directly related to the
topic I'm about to discuss now, but it probably illustrates the
greater complexity of backwards compatibility with the drivers we now
support. For instance, I want to replace the algorithm that is used to
calculat
Hello Stefan,
+1
Do we plan to release these changes? I am mostly interested in using
4.0, 4.1 :-)
On Tue, 26 Sept 2023 at 17:49, Miklosovic, Stefan
wrote:
>
> 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
A few updates.
We've posted a message to the user-list asking the question about the
use of the metrics-reporter-config library to make sure we are on the
safe side with the removal:
https://lists.apache.org/thread/c4m3tc08zhd4d41zs05jcdkr3gjwlhno
The issue for the `org.caffinitas.ohc:ohc-core-j8
Hello everyone,
CASSANDRA-14667 when the 3.11.5 driver version with shaded metrics
dependencies is released, it will be fairly easy to handle the
cassandra-related part and get rid of the old metrics version in
Cassandra itself (the number of changes to the Cassandra part is also
minimal ~10 line
There are a few other dependencies that are probably no longer used
and can be removed. I'm not talking about the netty-related
dependencies, because they seem to be used transitively and required
to be in the classpath, but the others are good candidates, I think.
For example, org.caffinitas.ohc:
te with something like an "API" section (gasp) here:
> >> https://cassandra.apache.org/doc/latest/.
> >>
> >> Would certainly help motivate us to clarify the whole "what is an external
> >> API we're committing to or not" discussions.
>
+1 (nb)
verified checksums, signing, and build from sources.
The link is broken :-(
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1306/org/apache/cassandra/cassandra-all/3.11.16/
On Wed, 16 Aug 2023 at 19:18, Brandon Williams wrote:
>
> +1
>
> Kind Regar
+1
The rationale for deprecating/removing this library is not just that
it is obsolete and doesn't get updates. In fact, when the
metrics-reporter-config [1] was added the dropwizard metrics library
(formerly com.yammer.metrics [2]) didn't support exporting metrics to
files like csv, so it made se
hould fix things and add the task to
> CI, if we don’t because no one wants the html pages - then better to remove
> it this ant task.
> On your comment about 100 errors - it seems they are more. There is a cap of
> 100 but when you fix them, more errors appear.
> Further discussion
Personally, I find javadocs quite useful, especially when htmls are
indexed by search engines, which in turn increases the chances of
finding the right answer faster (I have seen a lot of useful javadocs
in the source code).
I have done a quick build of the javadocs:
[javadoc] Building index fo
[blank line]
net.*
[blank line]
org.*
[blank line]
org.apache.cassandra.*
[blank line]
all other imports
[blank line]
static all other imports
On Mon, 27 Feb 2023 at 13:26, Maxim Muzafarov wrote:
>
> > I suppose it can be easy for the existing feature branches if they have a
> >
, Maxim Muzafarov wrote:
>
> Hello everyone,
>
> It still needs a pair of eyes to push it forward.
>
>
> I came across another good thing that might help us to overcome the
> difficulties with the dropwizard metrics dependency upgrade. The
> change relates to the driver
s
On Mon, 3 Jul 2023 at 15:15, Maxim Muzafarov wrote:
>
> I'd like to mention the approach we took here: to untangle the driver
> update in tests with the dropwizard library version (cassandra-driver
> 3.11 requires the "old" JMXReporter classes in the classpath) we ha
+1 (nb)
Checked:
- the rc version
- the branch builds
- the branch version matches the rc version
- downloaded binaries and sources
- checksums and signature verified
I have created the following GitHub Action to automate the process:
https://github.com/apache/cassandra/compare/trunk...Mmuzaf:c
introduce any new column to
> system_views.settings.
> We could also go with the introduction of this column to 4.1 if people are ok
> with that.
>
> For the simplicity, I am slightly leaning towards introducing this feature to
> 5.0 only.
>
> (1) https://github.com/apache/cas
In my humble opinion, it is better to have only one plain and
straightforward build pipeline for the whole project, with custom
flags used to skip a particular step, than to have multiple pipelines
under the ant tool with multiple endpoints accordingly. I mean, all
the steps need to be lined up, wi
For me, the biggest benefit of keeping the build scripts and CI
configurations as well in the same project is that these files are
versioned in the same way as the main sources do. This ensures that we
can build past releases without having any annoying errors in the
scripts, so I would say that th
version numbers.
>
> Since the library upgrade need to happen sooner or later, I don't see
> any reason why it should not happen in the 5.0 release.
>
>
> On 27/06/2023 19:21, Maxim Muzafarov wrote:
> > Hello everyone,
> >
> >
> > We use the Dropwizard
Hello everyone,
We use the Dropwizard Metrics 3.1.5 library, which provides a basic
set of classes to easily expose Cassandra internals to a user through
various interfaces (the most common being JMX). We want to upgrade
this library version in the next major release 5.0 up to the latest
stable 4
Hello everyone,
We can replace RAT with the appropriate checkstyle rule - the HeaderCheck,
I think. This will reduce the number of tools we now use and reduce the
build time as only modified files will be checked, and this, in turn, will
remove some of the concerns mentioned in the first message.
actual:
seeds: 127.0.0.1:7012
-
Property 'data_file_directories' expected:
[Ljava.lang.String;@436813f3
Property 'data_file_directories' actual:
[build/test/cassandra/data]
-----
On Mon, 1 May 2023 at 15:11, Maxim Muz
perties or
> just properties for tests or just Java properties and selecting just the
> first two groups would not break CQLSH. It is nice that it would have same
> prefix but I am trying to find a way how to utilize the same prefix in CQLSH
> as well.
>
> _
Hello everyone,
I would like to make the source code of the Cassandra project more
visible to people outside of the Cassandra Community and highlight the
typical known issues in new contributions in the GitHub pull-request
interface as well. This makes it easier for those who are unfamiliar
with t
;>
>>
>>
>>
>> Hi Maxim,
>>
>> thanks for letting us know.
>>
>> I reviewed it couple months ago but I can revisit it to double check. We
>> need the second reviewer. Until we find somebody, we can not merge this.
>>
>> If anybod
roposed design is our
best.
Thoughts?
On Thu, 30 Mar 2023 at 01:42, Maxim Muzafarov wrote:
>
> Hello everyone,
>
>
> It seems to me that we need another consensus to make the
> SettingsTable virtual table updatable. There is an issue with
> validating configuration properties th
Hello Claude,
I have seen two options and the option you mentioned is probably the
third from ways of disabling a feature :-)
So, we have
1.
public class TransparentDataEncryptionOptions
{
public boolean enabled = false;
public ParameterizedClass key_provider;
}
2.
public boolean cdc_en
re appropriate, please share. From my point of view,
option 2 is the most appropriate here, as it fits with everything we
have discussed in this thread. However, they are all fine to go with.
I'm looking forward to hearing your thoughts.
On Tue, 21 Feb 2023 at 22:06, Maxim Muzafarov wrote:
>
> H
s
On Wed, 8 Feb 2023 at 19:48, Maxim Muzafarov wrote:
>
> Hello everyone,
>
>
> We are trying to clean up the source code around the direct use of
> system properties and make this use more manageable and transparent.
> To achieve this, I have prepared a patch that moves all
When I was a release manager for another Apache project, I found it
useful to create confluence pages for the upcoming release, both for
transparency of release dates and for benchmarks. Of course, the dates
can be updated when we will have a better understanding of the scope
of the release.
Do we
n code and no longer in conf/cassandra.yml… I am ok with this, but
> this does increase the scope as it needs to address the existing models. We
> also need better clarity on compatibility with column additions… there is
> another dev@ thread pointing out that durable tables cause d
approaches - the annotations one seems most reasonable
> to me and I didn’t have the chance to consider any others. Volatile seems
> fragile and unclear as a differentiator. I agree
>
> On Tue, 28 Feb 2023 at 17:47, Maxim Muzafarov
> mailto:mmu...@apache.org>> wrote:
> Folks,
ll of them, should NOT
> >> be volatile at all. Someone started the trend and most folks have been
> >> copycatting or doing the same for consistency with the rest of the
> >> codebase.
> >>
> >> Please definitely don’t rely on that.
> >>
>
ewandowski
wrote:
>
> I suppose it can be easy for the existing feature branches if they have a
> single commit. Don't we need to adjust each commit for multi-commit feature
> branches?
>
> śr., 22 lut 2023, 19:48 użytkownik Maxim Muzafarov
> napisał:
>>
>>
with any work
> people would like to include in 5.0. This can go in anytime, basically.
>
> Are people on the same page?
>
> Regards
>
> ____
> From: Maxim Muzafarov
> Sent: Monday, January 23, 2023 19:46
> To: dev@cassandra.apache
Hello everyone,
I would like to share and discuss the key point of the solution design
with you before I finalise a pull request with tedious changes
remaining so that we are all on the same page with the changes to the
valuable Config class and its accessors.
Here is the issue I'm working on:
"
d format and they should move to the new ones.
>
> Anyway, I am glad this is happening and we are making progress. It will be
> also way easier to dump all properties to the website when everything is
> centralized at once place.
>
> Regards
>
>
>
Hello everyone,
We are trying to clean up the source code around the direct use of
system properties and make this use more manageable and transparent.
To achieve this, I have prepared a patch that moves all system
property names to the CassandraRelevantProperties, which in turn makes
some of the
1 - 100 of 112 matches
Mail list logo
