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

inking behind those plans. Secondary indexes are being > worked on. We hope that the optimizer will also help with some index > queries. > > It seems to me that this proposal is going toward the direction that you > want without introducing new problems for scalability. > > > L

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

I don't wanna be a blocker for this CEP or anything but did want to put my 2 cents in. This CEP is horrifying to me. I have seen thousands of clusters across multiple companies and helped them get working successfully. A vast majority of that involved blocking the use of MVs, GROUP BY, secondary

Re: CASSANDRA-18941 produce size bounded SSTables from CQLSSTableWriter

+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 to > trunk and hope we are all OK with it. > > > > In

Re: [VOTE] Accept java-driver

+1 On Tue, Oct 3, 2023 at 10:30 AM Jeff Jirsa wrote: > +1 > > > On Mon, Oct 2, 2023 at 9:53 PM Mick Semb Wever wrote: > >> The donation of the java-driver is ready for its IP Clearance vote. >> https://incubator.apache.org/ip-clearance/cassandra-java-driver.html >> >> The SGA has been sent to

Re: [DISCUSS] Backport CASSANDRA-18816 to 5.0? Add support for repair coordinator to retry messages that timeout

I absolutely love the idea of this being in 5.0, I am +1 for what it is worth On Tue, Sep 19, 2023 at 4:04 PM David Capwell wrote: > To try to get repair more stable, I added optional retry logic (patch is > still in review) to a handful of critical repair verbs. This patch is > disabled by

Re: [Discuss] Repair inside C*

I think a CEP is the next step. Considering the number of companies involved, this might necessitate several drafts and rounds of discussions. I appreciate your initiative in starting this process, and I'm eager to contribute to the ensuing discussions. Maybe in a google docs or something

Re: [VOTE] CEP-8 Datastax Drivers Donation

+1 On Wed, Jun 14, 2023 at 9:05 PM Jon Haddad wrote: > +1 > > On 2023/06/13 14:14:35 Jeremy Hanna wrote: > > Calling for a vote on CEP-8 [1]. > > > > To clarify the intent, as Benjamin said in the discussion thread [2], > the goal of this vote is simply to ensure that the community is in favor

Re: [VOTE] CEP-21 Transactional Cluster Metadata

+1 On Wed, Feb 8, 2023 at 10:36 AM Blake Eggleston wrote: > +1 > > On Feb 6, 2023, at 8:15 AM, Sam Tunnicliffe wrote: > > Hi everyone, > > I would like to start a vote on this CEP. > > Proposal: > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21%3A+Transactional+Cluster+Metadata

Re: Implicitly enabling ALLOW FILTERING on virtual tables

the big ones. That could be specified in the doc for each > table, and it could also be included in the table properties, so it's > displayed by DESCRIBE TABLE queries. > > On Fri, 3 Feb 2023 at 20:56, Chris Lohfink wrote: > >> Just to 2nd what Scott days. While everything is

Re: Implicitly enabling ALLOW FILTERING on virtual tables

Just to 2nd what Scott days. While everything is in memory now, it may not be in the future, and if we add it implicitly, we are tying ourselves to be in memory only. However, I wouldn't -1 the idea. Another option may be a cqlsh option (ie like expand on/off) to always include a flag so it

Re: [DISCUSS] Diagnostic events in virtual tables

Perhaps re-add the settings virtual table mutability. That way the same place can be used to update settings at runtime for multiple things instead of creating a new virtual table per service we want to make hot props for. Might be kinda nice to allow REGISTER and EVENT CQL events to be created

Re: [VOTE] CEP-13: Denylisting partitions

+1 On Wed, Sep 8, 2021 at 11:58 AM bened...@apache.org wrote: > +1 > > From: Brandon Williams > Date: Wednesday, 8 September 2021 at 17:57 > To: dev@cassandra.apache.org > Subject: Re: [VOTE] CEP-13: Denylisting partitions > +1 > > On Wed, Sep 8, 2021 at 11:31 AM Sumanth Pasupuleti > wrote:

Re: [DISCUSS] Virtual Tables and the future of NodeTool/JMX

> a) Allow VirtualTables to be settable - to support changing parameters (ie. > nodetool setcompactionthroughput 32). Can be accomplished by updating or inserting on the settings virtual table via UPDATE system_views.settings SET value = 32 WHERE name = 'compaction_throughput'; INSERT INTO

Re: [VOTE] Release dtest-api 0.0.5

+1 On Fri, Sep 25, 2020 at 10:11 AM Caleb Rackliffe wrote: > +1 > > On Fri, Sep 25, 2020 at 10:08 AM Brandon Williams > wrote: > > > +1 > > > > On Fri, Sep 25, 2020, 9:45 AM Oleksandr Petrov < > oleksandr.pet...@gmail.com > > > > > wrote: > > > > > Proposing the test build of in-jvm dtest API

Re: purpose of queryStates map in ServerConnection

I cant see your profiler image so I may be missing something. I remember looking at this in past too. At least with 3.x version of java client the stream ids are reused as released so low volume apps wont have much overhead and highly concurrent ones it prevents allocating 20-100k objs/sec. I

Re: Calling for release managers (Committers and PMC)

I'd like to get involved in this as well. On Thu, May 7, 2020 at 2:06 PM Jon Meredith wrote: > Sign me up. > > On Thu, May 7, 2020 at 12:36 PM Robert Stupp wrote: > > > > I can help > > > > -- > > Robert Stupp > > @snazy > > > > > Am 07.05.2020 um 20:29 schrieb Mick Semb Wever : > > > > > >

Re: server side describe

I'd be in favor of going with the newer DESCRIBE option. The original patch was mostly focused on just getting the CQL correct and used virtual tables because its what the initial feedback was to do. Robert added a lot of functionality on top of what was there which is what people were starting to

Re: Virtual tables in Cassandra 4.0

It's a new feature in a version thats just in alpha so how they will look may change in the end. There will hopefully be documentation around 4.0 GA release. The feature at a high level though is an interface to handle queries with an implementing class instead of the storage engine. A usecase

Re: [DISCUSS] Server side CQL schema

> > > On Sep 5, 2019, at 2:57 PM, Chris Lohfink wrote: > > > > In https://issues.apache.org/jira/browse/CASSANDRA-14825 its been > discussed > > on how a server side DDL can be provided to clients. > > > > The original thought was to use a virt

[DISCUSS] Server side CQL schema

In https://issues.apache.org/jira/browse/CASSANDRA-14825 its been discussed on how a server side DDL can be provided to clients. The original thought was to use a virtual table to make it less invasive of a change while providing access to the TableCQLHelper output (and fixing it). The other is

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

I think that was intent but ran out of time. There were 2 approaches to this, one being dumping the Metric's into a virtual table, and another to have specialized views (like nodetool). The later is started in CASSANDRA-14670 and still

Re: Audit logging to tables.

> > > > >> On Mon, Mar 25, 2019 at 11:29 AM Sagar < > sagarmeansoc...@gmail.com> > > > > wrote: > > > > >> > > > > >> > Thanks Chris. I got caught up with a few things and couldn't > > reply > > &g

Re: Audit logging to tables.

As Chris pointed out, there's > other > >> work that would need to be done to work on virtual tables for large > >> datasets. > >> > >> Jon > >> > >> On Mon, Mar 4, 2019 at 6:42 AM Chris Lohfink > >> wrote: > >> > &g

Re: Audit logging to tables.

While you probably could put a virtual table wrapper over the binlogs, you would want to wait for something like https://issues.apache.org/jira/browse/CASSANDRA-14629 to get in so you would not OOM. The current virtual table implementation requires you have the entire result set to be returned at

Re: Which approach should we use for exposing metrics through Virtual tables?

ns and there limitations and > advantages to find out which is the solution that people prefer or to see > if somebody can come up with another solution. > > In CASSANDRA-7622, Chris Lohfink proposed to expose the table metric using > the following schema: > > VIRTUAL TABLE t

Re: Repair scheduling tools

> I do have a hard time buying that an opt-in repair *scheduling* is going to > cause heap problems or impact the daemon significantly; the scheduler > literally reads a few bytes out of a Cassandra table and makes a function > call or two, and then sleeps for 2 minutes. I wouldn't trivialize

Re: Expensive metrics?

> our histograms when built with a Meter use a ExponentiallyDecayingReservoir > but our histograms built directly use DecayingEstimatedHistogramReservoir > algorithm Meters dont use a decaying reservoir, they use EMWA

Re: Cassandra Needs to Grow Up by Version Five!

Instead of saying "Make X better" you can quantify "Here's how we can make X better" in a jira and the conversation will continue with interested parties (opening jiras are free!). Being combative and insulting project on mailing list may help vent some frustrations but it is counter productive

Re: Coordinator Write Metrics per CF

It would be good to have it. Its not that its not there because its difficult or anything. I think its more that the read latency metric was needed for speculative retry so it was added but the write side wasn't needed for that feature so wasn't added at same time. It would be very useful in

Re: High CPU after read timeout

There is no mechanism for reads to timeout once they have started. The messaging service will drop the request when its received on the ReadStage or RequestResponseStage. This is how its always operated so not unique to 3.9. If a client disconnects from a coordinator there is also no way for the

Re: Weekly Cassandra Wrap-up

https://github.com/tolbertam/sstable-tools https://github.com/instaclustr/cassandra-sstable-tools https://github.com/spotify/cassandra-opstools

Re: Truncate operation not available in Mutation Object

The truncates are written to the truncated_at field in system.local and should be honored by the commit log replayer ( https://github.com/apache/cassandra/blob/af3fe39dcabd9ef77a00309ce6741268423206df/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java#L102 ). Chris On Wed, Feb 22,

Re: Cassandra Mutation object decoding

There are different kinds of tombstones, a partition tombstone is held in the MutableDeletionInfo of the PartitionUpdate that you can get from deletionInfo() method which returns the private deletionInfo field from the holder. There are also row and cell deletions so you have to handle each of

Re: Contribution

I would second the suggestion of going over https://academy.datastax.com/ then can check out http://www.datastax.com/dev/blog/deep-into-cassandra-internals Chris On Mon, Mar 28, 2016 at 8:04 AM, Pedro Gordo wrote: > Hi! > > I think that the best place to start is to