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

+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

Re: Merging CEP-15 to trunk

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

Re: Merging CEP-15 to trunk

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

Re: Welcome Patrick McFadin as Cassandra Committer

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

Re: [DISCUSS] Next release date

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

Re: [DISCUSS] Next release date

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,

Re: Role of Hadoop code in Cassandra 5.0

+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

Re: [DISCUSS] New dependencies with Chronicle-Queue update

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

Re: [DISCUSS] Drop support for sstable formats m* (in trunk)

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

Re: Welcome our next PMC Chair Josh McKenzie

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

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

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.

Re: [EXTERNAL] [DISCUSS] Next release date

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

Re: [VOTE] CEP-26: Unified Compaction Strategy

+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

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

,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

Re: [DISCUSS] CEP-29 CQL NOT Operator

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

Re: [DISCUSS] Next release date

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

Re: [DISCUSS] Next release date

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

Re: Adding vector search to SAI with heirarchical navigable small world graph index

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

Re: [DISCUSS] New data type for vector search

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

[DISCUSS] Feature branch version hygiene

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

Re: [VOTE] CEP-30 ANN Vector Search

+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

Re: [DISCUSS] Using ACCP or tc-native by default

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

Re: [DISCUSS] Using ACCP or tc-native by default

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

Re: [DISCUSS] Using ACCP or tc-native by default

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,

Re: Status Update on CEP-7 Storage Attached Indexes (SAI)

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

Re: August 5.0 Freeze (with waivers…) and a 5.0-alpha1

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

Re: Tokenization and SAI query syntax

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

Re: Tokenization and SAI query syntax

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

Re: [VOTE] Release Apache Cassandra 5.0-alpha1

+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

Re: [VOTE] Release Apache Cassandra 5.0-alpha1

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

Re: [DISCUSS] Addition of smile-nlp test dependency for CEP-30

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

Re: [DISCUSS] Vector type and empty value

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

Re: [DISCUSS] Add JVector as a dependency for CEP-30

+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

Re: [DISCUSS] Add JVector as a dependency for CEP-30

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

Re: [DISCUSS] Add JVector as a dependency for CEP-30

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:

Re: [VOTE] Accept java-driver

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

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

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

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

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,

Re: [VOTE] Release Apache Cassandra 5.0-beta1

-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

Re: [VOTE] Release Apache Cassandra 5.0-beta1

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

Re: Welcome Francisco Guerrero Hernandez as Cassandra Committer

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

Re: [DISCUSS] CASSANDRA-18940 SAI post-filtering reads don't update local table latency metrics

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

Re: [DISCUSS] CASSANDRA-18940 SAI post-filtering reads don't update local table latency metrics

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

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

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

Re: [DISCUSS] Add subscription mangement instructions to user@, dev@ message footers

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:

Re: [Discuss] CASSANDRA-16999 introduction of a column in system.peers_v2

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

Re: [Discuss] CASSANDRA-16999 introduction of a column in system.peers_v2

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

Re: [DISCUSS] Cassandra 5.0 support for RHEL 7

<<< multipart/alternative: No recognizable part >>>

Re: [EXTERNAL] Re: [DISCUSS] Adding experimental vtables and rules around them

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

Re: [DISCUSS] Stream Pipelines on hot paths

+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

Re: [VOTE][IP CLEARANCE] GoCQL driver

+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

Re: [VOTE] Release Apache Cassandra 5.0-rc1

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

Re: Improve the performance of CAS

I have not reasoned through this completely, but something I would want to see before messing with this is how changing the number of rounds behaves under contention and failure scenarios. Also how ignoring commit success behaves in those scenarios especially under contention and with respect to

Re: [DISCUSS] Cassandra and future Java

+1 for “Option 3: both 8 + 11” it shouldn’t be too hard to maintain code wise, and leaves people’s options open. -Jeremiah > On May 25, 2018, at 6:31 AM, Robert Stupp wrote: > > I'd like to bring up the C*/Java discussion again. It's been a while since > we've discussed this. > > To me it so

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

All for using six and supporting both. Sorry, I read your initial email as wanting to drop support for 2 at the end of the year. > On Jun 1, 2018, at 1:01 PM, Jonathan Haddad wrote: > > And that's why I said supporting both with six is the right path > forward, later dropping support for 2. I'

Re: [VOTE] Branching Change for 4.0 Freeze

-0 (non-binding) as well for similar reasons to Gary. > On Jul 12, 2018, at 8:23 AM, Gary Dusbabek wrote: > > -0 > > I'm not interested in sparking a discussion on this, because a) it has > already happened and b) it seems I am in a minority. But thought I should > at least include the rational

Re: QA signup

I would suggest that JIRA’s tagged as 4.0 blockers be created for the list once it is fleshed out. Test plans and results could be posted to said JIRAs, to be closed once a given test passes. Any bugs found can also then be related back to such a ticket for tracking them as well. -Jeremiah >

Re: Deprecating/removing PropertyFileSnitch?

Do you have a specific gossip bug that you have seen recently which caused a problem that would make this happen? Do you have a specific JIRA in mind? “We can’t remove this because what if there is a bug” doesn’t seem like a good enough reason to me. If that was a reason we would never make an

Re: Deprecating/removing PropertyFileSnitch?

ll instances in the cluster and status for some >> host >>>>>> goes missing. Now when you start a host replacement, the new host >> won’t >>>>>> learn about the host whose status is missing and the view of this >> host will >>>>>>

Re: Stabilising Internode Messaging in 4.0

Definitely sounds like it is worth taking a 2nd look here. Given that this is in relation to brand new code for 4.0, I agree that it makes sense to get it right the first time, rather than applying bandaids to 4.0 and rewriting things for 4.next. I think 4.0 should be a solid starting point for

Re: fixing paging state for 4.0

Are their drivers that try to do mixed protocol version connections? If so that would be a mistake on the drivers part if it sent the new paging state to an old server. Pretty easily protected against in said driver when it implements support for the new protocol version. The payload is opaqu

Re: fixing paging state for 4.0

t;a lot" is > fine for now till we have time to rework it is a reasonable approach. > > Jon > >> On Tue, Sep 24, 2019 at 6:52 PM J. D. Jordan >> wrote: >> >> Are their drivers that try to do mixed protocol version connections? If >> so that would

Re: fixing paging state for 4.0

And as I said, that would be a bug in the driver that did this. Any driver implementing a protocol that has a “new” paging state, that supports mixed version connections, would need to handle that correctly and not send new states over the old protocol or old states over the new protocol. As fa

Re: Offering some project management services

Isn’t doing such things the way people who are not writing code become part of a project? By offering their time to do things that benefit the project? Why does anyone “with a formal role” need to agree that Patrick is allowed to use his time to try and get some people together to discuss contr

Re: [DISCUSS] Switch to using GitHub pull requests?

Doesn’t this github review workflow as described work right now? It’s just not the “only” way people do things? I don’t think we need to forbid other methods of contribution as long as the review and testing needs are met. -Jeremiah > On Jan 22, 2020, at 6:35 PM, Yifan Cai wrote: > > +1 nb

Re: Simplify voting rules for in-jvm-dtest-api releases

I was taking with Alex on slack earlier today brainstorming ideas and two that might work are using a git submodule to reference the code by git hash, so no release needed, or using jitpack.io to be able to pull the jar down by git hash without doing a release. Does anyone find either of those

Re: [VOTE] Project governance wiki doc (take 2)

+1 non-binding > On Jun 22, 2020, at 1:18 PM, Stefan Podkowinski wrote: > > +1 > >> On 22.06.20 20:12, Blake Eggleston wrote: >> +1 >> On Jun 20, 2020, at 8:12 AM, Joshua McKenzie wrote: >>> >>> Link to doc: >>> https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Pro

Re: [DISCUSS] Future of MVs

>>> Instead of ripping it out, we could instead disable them in the yaml >>> with big fat warning comments around it. FYI we have already disabled use of materialized views, SASI, and transient replication by default in 4.0 https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L13

Re: [DISCUSS] Revisiting Java 11's experimental status

This makes sense to me. A bug is a bug regardless of the JVM that exposes it. Java 11 still considered experimental. Users should understand they are on the less trodden path when using it. -Jeremiah > On Aug 19, 2020, at 7:36 PM, David Capwell wrote: > -

Re: Welcome Yifan Cai as Cassandra committer

Congrats! > On Dec 21, 2020, at 11:36 AM, Paulo Motta wrote: > > Congratulations and welcome! :) > >> Em seg., 21 de dez. de 2020 às 14:27, sankalp kohli >> escreveu: >> >> Congratulations Yifan. >> >> On Mon, Dec 21, 2020 at 9:10 AM Benjamin Lerer < >> benjamin.le...@datastax.com> >> wrote

Re: Welcome Paulo Motta as Cassandra PMC member

Congrats Paulo! A great addition to the PMC. > On Feb 9, 2021, at 9:59 AM, Jonathan Ellis wrote: > > Congratulations, Paulo! Well deserved. > >> On Tue, Feb 9, 2021 at 9:54 AM Benjamin Lerer >> wrote: >> >> The PMC's members are pleased to announce that Paulo Motta has accepted >> the invit

Re: Cassandra Java Driver and DataStax

The Apache Cassandra project has always left development of its drivers up to the community. The DataStax Java Driver is not part of the Apache Cassandra project, it is an open source project created by DataStax. You can find a large list of drivers for Cassandra here: https://wiki.apache.org

Re: Cassandra Java Driver and DataStax

This is the way our community has operated for at least the 6ish years I have been involved with it. The Apache project develops the database, others in the community develop drivers. It's the way we have always worked, I'm sorry if you don't like that. DataStax has released their driver under

Re: NewBie Question

I think high level concepts of how data is stored should be in user facing documentation. Storage format affects schema design. But low level specifics should be kept to contributor documentation. > On Jun 15, 2016, at 12:20 PM, Jonathan Ellis wrote: > > I agree that it should be documented bu

Re: A proposal to move away from Jira-centric development

From my interactions with people who are not actively involved I think it is much easier for them to follow a JIRA link and then start being involved in the discussion than it is to get a link to the mail archive and then figure out how to get in on the discussion. People who aren't used to mai

Re: Failing tests 2016-08-15 [cassandra-3.9]

+1 for one email. > On Aug 16, 2016, at 7:45 AM, Josh McKenzie wrote: > > Assuming we're single digit failures combined between the two, I think a > single test failure email would be manageable. > > On Tue, Aug 16, 2016 at 2:46 AM, Joel Knighton > wrote: > >>

Re: Github pull requests

I think it goes the other way around. When you push to ASF git with the right commit message then the integration from that side closes the pull request. > On Aug 28, 2016, at 11:48 PM, Jonathan Ellis wrote: > > Don't we need something on the infra side to turn a merged pull request > into a co

Re: Support Multi-Tenant in Cassandra

I think the resource constraining aspects are one of the most important things we are missing. Actually doing resource constraints in SEDA is hard. In TPC it should be easier, so we put off some discussions we were having about it until we have TPC in place such that tracking resource use of a

Re: [VOTE] Release Apache Cassandra 3.0.9

It shows how many failed. Not how many passed. 0 failed so they all passed. > On Sep 18, 2016, at 12:06 PM, Jonathan Ekwempu wrote: > > The test results from Michael Shuler show that version 3.0.9 is really not > ready for release. Not even one test passed. > > On Sun, Sep 18, 2016 at 1:05 PM,

Re: sstableloader from java

Yeah. I wouldn't use that class, I was just pointing it out as an example of code doing a similar thing. > On Sep 21, 2016, at 8:16 PM, Paul Weiss wrote: > > Great will try out. I noticed the code is within the hadoop folder, I am > using local disk so hopefully it will work without hadoop.

Re: Proprietary Replication Strategies: Cassandra Driver Support

The Python driver does support it, it is supported as a custom strategy. I was the one to implement it in https://datastax-oss.atlassian.net/browse/PYTHON-191 It makes the class for it on the fly. Not sure what else you want it to do, but if you have a suggestion for an improvement to a specif

Re: Proposal - 3.5.1

If you think of the tick tock releases as interim development releases I actually think they have been working pretty well. What if we continue with the same process and do 4.0.x as LTS like we have 3.0.x LTS. So you get 4.x releases that are trickling out new features which will eventually be

Re: Status of dtest donation?

No. ccm is pulled in by dtest as a library just like other libraries used. > On Nov 21, 2016, at 8:56 AM, Jake Luciani wrote: > > I think the main blocker is identifying and contacting the folks who have > contributed code to dtest without an ICLA > >> On Mon, Nov 21, 2016 at 4:40 AM, Dave Lest

Re: Cassandra Mutation object decoding

You may also want to look at the triggers interface. > On Nov 22, 2016, at 7:45 PM, Chris Lohfink wrote: > > 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

Re: Where do I find EverywhereStrategy?

Prior to https://issues.apache.org/jira/browse/CASSANDRA-12788 that was the only way to implement a new replication strategy. > On Nov 30, 2016, at 8:46 AM, James Carman wrote: > > Oh, ok, thanks. Why would a DSE class be in the "org.apache.cassandra" > package structure? That seems a bit mis

Re: Where do I find EverywhereStrategy?

I would suggest that an RF of at most 5 per DC for auth is plenty. And least likely to cause problems in other ways. > On Nov 30, 2016, at 7:08 PM, sankalp kohli wrote: > > If we think that having this strategy can be misused, we can always have a > check to allow this only on Auth keyspace. >

Re: Where do I find EverywhereStrategy?

Yes. There really isn't a good answer for this at the moment. Unless we implement some kind of staged node addition process where you can add an entire set of nodes at once (we discussed some ideas at NGCC two years ago, but I don't think it has gone anywhere) you run into problems with any stra

Re: Integrating vendor-specific code and developing plugins

In tree would foster more committers which is a good thing. But I also agree that not being able to actually run unit tests is a bad thing. What if we asked people who want to contribute these types of optimizations to provide the ASF with a Jenkins slave we could test them on, if they want them

Re: Proposal - GroupCommitLogService

Sounds interesting. You should open a JIRA and attach your code for discussion of it. https://issues.apache.org/jira/browse/CASSANDRA/ -Jeremiah > On May 13, 2017, at 7:21 AM, Yuji Ito wrote: > > Hi dev, > > I propose a new CommitLogService, GroupCommitLogService, to improve the > throughpu

Re: Potential block issue for 3.0.13: schema version id mismatch while upgrading

I would guess there are way fewer people who have already upgraded than people who haven't. So better to fix this as fast as possible and cut a release than wait longer and not. At the very least we should pull 3.0.13 so even less people can/have upgrade to it. > On May 31, 2017, at 7:45 AM, J

Re: Integrating vendor-specific code and developing plugins

The site is in svn for the main pages. https://svn.apache.org/repos/asf/cassandra/site/src/ And in git for the docs. https://github.com/apache/cassandra/tree/trunk/doc/source For suggested changes make a JIRA with proposed changes. -Jeremiah > On Jun 2, 2017, at 5:36 PM, 大平怜 wrote: > > Hi al

Re: New contribution - Burst Hour Compaction Strategy

GitHub has some good guides on how to use git and make a pull request for a project. https://guides.github.com/introduction/flow/ https://guides.github.com/activities/forking/ > On Jun 10, 2017, at 3:17 PM, Pedro Gordo wrote: > > Hi all > > I've added to JIRA, a document explaining how BHCS w

Re: Porting cqlsh to Python 3

I don't think anyone is working on it. If you would like to then I would post on that ticket that you are going to take a stab at it and then go for it. I would keep any changes so they are working on 2.7 and 3.0 as many of the in use Linux distributions still default to 2.7. > On Jul 20, 2017,

Re: Compact Storage and SuperColumn Tables in 4.0/trunk

Thanks for the clarification. +1 for adding a "DROP COMPACT STORAGE" option in 3.x and then not allowing it to be specified in 4.0. On Sep 19, 2017, at 1:27 PM, Alex P wrote: >> If we provide a way to drop the flag, but still access the data, I think >> that is fine and perfectly reasonable.

Re: Should we do some releases?

Lots of people thinking alike. This was just being discussed on #cassandra-dev https://wilderness.apache.org/channels/?f=cassandra-dev/2017-09-19#1505841128 There were a couple tickets that are almost done that people wanted to get in before we cut a patch release. -Jeremiah > On Sep 19, 2017,

Re: Do it need to run 'nodetool upgradesstables' when updating from 2.0.9 to 2.1.19?

Old restrictions that have been lifted Jeff :) Ever since 2.0 we have supported streaming old sstables, see here for the 2.0 ticket: https://issues.apache.org/jira/browse/CASSANDRA-5772 That was broken in early 3.0, but had since been fixed by the ticket Marcus linked https://issues.apache.org/j

Re: V5 as a protocol beta version in 3.11

Again. V5 beta in 3.11 was always meant to stop working when future things happened to V5 in the drivers and in C*. I see no problem with leaving the beta V5, which is an opt in thing to try out, in 3.11 alone. 4.0 will have the full non beta V5 with extra stuff in it, and will not work with be

Re: URGENT: CASSANDRA-14092 causes Data Loss

Where is the dataloss? Does the INSERT operation return successfully to the client in this case? From reading the linked issues it sounds like you get an error client side. -Jeremiah > On Jan 25, 2018, at 1:24 PM, Anuj Wadehra > wrote: > > Hi, > > For all those people who use MAX TTL=20 y

Re: range queries on partition key supported?

A range query can be performed on the token of a partition key, not on the value. -Jeremiah > On Jan 30, 2018, at 12:21 PM, Tyagi, Preetika > wrote: > > Hi All, > > I have a quick question on Cassandra's behavior in case of partition keys. I > know that range queries are allowed in general,

Re: row tombstones as a separate sstable citizen

Have you taken a look at the new stuff introduced by https://issues.apache.org/jira/browse/CASSANDRA-7019 ? I think it may go a ways to reducing the need for something complicated like this. Though it is an interesting idea as special handling for bulk deletes. If they were truly just sstables

  1   2   >