You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Mick Semb Wever <mc...@apache.org> on 2022/02/11 09:39:04 UTC
[RELEASE] Apache Cassandra 4.0.2 released
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0.2.
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 and binary distributions are listed in our download section:
http://cassandra.apache.org/download/
This version is a bug fix release[1] on the 4.0 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.
Enjoy!
[1]: CHANGES.txt
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.2
[2]: NEWS.txt https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.2
[3]: https://issues.apache.org/jira/browse/CASSANDRA
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Brandon Williams <dr...@gmail.com>.
I don't think that's enough. We noop'd this in 3.11:
https://github.com/apache/cassandra/blob/cassandra-3.11/NEWS.txt#L310
but never mentioned it again or did a proper deprecation notice, so
dropping them in a minor is especially not nice.
On Fri, Feb 11, 2022 at 4:26 PM Erick Ramirez
<er...@datastax.com> wrote:
>
> (moved dev@ to BCC)
>
>>
>> It looks like the otc_coalescing_strategy config key is no longer supported in cassandra.yaml in 4.0.2, despite this not being mentioned anywhere in CHANGES.txt or NEWS.txt.
>
>
> James, you're right -- it was removed by CASSANDRA-17132 in 4.0.2 and 4.1.
>
> I agree that the CHANGES.txt entry should be clearer and we'll improve it plus add detailed info in NEWS.txt. I'll get this done soon in CASSANDRA-17135. Thanks for the feedback. Cheers!
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by David Capwell <dc...@apple.com>.
Agree
Sent from my iPhone
> On Feb 13, 2022, at 5:53 AM, Ekaterina Dimitrova <e....@gmail.com> wrote:
>
>
> “ We sadly don’t document when a config is free to remove, we should do that to enhance our warnings to users as well as make clear when free to remove; we spoke about this in 4.0 timeline that your deprecate in X.0.0 and remove in (X+1).0.0, we should document this in code for each config”
>
> This and IMHO it should be absolutely clear where deprecated means that things are still usable (but will be removed) and where it means that they are removed(maybe replaced by different solution) and this is just a placeholder.
>
>> On Sun, 13 Feb 2022 at 8:34, David Capwell <dc...@apple.com> wrote:
>> In CASSANDRA-17166 I am adding a test that detects breaking changes; this is not compile time, rather test case time…
>>
>> We sadly don’t document when a config is free to remove, we should do that to enhance our warnings to users as well as make clear when free to remove; we spoke about this in 4.0 timeline that your deprecate in X.0.0 and remove in (X+1).0.0, we should document this in code for each config
>>
>> Sent from my iPhone
>>
>>>> On Feb 12, 2022, at 10:54 AM, Dinesh Joshi <dj...@apache.org> wrote:
>>>>
>>> +1 on introducing compile time checks to ensure backward compatibility.
>>
>>>
>>> Confusion due to usage of deprecated settings is understandable. However, settings marked deprecated should produce a warning in logs so that the operators become aware of their usage in the YAML and can migrate to the newer settings.
>>>
>>> Also breakages do happen once in a while. As long as we fix them quickly and/or revert the code in the meanwhile it's fine.
>>>
>>>> On Feb 12, 2022, at 3:56 AM, Ekaterina Dimitrova <e....@gmail.com> wrote:
>>>>
>>>> 15234 was a discussion about changing names and making parameters work with the old ones. Still working parameters, backward compatibility and not placeholders.
>>>>
>>>> Benedict, I can understand that when I said removal in this ticket you thought I will deprecate in Config but unfortunately it is not what I meant. I should have asked you also for review. I take the responsibility of doing a mistake here by removing in minor release thinking this is a bug that leads to dangerous confusion you can still use them. Indeed CHANGES.txt entry was created but not NEWS.txt and it requires a person to check which exact parameters were removed to take an action. I pushed a patch already to fix this. Docs are also on the way now when ADOC migration is over.
>>>>
>>>> One of the yaml parameters was actually also already removed with the rewrite of the messaging system in 4.0. I added back that one to Config too yesterday, to be on the safe side.
>>>>
>>>> “ I wonder if we should introduce a compile time check that validates config compatibility with prior versions, to avoid this in future”
>>>>
>>>> I think David is working on some tests to catch removed config in trunk, I will follow up on Monday with him.
>>>>
>>>>> On Sat, 12 Feb 2022 at 5:49, benedict@apache.org <be...@apache.org> wrote:
>>>>> As discussed on 15234, there is never a rush to remove Config parameters, and it should only be done when there’s some clear value. Since the overhead of having an unused parameter is ~zero, in my opinion this occurs only when we really need the operator to consider the semantic impact of its deprecation.
>>>>>
>>>>>
>>>>>
>>>>> We should never break minor upgrades, but we shouldn’t break any upgrade unnecessarily.
>>>>>
>>>>>
>>>>>
>>>>> I wonder if we should introduce a compile time check that validates config compatibility with prior versions, to avoid this in future.
>>>>>
>>>>>
>>>>>
>>>>> From: Dinesh Joshi <dj...@apache.org>
>>>>> Date: Saturday, 12 February 2022 at 00:09
>>>>> To: dev@cassandra.apache.org <de...@cassandra.apache.org>
>>>>> Subject: Re: [RELEASE] Apache Cassandra 4.0.2 released
>>>>>
>>>>> We should also have deprecation guidance in Config.java. This will help when anybody is making changes in the future.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Feb 11, 2022, at 3:07 PM, Ekaterina Dimitrova <e....@gmail.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Note taken, I had to document only in 4.0.x that those are placeholder. I just opened ticket to fix that - CASSANDRA-17377. I am going to submit a patch soon
>>>>>
>>>>>
>>>>>
>>>>> On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jj...@gmail.com> wrote:
>>>>>
>>>>> We don't HAVE TO remove the Config.java entry - we can mark it as deprecated and ignored and remove it in a future version (and you could update Config.java to log a message about having a deprecated config option). It's a much better operator experience: log for a major version, then remove in the next.
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e....@gmail.com> wrote:
>>>>>
>>>>> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to fix a bug that gives impression those work. Confirmed with Benedict on the ticket.
>>>>>
>>>>>
>>>>>
>>>>> I agree I absolutely had to document it better, a ticket for documentation was opened but it slipped from my mind with this emergency release this week. It is unfortunate it is still in our backlog after the ADOC migration.
>>>>>
>>>>>
>>>>>
>>>>> Note taken. I truly apologize and I am going to prioritize CASSANDRA-17135. Let me know if there is anything else I can/should do at this point.
>>>>>
>>>>>
>>>>>
>>>>> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com> wrote:
>>>>>
>>>>> (moved dev@ to BCC)
>>>>>
>>>>>
>>>>>
>>>>> It looks like the otc_coalescing_strategy config key is no longer supported in cassandra.yaml in 4.0.2, despite this not being mentioned anywhere in CHANGES.txt or NEWS.txt.
>>>>>
>>>>>
>>>>>
>>>>> James, you're right -- it was removed by CASSANDRA-17132 in 4.0.2 and 4.1.
>>>>>
>>>>>
>>>>>
>>>>> I agree that the CHANGES.txt entry should be clearer and we'll improve it plus add detailed info in NEWS.txt. I'll get this done soon in CASSANDRA-17135. Thanks for the feedback. Cheers!
>>>>>
>>>>>
>>>>>
>>>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Ekaterina Dimitrova <e....@gmail.com>.
“ We sadly don’t document when a config is free to remove, we should do
that to enhance our warnings to users as well as make clear when free to
remove; we spoke about this in 4.0 timeline that your deprecate in X.0.0
and remove in (X+1).0.0, we should document this in code for each config”
This and IMHO it should be absolutely clear where deprecated means that
things are still usable (but will be removed) and where it means that they
are removed(maybe replaced by different solution) and this is just a
placeholder.
On Sun, 13 Feb 2022 at 8:34, David Capwell <dc...@apple.com> wrote:
> In CASSANDRA-17166 I am adding a test that detects breaking changes; this
> is not compile time, rather test case time…
>
> We sadly don’t document when a config is free to remove, we should do that
> to enhance our warnings to users as well as make clear when free to remove;
> we spoke about this in 4.0 timeline that your deprecate in X.0.0 and remove
> in (X+1).0.0, we should document this in code for each config
>
> Sent from my iPhone
>
> On Feb 12, 2022, at 10:54 AM, Dinesh Joshi <dj...@apache.org> wrote:
>
> +1 on introducing compile time checks to ensure backward compatibility.
>
>
> Confusion due to usage of deprecated settings is understandable. However,
> settings marked deprecated should produce a warning in logs so that the
> operators become aware of their usage in the YAML and can migrate to the
> newer settings.
>
> Also breakages do happen once in a while. As long as we fix them quickly
> and/or revert the code in the meanwhile it's fine.
>
> On Feb 12, 2022, at 3:56 AM, Ekaterina Dimitrova <e....@gmail.com>
> wrote:
>
> 15234 was a discussion about changing names and making parameters work
> with the old ones. Still working parameters, backward compatibility and
> not placeholders.
>
> Benedict, I can understand that when I said removal in this ticket you
> thought I will deprecate in Config but unfortunately it is not what I
> meant. I should have asked you also for review. I take the responsibility
> of doing a mistake here by removing in minor release thinking this is a bug
> that leads to dangerous confusion you can still use them. Indeed
> CHANGES.txt entry was created but not NEWS.txt and it requires a person to
> check which exact parameters were removed to take an action. I pushed a
> patch already to fix this. Docs are also on the way now when ADOC migration
> is over.
>
> One of the yaml parameters was actually also already removed with the
> rewrite of the messaging system in 4.0. I added back that one to Config too
> yesterday, to be on the safe side.
>
> “ I wonder if we should introduce a compile time check that validates
> config compatibility with prior versions, to avoid this in future”
>
> I think David is working on some tests to catch removed config in trunk, I
> will follow up on Monday with him.
>
> On Sat, 12 Feb 2022 at 5:49, benedict@apache.org <be...@apache.org>
> wrote:
>
>> As discussed on 15234, there is never a rush to remove Config parameters,
>> and it should only be done when there’s some clear value. Since the
>> overhead of having an unused parameter is ~zero, in my opinion this occurs
>> only when we really need the operator to consider the semantic impact of
>> its deprecation.
>>
>>
>>
>> We should never break minor upgrades, but we shouldn’t break any upgrade
>> unnecessarily.
>>
>>
>>
>> I wonder if we should introduce a compile time check that validates
>> config compatibility with prior versions, to avoid this in future.
>>
>>
>>
>> *From: *Dinesh Joshi <dj...@apache.org>
>> *Date: *Saturday, 12 February 2022 at 00:09
>> *To: *dev@cassandra.apache.org <de...@cassandra.apache.org>
>> *Subject: *Re: [RELEASE] Apache Cassandra 4.0.2 released
>>
>> We should also have deprecation guidance in Config.java. This will help
>> when anybody is making changes in the future.
>>
>>
>>
>> On Feb 11, 2022, at 3:07 PM, Ekaterina Dimitrova <e....@gmail.com>
>> wrote:
>>
>>
>>
>> Note taken, I had to document only in 4.0.x that those are placeholder. I
>> just opened ticket to fix that - CASSANDRA-17377. I am going to submit a
>> patch soon
>>
>>
>>
>> On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jj...@gmail.com> wrote:
>>
>> We don't HAVE TO remove the Config.java entry - we can mark it as
>> deprecated and ignored and remove it in a future version (and you could
>> update Config.java to log a message about having a deprecated config
>> option). It's a much better operator experience: log for a major version,
>> then remove in the next.
>>
>>
>>
>> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <
>> e.dimitrova@gmail.com> wrote:
>>
>> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it
>> to fix a bug that gives impression those work. Confirmed with Benedict on
>> the ticket.
>>
>>
>>
>> I agree I absolutely had to document it better, a ticket for
>> documentation was opened but it slipped from my mind with this emergency
>> release this week. It is unfortunate it is still in our backlog after the
>> ADOC migration.
>>
>>
>>
>> Note taken. I truly apologize and I am going to prioritize
>> CASSANDRA-17135. Let me know if there is anything else I can/should do at
>> this point.
>>
>>
>>
>> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>
>> wrote:
>>
>> (moved dev@ to BCC)
>>
>>
>>
>> It looks like the otc_coalescing_strategy config key is no longer
>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>> anywhere in CHANGES.txt or NEWS.txt.
>>
>>
>>
>> James, you're right -- it was removed by CASSANDRA-17132
>> <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
>>
>>
>>
>> I agree that the CHANGES.txt entry should be clearer and we'll improve it
>> plus add detailed info in NEWS.txt. I'll get this done soon in
>> CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
>> Thanks for the feedback. Cheers!
>>
>>
>>
>
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by David Capwell <dc...@apple.com>.
In CASSANDRA-17166 I am adding a test that detects breaking changes; this is not compile time, rather test case time…
We sadly don’t document when a config is free to remove, we should do that to enhance our warnings to users as well as make clear when free to remove; we spoke about this in 4.0 timeline that your deprecate in X.0.0 and remove in (X+1).0.0, we should document this in code for each config
Sent from my iPhone
> On Feb 12, 2022, at 10:54 AM, Dinesh Joshi <dj...@apache.org> wrote:
>
> +1 on introducing compile time checks to ensure backward compatibility.
>
> Confusion due to usage of deprecated settings is understandable. However, settings marked deprecated should produce a warning in logs so that the operators become aware of their usage in the YAML and can migrate to the newer settings.
>
> Also breakages do happen once in a while. As long as we fix them quickly and/or revert the code in the meanwhile it's fine.
>
>> On Feb 12, 2022, at 3:56 AM, Ekaterina Dimitrova <e....@gmail.com> wrote:
>>
>> 15234 was a discussion about changing names and making parameters work with the old ones. Still working parameters, backward compatibility and not placeholders.
>>
>> Benedict, I can understand that when I said removal in this ticket you thought I will deprecate in Config but unfortunately it is not what I meant. I should have asked you also for review. I take the responsibility of doing a mistake here by removing in minor release thinking this is a bug that leads to dangerous confusion you can still use them. Indeed CHANGES.txt entry was created but not NEWS.txt and it requires a person to check which exact parameters were removed to take an action. I pushed a patch already to fix this. Docs are also on the way now when ADOC migration is over.
>>
>> One of the yaml parameters was actually also already removed with the rewrite of the messaging system in 4.0. I added back that one to Config too yesterday, to be on the safe side.
>>
>> “ I wonder if we should introduce a compile time check that validates config compatibility with prior versions, to avoid this in future”
>>
>> I think David is working on some tests to catch removed config in trunk, I will follow up on Monday with him.
>>
>> On Sat, 12 Feb 2022 at 5:49, benedict@apache.org <be...@apache.org> wrote:
>>> As discussed on 15234, there is never a rush to remove Config parameters, and it should only be done when there’s some clear value. Since the overhead of having an unused parameter is ~zero, in my opinion this occurs only when we really need the operator to consider the semantic impact of its deprecation.
>>>
>>>
>>>
>>> We should never break minor upgrades, but we shouldn’t break any upgrade unnecessarily.
>>>
>>>
>>>
>>> I wonder if we should introduce a compile time check that validates config compatibility with prior versions, to avoid this in future.
>>>
>>>
>>>
>>> From: Dinesh Joshi <dj...@apache.org>
>>> Date: Saturday, 12 February 2022 at 00:09
>>> To: dev@cassandra.apache.org <de...@cassandra.apache.org>
>>> Subject: Re: [RELEASE] Apache Cassandra 4.0.2 released
>>>
>>> We should also have deprecation guidance in Config.java. This will help when anybody is making changes in the future.
>>>
>>>
>>>
>>>
>>> On Feb 11, 2022, at 3:07 PM, Ekaterina Dimitrova <e....@gmail.com> wrote:
>>>
>>>
>>>
>>> Note taken, I had to document only in 4.0.x that those are placeholder. I just opened ticket to fix that - CASSANDRA-17377. I am going to submit a patch soon
>>>
>>>
>>>
>>> On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jj...@gmail.com> wrote:
>>>
>>> We don't HAVE TO remove the Config.java entry - we can mark it as deprecated and ignored and remove it in a future version (and you could update Config.java to log a message about having a deprecated config option). It's a much better operator experience: log for a major version, then remove in the next.
>>>
>>>
>>>
>>> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e....@gmail.com> wrote:
>>>
>>> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to fix a bug that gives impression those work. Confirmed with Benedict on the ticket.
>>>
>>>
>>>
>>> I agree I absolutely had to document it better, a ticket for documentation was opened but it slipped from my mind with this emergency release this week. It is unfortunate it is still in our backlog after the ADOC migration.
>>>
>>>
>>>
>>> Note taken. I truly apologize and I am going to prioritize CASSANDRA-17135. Let me know if there is anything else I can/should do at this point.
>>>
>>>
>>>
>>> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com> wrote:
>>>
>>> (moved dev@ to BCC)
>>>
>>>
>>>
>>> It looks like the otc_coalescing_strategy config key is no longer supported in cassandra.yaml in 4.0.2, despite this not being mentioned anywhere in CHANGES.txt or NEWS.txt.
>>>
>>>
>>>
>>> James, you're right -- it was removed by CASSANDRA-17132 in 4.0.2 and 4.1.
>>>
>>>
>>>
>>> I agree that the CHANGES.txt entry should be clearer and we'll improve it plus add detailed info in NEWS.txt. I'll get this done soon in CASSANDRA-17135. Thanks for the feedback. Cheers!
>>>
>>>
>>>
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Dinesh Joshi <dj...@apache.org>.
+1 on introducing compile time checks to ensure backward compatibility.
Confusion due to usage of deprecated settings is understandable. However, settings marked deprecated should produce a warning in logs so that the operators become aware of their usage in the YAML and can migrate to the newer settings.
Also breakages do happen once in a while. As long as we fix them quickly and/or revert the code in the meanwhile it's fine.
> On Feb 12, 2022, at 3:56 AM, Ekaterina Dimitrova <e....@gmail.com> wrote:
>
> 15234 was a discussion about changing names and making parameters work with the old ones. Still working parameters, backward compatibility and not placeholders.
>
> Benedict, I can understand that when I said removal in this ticket you thought I will deprecate in Config but unfortunately it is not what I meant. I should have asked you also for review. I take the responsibility of doing a mistake here by removing in minor release thinking this is a bug that leads to dangerous confusion you can still use them. Indeed CHANGES.txt entry was created but not NEWS.txt and it requires a person to check which exact parameters were removed to take an action. I pushed a patch already to fix this. Docs are also on the way now when ADOC migration is over.
>
> One of the yaml parameters was actually also already removed with the rewrite of the messaging system in 4.0. I added back that one to Config too yesterday, to be on the safe side.
>
> “ I wonder if we should introduce a compile time check that validates config compatibility with prior versions, to avoid this in future”
>
> I think David is working on some tests to catch removed config in trunk, I will follow up on Monday with him.
>
> On Sat, 12 Feb 2022 at 5:49, benedict@apache.org <ma...@apache.org> <benedict@apache.org <ma...@apache.org>> wrote:
> As discussed on 15234, there is never a rush to remove Config parameters, and it should only be done when there’s some clear value. Since the overhead of having an unused parameter is ~zero, in my opinion this occurs only when we really need the operator to consider the semantic impact of its deprecation.
>
>
>
> We should never break minor upgrades, but we shouldn’t break any upgrade unnecessarily.
>
>
>
> I wonder if we should introduce a compile time check that validates config compatibility with prior versions, to avoid this in future.
>
>
>
> From: Dinesh Joshi <djoshi@apache.org <ma...@apache.org>>
> Date: Saturday, 12 February 2022 at 00:09
> To: dev@cassandra.apache.org <ma...@cassandra.apache.org> <dev@cassandra.apache.org <ma...@cassandra.apache.org>>
> Subject: Re: [RELEASE] Apache Cassandra 4.0.2 released
>
> We should also have deprecation guidance in Config.java. This will help when anybody is making changes in the future.
>
>
>
>
> On Feb 11, 2022, at 3:07 PM, Ekaterina Dimitrova <e.dimitrova@gmail.com <ma...@gmail.com>> wrote:
>
>
>
> Note taken, I had to document only in 4.0.x that those are placeholder. I just opened ticket to fix that - CASSANDRA-17377. I am going to submit a patch soon
>
>
>
> On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jjirsa@gmail.com <ma...@gmail.com>> wrote:
>
> We don't HAVE TO remove the Config.java entry - we can mark it as deprecated and ignored and remove it in a future version (and you could update Config.java to log a message about having a deprecated config option). It's a much better operator experience: log for a major version, then remove in the next.
>
>
>
> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e.dimitrova@gmail.com <ma...@gmail.com>> wrote:
>
> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to fix a bug that gives impression those work. Confirmed with Benedict on the ticket.
>
>
>
> I agree I absolutely had to document it better, a ticket for documentation was opened but it slipped from my mind with this emergency release this week. It is unfortunate it is still in our backlog after the ADOC migration.
>
>
>
> Note taken. I truly apologize and I am going to prioritize CASSANDRA-17135. Let me know if there is anything else I can/should do at this point.
>
>
>
> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <erick.ramirez@datastax.com <ma...@datastax.com>> wrote:
>
> (moved dev@ to BCC)
>
>
>
> It looks like the otc_coalescing_strategy config key is no longer supported in cassandra.yaml in 4.0.2, despite this not being mentioned anywhere in CHANGES.txt or NEWS.txt.
>
>
>
> James, you're right -- it was removed by CASSANDRA-17132 <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
>
>
>
> I agree that the CHANGES.txt entry should be clearer and we'll improve it plus add detailed info in NEWS.txt. I'll get this done soon in CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>. Thanks for the feedback. Cheers!
>
>
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Ekaterina Dimitrova <e....@gmail.com>.
15234 was a discussion about changing names and making parameters work
with the old ones. Still working parameters, backward compatibility and
not placeholders.
Benedict, I can understand that when I said removal in this ticket you
thought I will deprecate in Config but unfortunately it is not what I
meant. I should have asked you also for review. I take the responsibility
of doing a mistake here by removing in minor release thinking this is a bug
that leads to dangerous confusion you can still use them. Indeed
CHANGES.txt entry was created but not NEWS.txt and it requires a person to
check which exact parameters were removed to take an action. I pushed a
patch already to fix this. Docs are also on the way now when ADOC migration
is over.
One of the yaml parameters was actually also already removed with the
rewrite of the messaging system in 4.0. I added back that one to Config too
yesterday, to be on the safe side.
“ I wonder if we should introduce a compile time check that validates
config compatibility with prior versions, to avoid this in future”
I think David is working on some tests to catch removed config in trunk, I
will follow up on Monday with him.
On Sat, 12 Feb 2022 at 5:49, benedict@apache.org <be...@apache.org>
wrote:
> As discussed on 15234, there is never a rush to remove Config parameters,
> and it should only be done when there’s some clear value. Since the
> overhead of having an unused parameter is ~zero, in my opinion this occurs
> only when we really need the operator to consider the semantic impact of
> its deprecation.
>
>
>
> We should never break minor upgrades, but we shouldn’t break any upgrade
> unnecessarily.
>
>
>
> I wonder if we should introduce a compile time check that validates config
> compatibility with prior versions, to avoid this in future.
>
>
>
> *From: *Dinesh Joshi <dj...@apache.org>
> *Date: *Saturday, 12 February 2022 at 00:09
> *To: *dev@cassandra.apache.org <de...@cassandra.apache.org>
> *Subject: *Re: [RELEASE] Apache Cassandra 4.0.2 released
>
> We should also have deprecation guidance in Config.java. This will help
> when anybody is making changes in the future.
>
>
>
> On Feb 11, 2022, at 3:07 PM, Ekaterina Dimitrova <e....@gmail.com>
> wrote:
>
>
>
> Note taken, I had to document only in 4.0.x that those are placeholder. I
> just opened ticket to fix that - CASSANDRA-17377. I am going to submit a
> patch soon
>
>
>
> On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jj...@gmail.com> wrote:
>
> We don't HAVE TO remove the Config.java entry - we can mark it as
> deprecated and ignored and remove it in a future version (and you could
> update Config.java to log a message about having a deprecated config
> option). It's a much better operator experience: log for a major version,
> then remove in the next.
>
>
>
> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e....@gmail.com>
> wrote:
>
> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to
> fix a bug that gives impression those work. Confirmed with Benedict on the
> ticket.
>
>
>
> I agree I absolutely had to document it better, a ticket for documentation
> was opened but it slipped from my mind with this emergency release this
> week. It is unfortunate it is still in our backlog after the ADOC migration.
>
>
>
> Note taken. I truly apologize and I am going to prioritize
> CASSANDRA-17135. Let me know if there is anything else I can/should do at
> this point.
>
>
>
> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>
> wrote:
>
> (moved dev@ to BCC)
>
>
>
> It looks like the otc_coalescing_strategy config key is no longer
> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
> anywhere in CHANGES.txt or NEWS.txt.
>
>
>
> James, you're right -- it was removed by CASSANDRA-17132
> <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
>
>
>
> I agree that the CHANGES.txt entry should be clearer and we'll improve it
> plus add detailed info in NEWS.txt. I'll get this done soon in
> CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
> Thanks for the feedback. Cheers!
>
>
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by "benedict@apache.org" <be...@apache.org>.
As discussed on 15234, there is never a rush to remove Config parameters, and it should only be done when there’s some clear value. Since the overhead of having an unused parameter is ~zero, in my opinion this occurs only when we really need the operator to consider the semantic impact of its deprecation.
We should never break minor upgrades, but we shouldn’t break any upgrade unnecessarily.
I wonder if we should introduce a compile time check that validates config compatibility with prior versions, to avoid this in future.
From: Dinesh Joshi <dj...@apache.org>
Date: Saturday, 12 February 2022 at 00:09
To: dev@cassandra.apache.org <de...@cassandra.apache.org>
Subject: Re: [RELEASE] Apache Cassandra 4.0.2 released
We should also have deprecation guidance in Config.java. This will help when anybody is making changes in the future.
On Feb 11, 2022, at 3:07 PM, Ekaterina Dimitrova <e....@gmail.com>> wrote:
Note taken, I had to document only in 4.0.x that those are placeholder. I just opened ticket to fix that - CASSANDRA-17377. I am going to submit a patch soon
On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jj...@gmail.com>> wrote:
We don't HAVE TO remove the Config.java entry - we can mark it as deprecated and ignored and remove it in a future version (and you could update Config.java to log a message about having a deprecated config option). It's a much better operator experience: log for a major version, then remove in the next.
On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e....@gmail.com>> wrote:
This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to fix a bug that gives impression those work. Confirmed with Benedict on the ticket.
I agree I absolutely had to document it better, a ticket for documentation was opened but it slipped from my mind with this emergency release this week. It is unfortunate it is still in our backlog after the ADOC migration.
Note taken. I truly apologize and I am going to prioritize CASSANDRA-17135. Let me know if there is anything else I can/should do at this point.
On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>> wrote:
(moved dev@ to BCC)
It looks like the otc_coalescing_strategy config key is no longer supported in cassandra.yaml in 4.0.2, despite this not being mentioned anywhere in CHANGES.txt or NEWS.txt.
James, you're right -- it was removed by CASSANDRA-17132<https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
I agree that the CHANGES.txt entry should be clearer and we'll improve it plus add detailed info in NEWS.txt. I'll get this done soon in CASSANDRA-17135<https://issues.apache.org/jira/browse/CASSANDRA-17135>. Thanks for the feedback. Cheers!
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Ekaterina Dimitrova <e....@gmail.com>.
Patch submitted for review.
I will also add explicit point on deprecation to the config docs I am
writing now too.
On Fri, 11 Feb 2022 at 19:10, Dinesh Joshi <dj...@apache.org> wrote:
> We should also have deprecation guidance in Config.java. This will help
> when anybody is making changes in the future.
>
> On Feb 11, 2022, at 3:07 PM, Ekaterina Dimitrova <e....@gmail.com>
> wrote:
>
> Note taken, I had to document only in 4.0.x that those are placeholder. I
> just opened ticket to fix that - CASSANDRA-17377. I am going to submit a
> patch soon
>
> On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jj...@gmail.com> wrote:
>
>> We don't HAVE TO remove the Config.java entry - we can mark it as
>> deprecated and ignored and remove it in a future version (and you could
>> update Config.java to log a message about having a deprecated config
>> option). It's a much better operator experience: log for a major version,
>> then remove in the next.
>>
>> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <
>> e.dimitrova@gmail.com> wrote:
>>
>>> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it
>>> to fix a bug that gives impression those work. Confirmed with Benedict on
>>> the ticket.
>>>
>>> I agree I absolutely had to document it better, a ticket for
>>> documentation was opened but it slipped from my mind with this emergency
>>> release this week. It is unfortunate it is still in our backlog after the
>>> ADOC migration.
>>>
>>> Note taken. I truly apologize and I am going to prioritize
>>> CASSANDRA-17135. Let me know if there is anything else I can/should do at
>>> this point.
>>>
>>> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>
>>> wrote:
>>>
>>>> (moved dev@ to BCC)
>>>>
>>>>
>>>>> It looks like the otc_coalescing_strategy config key is no longer
>>>>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>>>>> anywhere in CHANGES.txt or NEWS.txt.
>>>>>
>>>>
>>>> James, you're right -- it was removed by CASSANDRA-17132
>>>> <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and
>>>> 4.1.
>>>>
>>>> I agree that the CHANGES.txt entry should be clearer and we'll improve
>>>> it plus add detailed info in NEWS.txt. I'll get this done soon in
>>>> CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
>>>> Thanks for the feedback. Cheers!
>>>>
>>>
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Dinesh Joshi <dj...@apache.org>.
We should also have deprecation guidance in Config.java. This will help when anybody is making changes in the future.
> On Feb 11, 2022, at 3:07 PM, Ekaterina Dimitrova <e....@gmail.com> wrote:
>
> Note taken, I had to document only in 4.0.x that those are placeholder. I just opened ticket to fix that - CASSANDRA-17377. I am going to submit a patch soon
>
> On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jjirsa@gmail.com <ma...@gmail.com>> wrote:
> We don't HAVE TO remove the Config.java entry - we can mark it as deprecated and ignored and remove it in a future version (and you could update Config.java to log a message about having a deprecated config option). It's a much better operator experience: log for a major version, then remove in the next.
>
> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e.dimitrova@gmail.com <ma...@gmail.com>> wrote:
> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to fix a bug that gives impression those work. Confirmed with Benedict on the ticket.
>
> I agree I absolutely had to document it better, a ticket for documentation was opened but it slipped from my mind with this emergency release this week. It is unfortunate it is still in our backlog after the ADOC migration.
>
> Note taken. I truly apologize and I am going to prioritize CASSANDRA-17135. Let me know if there is anything else I can/should do at this point.
>
> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <erick.ramirez@datastax.com <ma...@datastax.com>> wrote:
> (moved dev@ to BCC)
>
> It looks like the otc_coalescing_strategy config key is no longer supported in cassandra.yaml in 4.0.2, despite this not being mentioned anywhere in CHANGES.txt or NEWS.txt.
>
> James, you're right -- it was removed by CASSANDRA-17132 <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
>
> I agree that the CHANGES.txt entry should be clearer and we'll improve it plus add detailed info in NEWS.txt. I'll get this done soon in CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>. Thanks for the feedback. Cheers!
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Ekaterina Dimitrova <e....@gmail.com>.
Note taken, I had to document only in 4.0.x that those are placeholder. I
just opened ticket to fix that - CASSANDRA-17377. I am going to submit a
patch soon
On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jj...@gmail.com> wrote:
> We don't HAVE TO remove the Config.java entry - we can mark it as
> deprecated and ignored and remove it in a future version (and you could
> update Config.java to log a message about having a deprecated config
> option). It's a much better operator experience: log for a major version,
> then remove in the next.
>
> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e....@gmail.com>
> wrote:
>
>> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it
>> to fix a bug that gives impression those work. Confirmed with Benedict on
>> the ticket.
>>
>> I agree I absolutely had to document it better, a ticket for
>> documentation was opened but it slipped from my mind with this emergency
>> release this week. It is unfortunate it is still in our backlog after the
>> ADOC migration.
>>
>> Note taken. I truly apologize and I am going to prioritize
>> CASSANDRA-17135. Let me know if there is anything else I can/should do at
>> this point.
>>
>> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>
>> wrote:
>>
>>> (moved dev@ to BCC)
>>>
>>>
>>>> It looks like the otc_coalescing_strategy config key is no longer
>>>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>>>> anywhere in CHANGES.txt or NEWS.txt.
>>>>
>>>
>>> James, you're right -- it was removed by CASSANDRA-17132
>>> <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and
>>> 4.1.
>>>
>>> I agree that the CHANGES.txt entry should be clearer and we'll improve
>>> it plus add detailed info in NEWS.txt. I'll get this done soon in
>>> CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
>>> Thanks for the feedback. Cheers!
>>>
>>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Brandon Williams <dr...@gmail.com>.
Agreed, I've opened CASSANDRA-17376 to handle this.
On Fri, Feb 11, 2022 at 4:44 PM Jeff Jirsa <jj...@gmail.com> wrote:
>
> We don't HAVE TO remove the Config.java entry - we can mark it as deprecated and ignored and remove it in a future version (and you could update Config.java to log a message about having a deprecated config option). It's a much better operator experience: log for a major version, then remove in the next.
>
> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e....@gmail.com> wrote:
>>
>> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to fix a bug that gives impression those work. Confirmed with Benedict on the ticket.
>>
>> I agree I absolutely had to document it better, a ticket for documentation was opened but it slipped from my mind with this emergency release this week. It is unfortunate it is still in our backlog after the ADOC migration.
>>
>> Note taken. I truly apologize and I am going to prioritize CASSANDRA-17135. Let me know if there is anything else I can/should do at this point.
>>
>> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com> wrote:
>>>
>>> (moved dev@ to BCC)
>>>
>>>>
>>>> It looks like the otc_coalescing_strategy config key is no longer supported in cassandra.yaml in 4.0.2, despite this not being mentioned anywhere in CHANGES.txt or NEWS.txt.
>>>
>>>
>>> James, you're right -- it was removed by CASSANDRA-17132 in 4.0.2 and 4.1.
>>>
>>> I agree that the CHANGES.txt entry should be clearer and we'll improve it plus add detailed info in NEWS.txt. I'll get this done soon in CASSANDRA-17135. Thanks for the feedback. Cheers!
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Ekaterina Dimitrova <e....@gmail.com>.
Note taken, I had to document only in 4.0.x that those are placeholder. I
just opened ticket to fix that - CASSANDRA-17377. I am going to submit a
patch soon
On Fri, 11 Feb 2022 at 17:44, Jeff Jirsa <jj...@gmail.com> wrote:
> We don't HAVE TO remove the Config.java entry - we can mark it as
> deprecated and ignored and remove it in a future version (and you could
> update Config.java to log a message about having a deprecated config
> option). It's a much better operator experience: log for a major version,
> then remove in the next.
>
> On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e....@gmail.com>
> wrote:
>
>> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it
>> to fix a bug that gives impression those work. Confirmed with Benedict on
>> the ticket.
>>
>> I agree I absolutely had to document it better, a ticket for
>> documentation was opened but it slipped from my mind with this emergency
>> release this week. It is unfortunate it is still in our backlog after the
>> ADOC migration.
>>
>> Note taken. I truly apologize and I am going to prioritize
>> CASSANDRA-17135. Let me know if there is anything else I can/should do at
>> this point.
>>
>> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>
>> wrote:
>>
>>> (moved dev@ to BCC)
>>>
>>>
>>>> It looks like the otc_coalescing_strategy config key is no longer
>>>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>>>> anywhere in CHANGES.txt or NEWS.txt.
>>>>
>>>
>>> James, you're right -- it was removed by CASSANDRA-17132
>>> <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and
>>> 4.1.
>>>
>>> I agree that the CHANGES.txt entry should be clearer and we'll improve
>>> it plus add detailed info in NEWS.txt. I'll get this done soon in
>>> CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
>>> Thanks for the feedback. Cheers!
>>>
>>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Jeff Jirsa <jj...@gmail.com>.
We don't HAVE TO remove the Config.java entry - we can mark it as
deprecated and ignored and remove it in a future version (and you could
update Config.java to log a message about having a deprecated config
option). It's a much better operator experience: log for a major version,
then remove in the next.
On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e....@gmail.com>
wrote:
> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to
> fix a bug that gives impression those work. Confirmed with Benedict on the
> ticket.
>
> I agree I absolutely had to document it better, a ticket for documentation
> was opened but it slipped from my mind with this emergency release this
> week. It is unfortunate it is still in our backlog after the ADOC migration.
>
> Note taken. I truly apologize and I am going to prioritize
> CASSANDRA-17135. Let me know if there is anything else I can/should do at
> this point.
>
> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>
> wrote:
>
>> (moved dev@ to BCC)
>>
>>
>>> It looks like the otc_coalescing_strategy config key is no longer
>>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>>> anywhere in CHANGES.txt or NEWS.txt.
>>>
>>
>> James, you're right -- it was removed by CASSANDRA-17132
>> <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
>>
>> I agree that the CHANGES.txt entry should be clearer and we'll improve it
>> plus add detailed info in NEWS.txt. I'll get this done soon in
>> CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
>> Thanks for the feedback. Cheers!
>>
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Jeff Jirsa <jj...@gmail.com>.
We don't HAVE TO remove the Config.java entry - we can mark it as
deprecated and ignored and remove it in a future version (and you could
update Config.java to log a message about having a deprecated config
option). It's a much better operator experience: log for a major version,
then remove in the next.
On Fri, Feb 11, 2022 at 2:41 PM Ekaterina Dimitrova <e....@gmail.com>
wrote:
> This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to
> fix a bug that gives impression those work. Confirmed with Benedict on the
> ticket.
>
> I agree I absolutely had to document it better, a ticket for documentation
> was opened but it slipped from my mind with this emergency release this
> week. It is unfortunate it is still in our backlog after the ADOC migration.
>
> Note taken. I truly apologize and I am going to prioritize
> CASSANDRA-17135. Let me know if there is anything else I can/should do at
> this point.
>
> On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>
> wrote:
>
>> (moved dev@ to BCC)
>>
>>
>>> It looks like the otc_coalescing_strategy config key is no longer
>>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>>> anywhere in CHANGES.txt or NEWS.txt.
>>>
>>
>> James, you're right -- it was removed by CASSANDRA-17132
>> <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
>>
>> I agree that the CHANGES.txt entry should be clearer and we'll improve it
>> plus add detailed info in NEWS.txt. I'll get this done soon in
>> CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
>> Thanks for the feedback. Cheers!
>>
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Ekaterina Dimitrova <e....@gmail.com>.
This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to
fix a bug that gives impression those work. Confirmed with Benedict on the
ticket.
I agree I absolutely had to document it better, a ticket for documentation
was opened but it slipped from my mind with this emergency release this
week. It is unfortunate it is still in our backlog after the ADOC migration.
Note taken. I truly apologize and I am going to prioritize CASSANDRA-17135.
Let me know if there is anything else I can/should do at this point.
On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>
wrote:
> (moved dev@ to BCC)
>
>
>> It looks like the otc_coalescing_strategy config key is no longer
>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>> anywhere in CHANGES.txt or NEWS.txt.
>>
>
> James, you're right -- it was removed by CASSANDRA-17132
> <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
>
> I agree that the CHANGES.txt entry should be clearer and we'll improve it
> plus add detailed info in NEWS.txt. I'll get this done soon in
> CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
> Thanks for the feedback. Cheers!
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Ekaterina Dimitrova <e....@gmail.com>.
This had to be removed in 4.0 but it wasn’t. The patch mentioned did it to
fix a bug that gives impression those work. Confirmed with Benedict on the
ticket.
I agree I absolutely had to document it better, a ticket for documentation
was opened but it slipped from my mind with this emergency release this
week. It is unfortunate it is still in our backlog after the ADOC migration.
Note taken. I truly apologize and I am going to prioritize CASSANDRA-17135.
Let me know if there is anything else I can/should do at this point.
On Fri, 11 Feb 2022 at 17:26, Erick Ramirez <er...@datastax.com>
wrote:
> (moved dev@ to BCC)
>
>
>> It looks like the otc_coalescing_strategy config key is no longer
>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>> anywhere in CHANGES.txt or NEWS.txt.
>>
>
> James, you're right -- it was removed by CASSANDRA-17132
> <https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
>
> I agree that the CHANGES.txt entry should be clearer and we'll improve it
> plus add detailed info in NEWS.txt. I'll get this done soon in
> CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
> Thanks for the feedback. Cheers!
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Erick Ramirez <er...@datastax.com>.
(moved dev@ to BCC)
> It looks like the otc_coalescing_strategy config key is no longer
> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
> anywhere in CHANGES.txt or NEWS.txt.
>
James, you're right -- it was removed by CASSANDRA-17132
<https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
I agree that the CHANGES.txt entry should be clearer and we'll improve it
plus add detailed info in NEWS.txt. I'll get this done soon in
CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
Thanks for the feedback. Cheers!
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Jeff Jirsa <jj...@gmail.com>.
Accidentally dropped dev@, so adding back in the dev list, with the hopes
that someone on the dev list helps address this.
On Fri, Feb 11, 2022 at 2:22 PM Jeff Jirsa <jj...@gmail.com> wrote:
> That looks like https://issues.apache.org/jira/browse/CASSANDRA-17132 +
> https://github.com/apache/cassandra/commit/b6f61e850c8cfb1f0763e0f15721cde8893814b5
>
> I suspect this needs to be reverted, at least in 4.0.x, and it definitely
> deserved a NEWS.txt entry (and ideally some period of deprecation/warning).
>
>
>
> On Fri, Feb 11, 2022 at 2:09 PM James Brown <jb...@easypost.com> wrote:
>
>> It looks like the otc_coalescing_strategy config key is no longer
>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>> anywhere in CHANGES.txt or NEWS.txt.
>>
>> Attempting to upgrade a test cluster from 4.0.1 to 4.0.2 failed with *"Invalid
>> yaml. Please remove properties [otc_coalescing_strategy] from your
>> cassandra.yaml*"
>>
>> Is this change intentional?
>>
>> On Fri, Feb 11, 2022 at 1:40 AM Mick Semb Wever <mc...@apache.org> wrote:
>>
>>> The Cassandra team is pleased to announce the release of Apache
>>> Cassandra version 4.0.2.
>>>
>>> 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 and binary distributions are listed in our download
>>> section:
>>>
>>> http://cassandra.apache.org/download/
>>>
>>> This version is a bug fix release[1] on the 4.0 series. As always,
>>> please pay attention to the release notes[2] and Let us know[3] if you
>>> were to encounter any problem.
>>>
>>> Enjoy!
>>>
>>> [1]: CHANGES.txt
>>>
>>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.2
>>> [2]: NEWS.txt
>>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.2
>>> [3]: https://issues.apache.org/jira/browse/CASSANDRA
>>>
>>
>>
>> --
>> James Brown
>> Engineer
>>
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Jeff Jirsa <jj...@gmail.com>.
Accidentally dropped dev@, so adding back in the dev list, with the hopes
that someone on the dev list helps address this.
On Fri, Feb 11, 2022 at 2:22 PM Jeff Jirsa <jj...@gmail.com> wrote:
> That looks like https://issues.apache.org/jira/browse/CASSANDRA-17132 +
> https://github.com/apache/cassandra/commit/b6f61e850c8cfb1f0763e0f15721cde8893814b5
>
> I suspect this needs to be reverted, at least in 4.0.x, and it definitely
> deserved a NEWS.txt entry (and ideally some period of deprecation/warning).
>
>
>
> On Fri, Feb 11, 2022 at 2:09 PM James Brown <jb...@easypost.com> wrote:
>
>> It looks like the otc_coalescing_strategy config key is no longer
>> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
>> anywhere in CHANGES.txt or NEWS.txt.
>>
>> Attempting to upgrade a test cluster from 4.0.1 to 4.0.2 failed with *"Invalid
>> yaml. Please remove properties [otc_coalescing_strategy] from your
>> cassandra.yaml*"
>>
>> Is this change intentional?
>>
>> On Fri, Feb 11, 2022 at 1:40 AM Mick Semb Wever <mc...@apache.org> wrote:
>>
>>> The Cassandra team is pleased to announce the release of Apache
>>> Cassandra version 4.0.2.
>>>
>>> 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 and binary distributions are listed in our download
>>> section:
>>>
>>> http://cassandra.apache.org/download/
>>>
>>> This version is a bug fix release[1] on the 4.0 series. As always,
>>> please pay attention to the release notes[2] and Let us know[3] if you
>>> were to encounter any problem.
>>>
>>> Enjoy!
>>>
>>> [1]: CHANGES.txt
>>>
>>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.2
>>> [2]: NEWS.txt
>>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.2
>>> [3]: https://issues.apache.org/jira/browse/CASSANDRA
>>>
>>
>>
>> --
>> James Brown
>> Engineer
>>
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Jeff Jirsa <jj...@gmail.com>.
That looks like https://issues.apache.org/jira/browse/CASSANDRA-17132 +
https://github.com/apache/cassandra/commit/b6f61e850c8cfb1f0763e0f15721cde8893814b5
I suspect this needs to be reverted, at least in 4.0.x, and it definitely
deserved a NEWS.txt entry (and ideally some period of deprecation/warning).
On Fri, Feb 11, 2022 at 2:09 PM James Brown <jb...@easypost.com> wrote:
> It looks like the otc_coalescing_strategy config key is no longer
> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
> anywhere in CHANGES.txt or NEWS.txt.
>
> Attempting to upgrade a test cluster from 4.0.1 to 4.0.2 failed with *"Invalid
> yaml. Please remove properties [otc_coalescing_strategy] from your
> cassandra.yaml*"
>
> Is this change intentional?
>
> On Fri, Feb 11, 2022 at 1:40 AM Mick Semb Wever <mc...@apache.org> wrote:
>
>> The Cassandra team is pleased to announce the release of Apache
>> Cassandra version 4.0.2.
>>
>> 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 and binary distributions are listed in our download
>> section:
>>
>> http://cassandra.apache.org/download/
>>
>> This version is a bug fix release[1] on the 4.0 series. As always,
>> please pay attention to the release notes[2] and Let us know[3] if you
>> were to encounter any problem.
>>
>> Enjoy!
>>
>> [1]: CHANGES.txt
>>
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.2
>> [2]: NEWS.txt
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.2
>> [3]: https://issues.apache.org/jira/browse/CASSANDRA
>>
>
>
> --
> James Brown
> Engineer
>
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by Erick Ramirez <er...@datastax.com>.
(moved dev@ to BCC)
> It looks like the otc_coalescing_strategy config key is no longer
> supported in cassandra.yaml in 4.0.2, despite this not being mentioned
> anywhere in CHANGES.txt or NEWS.txt.
>
James, you're right -- it was removed by CASSANDRA-17132
<https://issues.apache.org/jira/browse/CASSANDRA-17132> in 4.0.2 and 4.1.
I agree that the CHANGES.txt entry should be clearer and we'll improve it
plus add detailed info in NEWS.txt. I'll get this done soon in
CASSANDRA-17135 <https://issues.apache.org/jira/browse/CASSANDRA-17135>.
Thanks for the feedback. Cheers!
Re: [RELEASE] Apache Cassandra 4.0.2 released
Posted by James Brown <jb...@easypost.com>.
It looks like the otc_coalescing_strategy config key is no longer supported
in cassandra.yaml in 4.0.2, despite this not being mentioned anywhere in
CHANGES.txt or NEWS.txt.
Attempting to upgrade a test cluster from 4.0.1 to 4.0.2 failed with *"Invalid
yaml. Please remove properties [otc_coalescing_strategy] from your
cassandra.yaml*"
Is this change intentional?
On Fri, Feb 11, 2022 at 1:40 AM Mick Semb Wever <mc...@apache.org> wrote:
> The Cassandra team is pleased to announce the release of Apache
> Cassandra version 4.0.2.
>
> 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 and binary distributions are listed in our download
> section:
>
> http://cassandra.apache.org/download/
>
> This version is a bug fix release[1] on the 4.0 series. As always,
> please pay attention to the release notes[2] and Let us know[3] if you
> were to encounter any problem.
>
> Enjoy!
>
> [1]: CHANGES.txt
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/cassandra-4.0.2
> [2]: NEWS.txt
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-4.0.2
> [3]: https://issues.apache.org/jira/browse/CASSANDRA
>
--
James Brown
Engineer