With five +1 (four binding) and no -1, the vote passes. I'll work on
getting the release published.
On Wed, Aug 14, 2024 at 11:54 AM Brandon Williams
wrote:
>
> Proposing the test build of Cassandra 4.1.6 for release.
>
> sha1: 790de1079811278a2b431c2ced7c7ea02d290a25
> Git: https://github.com/a
.
> The vote will be open for 72 hours (longer if needed). Everyone who
> has tested the build is invited to vote. Votes by PMC members are
> considered binding. A vote passes if there are at least three binding
> +1s and no -1's.
>
+1
Checked
- signing correct
- checksums are correct
- so
+1
On Wed, Aug 14, 2024 at 11:54 AM Brandon Williams
wrote:
>
> Proposing the test build of Cassandra 4.1.6 for release.
>
> sha1: 790de1079811278a2b431c2ced7c7ea02d290a25
> Git: https://github.com/apache/cassandra/tree/4.1.6-tentative
> Maven Artifacts:
> https://repository.apache.org/content/re
gt;
> *Reply-To*: dev@cassandra.apache.org
> *To*: dev@cassandra.apache.org
> *Subject*: Re: [VOTE] Release Apache Cassandra 4.1.6 - take 2
> *Date*: Wed, 14 Aug 2024 11:07:54 -0700
>
> +1
>
> On Wed, Aug 14, 2024 at 9:55 AM Brandon Williams <
> brandonwilli...@apache.org>
+1 (nb)
-Original Message-
From: Jon Haddad
mailto:jon%20haddad%20%3c...@jonhaddad.com%3e>>
Reply-To: dev@cassandra.apache.org<mailto:dev@cassandra.apache.org>
To: dev@cassandra.apache.org<mailto:dev@cassandra.apache.org>
Subject: Re: [VOTE] Release Apache Cassandra 4
+1
On Wed, Aug 14, 2024 at 9:55 AM Brandon Williams
wrote:
> Proposing the test build of Cassandra 4.1.6 for release.
>
> sha1: 790de1079811278a2b431c2ced7c7ea02d290a25
> Git: https://github.com/apache/cassandra/tree/4.1.6-tentative
> Maven Artifacts:
>
> https://repository.apache.org/content/re
Proposing the test build of Cassandra 4.1.6 for release.
sha1: 790de1079811278a2b431c2ced7c7ea02d290a25
Git: https://github.com/apache/cassandra/tree/4.1.6-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1340/org/apache/cassandra/cassandra-all/4.1.6
gt; > and prioritize requests. I would say that the QueryHandler interface
>> > together with the custom payload feature in the native protocol is a
>> > powerful combination and I would not be surprised if this is used more
>> > then you might expect.
>> >
>> > -O
ure in the native protocol
> is a powerful combination and I would not be surprised if this is used more
> then you might expect.
> >
> > -Original Message-
> > From: J. D. Jordan
> > Reply-To: dev@cassandra.apache.org
> > To: dev@cassandra.apache.org
&g
--
> From: J. D. Jordan
> Reply-To: dev@cassandra.apache.org
> To: dev@cassandra.apache.org
> Subject: Re: [VOTE] Release Apache Cassandra 4.1.6
> Date: Thu, 01 Aug 2024 08:26:42 -0500
>
> @Tommy do you think? You brought the issue up, I am assuming because you
> found
ailto:%22j.%20d.%20jordan%22%20%3cjeremiah.jor...@gmail.com%3e>>
Reply-To: dev@cassandra.apache.org<mailto:dev@cassandra.apache.org>
To: dev@cassandra.apache.org<mailto:dev@cassandra.apache.org>
Subject: Re: [VOTE] Release Apache Cassandra 4.1.6
Date: Thu, 01 Aug 2024 08:26:42 -0500
@Tom
@Tommy do you think? You brought the issue up, I am assuming because you found the issue while trying to test ecaudit against the proposed release and it broke the integration? As an active consumer of the interface what are your thoughts?On Aug 1, 2024, at 8:17 AM, Alex Petrov wrote:> If we hav
> library. There is no official way to plug in a QueryHandler, so I did
>>>>>>>> not consider it to be a part of our public API.
>>>>>>>>
>>>>>>>> From [1]:
>>>>>>>>
>>>>>>>
hanges such changes between 4.1.5 and 4.1.6? CASSANDRA-19534 looks like a very good change so maybe there is an exception in this case?
/Tommy -Original Message- From : Brandon Williams < brandonwilli...@apache.org > Reply-To : dev@cassandra.apache.org To : dev < dev@cassandra.apach
t; Hi,
>
> There is a change in the QueryHandler interface introduced by
> https://issues.apache.org/jira/browse/CASSANDRA-19534
>
> Do we allow changes such changes between 4.1.5 and 4.1.6?
> CASSANDRA-19534 looks like a very good change so maybe there is an
> exception in thi
lso which classes/interfaces
>>>>> specifically should be evolved with care.
>>>>>
>>>>> Thank you,
>>>>> --Alex
>>>>>
>>>>> [1] https://cassandra.apache.org/_/development/index.html
>>>>>
&g
interface introduced by
>> https://issues.apache.org/jira/browse/CASSANDRA-19534
>>
>> Do we allow changes such changes between 4.1.5 and 4.1.6?
>> CASSANDRA-19534 looks like a very good change so maybe there is an
>> exception in this case?
>>
>> /Tommy
&g
.org/_/development/index.html
>>
>> On Tue, Jul 30, 2024, at 10:56 AM, Tommy Stendahl via dev wrote:
>>
>> Hi,
>>
>> There is a change in the QueryHandler interface introduced by
>> https://issues.apache.org/jira/browse/CASSANDRA-19534
>>
>
n the QueryHandler interface introduced by
>>>> https://issues.apache.org/jira/browse/CASSANDRA-19534
>>>>
>>>> Do we allow changes such changes between 4.1.5 and 4.1.6?
>>>> CASSANDRA-19534 looks like a very good change so maybe there is an
>>>&g
Stendahl via dev wrote:
>>>>> Hi,
>>>>>
>>>>> There is a change in the QueryHandler interface introduced by
>>>>> https://issues.apache.org/jira/browse/CASSANDRA-19534
>>>>>
>>>>> Do we allow changes
;
>> Hi,
>>
>> There is a change in the QueryHandler interface introduced by
>> https://issues.apache.org/jira/browse/CASSANDRA-19534
>>
>> Do we allow changes such changes between 4.1.5 and 4.1.6?
>> CASSANDRA-19534 looks like a ve
I know of a few custom tracing implementations that implement a custom query handler to work. No clue how maintained they still are.The elassandra project uses the custom query handler.DataStax uses the customer query handler for DSE (we maintain our own forks now, so can work around what ever hap
4.1.6?
> CASSANDRA-19534 looks like a very good change so maybe there is an
> exception in this case?
>
> /Tommy
>
> -Original Message-
> *From*: Brandon Williams >
> *Reply-To*: dev@cassandra.apache.org
> *To*: dev
> >
> *Subject*: [VOTE] Rele
ge in the QueryHandler interface introduced by
>>> https://issues.apache.org/jira/browse/CASSANDRA-19534
>>>
>>> Do we allow changes such changes between 4.1.5 and 4.1.6?
>>> CASSANDRA-19534 looks like a very good change so maybe there is an
>>> exception in
Given we allow a pluggable query handler implementation to be specified for the server with a -D during startup. So I would consider the query handler one of our public interfaces.On Jul 30, 2024, at 9:35 AM, Alex Petrov wrote:Hi Tommy,Thank you for spotting this and bringing this to community's
an exception
> in this case?
>
> /Tommy
>
> -Original Message-
> *From*: Brandon Williams <mailto:brandon%20williams%20%3cbrandonwilli...@apache.org%3e>>
> *Reply-To*: dev@cassandra.apache.org
> *To*: dev <mailto:dev%20%3c...@cassandra.apache.org%3e>>
Message-
From: Brandon Williams
mailto:brandon%20williams%20%3cbrandonwilli...@apache.org%3e>>
Reply-To: dev@cassandra.apache.org<mailto:dev@cassandra.apache.org>
To: dev mailto:dev%20%3c...@cassandra.apache.org%3e>>
Subject: [VOTE] Release Apache Cassandra 4.1.6
Date: Mon, 29
Thanks Brandon!
+1
Jon
On Mon, Jul 29, 2024 at 7:37 AM Brandon Williams
wrote:
> Proposing the test build of Cassandra 4.1.6 for release.
>
> sha1: b662744af59f3a3dfbfeb7314e29fecb93abfd80
> Git: https://github.com/apache/cassandra/tree/4.1.6-tentative
> Maven Artifacts:
>
> https://repository
Proposing the test build of Cassandra 4.1.6 for release.
sha1: b662744af59f3a3dfbfeb7314e29fecb93abfd80
Git: https://github.com/apache/cassandra/tree/4.1.6-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1339/org/apache/cassandra/cassandra-all/4.1.6
29 matches
Mail list logo
