+1 (nb)
On Tue, Feb 4, 2025 at 5:07 PM guo Maxwell wrote:
> +1
> Dmitry Konstantinov 于2025年2月5日 周三上午6:04写道：
>
>> +1 (nb)
>>
>> On Tue, 4 Feb 2025 at 22:00, Abe Ratnofsky wrote:
>>
>>> +1 (nb)
>>
>>
>>>
>>
>> --
>> Dmitry Konstantinov
>>
>
I had another read through for the CEP and had some follow up
questions/thoughts.
Write Path - for recovery, how does a node safely recover the highest
hybrid logical clock it has issued? Checking the last entry in the
addressable log is insufficient unless we ensure every individual update is
dur
I think the Native dependencies were disabled for in-jvm Netty because they
prevented the in-jvm dtest InstanceClassLoaders from being garbage
collected and were a source of out-of-metaspace exceptions. I'll echo
Alex's comment that you will also need to investigate in-jvm upgrade tests.
I'm not s
+1
On Fri, Jul 21, 2023 at 2:33 PM Blake Eggleston
wrote:
> +1
>
> On Jul 21, 2023, at 9:57 AM, Jyothsna Konisa
> wrote:
>
> Hi Everyone!
>
> I would like to start a vote thread for CEP-34.
>
> Proposal:
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-34%3A+mTLS+
+1 from me too. I would support removing all of the optional checks from
jar/test as I also hit issues with rat from time to time while iterating,
as long as the CI system runs them and makes it very clear for any
committer there are failures.
On Mon, Jul 10, 2023 at 9:40 AM Josh McKenzie wrote:
sorry, hit send early.
ant test is an interesting one as it seems impractical to run all tests
sequentially, but somebody may want to I suppose.
On Thu, Jul 6, 2023 at 11:53 AM Jon Meredith wrote:
> I think the -Dno-blah settings have usability issues. As they look at
> the property nam
I think the -Dno-blah settings have usability issues. As they look at
the property name, not the value, you cannot override them or default
them with ANT_ARGS or by importing to another ant build file. The way
rat.skip does it seems much better using configured value.
Ideally, I would like an eas
+1
On Wed, May 24, 2023 at 10:13 AM Francisco Guerrero
wrote:
> +1 (nb)
>
> On 2023/05/24 15:38:54 Alex Petrov wrote:
> > +1
> >
> > On Wed, May 24, 2023, at 5:36 PM, Doug Rohrer wrote:
> > > +1 (nb)
> > >
> > > > On May 24, 2023, at 11:32 AM, Brandon Williams
> wrote:
> > > >
> > > > +1
> > >
+1
On Tue, May 16, 2023 at 3:39 AM Andrés de la Peña
wrote:
> +1
>
> On Tue, 16 May 2023 at 07:24, Alex Petrov wrote:
>
>> +1
>>
>> On Tue, May 16, 2023, at 4:45 AM, Doug Rohrer wrote:
>>
>> +1 (nb)
>>
>> Doug Rohrer
>>
>> > On May 15, 2023, at 7:17 PM, Brandon Williams wrote:
>> >
>> > +1
>>
>
>
> On Sat, 10 Dec 2022 at 23:09, Abe Ratnofsky wrote:
>
>> Sorry - responded on the take1 thread:
>>
>> Could we defer the close of this vote til Monday, December 12th after 6pm
>> Pacific Time?
>>
>> Jon Meredith and I have been working thru an
The reason I brought up static columns was for cases where multiple
statements update them and there could be ambiguity.
CREATE TABLE tbl
{
pk1 int,
ck2 int,
s3 static int,
r4 static int,
PRIMARY KEY (pk1, ck2)
}
BEGIN TRANSACTION
UPDATE tbl SET s3=1, r4=1 WHERE pk1=1 AND ck2=1;
UPDATE
I think checking the validation rules as part of testing is important, but
making that a per-test concern for handling it may be frustrating.
What do you think about extending in-JVM with a method that provides the
previous config and version and expects the Instance implementation to
upgrade it,
Wouldn't modifying the CQL grammar would require updating the
application under test to perform experimentation?
The other thing I was wondering about is extensibility - for example
you would like to add a percentage chance for dropping messages for
more deterministic overload modeling.
I can see
+1 to all (nb)
I think this CEP is valuable because it improves on the existing
shortcomings in performance and ability to execute queries that can be
expressed in CQL statements and provides a foundation for future work.
Adding interactive transactions is not in the original scope of the
CEP, nor
0 juil. 2021 à 15:42, Ekaterina Dimitrova <
> > > > > e.dimitr...@gmail.com>
> > > > > >> a écrit :
> > > > > >>
> > > > > >>> Congrats!!! Well deserved!!! 🎉 👏🏻
> > > > > >>>
+1 (nb)
On Fri, Jul 23, 2021 at 10:22 AM Jake Luciani wrote:
> +1
>
> On Fri, Jul 23, 2021 at 11:31 AM Blake Eggleston
> wrote:
>
> > +1
> >
> > > On Jul 23, 2021, at 6:39 AM, Branimir Lambov <
> > branimir.lam...@datastax.com> wrote:
> > >
> > > +1
> > >
> > >> On Fri, Jul 23, 2021 at 4:15 PM
logic for whether to use the same messageid when forwarding or not
needs to include the base message id as well as the forwarding ids. If
there was a single node to forward onto, the forwarded request was not
being sent with the correct messageId.
On Fri, Jul 16, 2021 at 3:05 PM Jon Meredith wrote:
&g
I'd like to request an extension to the vote. There's a possible issue
with 4.0 instances serializing FWD_FRM message parameters to pre-4.0
nodes that I'm investigating and need a little more time.
On Thu, Jul 15, 2021 at 9:45 AM Sam Tunnicliffe wrote:
>
> +1
>
> > On 13 Jul 2021, at 23:13, Mick
+1 (nb)
On Mon, Jun 28, 2021 at 9:47 AM Yifan Cai wrote:
>
> +1
>
>
> - Yifan
>
> > On Jun 28, 2021, at 8:40 AM, Ekaterina Dimitrova
> > wrote:
> >
> > +1 Thanks everyone!
> >
> >> On Mon, 28 Jun 2021 at 11:39, Aleksey Yeschenko wrote:
> >>
> >> +1
> >>
> On 28 Jun 2021, at 14:05, Gary D
+1 (nb)
On Thu, Apr 22, 2021 at 7:59 AM Brandon Williams wrote:
>
> +1
>
> On Wed, Apr 21, 2021 at 1:58 PM Mick Semb Wever wrote:
> >
> > Proposing the test build of Cassandra 4.0-rc1 for release.
> >
> > sha1: 3282f5ecf187ecbb56b8d73ab9a9110c010898b0
> > Git:
> > https://gitbox.apache.org/repo
We may also want to wait for CASSANDRA-16524 given it has been
reproduced for a susceptible certificate configuration and would
prevent internode messaging from being established after the upgrade.
On Thu, Apr 1, 2021 at 7:29 AM Mick Semb Wever wrote:
>
> With Marcus' binding veto, on technical g
attention. I encourage anyone to respond to these reports calling
attention to any localized things that could use it.
As always thanks to everyone for the continued work on the project.
-Jon Meredith
-
To unsubscribe, e-mai
+1 (nb)
On Thu, Dec 3, 2020 at 6:02 AM Oleksandr Petrov
wrote:
>
> Proposing the test build of in-jvm dtest API 0.0.7 for release.
>
> Repository:https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.7
>
> Candidate
> SHA:https://github.com/apache/cassan
I didn't receive any feedback on the previous email I sent about this
on September 23rd. A couple of people pointed out the email got
flagged as suspicious so I've updated the an older JIRA that captures
the same problem instead.
https://issues.apache.org/jira/browse/CASSANDRA-13325
Please take a
+1 (non-binding)
On Fri, Sep 25, 2020 at 9:16 AM Marcus Eriksson wrote:
>
> +1
>
> On 25 September 2020 at 17:13:36, Chris Lohfink (clohfin...@gmail.com) wrote:
> > +1
> >
> > On Fri, Sep 25, 2020 at 10:11 AM Caleb Rackliffe
> > wrote:
> >
> > > +1
> > >
> > > On Fri, Sep 25, 2020 at 10:08 AM Bra
tl;dr Setting encryption_options.protocol does not control which TLS
protocols are accepted, only restricting cipher_suites by protocol
does and I think we should fix encryption_options.protocol to actually
restrict, and have a proposal to do so at the end of the email.
I've been investigating re
+1 (non-binding)
On Wed, Sep 16, 2020 at 8:28 AM David Capwell
wrote:
>
> +1
>
> Sent from my iPhone
>
> > On Sep 16, 2020, at 6:34 AM, Brandon Williams wrote:
> >
> > +1
> >
> >> On Wed, Sep 16, 2020, 4:45 AM Mick Semb Wever wrote:
> >>
> >> This vote is about officially accepting the Harry d
Thanks for the feedback, given three +1s and no objections then I'll
move on to get it merged.
I'm satisfied with the code and David Capwell has completed his
review. If another contributor with more experience with how JMX is
used in the community could look (particularly somebody with operator
e
Following up on Mick's email about interface incompatible changes,
CASSANDRA-15937 is ready for review. In my opinion, this just fixes
some bugs in CASSANDRA-7544 patch that slipped through the original
review, but before we review & merge fixes I wanted to ask if anybody
had any objections to merg
(dropping user)
It's probably also worth mentioning that CASSANDRA-15937 will impact
what gets received on some of the JMX endpoints related to including
storage ports along with addresses, but all of the changes I view as
bugfixes on the original rather than any new functionality (for
example Loa
The majority of the testing that I'm doing and likely the people I
work with day to day tests 4.0 on Java 11, so we should gain some
experience over the next few months.
On Mon, Jul 13, 2020 at 5:27 PM Sumanth Pasupuleti
wrote:
>
> We at Netflix have been testing 4.0 on Java 8, and we do not plan
Hi Everyone,
[Board]
The board can be found here:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355
[New Tickets]
In the last 7 days we have opened 6 new tickets (2 alpha, 3 beta, 1 rc) and
closed 13 (8 alpha, 4 beta, 1 rc).
Please remember to be thoughtful about what Fix Versi
Hi Everyone,
[Board]
The board can be found here:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355
[New Tickets]
In the last seven days we have opened three new alpha tickets, two of which
closed already and seven beta tickets, one closed, two in review.
Please remember to be
Sign me up.
On Thu, May 7, 2020 at 12:36 PM Robert Stupp wrote:
>
> I can help
>
> --
> Robert Stupp
> @snazy
>
> > Am 07.05.2020 um 20:29 schrieb Mick Semb Wever :
> >
> > The Cassandra release process has had some improvements to better in
> > line with the ASF guidelines: sha256 & sha512 chec
The board can be found here:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355
[LHF]
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA&quickFilter=1661&quickFilter=1726&quickFilter=1658
[Tickets That Need Attention]
https://issues.apache.or
Hello dev@cassandra, here is the state of 4.0 things.
Link to the JIRA board:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA
Josh has added a new 'Needs Attention' filter to show any tasks that
are stalled, need an assignee or need a reviewer. Makes it e
Link to JIRA board:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355&projectKey=CASSANDRA
It's been a week of toiling on the tasks we need to ship a release --
fixing bugs and flaky tests.
We've had 0 new ticket opened against 4.0 since the last status email (6d).
https://issue
My turn to give an update on 4.0 status. The 4.0 board created by Josh can
be found at
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=355.
We have 94 unresolved tickets marked against the 4.0 release. [1]
Things seem to have settled into a phase of working to resolve issues,
+1 nb
> On Nov 1, 2019, at 8:07 AM, Scott Andreas wrote:
>
> +1 nb
>
>> On Nov 1, 2019, at 5:36 AM, Benedict Elliott Smith
>> wrote:
>>
>> +1
>>
>> On 01/11/2019, 12:33, "Mick Semb Wever" wrote:
>>
>> Please vote on accepting the Cassandra Enhancement Proposal (CEP) document
>> as a
The DatabaseDescriptorRefTest breakage is on me - there's a fix included as
part of CASSANDRA-15371. Sorry for breaking it - it's benign, just forgot
to add to the new DistributedTestSnitch to the validClasses list.
On Fri, Oct 25, 2019 at 11:06 AM Vinay Chella
wrote:
> Unit test "*testDatabas
I don’t think it will need too much rewriting, and you’re welcome to give
it a go. However trunk is mostly feature frozen while it undergoes testing
ahead of release.
On Fri, Mar 15, 2019 at 9:43 AM A. Soroka (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/CASSANDRA-15005?page=co
41 matches
Mail list logo
