Hi all,
thanks for your answers!.
To Benedict's point: In terms of the uvint enconding of deletionTime
i.e. it is true it happens here
https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/SerializationHeader.java#L170.
But we also have a DeletionTime serializer
+1 to waiver
On 15/11/22 2:07, Josh McKenzie wrote:
+1 to waiver.
We still don't have some kind of @flaky annotation that sequesters
tests do we? :)
On Mon, Nov 14, 2022, at 5:58 PM, Ekaterina Dimitrova wrote:
+1
On Mon, 14 Nov 2022 at 17:55, Brandon Williams wrote:
+1 to waiving
Hi,
I am running Cassandra 3.0.27 in my production. In some corner case
scenarios, we have tombstones disappearing during bootstrap/decommission.
I've outlined a possible theory with the root cause in this ticket:
https://issues.apache.org/jira/browse/CASSANDRA-17991
Could someone please help
+1 to waiver.
We still don't have some kind of @flaky annotation that sequesters tests do we?
:)
On Mon, Nov 14, 2022, at 5:58 PM, Ekaterina Dimitrova wrote:
> +1
>
> On Mon, 14 Nov 2022 at 17:55, Brandon Williams wrote:
>> +1 to waiving these.
>>
>> On Mon, Nov 14, 2022, 4:49 PM Miklosovic,
+1
On Mon, 14 Nov 2022 at 17:55, Brandon Williams wrote:
> +1 to waiving these.
>
> On Mon, Nov 14, 2022, 4:49 PM Miklosovic, Stefan <
> stefan.mikloso...@netapp.com> wrote:
>
>> Tickets for the flaky tests are here
>>
>> https://issues.apache.org/jira/browse/CASSANDRA-18047
>>
+1 to waiving these.
On Mon, Nov 14, 2022, 4:49 PM Miklosovic, Stefan <
stefan.mikloso...@netapp.com> wrote:
> Tickets for the flaky tests are here
>
> https://issues.apache.org/jira/browse/CASSANDRA-18047
> https://issues.apache.org/jira/browse/CASSANDRA-18048
>
>
Tickets for the flaky tests are here
https://issues.apache.org/jira/browse/CASSANDRA-18047
https://issues.apache.org/jira/browse/CASSANDRA-18048
From: Mick Semb Wever
Sent: Monday, November 14, 2022 23:28
To: dev@cassandra.apache.org
Subject: Re: Some
> in CASSANDRA-18029, two flaky tests were committed by mistake due to my
> misunderstanding. We agreed on this thread that we should not commit flaky
> tests right before rc. So now the rc is technically blocked by them. To
> unblock it, what is needed is to have a waiver on them. If there is not
Hi list,
in CASSANDRA-18029, two flaky tests were committed by mistake due to my
misunderstanding. We agreed on this thread that we should not commit flaky
tests right before rc. So now the rc is technically blocked by them. To unblock
it, what is needed is to have a waiver on them. If there
I like this suggestion and I'd take it a step further. I think the project
should be publishing docker images. If we manage to migrate to Gradle this
would be pretty trivial as the jib Gradle plugin is excellent and makes
creating and publishing Docker images really easy.
> in 2035 we'd hit the same problem again.
In terms of "kicking a can down the road", this would be a pretty vigorous
kick. I wouldn't push back against this deferral. :)
On Mon, Nov 14, 2022, at 9:28 AM, Benedict wrote:
>
> I’m confused why we see *any* increase in sstable size - TTLs and
I’m confused why we see *any* increase in sstable size - TTLs and deletion
times are already written as unsigned vints as offsets from an sstable epoch
for each value.
I would dig in more carefully to explore why you’re seeing this increase? For
the same data there should be no change to size
12 matches
Mail list logo
