[DISCUSS] Slack notifications for new Stack Overflow, Stack Exchange questions

[Erick Ramirez]

I previously floated with a couple of PMC members the idea of posting new
Stack Overflow/Stack Exchange questions to the #cassandra Slack channel.
The motivation for doing so include:

   - Promote/advertise the questions (AND answers) on Stack Overflow +
   Stack Exchange.
   - Answers on the Stack network are SEO-friendly unlike Slack
   conversations.
   - Asking on the Stack network reduces duplication for already-answered
   questions.

It was suggested that I do some research on whether other Apache projects
are already using the Slack integration but I haven't been successful in
finding any previous Jira tickets or info on ASF wikis so I logged a ticket
with the ASF Infrastructure team to ask (a) if it's been requested before,
and/or (b) if it's allowed (INFRA-24004
). The Slack-Stack
integration hasn't been requested before but Infra thought it was a good
idea and implemented it before I've had the chance to circle back to the
PMC for next steps.

In any case, does anyone have concerns about the notifications in Slack? Do
you foresee any issues with it? Cheers!

[VOTE] CEP-25: Trie-indexed SSTable format

[Branimir Lambov]

Hi everyone,

I'd like to propose CEP-25 for approval.

Proposal:
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
Discussion: https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh

The vote will be open for 72 hours.
Votes by committers are considered binding.
A vote passes if there are at least three binding +1s and no binding vetoes.

Thank you,
Branimir

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Benedict]

+1

> On 19 Dec 2022, at 13:00, Branimir Lambov  wrote:
> 
> 
> Hi everyone,
> 
> I'd like to propose CEP-25 for approval.
> 
> Proposal: 
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
> Discussion: https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
> 
> The vote will be open for 72 hours.
> Votes by committers are considered binding.
> A vote passes if there are at least three binding +1s and no binding vetoes.
> 
> Thank you,
> Branimir

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Jacek Lewandowski]

+1

- - -- --- -  -
Jacek Lewandowski


On Mon, Dec 19, 2022 at 2:00 PM Branimir Lambov  wrote:

> Hi everyone,
>
> I'd like to propose CEP-25 for approval.
>
> Proposal:
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
> Discussion:
> https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
>
> The vote will be open for 72 hours.
> Votes by committers are considered binding.
> A vote passes if there are at least three binding +1s and no binding
> vetoes.
>
> Thank you,
> Branimir
>

Re: [DISCUSS] Slack notifications for new Stack Overflow, Stack Exchange questions

[Mick Semb Wever]

> In any case, does anyone have concerns about the notifications in Slack?
> Do you foresee any issues with it? Cheers!
>


Thanks for writing it up Erick. Perfectly fine to have a bias for action
here, it being an easy-to-undo action.
No objections, my only concern is if it is considered too noisy by some and
reduces interaction on #cassandra
Can you take a poll there to gauge folks' receptiveness to it?

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Brandon Williams]

+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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
> Discussion: https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
>
> The vote will be open for 72 hours.
> Votes by committers are considered binding.
> A vote passes if there are at least three binding +1s and no binding vetoes.
>
> Thank you,
> Branimir

Re: [DISCUSS] Slack notifications for new Stack Overflow, Stack Exchange questions

[Brandon Williams]

I find it to be more noise than signal thus far.  I noticed it had
been added and put it on my list to ask for it to be removed, since it
seemed to just randomly appear, but I guess we can give it more time.

On Mon, Dec 19, 2022 at 7:06 AM Mick Semb Wever  wrote:
>
>
>> In any case, does anyone have concerns about the notifications in Slack? Do 
>> you foresee any issues with it? Cheers!
>
>
>
> Thanks for writing it up Erick. Perfectly fine to have a bias for action 
> here, it being an easy-to-undo action.
> No objections, my only concern is if it is considered too noisy by some and 
> reduces interaction on #cassandra
> Can you take a poll there to gauge folks' receptiveness to it?

Re: [Discuss] CEP-24 Password validation and generation

[Miklosovic, Stefan]

One not-so-obvious consequence of the configuration of password validator - 
since it is based on guardrails - is that if there is a cluster of 50 nodes and 
we change a configuration (in runtime) in one node, it needs to be done for all 
remaining 49. We need to be sure that the configuration is same for all nodes 
because if we do not configure one node the way we want, all it takes to pass 
the (less secure) validation is to create passwords while being logged on that 
node. I think that something similar was done to memtables CEP and there was 
some additional discussion about that - the way how it is configured - it is in 
yaml and not in schema so it is only node-specific, right? (not saying it is 
wrong, I just noticed that there was additional discussion questioning that 
approach which was further clarified). However when it comes to security, I 
think it should be as robust as possible.

I am not completely sure what to do here. It would be great to have some 
"distributed configuration" otherwise all I can do is to mimic this behavior by 
a table, similarly as system_auth.roles is done for passwords, for example. 
However, I feel like it should be more robust and I think that in the future 
there might be more cases when we need to have the configuration distributed 
like this.

However, I am fine to proceed with my original plan when community thinks that 
the current approach is enough.


From: Claude Warren, Jr via dev 
Sent: Wednesday, October 19, 2022 10:58
To: dev@cassandra.apache.org
Subject: Re: [Discuss] CEP-24 Password validation and generation

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.



Just to clarify, I have no objections to the current plan.

On Thu, Oct 13, 2022 at 2:56 PM Claude Warren, Jr 
mailto:claude.war...@aiven.io>> wrote:
I am not familiar with the Diagnostics framework but it sounds like it would 
satisfy the need.  Thanks for pointing it out.  I will dive into it to get an 
understanding of how it works.

On Thu, Oct 13, 2022 at 1:52 PM Miklosovic, Stefan 
mailto:stefan.mikloso...@netapp.com>> wrote:
Hi Claude,

we may also integrate with Diagnostics framework Cassandra already ships. I 
would say this better suits to your requirements for observability. I am not 
sure to what degree you are familiar with Diagnostics though. To give you a 
better picture, events are fired and external observers (in the framework 
called "subscribers") would be notified about the internal accordingly. As of 
now, observers / subscribers are meant to integrate with JMX through which 
these events flow.

Do you think Diagnostics events would satisfy your needs?

Regards


From: Claude Warren, Jr via dev 
mailto:dev@cassandra.apache.org>>
Sent: Thursday, October 13, 2022 14:43
To: dev@cassandra.apache.org
Subject: Re: [Discuss] CEP-24 Password validation and generation

NetApp Security WARNING: This is an external email. Do not click links or open 
attachments unless you recognize the sender and know the content is safe.



The only difference I see is that I see observability (observer) as being a way 
to retrieve (or be notified about) data used within a process.  Logging on the 
other hand, is a preservation of a state discovered in an observable object.  
Observability can drive logging but it can also drive aggregate statistics in 
grafana, and things like that.

My reading of the CEP-3 is that it is intended to provide system-wide soft and 
hard limits, it is not an observability framework.  It makes sense for the 
validator to implement CEP-3 but I think that an observability interface is 
required as well.

On Thu, Oct 13, 2022 at 12:36 PM Miklosovic, Stefan 
mailto:stefan.mikloso...@netapp.com>>>
 wrote:
Hi Claude,

all you say makes sense to me. I do not see any discrepancies. It will be 
logged as discussed already.

The complexity of password validation is partly covered by the library we want 
to use (Passay). It will inform you in a very detailed manner when it comes to 
what violations of a policy there are. We are not going to invent a wheel here, 
fortunately.

Terminology you used - "observer" - is Guardrail itself (CEP-3). It will be the 
one doing reporting e.g by logging and returning warnings / errors, if any, 
back to user who executed that query.

The approach we took indeed can also be extended in such a way that it would be 
possible to know what was the last time a password was changed for some user. 
This is the direct consequence of us having a table of previous password for 
checking that a user is not reusing them. There is a timestamp column specified 
here (1) if you check the schema of that table closely so to answer "when was 
the password changed lastly" is rath

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[J. D. Jordan]

+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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
>> Discussion: https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
>> 
>> The vote will be open for 72 hours.
>> Votes by committers are considered binding.
>> A vote passes if there are at least three binding +1s and no binding vetoes.
>> 
>> Thank you,
>> Branimir

[DISCUSS] CEP-26: Unified Compaction Strategy

[Branimir Lambov]

Hello everyone,

I would like to open the discussion on our proposal for a unified
compaction strategy that aims to solve well-known problems with compaction
and improve parallelism to permit higher levels of sustained write
throughput.

The proposal is here:
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-26%3A+Unified+Compaction+Strategy

The strategy is based on two main observations:
- that tiered and levelled compaction can be generalized as the same thing
if one observes that both form exponentially-growing levels based on the
size of sstables (or non-overlapping sstable runs) and trigger a compaction
when more than a given number of sstables are present on one level;
- that instead of "size" in the description above we can use "density",
i.e. the size of an sstable divided by the width of the token range it
covers, which permits sstables to be split at arbitrary points when the
output of a compaction is written and still produce a levelled hierarchy.

The latter allows us to shard the compaction space into
progressively higher numbers of shards as data moves to the higher levels
of the hierarchy, improving parallelism, space requirements and the
duration of compactions, and the former allows us to cover the existing
strategies, as well as hybrid mixtures that can prove more efficient for
some workloads.

Thank you,
Branimir

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Ekaterina Dimitrova]

+1

On Mon, 19 Dec 2022 at 8:30, J. D. Jordan  wrote:

> +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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
> >> Discussion:
> https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
> >>
> >> The vote will be open for 72 hours.
> >> Votes by committers are considered binding.
> >> A vote passes if there are at least three binding +1s and no binding
> vetoes.
> >>
> >> Thank you,
> >> Branimir
>

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Aleksey Yeshchenko]

+1

> On 19 Dec 2022, at 13:42, Ekaterina Dimitrova  wrote:
> 
> +1
> 
> On Mon, 19 Dec 2022 at 8:30, J. D. Jordan  > wrote:
>> +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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
>> >> Discussion: 
>> >> https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
>> >> 
>> >> The vote will be open for 72 hours.
>> >> Votes by committers are considered binding.
>> >> A vote passes if there are at least three binding +1s and no binding 
>> >> vetoes.
>> >> 
>> >> Thank you,
>> >> Branimir

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Andrés de la Peña]

+1

On Mon, 19 Dec 2022 at 15:11, Aleksey Yeshchenko  wrote:

> +1
>
> On 19 Dec 2022, at 13:42, Ekaterina Dimitrova 
> wrote:
>
> +1
>
> On Mon, 19 Dec 2022 at 8:30, J. D. Jordan 
> wrote:
>
>> +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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
>> >> Discussion:
>> https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
>> >>
>> >> The vote will be open for 72 hours.
>> >> Votes by committers are considered binding.
>> >> A vote passes if there are at least three binding +1s and no binding
>> vetoes.
>> >>
>> >> Thank you,
>> >> Branimir
>>
>
>

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Benjamin Lerer]

+1

Le lun. 19 déc. 2022 à 16:31, Andrés de la Peña  a
écrit :

> +1
>
> On Mon, 19 Dec 2022 at 15:11, Aleksey Yeshchenko 
> wrote:
>
>> +1
>>
>> On 19 Dec 2022, at 13:42, Ekaterina Dimitrova 
>> wrote:
>>
>> +1
>>
>> On Mon, 19 Dec 2022 at 8:30, J. D. Jordan 
>> wrote:
>>
>>> +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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
>>> >> Discussion:
>>> https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
>>> >>
>>> >> The vote will be open for 72 hours.
>>> >> Votes by committers are considered binding.
>>> >> A vote passes if there are at least three binding +1s and no binding
>>> vetoes.
>>> >>
>>> >> Thank you,
>>> >> Branimir
>>>
>>
>>

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[SAURABH VERMA]

+1

On Mon, Dec 19, 2022 at 9:36 PM Benjamin Lerer  wrote:

> +1
>
> Le lun. 19 déc. 2022 à 16:31, Andrés de la Peña  a
> écrit :
>
>> +1
>>
>> On Mon, 19 Dec 2022 at 15:11, Aleksey Yeshchenko 
>> wrote:
>>
>>> +1
>>>
>>> On 19 Dec 2022, at 13:42, Ekaterina Dimitrova 
>>> wrote:
>>>
>>> +1
>>>
>>> On Mon, 19 Dec 2022 at 8:30, J. D. Jordan 
>>> wrote:
>>>
 +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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
 >> Discussion:
 https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
 >>
 >> The vote will be open for 72 hours.
 >> Votes by committers are considered binding.
 >> A vote passes if there are at least three binding +1s and no binding
 vetoes.
 >>
 >> Thank you,
 >> Branimir

>>>
>>>

-- 
Thanks & Regards,
Saurabh Verma,
India

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Josh McKenzie]

+1

On Mon, Dec 19, 2022, at 11:54 AM, SAURABH VERMA wrote:
> +1
> 
> On Mon, Dec 19, 2022 at 9:36 PM Benjamin Lerer  wrote:
>> +1
>> 
>> Le lun. 19 déc. 2022 à 16:31, Andrés de la Peña  a 
>> écrit :
>>> +1
>>> 
>>> On Mon, 19 Dec 2022 at 15:11, Aleksey Yeshchenko  wrote:
 +1
 
> On 19 Dec 2022, at 13:42, Ekaterina Dimitrova  
> wrote:
> 
> +1
> 
> On Mon, 19 Dec 2022 at 8:30, J. D. Jordan  
> wrote:
>> +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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
>> >> Discussion: 
>> >> https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
>> >> 
>> >> The vote will be open for 72 hours.
>> >> Votes by committers are considered binding.
>> >> A vote passes if there are at least three binding +1s and no binding 
>> >> vetoes.
>> >> 
>> >> Thank you,
>> >> Branimir
 
> 
> 
> -- 
> Thanks & Regards,
> Saurabh Verma, 
> India
> 

Cassandra project status, Year in Review Holiday Edition

[Josh McKenzie]

As you may have heard, Cassandra-4.1 is GA! Congrats to everyone that worked 
hard to get this release out the door. I'm certain users of Cassandra are going 
to appreciate the new functionality in the release combined with the robust 
testing and validation we've all done on this so keep the high quality bar we 
set with 4.0

Downloads of the build can be found here: 
https://cassandra.apache.org/_/download.html

So year in review - I figured I'd snapshot a little data to see how we did in 
2022 in aggregate vs. 2021; some of this (plus quite a bit more) I hope to 
cover at the Cassandra Summit next spring in a talk (review board willing), but 
worth taking a moment to look back at the calendar year and see if any trends 
emerge.

Some stats from git:
2021:
35 unique contributors

https://github.com/apache/cassandra/graphs/contributors?from=2021-01-01&to=2021-12-31&type=c
Commits in the year sans Merge commits:
git log --after="2021-01-01" --before="2022-01-01" --oneline | grep -v 
"Merge branch" | wc -l
579
Files changed, additions, and deletions calendar year 2021:
git log --after="2021-01-01" --before="2021-12-31" --shortstat trunk | 
\ 
awk '/^ [0-9]/ { f += $1; i += $4; d += $6 } \  
   
END { printf("%d files changed, %d insertions(+), %d deletions(-)", f, 
i, d) }'
- 5125 files changed, 141894 insertions(+), 73409 deletions(-)% 

2022:
31 unique contributors

https://github.com/apache/cassandra/graphs/contributors?from=2022-01-01&to=2022-12-19&type=c
Commits in the year sans Merge commits:
git log --after="2022-01-01" --before="2022-12-19" --oneline | grep -v 
"Merge branch" | wc -l
564
Files changed, additions, and deletions calendar year 2022:
git log --after="2022-01-01" --before="2022-12-19" --shortstat trunk | 
\ 
awk '/^ [0-9]/ { f += $1; i += $4; d += $6 } \  
   
END { printf("%d files changed, %d insertions(+), %d deletions(-)", f, 
i, d) }'
- 5974 files changed, 321989 insertions(+), 63759 deletions(-)%

All told, some interesting vanity stats. Looks like things are continuing at a 
healthy pace on the project with a marked uptick in additions over the past 
year compared to the year prior. Marked as in "double". ;)


[To Pay Attention To]
We have three tickets that need committer attention: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20and%20resolution%20%3D%20unresolved%20and%20status%20%3D%20%22Needs%20Committer%22.
 The first 2 are a repeat from the last status email and the third is new:

CASSANDRA-17997: Improve git branch handling for CircleCI generate.sh
CASSANDRA-17861: Update Python test framework from nose to pytest in CCM
CASSANDRA-17797: All system properties and environment variables should be 
accessed via the new CassandraRelevantProperties and CassandraRelevantEnv 
classes

If you're a committer with some spare time please take a look at one of the 
above and see if you can help unstick them.

We have 20 tickets marked 4.0.x that could use a reviewer and 35 on 4.x: 
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&selectedIssue=CASSANDRA-17251&quickFilter=2259


[New Contributors Getting Started]
We currently have a curated list of 12 starter tickets that are unassigned on 
our current patch release version and the link can be found here: 
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2162&quickFilter=2454&quickFilter=2160

Another good option if you're looking to engage with the ecosystem, we have the 
official Cassandra Sidecar JIRA and open issues can be found here: 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRASC%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20assignee%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

The project can be cloned from the github repo here: 
https://github.com/apache/cassandra-sidecar

We hang out in #cassandra-dev on https://the-asf.slack.com and there's a 
@cassandra_mentors alias you can use to reach a bunch of us that have 
volunteered to help newcomers get situated. If you need an invite to the slack 
channel feel free to reply to just me on this email and I'll get you set up.

Here's reference explaining the various types of contribution: 
https://cassandra.apache.org/_/community.html#how-to-contribute
An overview of the C* architecture: 
https://cassandra.apache.org/doc/latest/cassandra/architecture/overview.html
The getting started contributing guide: 
https://cassandra.apache.org/_/development/index.html


[Dev list Digest]
https://lists.apache.org/list?dev@cassandra.apache.org:lte=23d:
We had a fairly thorough discussion about what constitutes an API change and 
when to bring things to the dev list proactively vs. lazy consensus that can be 
found here: https://lists.apache.org/thread/3n8lb1syrsmx89d10kyqz94zzdqhz3o5. I 
plan to poke th

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[C. Scott Andreas]

+1nbOn Dec 19, 2022, at 1:27 PM, Josh McKenzie  wrote:+1On Mon, Dec 19, 2022, at 11:54 AM, SAURABH VERMA wrote:+1On Mon, Dec 19, 2022 at 9:36 PM Benjamin Lerer  wrote:+1Le lun. 19 déc. 2022 
à 16:31, Andrés de la Peña  a écrit :+1On Mon, 19 Dec 2022 at 15:11, Aleksey Yeshchenko  wrote:+1On 19 Dec 2022, at 13:42, Ekaterina Dimitrova  wrote:+1On Mon, 
19 Dec 2022 at 8:30, J. D. Jordan  wrote:+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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format>> Discussion: https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh>> >> The vote will be open for 72 hours.>> 
Votes by committers are considered binding.>> A vote passes if there are at least three binding +1s and no binding vetoes.>> >> Thank you,>> Branimir-- Thanks & Regards,Saurabh Verma, India

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Jake Luciani]

+1

On Mon, Dec 19, 2022 at 7:27 PM C. Scott Andreas 
wrote:

> +1nb
>
> On Dec 19, 2022, at 1:27 PM, Josh McKenzie  wrote:
>
>
> +1
>
> On Mon, Dec 19, 2022, at 11:54 AM, SAURABH VERMA wrote:
>
> +1
>
> On Mon, Dec 19, 2022 at 9:36 PM Benjamin Lerer  wrote:
>
> +1
>
> Le lun. 19 déc. 2022 à 16:31, Andrés de la Peña  a
> écrit :
>
> +1
>
> On Mon, 19 Dec 2022 at 15:11, Aleksey Yeshchenko 
> wrote:
>
> +1
>
> On 19 Dec 2022, at 13:42, Ekaterina Dimitrova 
> wrote:
>
> +1
>
> On Mon, 19 Dec 2022 at 8:30, J. D. Jordan 
> wrote:
>
> +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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
> >> Discussion:
> https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
> >>
> >> The vote will be open for 72 hours.
> >> Votes by committers are considered binding.
> >> A vote passes if there are at least three binding +1s and no binding
> vetoes.
> >>
> >> Thank you,
> >> Branimir
>
>
>
>
> --
> Thanks & Regards,
> Saurabh Verma,
> India
>
>

-- 
http://twitter.com/tjake

Re: [VOTE] CEP-25: Trie-indexed SSTable format

[Dinesh Joshi]

+1

> On Dec 19, 2022, at 6:28 PM, Jake Luciani  wrote:
> 
> 
> +1
> 
>> On Mon, Dec 19, 2022 at 7:27 PM C. Scott Andreas  
>> wrote:
>> +1nb
>> 
>>> On Dec 19, 2022, at 1:27 PM, Josh McKenzie  wrote:
>>> 
>>> 
>>> +1
>>> 
 On Mon, Dec 19, 2022, at 11:54 AM, SAURABH VERMA wrote:
 +1
 
 On Mon, Dec 19, 2022 at 9:36 PM Benjamin Lerer  wrote:
 +1
 
 Le lun. 19 déc. 2022 à 16:31, Andrés de la Peña  a 
 écrit :
 +1
 
 On Mon, 19 Dec 2022 at 15:11, Aleksey Yeshchenko  wrote:
 +1
 
> On 19 Dec 2022, at 13:42, Ekaterina Dimitrova  
> wrote:
> 
> +1
> 
> On Mon, 19 Dec 2022 at 8:30, J. D. Jordan  
> wrote:
> +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/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format
> >> Discussion: 
> >> https://lists.apache.org/thread/3dpdg6dgm3rqxj96cyhn58b50g415dyh
> >> 
> >> The vote will be open for 72 hours.
> >> Votes by committers are considered binding.
> >> A vote passes if there are at least three binding +1s and no binding 
> >> vetoes.
> >> 
> >> Thank you,
> >> Branimir
 
 
 
 
 -- 
 Thanks & Regards,
 Saurabh Verma, 
 India
 
> 
> 
> -- 
> http://twitter.com/tjake