On Jul 26, 2024, at 11:09 AM, Yifan Cai wrote:Thanks Jeff for restating the policy.According to the release lifecycle docMissing features from newer generation releases are back-ported on per - PMC vote basis.https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle We do not have a
Hi Jeremiah,
It is an interesting idea. As of now, I think it is too much of a risk (or
not feasible at all) to only use 5.0/trunk Cassandra-all dependency in
Cassandra Analytics, since it depends on other components in Cassandra.
- Yifan
I thought the server now has the ability to write out old sstable versions? So you could use the CQLSSTableWriter from 5.0/trunk to write out sstables 4.0 can read?On Jul 26, 2024, at 1:07 PM, Yifan Cai wrote:
Caution: The sender name (Yifan Cai) is different from their email addr
Thanks Jeff for restating the policy.
According to the release lifecycle doc
>
>- Missing features from newer generation releases are back-ported on
>per - PMC vote basis.
>
> https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle
We do not have a policy to prevent new f
Everyone has a low risk change they want to backport to every branch, 4.0 and
4.1 in particular are way past the point we should be adding features
The policy exists and it’s a pure feature not a regression
> On Jul 26, 2024, at 9:59 AM, Brandon Williams wrote:
>
> Given how low risk thi
+1 to should block as well.
On Fri, Jul 26, 2024, at 12:15 PM, Patrick McFadin wrote:
> This is a weird regression but I'm borderline on this being a blocker. On a
> brand new node starting, this comes up but goes away on the first reboot of
> the node. What I don't get is why directIO is disabl
Given how low risk this is, I don't see an issue with backporting it
and I'm sure the usefulness outweighs what risk there is. +1 (5.0.1
though, not 5.0.0)
Kind Regards,
Brandon
On Fri, Jul 26, 2024 at 11:52 AM Yifan Cai wrote:
>
> Hi everyone,
>
> CASSANDRA-19800 is currently in the state of re
Hi everyone,
CASSANDRA-19800 is currently in the state of ready to be committed. Before
that, I want to propose backporting it to 4.0, 4.1 and 5.0.
The ability to notify CQLSSTableWriter user when new sstables are produced
is especially useful for Cassandra Analytics and other consumers. The API
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
This is a weird regression but I'm borderline on this being a blocker. On a
brand new node starting, this comes up but goes away on the first reboot of
the node. What I don't get is why directIO is disabled if there is no
commit log. What's specific about that?
Patrick
On Fri, Jul 26, 2024 at 7:4
+1 Should block
> On Jul 26, 2024, at 8:25 AM, Štefan Miklošovič wrote:
>
>
> I am formally asking for acknowledging (1) to be a blocker for 5.0-rc. I
> think it was introduced in (2) and it behaves like this (3).
>
> Regards
>
> (1) https://issues.apache.org/jira/browse/CASSANDRA-19779
>
I am formally asking for acknowledging (1) to be a blocker for 5.0-rc. I
think it was introduced in (2) and it behaves like this (3).
Regards
(1) https://issues.apache.org/jira/browse/CASSANDRA-19779
(2)
https://issues.apache.org/jira/browse/CASSANDRA-18464?focusedCommentId=17868946&page=com.atl
A release is always coming ;) I'll try to get the 4.1.6 ball rolling on Monday.
Kind Regards,
Brandon
On Wed, Jul 24, 2024 at 3:56 PM Elliott Sims via dev
wrote:
>
> Looks like this is out and there's a 5.0-rc release. Is a 4.1.6 release with
> a fix for CASSANDRA-19668 coming?
>
> On Sat, Ju
13 matches
Mail list logo
