Re: [VOTE] Simplifying our release versioning process

> > We have already agreed some time ago that any incompatible API change > requires a DISCUSS thread. I’m fairly sure it’s documented on the wiki. Yes, I remembered that we already have a thread to reach consensus on this. +1 on this vote. Mick Semb Wever 于2025年4月22日周二 13:35写道： > > . > >

Re: [DISCUSS] 5.1 should be 6.0

+1 to 6.0 Berenguer Blasi 于2025年4月11日周五 13:53写道： > +1 6.0 > On 10/4/25 23:57, David Capwell wrote: > > +1 to 6.0 > Strong +1 to T-3, we should support 4.0/4.1 to 6.0 upgrades. > > On Apr 10, 2025, at 2:18 PM, C. Scott Andreas > wrote: > > +1 6.0 > > - Scott > > — > Mobile > > On Apr 10, 2025,

Re: Huge NetApp donation of hardware for ci-cassandra

Thanks so much!!! Berenguer Blasi 于2025年3月20日周四 14:53写道： > Thanks a million! > > On 19/3/25 20:03, Francisco Guerrero wrote: > > wow! This is big! Thanks for the donation to the project. > > > > On 2025/03/19 15:50:34 Mick Semb Wever wrote: > >> Under a ASF targeted sponsorship, NetApp (Inst

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

Thank you very much, I'm certainly interested. I'll start working on the update for cep-36 next week. Mick Semb Wever 于2025年3月7日 周五下午7:07写道： > > > On Thu, 6 Mar 2025 at 09:40, Štefan Miklošovič > wrote: > >> That is cool but this still does not show / explain how it would look >> like when it c

Re: Welcome Ekaterina Dimitrova as Cassandra PMC member

Congratulations！ Rahul Singh (ANANT) 于2025年3月5日 周三上午5:15写道： > Congrats Ekaterina! > > Sent via Superhuman iOS > > > On Tue, Mar 4, 2025 at 3:57 PM, Aaron wrote: > >> Welcome Ekaterina! Congratulations!!! >> >> On Tue, Mar 4, 2025 at 2:50 PM Yifan Cai w

Re: Welcome Aaron Ploetz as Cassandra Committer

Congratulations Aaron! Aaron 于2025年3月4日 周二下午10:06写道： > Thank you everyone! > > Aaron > > > On Tue, Mar 4, 2025 at 7:02 AM J. D. Jordan > wrote: > >> 🎉 >> >> On Mar 4, 2025, at 5:49 AM, Ekaterina Dimitrova >> wrote: >> >>  >> Congrats!!! 🎉 >> >> On Tue, 4 Mar 2025 at 6:11, Josh McKenzie wrote:

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

ompaction > strategies like TWCS to migrate data older than a threshold from a local > filesystem to remote object. > >>> > >>> It’s not an area where I can currently dedicate engineering effort. > But if others are interested in contributing a feature like this, I

Re: Welcome Bernardo Botella as Cassandra Committer

Congratulations Bernardo ! 😀 Štefan Miklošovič 于2025年3月4日周二 15:32写道： > The Project Management Committee (PMC) for Apache Cassandra has invited > Bernardo Botella to become a committer and we are pleased to announce that > he has accepted. > > Please join us in welcoming Bernardo Botella to his

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

Is anyone else interested in continuing to discuss this topic? guo Maxwell 于2024年9月20日周五 09:44写道： > I discussed this offline with Claude, he is no longer working on this. > > It's a pity. I think this is a very valuable thing. Commitlog's archiving > and restore may be ab

Re: Welcome Caleb Rackliffe to the PMC

Congratulations Caleb! Berenguer Blasi 于2025年2月21日周五 14:37写道： > Congrats Sir :-) > > On 21/2/25 2:04, Brandon Williams wrote: > > Congratulations Caleb! > > > > Kind Regards, > > Brandon > > > > On Thu, Feb 20, 2025 at 4:06 PM Jon Haddad > wrote: > >> The PMC for Apache Cassandra is delighted t

Re: New committers: Maxwell Guo and Dmitry Konstantinov

Thank you to the PMC members, committers and everyone who have helped me with their advice and reviews. 😀 Jon Haddad 于2025年2月21日周五 08:56写道： > Welcome!! > > On Thu, Feb 20, 2025 at 4:21 PM Patrick McFadin > wrote: > >> Welcome and congratulations Maxwell and Dmitry! >> >> On Thu, Feb 20, 2025 at

Re: Welcome Jeremiah Jordan to the PMC

Congrats！ Tolbert, Andy 于2025年2月15日 周六上午6:22写道： > Congrats JD! > > On Fri, Feb 14, 2025 at 4:13 PM wrote: > >> Congratulations, well deserved! >> >> El 14 feb 2025, a las 20:40, Alex Petrov escribió: >> >>  >> Congratulations! >> >> On Fri, Feb 14, 2025, at 7:33 PM, Josh McKenzie wrote: >> >> C

Re: Merging compaction improvements to 5.0

the best buffer size that’s awesome. We could document which is suggested > for the community. I don’t think it’s necessary to block on that however. > > Also I am of course +1 to including this in 5.0. > > Jordan > > On Wed, Feb 12, 2025 at 19:50 guo Maxwell wrote: > &g

Re: Merging compaction improvements to 5.0

u give me an > example of what you think might be different here? This is already one of > the most well tested and documented performance patches ever contributed to > the project. > > On Wed, Feb 12, 2025 at 4:26 PM guo Maxwell wrote: > >> I think it should be tested on

Re: Merging compaction improvements to 5.0

I think it should be tested on most cloud platforms（at least aws、azure、gcp） before merged into 5.0 . Just like CASSANDRA-19488. Paulo Motta 于2025年2月13日 周四上午6:10写道： > I'm looking forward to these improvements, compaction needs tlc. :-) > A couple of questions: > > Has this been tested only on EB

Re: [DISCUSS] NOT_NULL constraint vs STRICTLY_NOT_NULL constraint

I think it may be better to use LOOSE_NOT_NULL instead of NOT_NULL. The reason is: NOT_NULL can easily make users think that it is a related function of MYSQL, but in fact we are different. Changing a different name may avoid users' preconceived feelings. Dinesh Joshi 于2025年2月11日周二 01:55写道： > On

Re: 【DISCUSS】What is the current status of triggers in Cassandra ?

sing specific columns, what would happen if a target table altered > its schema after we copy it (e.g. by adding or removing columns) while this > trigger would be active? And so on, and so on ... > > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandr

Re: 【DISCUSS】What is the current status of triggers in Cassandra ?

Referring to the opinions of most people, we ignore the cloning of triggers just for the CREATE TABLE LIKE feature. guo Maxwell 于2025年2月10日周一 16:39写道： > Then we don’t support trigger until CASSANDRA-20287 is fixed, and this > rule applies to custom index , too. right ? > > > Sam

Re: 【DISCUSS】What is the current status of triggers in Cassandra ?

Then we don’t support trigger until CASSANDRA-20287 is fixed, and this rule applies to custom index , too. right ? Sam Tunnicliffe 于2025年2月5日周三 01:24写道： > This is really a bug with the current implementation of > CreateTriggerStatement and I've filed CASSANDRA-20287 to address it. > > Thanks, >

Re: [DISCUSS] Fine grained max size guardails

Agree with you. Both Constraints and Guardails are valuable. Users can have their own choices, and what we need is to provide valuable choices for them. Brandon Williams 于2025年2月9日 周日上午4:07写道： > On Sat, Feb 8, 2025 at 2:04 PM Bernardo Botella > wrote: > > My two cents: My opinion is that these

Re: [VOTE] CEP-45: Mutation Tracking

+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 >

Re: 【DISCUSS】What is the current status of triggers in Cassandra ?

>> If a user copies a table like this, then, sure, a trigger will be > copied as well, but it will not match anymore. > >> > >> My argument against supporting copying triggers is that when we can not > guarantee that it will work _in all cases_, then I would say that w

【DISCUSS】What is the current status of triggers in Cassandra ?

Hello dev, I'm very sorry to disturb everyone's wonderful weekend time. Please allow me to ask about the trigger in Cassandra? Maybe everyone knows some implementations of Cassandra's trigger. If the user needs it to do something, it may be necessary to package the jar we need and load the corre

Re: [Committer/reviewer needed] Request for Review of Cassandra PRs

I have added you as a reviewer of CASSANDRA-11303, you can do that for CASSANDRA− <https://issues.apache.org/jira/browse/CASSANDRA-20097>20097 <https://issues.apache.org/jira/browse/CASSANDRA-20097> by yourself. guo Maxwell 于2025年1月17日周五 14:10写道： > Hi Wang, > I think Runtian

Re: [Committer/reviewer needed] Request for Review of Cassandra PRs

Hi Wang, I think Runtian should change the ticket 's status ,submit a pr , then you can add yourself as a reviewer. Cheng Wang via dev 于2025年1月17日周五 14:05写道： > I can review the CASSANDRA-19248 first since it looks straight forward. > For CASSANDRA−11303 and CASSANDRA− >

Re: Checkstyle as style contract for Cassandra

I agree with you for all these two points. I think you should open a ticket to solve this if you want to add a rule to checkstyle, as I know there are many old codes that do not comply with this rule. For point 2, this really feels like personal preference, but I'd probably listen to the reviewer'

Re: [DISCUSS] CEP-45: Mutation Tracking

After a brief understanding, there are 2 questions from me, If I ask something inappropriate, please feel free to correct me : 1、 Does it support changing the table to support mutation tracking through ALTER TABLE if it does not support mutation tracking before? 2、 > Available options for tables

Re: [DISCUSS] Index selection syntax for CASSANDRA-18112

imization logic. > I strongly believe that the proper solution for query optimization is what > was proposed in CEP-39: a cost based query optimizer located on the > coordinator. > Unfortunately do not have the time to work on it. > > > Le lun. 23 déc. 2024 à 07:11, guo Maxwell a

Re: [DISCUSS] Index selection syntax for CASSANDRA-18112

Wrong typing, it is DML not DDL ~~~😅 guo Maxwell 于2024年12月23日周一 11:56写道： > Thanks Caleb for bringing it up. > > When I opened this issue, I originally wanted to propose the following > syntax: > 1、When we want to force the selection of certain indexes: > SELECT ...USE INDEX

Re: [DISCUSS] Index selection syntax for CASSANDRA-18112

Thanks Caleb for bringing it up. When I opened this issue, I originally wanted to propose the following syntax: 1、When we want to force the selection of certain indexes: SELECT ...USE INDEX (ks.idx1, ks.idx2) ... FROM ...WHERE ... or SELECT .../*+ USE INDEX (ks.idx1, ks.idx2)*/ ... FROM

Re: [DISCUSS] Deprecation of IEndpointSnitch (CASSANDRA-19488)

node joing/decommission; 2、create keyspace and table then doing some insert and select; 3、nodetool ring/status/cms； All results are correct, the dc is c-hangzhou, rack is : b Thanks Sam ! guo Maxwell 于2024年12月12日周四 21:47写道： > Hi sam > I can help with the validation of AlibabaCloudSnith. >

Re: [DISCUSS] Deprecation of IEndpointSnitch (CASSANDRA-19488)

Hi sam I can help with the validation of AlibabaCloudSnith. Sam Tunnicliffe 于2024年12月12日 周四下午9:20写道： > This patch is probably now ready to merge, having been through several > iterations of review and with green CI. Before that though, I just want to > send one more reminder about it. We've endea

Re: [VOTE] CEP-43: Apache Cassandra CREATE TABLE LIKE

52, Benjamin Lerer wrote: >> >>> +1 >>> >>> Le ven. 8 nov. 2024 à 18:31, Yifan Cai a écrit : >>> >>>> +1 (nb) >>>> >>>> - Yifan >>>> >>>> On Thu, Nov 7, 2024 at 10:31 PM guo Maxwell >>>&g

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

ons is just a pure >> addition to that syntax. Everything stays, we would just expand this. Hence >> from the user's perspective it would be just an extension of this whole >> feature. >> >> Supporting the 5 examples is OK. It is crucial that the options of a >

Re: [VOTE] CEP-43: Apache Cassandra CREATE TABLE LIKE

f. >> >> I advise you to wait a little bit longer until at least three binding >> votes accumulate. >> >> Regards >> >> On Thu, Nov 7, 2024 at 4:42 PM guo Maxwell wrote: >> >>> Thank you everyone. If there is no other feedback, I feel that t

Re: [VOTE] CEP-43: Apache Cassandra CREATE TABLE LIKE

> Having all cleared out in discussion thread (1), I think we can finally > vote on this. > > +1 > > I welcome everybody to finish this vote or raise other issues in the > discussion thread if any. > > (1) https://lists.apache.org/thread/2z09twbrv75rszpxbm1przxxohpjvkk

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

Any update on this ?If there are no updates, I wonder if we can start a new update on the VOTE thread. guo Maxwell 于2024年11月5日周二 19:23写道： > Hello, everyone. > I have a point of view that our CREATE TABLE LIKE grammar should not > support the setting of table options, like : > >

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

a table is to copy the table, and support what is to or not to copy during the copying process. Not changing the options at the same time. WDYT ? guo Maxwell 于2024年11月5日周二 14:07写道： > Hi，stefan and Dave, > I do not intend to implement the BNF of COPY TABLE based on the BNF of > CREA

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

tion details for now. > > CREATE TABLE cycling.cyclist_name4 LIKE cycling.cyclist_name > WITH TRIGGERS > AND VIEWS > AND compaction = { 'class' : 'LeveledCompactionStrategy' } > AND default_time_to_live = 86400; > > In other words, it will copy all

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

ned in CEP for > being explicit about our intentions. > > After this is all reflected, I will be glad to vote on this CEP in the > other thread. > > (1) https://lists.apache.org/thread/d485w6lxvpoztmjnxj8msj0jjt3d5ltk > (2) https://lists.apache.org/thread/odc1s1pt5m2tk76owxq61

Re: [VOTE] CEP-43: Apache Cassandra CREATE TABLE LIKE

t;> >> Do you think it would make sense to add a fourth keyword to add after the >> WITH for Constraints? (See CEP-42) >> >> Copying a table without the defined constraints may be useful. >> >> Bernardo >> >> >> On Oct 9, 2024, at 9:32 PM, guo M

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

So we should be able to start voting on this now. guo Maxwell 于2024年10月28日周一 17:20写道： > Here is the latest updated CEP-43 > <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-43++Apache+Cassandra+CREATE+TABLE++LIKE> > > > guo Maxwell 于2024年10月24日周四 19:53写道： >

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

Here is the latest updated CEP-43 <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-43++Apache+Cassandra+CREATE+TABLE++LIKE> guo Maxwell 于2024年10月24日周四 19:53写道： > yes，you are right. I will add this > > Štefan Miklošovič 于2024年10月24日 周四下午4:42写道： > >> The CEP

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

at 7:16 AM Dave Herrington > wrote: > >> Strong +1 to copy all options by default. This is intuitive to me. Then >> I would like to explicitly override any options of my choosing. >> >> -Dave >> >> On Wed, Oct 23, 2024 at 9:57 PM guo Maxwell wrote: >> &

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

;but I think there are also some users want to do basic column >> information copy" >> >> where is this coming from? Do you have this idea somehow empirically >> tested? I just do not see why somebody would want to have Cassandra's >> defaults instead of what

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

would >> I want to have a copy of a table with options different from the base one? >> >> >> On Mon, Oct 21, 2024 at 3:55 PM Bernardo Botella < >> conta...@bernardobotella.com> wrote: >> >>> Hi Guo, >>> >>> +1 for the CONST

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

I think the CONSTRAINTS keyword keyword may be in the same situation as datamask. Maybe it is better to include constraints into the default behavior of table copy together with column name, column data type and data mask. guo Maxwell 于2024年10月21日周一 14:56写道： > To yifan : > I don&

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

a+CREATE+TABLE++LIKE> . We gave up PG-related grammar, including INCLUDING/EXCLUDING and so on . guo Maxwell 于2024年10月21日周一 14:52写道： > Hi , > To sefan : > I may want to explain that if there is no OPTION keyword in the CQL > statement, then the newly created table will only have

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

gt;>>>>>> >>>>>>> >>>>>>> My assumption of using WITH which I think I proposed first (4th post >>>>>>> in this thread) was to just blindly copy the most important "parts" >>>>>>> lo

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

>> schema? >>> >>> For instance, CREATE TABLE new_table LIKE original_table WITH ALL, it >>> replicates options, indexes, triggers, constraints and any applicable kinds >>> that are introduced in the future. >>> >>> - Yifan >>> >

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

Disscussed with Bernardo on slack，and +1 with his advice on adding a fourth keyword. The keyword would be CONSTRAINTS ， any more suggestion ？ guo Maxwell 于2024年10月16日 周三上午9:55写道： > Hi yifan, > Thanks for bringing this up. The SELECT permission on the original table > is needed. Mys

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

or CREATE TABLE LIKE. > > - Yifan > > On Sun, Sep 29, 2024 at 11:01 PM guo Maxwell wrote: > >> Hello, everyone , >> I have finished the doc for CEP-43 for CREATE_TABLE_LIKE >> <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-43++Apache+Cassand

Re: [VOTE] CEP-43: Apache Cassandra CREATE TABLE LIKE

ok, I think the time can be two weeks . Looking forward to your feedback. Abe Ratnofsky 于2024年10月10日周四 11:51写道： > With the CEP only being completed last week and the Community over Code > conference finishing up this week, I'd love to have a few more days to > review and discuss the proposal.

[VOTE] CEP-43: Apache Cassandra CREATE TABLE LIKE

Hi everyone, I would like to start the voting for CEP-43 as all the feedback in the discussion thread seems to be addressed. Proposal: CEP43-CREATE TABLE LIKE Discussion thread: discussion

Re: 【DISCUSS】The configuration of Commitlog archiving

ies of steps to an already compromised database. I don't > view either of them as a reason to inconvenience users. > > If someone wants to avoid the shell command, what's wrong with CDC? > > Jon > > > > > On Tue, Sep 24, 2024 at 9:21 AM guo Maxwell wrot

Re: Status of CEP-1

Have the same question ： what ‘s the plan ？ Jeff Jirsa 于2024年10月2日 周三上午10:43写道： > > > On Oct 1, 2024, at 7:26 PM, Josh McKenzie wrote: > > However it is used by a number of other features as a dependency such as > analytics, backup/restore, repair, metrics, and CDC > > It seems like a natural pr

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

I do not follow what you mean, maybe an example would help. > > On Tue, Sep 24, 2024 at 6:18 PM guo Maxwell wrote: > >> >> If there are multiple schema information changes in one ddl statement, >> will there be schema conflicts in extreme cases? >> For example, our

Re: [REVIEW REQUEST] Exposing the status of a cleanup command on a virtual table

Hi, Can we make some schema adjustments to System.compaction_history table to meet our needs? For example : If there is no task execution, what about just recording 0 bytes_in, 0 bytes_out for this compaction history . Other status can be placed in compaction_properties, and you can even add a c

Re: 【DISCUSS】The configuration of Commitlog archiving

Hello，are there any new updates？🤔 guo Maxwell 于2024年9月18日 周三下午4:06写道： > Do you have any new updates on this DISCUSS ? > > - The reason this pattern is popular is it allows extension of > functionality ahead of the database. Some people copy to a NAS/SAN. Some > people copy to

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

If there are multiple schema information changes in one ddl statement, will there be schema conflicts in extreme cases? For example, our statement contains both table creation and index creation. guo Maxwell 于2024年9月24日 周二下午8:12写道： > +1 on splitting this task and adding the ability to c

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

For simplicity, I mentioned that we might deal with the same > keyspace scenario only for now and iterate on that in the future. > > On Mon, Sep 23, 2024 at 8:53 AM guo Maxwell wrote: > >> Hello everyone, >> >> Cep is being written, and I encountered some pro

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

) so that users can manually change the names. guo Maxwell 于2024年9月20日周五 08:06写道： > No，I think still need some discuss on grammar detail after I finish the > first version > > Patrick McFadin 于2024年9月20日 周五上午2:24写道： > >> Is this CEP ready for a VOTE thread? >> >>

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

s one! > > On Wed, Sep 18, 2024 at 12:06 AM guo Maxwell wrote: > >> Is there any update on this topic? It seems that things can make a big >> progress if Jake Luciani can find someone who can make the >> FileSystemProvider code accessible. >> >> Jon Hadd

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

No，I think still need some discuss on grammar detail after I finish the first version Patrick McFadin 于2024年9月20日 周五上午2:24写道： > Is this CEP ready for a VOTE thread? > > On Sat, Aug 24, 2024 at 8:56 PM guo Maxwell wrote: > >> Thank you for your replies, I will prepare a CEP la

Re: 【DISCUSS】The configuration of Commitlog archiving

ow this works, I think that it should be somehow logically split >>> into archiving and restoring parts. >>> >>> So, we might introduce a property in cassandra.yaml to disable >>> commitlog_archiving.properties altogether and we might deprecate >>> commitlo

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

Is there any update on this topic? It seems that things can make a big progress if Jake Luciani can find someone who can make the FileSystemProvider code accessible. Jon Haddad 于2023年12月16日周六 05:29写道： > At a high level I really like the idea of being able to better leverage > cheaper storage

Re: Welcome Chris Bannister, James Hartig, Jackson Flemming and João Reis, as cassandra-gocql-driver committers

Congratulations! James Hartig 于2024年9月13日周五 08:11写道： > Thanks everyone! Excited to contribute. > > On Thu, Sep 12, 2024, at 4:59 PM, Francisco Guerrero wrote: > > Congratulations! > > On 2024/09/12 11:39:40 Mick Semb Wever wrote: > > The PMC's members are pleased to announce that Chris Bannister

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

correctness of the data storage (although it may be a preventive solution), and I think that should be the most important thing about the database, so that other things may not be so important. guo Maxwell 于2024年9月13日周五 10:50写道： > > +1，默认在所有分支上启用拒绝。我们做了类似的事情来解决这个问题。虽然默认行为可能会改变。但我们解决的是数据存储的正确性，

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

+1，默认在所有分支上启用拒绝。我们做了类似的事情来解决这个问题。虽然默认行为可能会改变。但我们解决的是数据存储的正确性，我认为这应该是数据库最重要的事情，这样其他事情可能就不那么重要了。 Josh McKenzie 于2024年9月13日周五 09:34写道： > 即使修复只是部分的，那么实际上它更多的是通过过于急切的不可用性更有力地提醒操作员问题……？ > > 有时原则立场可能会使我们远离讨论中的重要细节。 > > 我对此票的理解（没有深入研究代码，只是查看了 JIRA > 和此线程）是，这是我们在非确定性、非基于纪元、非事务性元数据系统中可以找到的最有效的解决方案。即 > Gos

Re: 【DISCUSS】The configuration of Commitlog archiving

gt; >>>> I'm not sure what is the concern here. Is it a malicious user >>>> exploiting this? Or human error with unintended consequences? >>>> >>>> For malicious user, in order to exploit this, an attacker needs to be >>>>

Re: 【DISCUSS】The configuration of Commitlog archiving

gt;> treat it as the operator actually wants to do that. I personally don't like >> software attempting to outsmart human, which often ends up interfering with >> legitimate use cases. The best thing a software can do is log it, so >> there's some traceability if a

Re: Welcome Jordan West and Stefan Miklosovic as Cassandra PMC members!

Congrats Stefan and Jordan!!! Jacek Lewandowski 于2024年9月1日 周日下午4:39写道： > Congrats Stefan and Jordan!!! This is great! > > sob., 31 sie 2024, 22:21 użytkownik Jordan West > napisał: > >> Thanks all!!! >> >> On Sat, Aug 31, 2024 at 07:55 J. D. Jordan >> wrote: >> >>> Two great additions to the PM

Re: [DISCUSS] Introduce CREATE TABLE LIKE grammer

erate on that in the future. >>>> >>>> UDTs are created per keyspace so there is nothing to re-create. We just >>>> need to reference it from a new table, right? >>>> >>>> Indexes and MVs are interesting but in theory they might be re-c

[DISCUSS] Introduce CREATE TABLE LIKE grammer

Hello， everyone： As Jira CASSANDRA-7662 has described , we would like to introduce a new grammer " CREATE TABLE LIKE " ,which simplifies creating new tables duplicating the existing ones . The format may be like : CREATE TABLE LIKE Before

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 =

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. > > > > Than

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 add

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

ng the occupancy 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

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: 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 >> 09.12.

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: 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 28,

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 > https://issues.apache.org/jira/brows

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: > https://issues.apache.org/jira/s

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: [V

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 configurab

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 up

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: [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] 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] 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: [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 d

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. Direct

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 agreement

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 it,

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

tem. > > As I stated 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

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

"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 the

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 reques

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

  1   2   >