Congrats!On Mar 4, 2025, at 5:48 AM, Ekaterina Dimitrova wrote:Congratulations!! 🎉 On Tue, 4 Mar 2025 at 6:15, Josh McKenzie wrote:Congrats Bernardo - it's been great collaborating with you thus far and looking forward to more!On Tue, Mar 4, 2025, at 4:13 AM, Paulo Motta wr
🎉 On Mar 4, 2025, at 5:49 AM, Ekaterina Dimitrova wrote:Congrats!!! 🎉 On Tue, 4 Mar 2025 at 6:11, Josh McKenzie wrote:Congrats Aaron!On Tue, Mar 4, 2025, at 4:08 AM, Soheil Rahsaz wrote:Congratulations Aaron!On Tue, Mar 4, 2025 at 12:09 PM Paulo Motta wro
Sounds like a reasonable plan to me. +1For the tests, maybe we can have two test class paths for a while? One for driver 3 and one for driver 4? That way we don’t need to migrate them all in a giant big bang patch? They could be moved over a few at a time making review much easier.On Feb 12, 202
That is the biggest “gotcha” of using the empty value for an int. As soon as
you try to use it as an int and not a byte array, all the drivers convert that
to a null pointer. If you just “SELECT v0” and then get its value from the
result set as a byte array, you get empty bytes, not null. It is
+1 (nb)
> On Feb 6, 2025, at 6:31 AM, Maxim Muzafarov wrote:
>
> +1 (nb)
>
>> On Thu, 6 Feb 2025 at 05:34, Patrick McFadin wrote:
>>
>> +1
>>
>>> On Wed, Feb 5, 2025 at 8:15 PM C. Scott Andreas
>>> wrote:
>>>
>>> +1
>>>
On Feb 5, 2025, at 2:50 PM, Alex Petrov wrote:
>>>
>>>
>>>
Congratulations!On Jan 22, 2025, at 10:36 AM, Aaron wrote:Woohoo! Congrats Patrick!On Wed, Jan 22, 2025 at 10:05 AM Jordan West wrote:The PMC's members are pleased to announce that Patrick McFadin has accepted an invitation to become a PMC member.Thanks a lot, Patrick, for ever
Your pagination case is not a violation of any guarantees Cassandra makes. It has never made guarantees across multiple queries.Trying to have MVCC/consistent data across multiple queries is a very different issue/problem from this CEP. If you want to have a discussion about MVCC I suggest creatin
SGTM.
Also I think you do actually need to resolve the full partition for the second
one. You have to merge tombstones+columns from all replicas to decide if the
partition exists. It’s the same reason we have to read all row data for a given
row during regular reads to decide if the row exists.
g authentication mechanism
>> with the client. Similarly, nodes that do not specify available
>> authenticators through their SUPPORTED response can be assumed to not
>> support negotiation and the client can use today's authentication mechanism
>> without negotiation.
>
I think you can implement this as a single authenticator that has separate
configuration of the supported mechanisms. So the single authenticator
maintained is the “negotiating authenticator” which can proxy off to which ever
other mechanisms you want.
> On Dec 3, 2024, at 6:37 PM, Joel Shepher
+1 nbOn Nov 9, 2024, at 9:57 PM, Vinay Chella wrote:+1Thanks,Vinay ChellaOn Sat, Nov 9, 2024 at 1:31 PM Ekaterina Dimitrova wrote:+1On Sat, 9 Nov 2024 at 15:56, Sumanth Pasupuleti wrote:+1 (nb)On Sat, Nov 9, 2024 at 12:43 PM Joseph Lynch <
If I read the ticket correctly, this is preventing bcrypt of incoming credentials from causing a DOS?I think that’s reasonable to backport. If we want to be conservative it could be backported with added code that keeps the current behavior by default?On Nov 5, 2024, at 7:43 AM, Josh McKenzie wro
Sounds good. Just wanted to bring it up. I agree that the scheduling bit is pretty light weight and the ideal would be to bring the whole of the repair external, which is a much bigger can of worms to open.-JeremiahOn Oct 21, 2024, at 11:21 AM, Chris Lohfink wrote:> I actually think we should be
I think reserializing the payload into a new format is counter productive to some of the performance goals of the binary logs?If you have to deserialize and reserialize the message you are going to be throwing off a ton of extra GC.I think we have done a lot of work in recent version to reduce the
Welcome to the project!
> On Sep 12, 2024, at 2:42 PM, Brandon Williams wrote:
>
> Congratulations!
>
> Kind Regards,
> Brandon
>
>> On Thu, Sep 12, 2024 at 6:40 AM Mick Semb Wever wrote:
>>
>> The PMC's members are pleased to announce that Chris Bannister, James
>> Hartig, Jackson Flemmin
I have lost sleep (and data) over this multiple times in the past few months, that was only recently tracked down to this exact scenario.+1 for including it in all active releases and enabling the failure of the writes on “wrong” nodes by default.I haven’t looked at the patch, but as long as only o
Two great additions to the PMC. Congratulations to you both!
-Jeremiah Jordan
> On Aug 30, 2024, at 3:21 PM, Jon Haddad wrote:
>
>
> The PMC's members are pleased to announce that Jordan West and Stefan
> Miklosovic have accepted invitations to become PMC members.
>
> Thanks a lot, Jordan a
If you have a lot of snapshots and have for example a metric monitoring them
and their sizes, if you don’t cache it, creating the metric can cause
performance degradation. We added the cache because we saw this happen to
databases more than once.
> On Aug 7, 2024, at 7:54 AM, Josh McKenzie wro
I would go with the mbean change option. I would add a new “list” function with
a new parameter to the mbean that allows specifying if it should refresh the
cache before returning the list.
No need to do the inotify stuff just for nodetool listsnapshot to be always
correct. Then add a new parame
I am +1 (nb) for 5.0. -0 for 4.0 and 4.1.I would rather promote people upgrade to the latest release to get new features.I also think we have been doing a pretty good job of backwards compatibility lately, so I would also promote the side projects using the latest release to work with data from old
s stability of the database for all users, so it's worth going in. Let's not be dogmatic about fixes that help 99% of users because an incredibly small number that actually implement a custom query handler will need to make a trivial update in order to use the latest 4.1.6 dependency
+1 to deprecate it. What does removing it buy us?
> On Jul 30, 2024, at 3:52 PM, David Capwell wrote:
>
> Users can provide ids and TCM can manage to make them safe, so agree we
> don’t really need the feature anymore. I am fine with deprecating the
> feature, but removing would be a breakin
x27;s worth going in. Let's not be dogmatic about fixes that help 99% of users because an incredibly small number that actually implement a custom query handler will need to make a trivial update in order to use the latest 4.1.6 dependency.JonOn Tue, Jul 30, 2024 at 8:09 AM J. D. Jordan &
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
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
I don’t know that I agree we should remove use if isDebugEnabled, but we should be assuming debug is enabled and not doing anything too crazy there.The description of the log levels from the old wiki describes the state of our logging very well, +1 to get that back into the docs.If someone wants to
How do we expose this for the already GA’ed 4.1.0-4.1.5 which are in use out in the world already?I would be more worried about that than the as yet to be released 5.0.0 which is likely not going to be in production for anyone for at least a few weeks after GA if not months in most shops.Seems like
+1 nb. Good to see this heavily used driver get continued development in the
project.
> On Jun 25, 2024, at 5:29 PM, Michael Shuler wrote:
>
> +1
>
> Kind regards,
> Michael
>
>> On 6/25/24 12:29, Mick Semb Wever wrote:
>> Please vote on the acceptance of the GoCQL driver and its IP Clearanc
+1 agree with all this. Also fine to just use in tests or ban completely.On Jun 2, 2024, at 11:58 AM, Jake Luciani wrote:+1 Java streams cause perf issues in hot paths. Its fine for tests and slow paths. But for clairity its fine to ban it as well if the majority agrees. On Sun, Jun 2, 2024 at 1
We have already agreed in the past that having experimental features, behind
feature flags, in stable releases is a good thing for keeping those features up
to date, for getting feedback from end users, and many others.
The question here is about how we ensure that end users are aware something i
<<< multipart/alternative: No recognizable part >>>
Correct. But that initial connection will work and the client will work, it
just won’t have connections to multiple nodes.
I didn’t say it’s optimal, but this is the best way I can see that doesn’t
break things more than they are now, and does give an improvement because you
can pick which port
We should not introduce a new column in a patch release. From what I have seen many drivers “select * from peers”, yes it’s not a good idea, but we can’t control what all clients do, and an extra column coming back may break the processing of that.For existing versions what about having a “default
I think we used to have this and removed them because it was breaking the
encryption signature on messages or something which meant they were very likely
to be treated as spam?
Not saying we can’t put it back on, but it was removed for good reasons from
what I recall.
> On Jan 22, 2024, at 12:
The CEP-29 “rejected alternatives” section mentions one such use case. Being able to put NOT arbitrarily in a query. Adding an OR operator is another thing we are likely to want to do in the near future that would benefit from this work, those benefit from the syntax tree and reordering parts of
er try batching rows reads per partition, it would come in handy again...)On Fri, Dec 1, 2023 at 12:30 PM J. D. Jordan <jeremiah.jor...@gmail.com> wrote:I prefer option 2. It is much easier to understand and roll up two metrics than to do subtractive dashboards.SAI reads are already “range rea
I prefer option 2. It is much easier to understand and roll up two metrics than to do subtractive dashboards.SAI reads are already “range reads” for the client level metrics, not regular reads. So grouping them into the regular read metrics at the lower level seems confusing to me in that sense as
Congrats!
> On Nov 28, 2023, at 12:57 PM, C. Scott Andreas wrote:
>
> Congratulations, Francisco!
>
> - Scott
>
>> On Nov 28, 2023, at 10:53 AM, Dinesh Joshi wrote:
>>
>> The PMC members are pleased to announce that Francisco Guerrero Hernandez
>> has accepted
>> the invitation to become
That said. This is clearly better than and with many fixes from the alpha. Would people be more comfortable if this cut was released as another alpha and we do beta1 once the known fixes land?On Nov 28, 2023, at 12:21 PM, J. D. Jordan wrote:-0 (NB) on this cut. Given the concerns expressed so
-0 (NB) on this cut. Given the concerns expressed so far in the thread I would think we should re-cut beta1 at the end of the week.On Nov 28, 2023, at 12:06 PM, Patrick McFadin wrote:I'm a +1 on a beta now vs maybe later. Beta doesn't imply perfect especially if there are declared known issues. W
Sounds like 18993 is not a regression in 5.0? But present in 4.1 as well? So I
would say we should fix it with the highest priority and get a new 4.1.x
released. Blocking 5.0 beta voting is a secondary issue to me if we have a
“data not being returned” issue in an existing release?
> On Nov 4,
That is my understanding as well. If the TCM and Accord based on TCM branches are ready to commit by ~12/1 we can cut a 5.1 branch and then a 5.1-alpha release.Where “ready to commit” means our usual things of two committer +1 and green CI etc.If we are not ready to commit then I propose that as lo
The software grant agreement covers all donated code. The ASF does not need any historical agreements. The agreement giving the ASF copyright etc is the Software Grant Agreement. Yes, any future work done after donation needs to be covered by ASF CLAs.But happy to see someone ask legal@ to confirm
This Gen AI generated code use thread should probably be its own mailing list DISCUSS thread? It applies to all source code we take in, and accept copyright assignment of, not to jars we depend on and not only to vector related code contributions.On Sep 22, 2023, at 7:29 AM, Josh McKenzie wrote:
Mick,I am confused by your +1 here. You are +1 on including it, but only if the copyright were different? Given DataStax wrote the library I don’t see how that will change?On Sep 21, 2023, at 3:05 AM, Mick Semb Wever wrote:On Wed, 20 Sept 2023 at 18:31, Mike Adamson wrote
+1 for jvector rather than forked lucene classes. On Sep 20, 2023, at 5:14 PM, German Eichberger via dev wrote:
+1
I am biased because DiskANN is from Microsoft Research but it's a good library/algorithm
From: Mike Adamson
Sent: Wednesday, September 20, 2023 8:58 AM
To: dev
Subject
When does empty mean null? My understanding was that empty is a valid value
for the types that support it, separate from null (aka a tombstone). Do we have
types where writing an empty value creates a tombstone?
I agree with David that my preference would be for only blob and string like
types
Reading through smile license again, it is licensed pure GPL 3, not GPL with classpath exception. So I think that kills all debate here.-1 on inclusion On Sep 13, 2023, at 2:30 PM, Jeremiah Jordan wrote:
I wonder if it can easily be replaced with Apache open-nlp? It also provides an implemen
These are not compiled code. They are serialized dumps of bloom filter data.
> On Aug 28, 2023, at 9:58 PM, Justin Mclean wrote:
>
> 1../test/data/serialization/3.0/utils.BloomFilter1000.bin
> 2. ./test/data/serialization/4.0/utils.BloomFilter1000.bin
+1 nb.I think it’s good to get an alpha out there for people to starting trying out the features which are done.On Aug 25, 2023, at 4:03 PM, Mick Semb Wever wrote:There was lazy consensus on this thread: https://lists.apache.org/thread/mzj3dq8b7mzf60k6mkby88b9n9ywmsgw and also the announcement a
atastax.com>
> wrote:
>
> > SASI just uses “=“ for the tokenized equality matching, which is the exact
> > thing this discussion is about changing/not liking.
> >
> > > On Aug 2, 2023, at 7:18 PM, J. D. Jordan <jeremiah.jor...@gmail.com>
> > wrote:
&g
I do not think LIKE actually applies here. LIKE is used for prefix, contains,
or suffix searches in SASI depending on the index type.
This is about exact matching of tokens.
> On Aug 2, 2023, at 5:53 PM, Jon Haddad wrote:
>
> Certain bits of functionality also already exist on the SASI side o
I think this plan seems reasonable to me. +1
-Jeremiah
> On Jul 26, 2023, at 5:28 PM, Mick Semb Wever wrote:
>
>
>
> The previous thread¹ on when to freeze 5.0 landed on freezing the first week
> of August, with a waiver in place for TCM and Accord to land later (but
> before October).
>
Thanks for all the work here!On Jul 26, 2023, at 1:57 PM, Caleb Rackliffe wrote:Alright, the cep-7-sai branch is now merged to trunk!Now we move to addressing the most urgent items from "Phase 2" (CASSANDRA-18473) before (and in the case of some testing after) the 5.0 freeze...On Wed, Jul 26, 202
Enabling ssl for the upgrade dtests would cover this use case. If those don’t
currently exist I see no reason it won’t work so I would be fine for someone to
figure it out post merge if there is a concern. What JCE provider you use
should have no upgrade concerns.
-Jeremiah
> On Jul 26, 2023,
I thought the crypto providers were supposed to “ask the next one down the
line” if something is not supported? Have you tried some unsupported thing and
seen it break? My understanding of the providers being an ordered list was
that isn’t supposed to happen.
-Jeremiah
> On Jul 26, 2023, at
Maybe we could start providing Dockerfile’s and/or make arch specific rpm/deb
packages that have everything setup correctly per architecture?
We could also download them all and have the startup scripts put stuff in the
right places depending on the arch of the machine running them?
I feel like t
+1 nbOn May 25, 2023, at 7:47 PM, Jasonstack Zhao Yang wrote:+1On Fri, 26 May 2023 at 8:44 AM, Yifan Cai wrote:
+1
From: Josh McKenzie
Sent: Thursday, May 25, 2023 5:37:02 PM
To: dev
Subject: Re: [VOTE] CEP-30 ANN
Process question/discussion. Should tickets that are merged to CEP feature
branches, like https://issues.apache.org/jira/browse/CASSANDRA-18204, have a
fixver of 5.0 on them After merging to the feature branch?
For the SAI CEP which is also using the feature branch method the "reviewed and
mer
Yes. Plugging in a new type server side is very easy. Adding that type to every client is not.Cassandra already supports plugging in custom types through a jar. What a given client does when encountering a custom type it doesn’t know about depends on the client.I was recently looking at this for D
If we look to postgresql it allows defining arrays using FLOAT[N] or FLOAT
ARRAY[N].
So that is an extra point for me to just using FLOAT[N].
From my quick search neither oracle* nor MySQL directly support arrays in
columns.
* oracle supports declaring a custom type using VARRAY and then using
That said I’m not opposed to Mick’s proposal. In Apache terms I am -0 on the proposal. So no need to try and convince me. If others think it is the way forward let’s go with it.On Apr 18, 2023, at 1:48 PM, J. D. Jordan wrote:I also don’t really see the value in “freezing with exceptions for two
I also don’t really see the value in “freezing with exceptions for two giant changes to come after the freeze”.-JeremiahOn Apr 18, 2023, at 1:08 PM, Caleb Rackliffe wrote:> Caleb, you appear to be the only one objecting, and it does not appear that you have made any compromises in this thread.All
The documentation is wrong. ALLOW FILTERING has always meant that “rows will need to be materialized in memory and accepted or rejected by a column filter” aka the full primary key was not specified and some other column was specified. It has never been about multiple partitions.Basically “will th
,DougOn Mar 28, 2023, at 1:14 PM, J. D. Jordan wrote:Maybe some data flow diagrams could be added to the cep showing some example operations for read/write?On Mar 28, 2023, at 11:35 AM, Yifan Cai wrote:A lot of great discussions! On the sidecar front, especially what the role sidecar plays in terms of
+1On Apr 4, 2023, at 7:29 AM, Brandon Williams wrote:+1On Tue, Apr 4, 2023, 7:24 AM Branimir Lambov wrote:Hi everyone,I would like to put CEP-26 to a vote.Proposal:https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-26%3A+Unified+Compaction+StrategyJIRA and draft implem
That was my understanding as well.On Mar 30, 2023, at 11:21 AM, Josh McKenzie wrote:So to confirm, let's make sure we all agree on the definition of "stabilize".Using the definition as "green run of all tests on circleci, no regressions on ASF CI" that we used to get 4.1 out the door, and combine
Maybe some data flow diagrams could be added to the cep showing some example operations for read/write?On Mar 28, 2023, at 11:35 AM, Yifan Cai wrote:A lot of great discussions! On the sidecar front, especially what the role sidecar plays in terms of this CEP, I feel there might be some confusion.
Congrats Josh!And thanks Mick for your time spent as Chair!On Mar 23, 2023, at 8:21 AM, Aaron Ploetz wrote:Congratulations, Josh!And of course, thank you Mick for all you've done for the project while in the PMC Chair role!On Thu, Mar 23, 2023 at 7:44 AM Derek Chen-Becker
Agreed. I also think it is worthwhile to keep that code around. Given how
widespread C* 3.x use is, I do not think it is worthwhile dropping support for
those sstable formats at this time.
-Jeremiah
> On Mar 14, 2023, at 9:36 AM, C. Scott Andreas wrote:
>
>
> I agree with Aleksey's view her
Yes exactly. If we are updating a library for some reason, we should update it to the latest one that makes sense.On Mar 13, 2023, at 1:17 PM, Josh McKenzie wrote:I think we should we use the most recent versions of all libraries where possible?”To clarify, are we talking "most recent versions of
+1 from me to deprecate in 4.x and remove in 5.0.
-Jeremiah
> On Mar 9, 2023, at 11:53 AM, Brandon Williams wrote:
>
> I think if we reach consensus here that decides it. I too vote to
> deprecate in 4.1.x. This means we would remove it in 5.0.
>
> Kind Regards,
> Brandon
>
>> On Thu, Mar 9
We have been talking a lot about the branch cutting date, but I agree with Benedict here, I think we should actually be talking about the expected release date. If we truly believe that we can release within 1-2 months of cutting the branch, and many people I have talked to think that is possible,
I think it makes sense to plan on cutting the branch later given when 4.1
actually released. I would suggest either August or September as a good time to
cut the branch, at the end of the summer.
-Jeremiah
> On Feb 28, 2023, at 7:42 AM, Benjamin Lerer wrote:
>
>
> Hi,
>
> We forked the 4.0
Congrats!On Feb 2, 2023, at 12:47 PM, Christopher Bradford wrote:Congrats Patrick! Well done. On Thu, Feb 2, 2023 at 10:44 AM Aaron Ploetz wrote:Patrick FTW!!!On Thu, Feb 2, 2023 at 12:32 PM Joseph Lynch wrote:W! Congratulations Patrick!!-JoeyOn
opment.> On 16 Jan 2023, at 15:57, J. D. Jordan <jeremiah.jor...@gmail.com> wrote:> > I haven’t been following the progress of the feature branch, but I would think the requirements for merging it into master would be the same as any other merge.> > A subset of those requirem
I haven’t been following the progress of the feature branch, but I would think
the requirements for merging it into master would be the same as any other
merge.
A subset of those requirements being:
Is the code to be merged in releasable quality? Is it disabled by a feature
flag by default if n
+1 nb
> On Dec 19, 2022, at 7:07 AM, Brandon Williams wrote:
>
> +1
>
> Kind Regards,
> Brandon
>
>> On Mon, Dec 19, 2022 at 6:59 AM Branimir Lambov wrote:
>>
>> Hi everyone,
>>
>> I'd like to propose CEP-25 for approval.
>>
>> Proposal:
>> https://cwiki.apache.org/confluence/display/CAS
DTs on "ORDER BY"? I don't think so.I rather think that basing MIN/MAX on the regular order of the column data type is consistent, easy to do and easy to understand. I don't see the need to add rules explicitly forbidding some data types on MIN/MAX functions just because we can'
If the functionality truly has never actually worked, then throwing an error
that MAX is not supported for collections seems reasonable.
But we should throw an error, I do not think we should have functions that
aggregate across rows and functions that operate within a row use the same name.
My
Seems well maintained and MIT licensed. +1 from me.
> On Nov 28, 2022, at 6:35 PM, Derek Chen-Becker wrote:
>
> Overall the library appears to be high quality, even going so far as
> to have regression tests between versions. I do, however, think that
> the long-term maintenance risk needs to b
+1 nbOn Nov 18, 2022, at 10:55 AM, Benjamin Lerer wrote:+1Le ven. 18 nov. 2022 à 16:50, Mick Semb Wever a écrit :+1Checked- signing correct- checksums are correct- source artefact builds (JDK 8+11)- binary artefact runs (JDK 8+11)- debian package runs (JDK 8+11)- debian repo run
gt;>> validation that the perf improvements are seen, there is not enough time
>>> left for that added performance work burden so strongly feel it should be
>>> pushed to 4.2/5.0 where it has plenty of time to be validated against. The
>>> ticket even asks to a
Heap -+1 for G1 in trunk+0 for G1 in 4.1 - I think it’s worthwhile and fairly well tested but I understand pushback against changing this so late in the game.Memtable --1 for off heap in 4.1. I think this needs more testing and isn’t something to change at the last minute.+1 for running performance
No vote required. Just add a comment on it.On Oct 25, 2022, at 10:51 AM, Claude Warren, Jr via dev wrote:I see that there is one proposal that was discarded. I wonder how that got there.On Tue, Oct 25, 2022 at 2:52 PM Josh McKenzie wrote:... I don't know that we've navigat
+1 nb
> On Sep 19, 2022, at 6:50 AM, Berenguer Blasi wrote:
>
> +1
>
>> On 19/9/22 13:39, Brandon Williams wrote:
>> +1
>>
>> Kind Regards,
>> Brandon
>>
>>> On Mon, Sep 19, 2022 at 6:39 AM Andrés de la Peña
>>> wrote:
>>> Hi everyone,
>>>
>>> I'd like to propose CEP-20 for approval.
>>>
+1 for removing on trunk. Pretty sure we already discussed that in the Java 17
thread? That trunk will move to 11+17?
> On Aug 29, 2022, at 3:40 PM, Blake Eggleston wrote:
>
> Sorry, I meant trunk, not 4.1 :)
>
>> On Aug 29, 2022, at 1:09 PM, Blake Eggleston wrote:
>>
>> Hi all, I wanted t
I like the third option, especially if it makes it consistent with repair,
which has supported ranges longer and I would guess most people would think the
compact ranges work the same as the repair ranges.
-Jeremiah Jordan
> On Jul 26, 2022, at 6:49 AM, Andrés de la Peña wrote:
>
>
> Hi all
Congrats!
> On Jul 6, 2022, at 7:20 AM, Berenguer Blasi wrote:
>
> Congrsss Sir! :-)
>
>> On 6/7/22 14:00, Benjamin Lerer wrote:
>> The PMC members are pleased to announce that Jacek Lewandowski has accepted
>> the invitation to become committer.
>>
>> Thanks a lot, Jacek, for e
+1 from me.
> On May 10, 2022, at 9:17 AM, Josh McKenzie wrote:
>
>
>>
>> at some later point it needs to be "easy" for
>> someone else to correct it.
> I don't want to optimize for cleaning up later; I want to optimize for our
> ability to know our workload blocking our next release and enc
Why do you need to change anything post release? The whole point is to set the
version to the release the ticket blocks. So you don’t need to change anything.
> On May 9, 2022, at 8:03 PM, Mick Semb Wever wrote:
>
> Jeremiah, around when was this? I can see that it makes sense (works in
> the
I would vote for option 1. We have done similar in the past and if something is
a blocker it means it will be in that version before it is released. So there
should not be any confusion of things getting bumped forward to another patch
number because they were not committed in time, which is whe
I think these are very interesting ideas for another new feature. Would one of
you like to write it up as a JIRA and start a new thread to discuss details? I
think it would be good to keep this thread about the simpler proposal from
CASSANDRA-17501 unless you all are against implementing that w
I think this is an important step in the authorization model of C*. It brings
parity with many other databases.
While further restrictions might make such restrictions less likely to be
worked around, in most places I have heard of using audit logging of user
management statements is how you p
Congratulations!
> On Mar 16, 2022, at 8:43 AM, Ekaterina Dimitrova
> wrote:
>
>
> Great news! Well deserved! Congrats and thank you for all your support!
>
>> On Wed, 16 Mar 2022 at 9:41, Paulo Motta wrote:
>> Congratulations Alex, well deserved! :-)
>>
>>> Em qua., 16 de mar. de 2022 às
+1 nb
> On Feb 17, 2022, at 4:25 PM, Brandon Williams wrote:
>
> +1
>
>> On Thu, Feb 17, 2022 at 4:23 PM Caleb Rackliffe
>> wrote:
>>
>> Hi everyone,
>>
>> I'd like to call a vote to approve CEP-7.
>>
>> Proposal:
>> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-7%3A+Storage+A
+1 nb
> On Feb 16, 2022, at 7:30 AM, Josh McKenzie wrote:
>
>
> +1
>
>> On Wed, Feb 16, 2022, at 7:33 AM, Ekaterina Dimitrova wrote:
>> +1nb
>>
>> On Wed, 16 Feb 2022 at 7:30, Brandon Williams wrote:
>> +1
>>
>> On Wed, Feb 16, 2022 at 3:00 AM Branimir Lambov wrote:
>> >
>> > Hi everyone,
Can we have the discussion on the ticket?
Thanks
-Jeremiah
> On Feb 16, 2022, at 6:23 AM, Bowen Song wrote:
>
> To me this doesn't sound very useful. Here's a few threat model I can think
> of that may be related to this proposal, and why is this not addressing the
> issues & what should be
Congratulations all of you! Well deserved additions.
> On Feb 15, 2022, at 12:30 PM, Brandon Williams wrote:
>
> Congratulations, well deserved!
>
>> On Tue, Feb 15, 2022 at 12:13 PM Benjamin Lerer wrote:
>>
>> The PMC members are pleased to announce that Anthony Grasso, Erick Ramirez
>> an
Correct. No need to revert anything or keep extra branches around. You just
checkout the tag and then make a branch with the single fix on it.
> On Feb 15, 2022, at 10:08 AM, Josh McKenzie wrote:
>
>
> Was thinking that too after I wrote this. Means we'd only need to change our
> process for
1 - 100 of 177 matches
Mail list logo