+1
On Mon, Apr 7, 2025 at 7:35 AM Brandon Williams
wrote:
>
> Proposing the test build of Cassandra 5.0.4 for release.
>
> sha1: b81163b04b1d99036730ff233595d7bfb88611d1
> Git: https://github.com/apache/cassandra/tree/5.0.4-tentative
> Maven Artifacts:
> https://repository.apache.org/content/repo
Currently we don't have Qbot notifying us on CASSSIDECAR ticket creation and
state change. Seems we could:
1. notify in #cassandra-dev and #cassandra-sidecar
2. notify in the #cassandra-sidecar channel
My preference is for 1 since there's a tight relationship between what we're
doing with the s
I'm +1 on "mimic current CASSANDRA tickets" as Ekaterina describes.
Kind Regards,
Brandon
On Tue, Apr 8, 2025 at 2:51 PM Ekaterina Dimitrova
wrote:
>
> I’d say we mimic the current CASSANDRA tickets handling plus adding to the
> #cassandra-sidecar. That means:
>
> 1) Open and close notification
+1 Important we get a release out that resolves CASSANDRA-20449: Serialization can lose
complex deletions in a mutation with multiple collections in a row On Apr 8, 2025, at 4:07
AM, Brandon Williams wrote: +1 On Mon, Apr 7, 2025 at
7:35 AM Brandon Williams wrote: Proposing the test build
of
FWIW, my personal experience is that mixing automated notifications
(beyond a very low volume) with human communications adds a bunch of
noise to the human conversations and increases the risk of an
interesting automated notification being missed (scrolling past them to
get to the meatier human
Patrick and Jeff,
I have to chime in with an opinion having been a SQL person for more than
30 years...
The DISTINCT concept is a little confusing to me, since, in SQL, DISTINCT
reduces a repeating result set to a unique result set (where all of the
selected values are repeating), rather than jus
+1 from me for that proposal.
On Apr 8, 2025 at 2:51:09 PM, Ekaterina Dimitrova
wrote:
> I’d say we mimic the current CASSANDRA tickets handling plus adding to the
> #cassandra-sidecar. That means:
>
> 1) Open and close notifications to #cassandra-dev and #cassandra-sidecar
> 2) all other notif
+1. Just one clarification, we already have CASSSIDECAR notifications going to
#cassandra-dev [1]. But I think we should also have them in #cassandra-sidecar
Best,
- Francisco
[1] https://issues.apache.org/jira/browse/INFRA-26216
On 2025/04/08 20:05:35 Jeremiah Jordan wrote:
> +1 from me for t
Yep - this is classic "Ready, Fire, Aim" from me.
But we did hit a new target (adding things to #cassandra-sidecar), so that's a
plus. :D
On Tue, Apr 8, 2025, at 4:12 PM, Francisco Guerrero wrote:
> +1. Just one clarification, we already have CASSSIDECAR notifications going
> to #cassandra-dev
