The Cassandra team is pleased to announce the release of Cassandra Java
Driver version 3.12.1. This is the first release of the 3.x Java driver to
contain new functionality since its donation to the Apache Software
Foundation.
The Source release and Binary convenience artifacts are available her
How are we going to document what each of 112 missing properties is doing
and / or exclude them from cassandra.yaml? There are a lot of properties
which just don't ring a bell exactly what they are for. I think we should
create a basic table and document what each is for and what is the decision
ab
So if you forget to update cassandra.yaml you fail the build? Makes sense to
me.
One additional thing I would like to see is the reverse… did you put something
in yaml that isn’t in Config? This is a bug I have seen a few times…. Mostly
because people don’t know the rules from SnakeYAML so ar
Love the suggestion of marking the hidden/advanced configuration properties
with annotations. Leaving a “configuration” property out of the main
configuration file should be deliberate and well thought and argued. I highly
doubt we have 112 “advanced” properties that really need to be hidden to
Love the suggestion of marking the hidden/advanced configuration properties
with annotations. Leaving a “configuration” property out of the main
configuration file should be deliberate and well thought and argued. I highly
doubt we have 112 “advanced” properties that really need to be hidden to
https://issues.apache.org/jira/browse/CASSANDRA-20249
On Fri, 24 Jan 2025 at 15:40, Dmitry Konstantinov
wrote:
> Maybe I missed some patterns but it looks like a pretty good estimation, I
> did like 10 random checks manually to verify :-)
> I will try to make an ant target with a similar logic (
Maybe I missed some patterns but it looks like a pretty good estimation, I
did like 10 random checks manually to verify :-)
I will try to make an ant target with a similar logic (hopefully, during
the weekend)
I will create a ticket to track this activity (to share attachments there
to not overload
Oh my god, 112? :DD I was thinking it would be less than 10.
Anyway, I think we need to integrate this to some ant target. If you
expanded on this, that would be great.
On Fri, Jan 24, 2025 at 4:31 PM Dmitry Konstantinov
wrote:
> A very primitive implementation of the 1st idea below:
>
> String
A very primitive implementation of the 1st idea below:
String configUrl =
"file:///Users/dmitry/IdeaProjects/cassandra-trunk/conf/cassandra.yaml";
Field[] allFields = Config.class.getFields();
List topLevelPropertyNames = new ArrayList<>();
for(Field field : allFields)
{
if (!Modifier.isStatic
It should also work the other way around. If there is a property which is
commented out in yaml and it is not in Config.java, that should fail as
well. If it is not commented out and it is not in Config.java, that will
fail in runtime as it fails on unrecognized property.
This will be used in prac
> > If "# my_cool_property: true" is NOT in cassandra.yaml, we might
indeed add it, also commented out. I think it would be quite easy to check
against yaml if there is a line starting on "# my_cool_property" or just on
"my_cool_property". Both cases would satisfy the check.
Makes sense, I think
+1 to making hidden properties explicit. No way to tell whether it's a mistake
or not atm.
On Fri, Jan 24, 2025, at 9:36 AM, Štefan Miklošovič wrote:
>
>
> On Fri, Jan 24, 2025 at 3:27 PM Paulo Motta wrote:
>> > from time to time I see configuration properties in Config.java and they
>> > are
Hi,
I do not care what bracing style we use. I do have a preferred one, but I don't
care which one we use.
I hate that we have check style, but not a gofmt equivalent. I would take any
amount of churn pain to have a gofmt equivalent so I could stop thinking about
style.
I would not want the c
On Fri, Jan 24, 2025 at 3:27 PM Paulo Motta wrote:
> > from time to time I see configuration properties in Config.java and they
> are clearly not in cassandra.yaml. Not every property in Config is in
> cassandra.yaml. I would like to know if there is some specific reason
> behind that.
>
> I thin
Same understanding here - the goal of property being presented in Config
but not cassandra.yaml was to keep those hidden from regular users aka -
advanced config. Also, in some cases I was told some of those did not have
a clear recommendation yet how to use them, one more reason to be hidden.
I t
Hi, I've just thought about the same as Stefan - can we automate this
consistency check.. (the topic is actually triggered by our recent review).
I definitely saw some other existing options which are available in Config
but not mentioned in cassandra.yaml.
The case with intentionally hidden option
> from time to time I see configuration properties in Config.java and they
are clearly not in cassandra.yaml. Not every property in Config is in
cassandra.yaml. I would like to know if there is some specific reason
behind that.
I think one of the original reasons was to "hide" advanced configs tha
I wouldn't oppose making things more well defined there.
Kind Regards,
Brandon
On Fri, Jan 24, 2025 at 8:22 AM Štefan Miklošovič
wrote:
>
> If that is the case, we could have something like this?
>
> @HiddenInYaml
> public boolean auto_bootstrap = true;
>
> Then a build-time check would
If that is the case, we could have something like this?
@HiddenInYaml
public boolean auto_bootstrap = true;
Then a build-time check would parse Config.java on these annotations etc
and skip that if it is not in yaml.
It is OK if we decide not to expose but we should have some basic overv
I think those are things we've decided we don't want to expose to the
average user, like auto_bootstrap.
Kind Regards,
Brandon
On Fri, Jan 24, 2025 at 8:16 AM Štefan Miklošovič
wrote:
>
> Hello,
>
> from time to time I see configuration properties in Config.java and they are
> clearly not in ca
Hello,
from time to time I see configuration properties in Config.java and they
are clearly not in cassandra.yaml. Not every property in Config is in
cassandra.yaml. I would like to know if there is some specific reason
behind that.
Question related to that is if we could not have a build-time ch
I think the status quo here extends to: operational issues and
performance regressions can be considered like bugs in this context,
and patches that are very isolated and deemed safe by any pmc member
with experience in that area of the code can approve it on the ticket
without it going to the mail
22 matches
Mail list logo
