Re: [DISCUSSION] Next release roadmap

“Filter rows from system and system_schema based on users permissions” I think the issue match this improvement. https://issues.apache.org/jira/browse/CASSANDRA-15871 David Capwell 于2021年4月9日周五 上午3:56写道： > Here are two things I descoped from 4.0 and plan to pick up after 4.0 > release > >

Re: [DISCUSSION] Next release roadmap

+1 Brandon Williams 于2021年4月15日周四 上午4:48写道： > Agreed. Everyone just please keep in mind this thread is for roadmap > contributions you plan to make, not contributions you would like to > see. > > On Wed, Apr 14, 2021 at 3:45 PM Nate McCall wrote: > > > > Agree with Stefan 100% on this. We

Re: [DISCUSSION] Next release roadmap

besides do we need a table level backup and restore solution for cassandra ? https://issues.apache.org/jira/browse/CASSANDRA-15402

Re: [VOTE] Release Apache Cassandra 4.0.0

+1 Benjamin Lerer 于2021年7月13日周二 下午4:12写道： > +1 > > Le mar. 13 juil. 2021 à 08:19, Mick Semb Wever a écrit : > > > Proposing the test build of Cassandra 4.0.0 for release. > > > > sha1: 69b8cc5cecc196fddb549f2edf01d962e7ef2dae > > Git: > > > > >

Re: [VOTE] Release Apache Cassandra 4.0.0 (take2)

+1 Paulo Motta 于2021年7月14日周三 下午7:03写道： > +1 > > Em qua., 14 de jul. de 2021 às 05:10, Benjamin Lerer > escreveu: > > > +1 > > > > Le mer. 14 juil. 2021 à 09:48, Mick Semb Wever a écrit > : > > > > > > > > > > The vote will be open for 72 hours (longer if needed). Everyone who > > > > has

Re: [VOTE] Release Apache Cassandra 5.0-alpha1 (take3)

+1 Berenguer Blasi 于2023年9月7日周四 15:27写道： > +1 > On 4/9/23 22:28, Mick Semb Wever wrote: > > > 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

Re: [DISCUSS] CommitLog default disk access mode

Strongly agree with this point of view that direct IO can bring great benefits. I have reviewed part of the code, and my preliminary judgment is that it is not very common and limited in some situations, for example, it works for commitlog's write path only for this patch.So I suggest that the

Re: [DISCUSS] CommitLog default disk access mode

-1 I still think we should keep it as it is until the direct io for commitlog (read and write) is ready and relatively stable. And then we may change the default value to direct io from mmap in a future version, such as 5.2, or 6.0. Pawar, Amit 于2023年10月17日周二 19:03写道： > [AMD Official Use Only

Re: [EXTERNAL] Re: [VOTE] Release Apache Cassandra 5.0-alpha2

+1 German Eichberger via dev 于2023年11月1日周三 04:58写道： > +1 > > Heck, yeah, we already tested the branch (build ourselves) and it works > great so far. > -- > *From:* Mick Semb Wever > *Sent:* Tuesday, October 31, 2023 1:43 PM > *Cc:* dev > *Subject:* [EXTERNAL] Re:

Re: CASSANDRA-18941 produce size bounded SSTables from CQLSSTableWriter

 Chris Lohfink 于2023年10月25日周三 05:02写道： > +1 > > On Tue, Oct 24, 2023 at 11:24 AM Brandon Williams > wrote: > >> +1 >> >> Kind Regards, >> Brandon >> >> On Mon, Oct 23, 2023 at 6:22 PM Yifan Cai wrote: >> > >> > Hi, >> > >> > I want to propose merging the patch in CASSANDRA-18941 to 4.0 and

Re: [DISCUSS] CommitLog default disk access mode

Thanks for your contribution  Pawar, Amit 于2023年10月26日 周四下午11:41写道： > [Public] > > Default behavior is not changed. Thank you, Josh for your appreciation. > This is my first patch, and it means lot to me. > > > > Thanks again, > > Amit > > > > +1 to adding the feature, clear and easy

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

Do I need permission to view this link? When I open it, an error appears, saying “It may have been deleted or you don't have permission to view it.” Benjamin Lerer 于2023年11月6日周一 18:34写道： > I created a Dashboard to track the progress and remaining tasks for 5.0: >

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

"Rather than building this piece by piece, I think it'd be awesome if someone drew up an end-to-end plan to implement tiered storage, so we can make sure we're discussing the whole final state, and not an implementation detail of one part of the final state?" Do agree with jeff for this ~~~ If

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

g > views into larger remotely stored files. > 2. Requiring a complete file to upload rather than using the > partial upload capability of the S3 interface. > > > > On Tue, Sep 26, 2023 at 4:11 AM guo Maxwell wrote: > >> "Rather than building this piec

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

d before I think that there may be a need for a > java.nio.FileSystem implementation for the proxies but I have not had the > time to dig into it yet. > > Claude > > > On Tue, Sep 26, 2023 at 9:01 AM guo Maxwell wrote: > > In my mind , it may be better to support

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

Thanks , So I think a jira can be created now. And I'd be happy to provide some help with this as well if needed. Henrik Ingo 于2023年9月28日周四 00:21写道： > It seems I was volunteered to rebase the Astra implementation of this > functionality (FileSystemProvider) onto Cassandra trunk. (And publish

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

Great suggestion, Can external storage only be local storage media? Or can it be stored in any storage medium, such as object storage s3 ? We have previously implemented a tiered storage capability, that is, there are multiple storage media on one node, SSD, HDD, and data placement based on

Re: [VOTE] Accept java-driver

+1 Benedict 于2023年10月7日周六 18:27写道： > +1 > > On 7 Oct 2023, at 10:03, Mick Semb Wever wrote: > >  > > LEGAL-658 > > > On Fri, 6 Oct 2023 at 17:43, J. D. Jordan > wrote: > >> The software grant agreement covers all donated code. The ASF does not >> need any historical agreements. The

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

Also >>>> is your code available somewhere? >>>> >>>> After looking at the code some more I think that the best solution is >>>> not a FileChannelProxy but to modify the Cassandra File class to get a >>>> FileSystem object for a Factory

Re: [DISCUSS] Change the useage of nodetool tablehistograms

On 23/03/2023 13:40, guo Maxwell wrote: > > firstly I think anything existing must be reasonable，so ignore option for > tablestats must be a need for the user to use. at least I used it some time > ； > secondly in order to keep this as simple as possible ，I think left the >

Re: [DISCUSS] CommitLog default disk access mode

I think what we should do is provide options, and let users make their own decisions. The default behavior should not be modified until some future released version. Pawar, Amit 于2023年10月16日周一 15:51写道： > [Public] > > Hi, > > > > CommitLog uses mmap (memory mapped ) segments by default.

Re: CASSANDRA-18941 produce size bounded SSTables from CQLSSTableWriter

+1, but I want to know why only trunk and 4.0 ? not all the versions involved, like 4.1 ,5.0 。 Francisco Guerrero 于2023年10月24日周二 07:47写道： > +1 (nb). I think this is a great addition to offline tools that use > SSTable writer in general. > > On 2023/10/23 23:21:13 Yifan Cai wrote: > > Hi, > > >

Re: [jira] [Commented] (CASSANDRA-17380) Add support for EXPLAIN statements

i would like to work on this issue if no one is working on this Paulo Motta (Jira) 于2022年5月23日 周一下午10:07写道： > > [ > https://issues.apache.org/jira/browse/CASSANDRA-17380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540970#comment-17540970 > ] > > Paulo Motta

Re: Event Report -- Cassandra Day China 2022 was a big success

thank you tom，and hoping there will be more and more Cassandra users in China. Mick Semb Wever 于2022年12月28日 周三上午5:04写道： > > Thank you all again for introducing and approving of this Cassandra Day > China event, we also thank the people at China Golden Bridge for their > dedication throughout

Re: Should we change 4.1 to G1 and offheap_objects ?

same with David Capwell，+1 on updating NEWS in 4.1.x and really change in 4.x /5.0 David Capwell 于2023年1月13日 周五上午3:11写道： > I am cool with updating NEWS in 4.1.1 to recommend the change and change > it in 4.2/5.0 > > > On Jan 12, 2023, at 10:56 AM, Josh McKenzie wrote: > > Potential compromise:

Re: [VOTE] Release Apache Cassandra 4.1.0 (take2)

+1 Jeremiah D Jordan 于2022年12月10日 周六上午5:59写道： > +1 nb > > > On Dec 7, 2022, at 3:40 PM, Mick Semb Wever wrote: > > > Proposing the (second) test build of Cassandra 4.1.0 for release. > > sha1: f9e033f519c14596da4dc954875756a69aea4e78 > Git: >

Re: [VOTE] Release Apache Cassandra 4.1.0 GA

+1 Mick Semb Wever 于2022年12月5日 周一下午5:33写道： > > Proposing the test build of Cassandra 4.1.0 GA for release. > > sha1: b807f97b37933fac251020dbd949ee8ef245b158 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.0-tentative > Maven Artifacts: >

Re: [DISCUSS] Change the useage of nodetool tablehistograms

if they have more complex or > specific need. > > For example, in this case: > > *> 6.nodetool tablehistograns -i -tbs ks.tb1 ks.tb2 -ks ks1 // print out > list tables' histograms except for table in ks.tb1 ks.tb2 and all tables in > ks1* > > The same result

Re: Welcome our next PMC Chair Josh McKenzie

Congratulations to Josh McKenzie !!! Mick Semb Wever 于2023年3月23日周四 16:23写道： > It is time to pass the baton on, and on behalf of the Apache Cassandra > Project Management Committee (PMC) I would like to welcome and congratulate > our next PMC Chair Josh McKenzie (jmckenzie). > > Most of you

Re: [DISCUSS] Change the useage of nodetool tablehistograms

enough if the above can cover the majority of use cases. The > remaining use cases can be dealt with individually, by multiple invocations > of the same command or providing it with a script-generated list of tables > in the format. > > TL;DR: The KISS principle <https://en.wikip

Re: [DISCUSS] Change the useage of nodetool tablehistograms

eak when the software is upgraded. > We can just add a line to the NEWS.txt and let them update their scripts. > > > On 16/03/2023 08:53, guo Maxwell wrote: > > Hello everyone : > The nodetool tablehistograms have one argument which you can fill with > only one table name wit

Re: [EXTERNAL] Re: Cassandra CI Status 2023-01-07

local expiration time should not be negative > > > > On Tue, 21 Feb 2023 at 03:41, guo Maxwell wrote: > > > > Hi all : > > Here comes Cassandra CI status for 2023-2-13 - 2023-2-17 : > > > > *** CASSANDRA-18274 - Test > Failures:org.apache.cassandra.u

[DISCUSS] Change the useage of nodetool tablehistograms

Hello everyone : The nodetool tablehistograms have one argument which you can fill with only one table name with the format "keyspace_name.table_name /keyspace_name table_name", so that you can get the table histograms of the specied table. And if none arguments is set, all the tables'

Re: [jira] [Updated] (CASSANDRA-18305) Enhance nodetool compactionstats with existing MBean metrics

Had a similar need early and have been trying to solve it. Looking forward to this patch. Brad Schoening (Jira) 于2023年3月8日 周三下午12:15写道： > > [ > https://issues.apache.org/jira/browse/CASSANDRA-18305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Brad Schoening

Re: [jira] [Commented] (CASSANDRA-17698) sstabledump errors when dumping data from index

for old version‘s index data using this version’s dump code ，I think there will not be much difference（may be only exception message‘s difference），It is backwards compactibility I think .But I change the content of sstable（adding a new base type for partitionordertype）. Benedict Elliott Smith

Re: Downgradability

It seems “An alternative solution is to implement/complete CASSANDRA-8110 ” can give us more options if it is finished Branimir Lambov 于2023年2月20日 周一下午11:03写道： > Hi everyone, > > There has been a discussion lately about changes to the

Re: [EXTERNAL] Re: Cassandra CI Status 2023-01-07

Hi all : Here comes Cassandra CI status for 2023-2-13 - 2023-2-17 : *** CASSANDRA-18274 - Test Failures:org.apache.cassandra.utils.binlog.BinLogTest.testTruncationReleasesLogSpace-compression -linked in 4.1 Other tests below are time out

Re: [DISCUSS] Introduce DATABASE as an alternative to KEYSPACE

learning > Cassandra from understanding the replication. > > There are probably many small projects where Cassandra is used on a > single node, or bigger projects where people > > try different things to make some PoC. Understanding the internals, > architecture of Cassandra i

Re: [DISCUSS] Introduce DATABASE as an alternative to KEYSPACE

either KEYSPACE or DATABASE or SCHEMA is better than NAMESPACE NAMESPACE is always used in hbase which is a table store in my mind. For existing users, NAMESPACE may take some time to be accepted. For hbase and cassandra users, it may be necessary to mix the corresponding terms. >From the

Re: [DISCUSS] Introduce DATABASE as an alternative to KEYSPACE

; replication config, like simple 1, so that > creating a names boils down to a simply CREATE > KEYSPACE|SCHEMA|DATABASE|NAMESPACE ; > > thanks, > - - -- --- - ----- > Jacek Lewandowski > > > czw., 6 kwi 2023 o 04:09 guo Maxwell napisał(a): > >>

Re: [VOTE] CEP-21 Transactional Cluster Metadata

+1 Yifan Cai 于2023年2月8日 周三下午4:11写道： > +1 > -- > *From:* Jon Haddad > *Sent:* Tuesday, February 7, 2023 4:55:51 PM > *To:* dev@cassandra.apache.org > *Subject:* Re: [VOTE] CEP-21 Transactional Cluster Metadata > > +1 > > On 2023/02/06 16:15:19 Sam Tunnicliffe wrote:

Re: [DISCUSS] CEP-28: Reading and Writing Cassandra Data with Spark Bulk Analytics

This is a very meaningful work, thanks , but I would like to ask a question that is not particularly related to the cep project's code design itself but the project engineering management : what is the future development and release plan of this project? As far as I know, project Cassandra Sidecar

Re: CASSANDRA-18654 - start publishing CQLSH to PyPI as part of the release process

Hi ： First of all, thank you very much for your work. I have a question: what is your long-term evolution plan for this project? How to achieve long-term continuous maintenance of this project? I have encountered some situations where some people's work is related to a certain project, and then

Re: [VOTE] CEP-30 ANN Vector Search

+1 Dinesh Joshi 于2023年5月26日 周五上午11:08写道： > +1 > > > On May 25, 2023, at 8:45 AM, Jonathan Ellis wrote: > >  > > Let's make this official. > > CEP: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-30%3A+Approximate+Nearest+Neighbor%28ANN%29+Vector+Search+via+Storage-Attached+Indexes

Re: Who wants a free Cassandra t-shirt?

It seems I‘ve never had one…  Patrick McFadin 于2023年7月22日 周六上午8:48写道： > We have about another week left on the user survey I posted last week. The > response has been slow, so it's time to get things in gear. > > I found a box of Cassandra t-shirts that will make an excellent thank you > for

Re: [DISCUSS] Creating a 5.0 landing page

Can we have some pages for 5.0 in Chinese？If we can，I can do some help to doing some translation ！ Ekaterina Dimitrova 于2023年8月4日 周五上午10:55写道： > I honestly didn’t realize events page was added already. Thank you, Josh! > > So yes, in that case I guess that is what I am asking - shall we add there

Re: [VOTE] CEP 33 - CIDR filtering authorizer

+1 Nate McCall 于2023年6月29日 周四上午9:25写道： > +1 > > On Wed, Jun 28, 2023 at 5:17 AM Shailaja Koppu wrote: > >> Hi Team, >> >> (Starting a new thread for VOTE instead of reusing the DISCUSS thread, to >> follow usual procedure). >> >> Please vote on CEP 33 - CIDR filtering authorizer >>

Re: [VOTE] CEP-8 Datastax Drivers Donation

+1 Jake Luciani 于2023年6月14日周三 09:21写道： > +1 > > On Tue, Jun 13, 2023 at 7:14 PM Nate McCall wrote: > >> +1 >> >> On Wed, Jun 14, 2023 at 2:15 AM Jeremy Hanna >> wrote: >> >>> Calling for a vote on CEP-8 [1]. >>> >>> To clarify the intent, as Benjamin said in the discussion thread [2], >>> the

Re: [DISCUSS] The future of CREATE INDEX

+1 , as we must Improve the image of your own default indexing ability. and As for *CREATE CUSTOM INDEX *, should we just left as it is and we can disable the ability for create SAI through *CREATE CUSTOM INDEX* in some version after 5.0? for as I know there may be users using this as a

Re: [DISCUSS] The future of CREATE INDEX

> > [POLL] Centralize existing syntax or create new syntax? 1.) CREATE INDEX ... USING WITH OPTIONS... and I think we should keep CREATE CUSTOM INDEX [POLL] Should there be a default? (YES/NO) of course YES [POLL] What do do with the default? 4.) YAML config/guardrail to require

Re: [DISCUSS] CEP-28: Reading and Writing Cassandra Data with Spark Bulk Analytics

Thanks Dinesh ， That will be great. Dinesh Joshi 于2023年5月4日 周四下午11:06写道： > Hi Guo, > > I would expect that there would be release artifacts for the sidecar as > well as the library once this functionality is available. > > Dinesh > > On May 4, 2023, at 12:0

Re: [DISCUSS] Replace Sigar with OSHI (CASSANDRA-16565)

+1 too Mick Semb Wever 于2023年12月15日周五 10:01写道： > > > >> >> Are there objections to making this switch and adding a new dependency? >> >> [1] https://github.com/apache/cassandra/pull/2842/files >> [2] https://issues.apache.org/jira/browse/CASSANDRA-16565 >> > > > > +1 to removing sigar and to

Re: Welcome Mike Adamson as Cassandra committer

Congrats Mike! Jasonstack Zhao Yang 于2023年12月9日周六 20:59写道： > Congrats Mike! > > On Sat, 9 Dec 2023 at 8:47 PM, Piotr Kołaczkowski > wrote: > >> Congratulations, Mike! Well deserved, working with you has always been a >> pleasure! >> >> >> Wiadomość napisana przez Melissa Logan w dniu >>

Re: [DISCUSS] CEP-39: Cost Based Optimizer

Nothing expresses my thoughts better than +1 ，It feels like it means a lot to Cassandra. I have a question. Is it easy to turn off cbo's optimizer or by pass in some way? Because some simple read and write requests will have better performance without cbo, which is also the advantage of Cassandra

Re: [DISCUSS] CEP-39: Cost Based Optimizer

ancy of our prepared query > cache. > > > > > > On 13 Dec 2023, at 00:44, Jon Haddad wrote: > > > >  > > I think it makes sense to see what the actual overhead is of CBO before > making the assumption it'll be so high that we need to have two code >

Re: Welcome Maxim Muzafarov as Cassandra Committer

Congratulations, Maxim! Francisco Guerrero 于2024年1月9日周二 09:00写道： > Congratulations, Maxim! Well deserved! > > On 2024/01/08 18:19:04 Josh McKenzie wrote: > > The Apache Cassandra PMC is pleased to announce that Maxim Muzafarov has > accepted > > the invitation to become a committer. > > > >

Re: Welcome Francisco Guerrero Hernandez as Cassandra Committer

Congrats! Jacek Lewandowski 于2023年11月29日周三 06:16写道： > Congrats!!! > > wt., 28 lis 2023, 23:08 użytkownik Abe Ratnofsky napisał: > >> Congrats Francisco! >> >> > On Nov 28, 2023, at 1:56 PM, C. Scott Andreas >> wrote: >> > >> > Congratulations, Francisco! >> > >> > - Scott >> > >> >> On Nov

Re: Include CASSANDRA-18464 in 5.0-beta1 (direct I/O support for commitlog write)

+1  Brandon Williams 于2023年11月27日周一 22:25写道： > As long as it's disabled by default that's an easy +1 from me. > > Kind Regards, > Brandon > > On Mon, Nov 27, 2023 at 7:03 AM Jacek Lewandowski > wrote: > > > > Hey, > > > > I'd like to ask if we can include >

Re: Downgradability

Hello everyone : What is the final conclusion of this discuss ? As https://issues.apache.org/jira/browse/CASSANDRA-18934 has been created , and we know that for system table of different c* version , the schema info may be different as we may add or delete column or modify the table properties in

Re: [DISCUSS] New CQL command/option for listing roles with superuser privileges

Hi , 1. can this cql "SELECT role from system_auth.roles where is_superuser = True ALLOW FILTERING ;" meet your needs if the user to execute the cql have the right to do so ？ 2. I think may be we can also add the ability to filter on list role/user grammar, for example : list user where super