Re: max_compaction_threshold removed - bad move

Yikes. Please would be nice.. Also, Sylvian already said they would update the documentation. As a developer, who hasn't forgotten to update documentation? On 1/9/13 8:07 AM, Radim Kolar h...@filez.com wrote: if this was renamed then update your documentation:

Re: [VOTE] Release Apache Cassandra 1.2.1

+1 On Jan 24, 2013, at 11:54 PM, Sylvain Lebresne sylv...@datastax.com wrote: That list of changes since 1.2.0 is getting pretty long, time to ship that to users. I propose the following artifacts for release as 1.2.1. sha1: 8540974dbd26989b1cd72608b06e57ebe053bf38 Git:

Re: Proposal: require Java7 for Cassandra 2.0

There seems to be a lot of confusion on this topic in the C* Community. Most people look at the Datastax docs that recommend Java 6 and ask why that recommendation is there. Threads never seem to finish with a clear definitive answer. There seem to be about 3-4 of these for the past few months on

Re: Understanding the Cassandra Code Base

Discussed in the users list on 1/23/13 http://mail-archives.apache.org/mod_mbox/incubator-cassandra-user/201301.mb ox/%3c11d9ef3eb41c401880e02e51269ea...@portico.io%3E On 2/8/13 2:23 PM, Rahman, Muntasir Raihan mrahm...@illinois.edu wrote: Thanks. I will start from there. Muntasir.

Re: [VOTE] Release Mojo's Cassandra Maven Plugin 1.2.0-1

Considering that 1.2.1 is out, and looking at your project very quickly (looks interesting)/overlaps a bit with CCMBridge no?/ I'd def say +1 :) From: Stephen Connolly stephen.alan.conno...@gmail.commailto:stephen.alan.conno...@gmail.com Reply-To:

Re: [VOTE] Release Apache Cassandra 1.2.2

+1 On 2/20/13 4:01 PM, Sylvain Lebresne sylv...@datastax.com wrote: We've fixed a fair amount of important fixes since 1.2.1 so I propose the following artifacts for release as 1.2.2. sha1: 068b53dd5de928fd80815b54963af796f51f1c38 Git:

Re: real leveldb vs cassandra leveldb

I can promise you it is not a matter of not being interested in performance enhancements, but there is a trade off between stability, backwards comparability, etc. Some of the changes you are proposing have merit but they fundamentally change some decisions that have been made and Jonathan

Re: Notes from committer's meeting: overview

https://www.google.com On 2/25/13 3:24 PM, Anton Prakash anton.prak...@cloudtalk.com wrote: unsubscribe On Mon, Feb 25, 2013 at 3:23 PM, Brandon Williams dri...@gmail.com wrote: On Mon, Feb 25, 2013 at 5:19 PM, Edward Capriolo edlinuxg...@gmail.com wrote: I am curious what you mean when

Re: bug report - CQL3 grammar should ignore VARCHAR column length in CREATE statements

Might want to create a Jira ticket at issues.apache.org instead of submitting the bug report thru email. On Mar 2, 2013, at 3:11 AM, Andrew Prendergast a...@andrewprendergast.com wrote: *DESCRIPTION* When creating a table in all ANSI-SQL compliant RDBMS' the VARCHAR datatype takes a

Re: C* 1.2.2 vs Raspberry Pi

This was due to https://issues.apache.org/jira/browse/CASSANDRA-4366 Should be safe to remove this when running on a you Raspberry Pi as it is a performance change for the JVM and I guess not supported on whatever version is supported on your distro for the Pi. -mike On 3/4/13 11:17 AM, Andrew

Re: Pycassa with Composite keys

You might have more luck on the users list or client-dev. Best, Michael On Mar 7, 2013, at 2:45 AM, Pushkar Prasad pushkar.pra...@airtightnetworks.net wrote: I want to insert a lot of rows from a csv file into Cassandra, and I figured out copy command would not be fast enough. I want to use

Re: Issue Upgrade to 1.2.2 from 1.2.1 Table column names changed

http://www.datastax.com/docs/1.2/index http://www.datastax.com/docs/1.2/cql_cli/using/alter The users list might be a better place for this discussion if you need further help. On 3/12/13 10:50 AM, Haithem Jarraya haithem.jarr...@struq.com wrote: Could you please point me to the right syntax

Re: Issue Upgrade to 1.2.2 from 1.2.1 Table column names changed

:53, Michael Kjellman mkjell...@barracuda.com wrote: http://www.datastax.com/docs/1.2/index http://www.datastax.com/docs/1.2/cql_cli/using/alter The users list might be a better place for this discussion if you need further help. On 3/12/13 10:50 AM, Haithem Jarraya haithem.jarr...@struq.com

Re: reading sstables stored in hdfs

Just curious, why would you want to store sstables in HDFS? On 3/23/13 12:43 PM, Amit Kumar kumarami...@gmail.com wrote: I am starting some work on an input-format that would let us read sstables stored in HDFS, I wonder if anyone has worked on something similar before. I did come across

Re: Creating namespace and column family from multiple nodes concurrently

You will most likely get better answers to your if you try the Cassandra users group instead for your question. Best, Michael On 5/22/13 5:52 PM, Emalayan Vairavanathan svemala...@yahoo.com wrote: Hi all, I am implementing a distributed application which runs on 100s of machines

Re: [VOTE] Release Apache Cassandra 1.2.6 (Strike 3)

I know non members aren¹t supposed to comment on these votes, but I was actually throwing 1.2.6 Strike 2ish into production when 3/4 of the way thru I got Jason¹s email as I was debugging Gossip issues across the cluster. It didn¹t appear to just break repair, but it also broke Gossip (makes since

Re: CQL 3.0

Better question for the users list, but everything about your cluster is available in the system column family and accessible with CQL. On 7/10/13, 11:46 PM, Murali muralidharan@gmail.com wrote: Hi experts, Can we use CQL 3.0 to get the partition / cluster information from cassandra server?

Re: Some node can not receive GossipDigestAckMessage

Glad you got it fixed. In the future, if you have other issues using Cassandra you might want to email the other C* mailing list at u...@cassandra.apache.org, which has people listening geared to these types of questions. On 7/11/13, 12:05 AM, HuS.Andy hushansm...@hotmail.com wrote: I got a

Re: cassandra vnodes

Okay, I¹ll take the bait. I apologize if I come off rude here (you certainly don¹t seem to care though if you do) but if you want production ready enterprise QA tested code please see Datastax Enterprise. Just because you didn¹t choose to use what is offered doesn¹t mean it doesn¹t exist. Much

Re: Regression in 1.2.7

+1 This late in the release cycle it might really bite some people upgrading for all the 1.2.x goodness. On Jul 27, 2013, at 12:40 PM, Jonathan Ellis jbel...@gmail.com wrote: The fix for range tombstone performance [1] introduced a regression [2] that breaks slice queries against

Re: should you reuse PreparedStatements?

Absolutely you should reuse prepared statements where possible in your client code. On 8/3/13, 5:34 PM, Michael Cohen mcohe...@gmail.com wrote: More specifically, is it best practice to reuse PreparedStatements, rather than creating a new one via session.prepare() on each database access? Is

Re: CQL or Thrift ?

Why? Please give me 3 reasons why this is good advice to the OP. The frame based binary protocol will be 100% easier to implement in C than the never-been-out-of-alpha libc Thrift implementation. I¹ve worked with that code for a while, it¹s *not* pretty. I can¹t think of one reason, other than

Re: Apache Cassandra 2.0.0 rc1

Thrift? Native? If Thrift- what threading model? On Aug 11, 2013, at 4:13 PM, Radim Kolar h...@filez.com wrote: Dne 10.8.2013 21:30, Brandon Williams napsal(a): Make a conf/triggers directory and that will fix it. We fixed this in trunk already. yes, that fixed it. 2.0 is considerably

Re: Apache Cassandra 2.0.0 rc1

Should probably use this instead. All benchmarks show it¹s faster than anything that has ever been written before. https://issues.apache.org/jira/browse/CASSANDRA-5582 On 8/12/13, 12:47 AM, Radim Kolar h...@filez.com wrote: thrift, sync

Re: JNA to activate cassandra row cache

No- not required, but there is zero reason not to. Keep as much off heap as possible. On Aug 14, 2013, at 12:13 PM, José Elias Queiroga da Costa Araújo je...@cesar.org.br wrote: Hi all, I have a question. In order to activate cassandra row cache is necessary to have JNA

Re: JNA to activate cassandra row cache

Cassandra memory usage. When installed and configured, Linux does not swap out the JVM, and thus avoids related performance issues. So my question is if Cassandra cache implementation is based ByteBuffer, there is any real reason to install JNA? Regards, 2013/8/14 Michael Kjellman mkjell

Re: [VOTE] Release Apache Cassandra 1.2.9

+1 This is currently broken. On Aug 27, 2013, at 5:14 AM, Chris Burroughs chris.burrou...@gmail.com wrote: Following up on a discussion in IRC. A caveat on the (not new, but not fixed) problems with replace_{node,token} would likely be appreciated by users. On 08/26/2013 02:53 PM,

Re: Cassandra support for Multitenancy

First, you should try the users list for your question. Someone there might know better. Second, I can't imagine sharing a C* instance with different workloads. If anything I'd like to split my cluster up in size just for my own use on the same project. Third, 1.2 has support for Auth so

Re: [VOTE] Release Apache Cassandra 1.2.11

Everything running smoothly. Ship it! +1 On 10/15/13, 4:44 PM, Gary Dusbabek gdusba...@gmail.com wrote: +1 On Tuesday, October 15, 2013, Sylvain Lebresne wrote: The changelog is getting big, I propose the following artifacts for release as 1.2.11. sha1:

Re: [VOTE CLOSED] Release Apache Cassandra 1.2.13 (Strike 2)

I¹ve also seen behavior where prepared statements are lost during a rolling restart..haven¹t had a chance to debug/git bisect yet. Anyone else seen anything similar? On 12/16/13, 10:40 PM, Sylvain Lebresne sylv...@datastax.com wrote: Alright, this vote is thus close. I'll re-roll when we've made

Re: [VOTE CLOSED] Release Apache Cassandra 1.2.13 (Strike 2)

Well. I feel stupid now :) On Dec 16, 2013, at 10:49 PM, Sylvain Lebresne sylv...@datastax.com wrote: On Tue, Dec 17, 2013 at 7:43 AM, Michael Kjellman mkjell...@barracuda.comwrote: I¹ve also seen behavior where prepared statements are lost during a rolling restart..haven¹t had a chance

Re: Product Catalog Data Format Investigation (NOW-18)

Your link doesn¹t resolve and I¹m 99% sure you have the wrong mailing list. Best, Michael On 2/21/14, 4:11 PM, Paul Cichonski paul.cichon...@lithium.com wrote: Hey All, I've documented the results of my investigation into product data standards here:

Re: Proposal: freeze Thrift starting with 2.1.0

Ed- I understand and respect your enthusiasm for Thrift, but it's ship has sailed. Yes- if you understand the low level thrift API I'm sure you can have a rewarding experience, but as someone who wrote a client and had to abstract thrift...I don't have many kind words, and I certainly have

Re: Timeuuid inserted with now(), how to get the value back in Java client?

Create a new Date() and insert that instead of using the NOW CQL macro. You have the time you inserted... Also, this is the type of question for the user list in the future. Hope that helps and I understood your question correctly. On Mar 28, 2014, at 4:46 PM, Andy Atj2 andya...@gmail.com

Re: Cannot subscribe to users mailing list

The ASF recently had catastrophic mail server issues. You should try again as some messages were unfortunately lost :( https://blogs.apache.org/infra/entry/mail_outage best, michael On May 12, 2014, at 9:58 AM, Maciej Miklas mac.mik...@gmail.com wrote: Hi *, I’ve tried to subscribe to

Proposed changes to C* Release Schedule

Hi Dev@ List— TL;DR: I’d love it if we could modify the C* release cycle to include an additional “experimental” release branch that straddles the current major releases that includes somewhat “untested” or “risky” commits that normally would only go into the next major release. Releases based

Re: Proposed changes to C* Release Schedule

__ Sent from iPhone On 17 Jun 2014, at 5:16 pm, Michael Kjellman mkjell...@internalcircle.com wrote: Hi Dev@ List— TL;DR: I’d love it if we could modify the C* release cycle to include an additional “experimental” release branch that straddles the current

Re: Proposed changes to C* Release Schedule

, Michael Kjellman mkjell...@internalcircle.com wrote: Hi Dev@ List— TL;DR: I’d love it if we could modify the C* release cycle to include an additional “experimental” release branch that straddles the current major releases that includes somewhat “untested” or “risky” commits that normally

Re: Proposed changes to C* Release Schedule

you are assuming will be constant across versions? -Jake On Tue, Jun 17, 2014 at 12:28 PM, Michael Kjellman mkjell...@internalcircle.com wrote: It's a bit about features - but it's more an attempt to achieve the goals of what might happen with a 4 week release cycle

Re: Proposed changes to C* Release Schedule

of the change which you are assuming will be constant across versions? -Jake On Tue, Jun 17, 2014 at 12:28 PM, Michael Kjellman mkjell...@internalcircle.com wrote: It's a bit about features - but it's more an attempt to achieve the goals of what might happen with a 4 week release

Re: Proposed changes to C* Release Schedule

. 2. Backport things to stable releases. We should discuss these separately since together it's hard to discuss. 1. is less controversial I would think :) On Tue, Jun 17, 2014 at 1:16 PM, Michael Kjellman mkjell...@internalcircle.com wrote: Totally agree — Also — i’m aware

Re: Proposed changes to C* Release Schedule

. -- Sylvain On Tue, Jun 24, 2014 at 8:27 AM, Chris Burroughs chris.burrou...@gmail.com wrote: On 06/17/2014 01:16 PM, Michael Kjellman wrote: That being said I don’t think i’m alone by identifying the problem. FWIW I'm not doing anything wildly unusual and I've been on a fork for as long

Re: 2.1 rc3?

Also putting my 2 cents in for more testing/another release. On Jul 5, 2014, at 4:31 PM, Jason Brown jasedbr...@gmail.com wrote: +1 on more testing. TBH, I was a little scared when I found #7465 as it was rather easy to uncover. On Wed, Jul 2, 2014 at 11:32 AM, Benedict Elliott Smith

Re: 3.0 and the Cassandra release process

❤️ it. +1 -kjellman On Mar 17, 2015, at 2:06 PM, Jonathan Ellis jbel...@gmail.com wrote: Cassandra 2.1 was released in September, which means that if we were on track with our stated goal of six month releases, 3.0 would be done about now. Instead, we haven't even delivered a beta. The

Re: 3.0 and the Cassandra release process

For most of my life I’ve lived on the software bleeding edge both personally and professionally. Maybe it’s a personal weakness, but I guess I get a thrill out of the problem solving aspect? Recently I came to a bit of an epiphany — the closer I keep to the daily build — generally the happier

Re: Proposal: release 2.2 (based on current trunk) before 3.0 (based on 8099)

Last I checked — and I could be wrong — we’ve never had to think about what to number a Cassandra version due to a ticket that could “impact” our users so dramatically due to the scope of the changes from a single ticket. Food for thought. love, kjellman On May 11, 2015, at 2:20 PM, Alex

Re: Cassandra Java Driver and DataStax

No need to argue your point to me anymore. I've already tuned you out. These are good people who I consider my friends and insulting people just shows your arguments really have no merit. Good luck with your new driver contribution! I look forward to reviewing the code. Sent from my iPhone

Re: NewBie Question ~ Book for Cassandra

Bhuvan, You didn't disrespect anyone, so please don't apologize! Appreciate your positive and helpful comment for the OP :) best, kjellman > On Jun 13, 2016, at 8:50 AM, Bhuvan Rawal wrote: > > Hi Matt, > > I suggested the resources keeping in mind the ease with which

Re: Jira down, again?

r me. >>> >>> Do others have the same experience? >>> >>> Best Regards >>> >>> On Tue, Jun 14, 2016 at 4:19 AM, Brandon Williams <dri...@gmail.com> >>> wrote: >>> >>>> Everyone. >>>> >>>

Re: NewBie Question

This was forwarded to me yesterday... a helpful first step https://github.com/apache/cassandra/blob/cassandra-3.0.0/guide_8099.md > On Jun 15, 2016, at 9:54 AM, Jonathan Haddad wrote: > > Maybe some brave soul will document the 3.0 on disk format as part of >

Jira down, again?

Seems like Apache Jira is 100% down, again, for like the 500th time in the last 2 months. Just me or everyone?

Re: Java Driver 3.0 for Apache Cassandra - Documentation Outdated?

: Excellent, why am I the first person to ask that, and why didn’t a PMC member point that out right away and why did it take me asking to point to the Apache docs. This is what I am talking about in terms of the Apache community.. On 6/6/16, 4:47 PM, "Michael Kjellman" <mkjell.

Re: Jira down, again?

Hm... weird, JIRA isn't working again? S bizarre!!  > On Jun 15, 2016, at 5:38 PM, Michael Kjellman <mkjell...@internalcircle.com> > wrote: > > down. again. > >> On Jun 14, 2016, at 11:14 AM, Alex Popescu <al...@datastax.com> wrote: >>

Re: Jira down, again?

down. again. > On Jun 14, 2016, at 11:14 AM, Alex Popescu <al...@datastax.com> wrote: > > I've been trying to get to a ticket for the last 2h and I only get service > unavailable :-( > > On Tue, Jun 14, 2016 at 10:26 AM, Michael Kjellman < > mkjell...@internalcirc

Re: Versioning policy?

Correct, this is an open source project. If you want a Enterprise support story Datastax has an Enterprise option for you. > On Jan 16, 2016, at 11:19 AM, Anuj Wadehra wrote: > > Hi Jonathan > > It would be really nice if you could share your thoughts on the four

Re: A short guid on how to contribute patches to Cassandra

Move to Wiki? Sent from my iPhone > On Feb 9, 2016, at 5:59 AM, Aleksey Yeschenko wrote: > > Hello everyone, > > I’ve compiled a short guide for contributors (who aren’t committers yet) > about how to properly contribute Cassandra patches: > >

Re: Cassandra 2.0.x OOM during startsup - schema version inconsistency after reboot

I'd recommend you create a JIRA! That way you can get some traction on the issue. Obviously an OOM is never correct, even if your process is wrong in some way! Best, kjellman Sent from my iPhone > On May 8, 2016, at 8:48 PM, Michael Fong > wrote: > > Hi,

Re: [Proposal] Mandatory comments

My vote is to start with BigTableScanner (SSTableScanner).. 5 iterators that all do something different with each other depending on how used with zero comments -- in a critical code path. What could go wrong! > On May 5, 2016, at 11:26 AM, Dave Brosius wrote: > > A

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

I'm a big fan of mailing lists, but google makes issues very findable for new people to the project as JIRA gets indexed. They won't be able to find the same thing on an email they didn't get -- because they weren't in the project in the first place. Mailing lists are good for broad discussion

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

nfused if you believe that the ASF mailing lists aren’t the source of truth. They are. That’s not optional. If you are an ASF project, mailing lists are the source of truth. Period. On 8/15/16, 11:01 AM, "Michael Kjellman" <mkjell...@internalcircle.com<mailto:mkjell...

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

+1 Sent from my iPhone On Aug 15, 2016, at 6:48 PM, Brandon Williams > wrote: So will I, if that happens, which has never happened in the last ~7 years. On Mon, Aug 15, 2016 at 4:27 PM, Jeff Jirsa

Thanks for all the fish.

Just wanted to say thank you publicly to Jonathan Ellis for his tireless work making this community and software what it is. He's always been level headed and I certainly wouldn't be where I am without his leadership. So, Jonathan, thanks for all the fish. best, kjellman Sent from my iPhone

Re: Question on assert

ed all their data." This is somewhat of my point. Why do assertions that sometimes are trapped "protect my data" better then a checked exception? On Wed, Sep 21, 2016 at 1:24 PM, Michael Kjellman < mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com>> wrote: I hat

Re: Question on assert

is uses as a quasi > IllegalStateException. Other times an class named "estimator" asserts when > the "estimate" "overflows". This seem far away from the defined purpose of > assert. > > The glaring issue is that it bubbles through try catch so it hardly makes

Re: Question on assert

I hate that comment with a passion. Please please please please do yourself a favor and *always* run with asserts on. `-ea` for life. In practice I'd be surprised if you actually got a reliable 5% performance win and I doubt your customers will care about a potential 5% performance win when

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

Looks like some very nice progress here! Mucho Exciting!!  On Aug 22, 2016, at 10:44 PM, Joel Knighton > wrote: === testall: All passed!

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

Awesome Joel Sent from my iPhone On Aug 24, 2016, at 8:22 PM, Joel Knighton > wrote: === testall: All passed! === dtest: 2 failures

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

Yes, We hit this as well. We have a internal patch that I wrote to mostly revert the behavior back to ByteBuffers with as small amount of code change as possible. Performance of our build is now even with 2.0.x and we've also forward ported it to 3.x (although the 3.x patch was even more

Re: Review of Cassandra actions

Thanks Jeff for your thoughtful comments. +100 Sent from my iPhone > On Nov 5, 2016, at 6:26 PM, Jeff Jirsa wrote: > > I hope the other 7 members of the board take note of this response, > and other similar reactions on dev@ today. > > When Datastax violated trademark, they

Re: 8099 Storage Format Documentation as used with PRIMARY_INDEX

Ugh, just finally figured the "header" bit of my question out. Mega lame. :\ > On Oct 18, 2016, at 9:17 AM, Michael Kjellman <mkjell...@internalcircle.com> > wrote: > > I'm working on writing Birch for trunk and I noticed the following: > > https://github.c

8099 Storage Format Documentation as used with PRIMARY_INDEX

I'm working on writing Birch for trunk and I noticed the following: https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/columniterator/AbstractSSTableIterator.java#L503 Prior to 3.0 the offset was the literal offset into the data file, yet now we seem to be doing the

Re: Use of posix_fadvise

Within a single SegmentedFile? On Oct 18, 2016, at 9:02 AM, Ariel Weisberg > wrote: With compaction there can be hot and cold data mixed together.

Re: Cleanup after yourselves please

Cool, as I would have assumed they would need to be. Given they were initially commented out on 6/30/15 maybe cleanup and removal of that dead code is still at least warranted. On Oct 18, 2016, at 9:15 AM, Oleksandr Petrov > wrote:

Re: Use of posix_fadvise

ASSANDRA-5863 On Tue, Oct 18, 2016 at 11:59 AM, Michael Kjellman < mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com>> wrote: Specifically regarding the behavior in different kernels, from `man posix_fadvise`: "In kernels before 2.6.6, if len was specified as 0, then

Re: Cleanup after yourselves please

egard the commented tests. My branch is going > to be ready for review soon. > > [1] https://issues.apache.org/jira/browse/CASSANDRA-12373 > > > On Tue, Oct 18, 2016 at 5:10 PM Michael Kjellman < > mkjell...@internalcircle.com> wrote: > >> There was

Re: Use of posix_fadvise

7-A24D-1AB8C0341D97@localhost] best, kjellman On Oct 18, 2016, at 8:33 AM, Benedict Elliott Smith <bened...@apache.org<mailto:bened...@apache.org>> wrote: ... and continuing in the fashion of behaviours one might like to disabuse people of, no code link is provided. On 18 October 2016

Re: Use of posix_fadvise

re. > > On Oct 18, 2016 11:29 AM, "Michael Kjellman" <mkjell...@internalcircle.com> > wrote: > >> We use posix_fadvise in a bunch of places, and in stereotypical Cassandra >> fashion no comments were provided. >> >> There is a check the OS is Linux

Cleanup after yourselves please

There was a bunch of tests hastily and messly commented out line by line (*whyy?*) ColumnFamilyStoreTest with comments that they are pending SuperColumns support post 8099. Could those responsible please cleanup after themselves? It's been a while since 8099 was committed in the first place

Use of posix_fadvise

We use posix_fadvise in a bunch of places, and in stereotypical Cassandra fashion no comments were provided. There is a check the OS is Linux (okay, a start) but it turns out the behavior of providing a length of 0 to posix_fadvise changed in some 2.6 kernels. We don't check the kernel version

Re: Use of posix_fadvise

Sorry, No. Always document your assumptions. I shouldn't need to git blame a thousand commits and read thru a billion tickets to maybe understand why something was done. Clearly thru the conversations on this topic I've had on IRC and the responses so far on this email thread it's not/still not

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

Honest question: are you *ever* positive Ed? Maybe give it a shot once in a while. It will be good for your mental health. Sent from my iPhone > On Nov 19, 2016, at 11:50 AM, Edward Capriolo wrote: > > This is especially relevant if people wish to focus on removing

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

Jason has asked for review and feedback many times. Maybe be constructive and review his code instead of just complaining (once again)? Sent from my iPhone > On Nov 19, 2016, at 1:49 PM, Edward Capriolo wrote: > > I would say start with a mindset like 'people will run

Re: Moderation

@Chris: instead of promoting the arguing going on on this thread could you please help lead by example and reply to Kelly's questions in her email? Thanks. I don't enjoy watching a community I care about continue to explode in front of my eyes ☹️ best, kjellman Sent from my iPhone > On Nov

Re: DataStax role in Cassandra and the ASF

Hi Kelly- I can't speak to many of your questions as it's not my position to do so. What I can say is that at Apple we are doubling down on open source. We have tons of code in flight -- really big ones in fact -- many already out for review. Our list of enhancements we want to do grows all

Re: DataStax role in Cassandra and the ASF

"Avalon. The database" yes autocorrect. That's exactly what I wanted. That should read "scaling the database and stability." Sorry. I'm typing this while walking up a big ass hill in San Francisco heading to the office.  Sent from my iPhone > On Nov 4, 2016, at 10:

Re: DataStax role in Cassandra and the ASF

es already in releases for people to adopt so we've got the "features" thing under control for at least a year in my opinion. best, kjellman Sent from my iPhone > On Nov 4, 2016, at 10:33 AM, Michael Kjellman <mkjell...@internalcircle.com> > wrote: > > "Av

Re: unsubscribe

http://apache.org/foundation/mailinglists.html Sent from my iPhone On Apr 6, 2017, at 9:57 AM, Nitija Patil > wrote: unsubscribe On Thu, Apr 6, 2017 at 10:25 PM, Vineet Gadodia > wrote: unsubscribe

Re: Does partition size limitation still exists in Cassandra 3.10 given there is a B-tree implementation?

I'm almost done with a rebased trunk patch. Hit a few snags. I want nothing more to finish this thing... The latest issue was due to range tombstones and the fact that the deletion time was being stored in the index from 3.0 onwards. I hope to have everything pushed very shortly. Sorry for the

Re: Dropped Mutation and Read messages.

This discussion should be on the C* user mailing list. Thanks! best, kjellman > On May 11, 2017, at 10:53 AM, Oskar Kjellin wrote: > > That seems way too low. Depending on what type of disk you have it should be > closer to 1-200MB. > That's probably causing your

Re: Integrating vendor-specific code and developing plugins

That’s epic Jeff. Very cool. Sent from my iPhone On May 18, 2017, at 10:28 AM, Jeff Jirsa > wrote: On Mon, May 15, 2017 at 5:25 PM, Jeremiah D Jordan < jeremiah.jor...@gmail.com> wrote: To me testable means that we

Re: CCM dependency in dtests

thanks for driving this Stefan this is definitely an issue that I recently saw too trying to get all the dtests passing. having logic you need to fix in 3 repos isn’t ideal at all. > On Nov 27, 2017, at 4:05 AM, Stefan Podkowinski wrote: > > Just wanted to bring a recent

Re: Flakey Dtests

Complicated question unfortunately — and something we’re actively working on improving: Cassci is no longer being offered/run by Datastax and so we've need to come up with a new solution, and what that ultimately is is still a WIP — it’s loss was very huge obviously and a testament to the

Re: Flakey Dtests

che.org/view/A-D/view/Cassandra/job/Cassandra-3.11-test-cdc/ > https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-trunk-test-cdc/ > > -- > Michael > >> On 11/27/2017 03:45 PM, Michael Kjellman wrote: >> Hey Jay: >> >> Thanks!! I just took a quick loo

[PROPOSAL] Migrate to pytest from nosetests for dtests

I'd like to propose we move from nosetest to pytest for the dtests. It looks like nosetests is basically abandoned, the python community doesn't like it, it hasn't been updated since 2015, and pytest even has nosetests support which would help us greatly during migration

Re: [PROPOSAL] Migrate to pytest from nosetests for dtests

cks? Is there some nosetest bug or > restriction getting in the way? > >> On Tue, Nov 28, 2017 at 8:34 PM, Jon Haddad <j...@jonhaddad.com> wrote: >> >> +1 >> >> I stopped using nose a long time ago in favor of py.test. It’s a >> significant

Re: [PROPOSAL] Migrate to pytest from nosetests for dtests

s/handling/hanging > On Nov 29, 2017, at 9:54 AM, Michael Kjellman <mkjell...@internalcircle.com> > wrote: > > i keep seeing nose randomly handing after a test successfully completes > execution. i’m very far from a python guru but i spent a few hours with gdb > t

Re: CCM dependency in dtests

Hey Stefan, any updates on this? Thanks. best, kjellman > On Nov 27, 2017, at 7:34 AM, Michael Kjellman <mkjell...@internalcircle.com> > wrote: > > thanks for driving this Stefan this is definitely an issue that I > recently saw too trying to get all the dtests pass

Re: Flakey Dtests

en Materialized Views and CDC >> DTests? > > I'll try to take a look at the CDC tests next week; looks like one of the > base unit tests is failing as well. > > On Fri, Nov 17, 2017 at 12:09 AM, Michael Kjellman < > mkjell...@internalcircle.com> wrote: > >> Quick

Re: Flakey Dtests

better. best, kjellman On Nov 27, 2017, at 2:43 PM, Michael Kjellman <mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com>> wrote: (with 100 containers we can actually build the project, run all of the unit tests, and run all of the dtests in roughly 28 minutes!).

Re: Test patch to Cassandra.3.0.15 using dtests

i’ve been working on a story to improve this around the clock. including better documentation (and a —help flag with options to make it easy to know how to run dtests and a few runtime sanity checks about the environment)! stay tuned! > On Dec 13, 2017, at 3:24 AM, Sergey

  1   2   >