Re: Debug logging enabled by default since 2.2

even asynchronously. > > It is up to reviewers and committers to understand the impact of and rules > around the use of different log levels. Said reviewers and committers should > teach new contributors those rules during reviews if they are violated. > > -Jeremiah > >> On

Re: Debug logging enabled by default since 2.2

in the first place. > On Mar 18, 2018, at 11:24 AM, Michael Kjellman <kjell...@apple.com> wrote: > > it’s too easy to make a regression there. and does anyone even have a splunk > (or equivalent) infrastructure to actually keep debug logs around for a long > enough retention per

Re: Debug logging enabled by default since 2.2

for our users. > On Mar 18, 2018, at 11:21 AM, Jonathan Ellis <jbel...@gmail.com> wrote: > > That really depends on whether you're judicious in deciding what to log at > debug, doesn't it? > > On Sun, Mar 18, 2018 at 12:57 PM, Michael Kjellman <kjell...@a

Re: Debug logging enabled by default since 2.2

+1. this is how it works. your computer doesn’t run at debug logging by default. your phone doesn’t either. neither does your smart tv. your database can’t be running at debug just because it makes our lives as engineers easier. > On Mar 18, 2018, at 5:14 AM, Alexander Dejanovski

Re: Debug logging enabled by default since 2.2

ive never understood this change. and it’s been explained to me multiple times. DEBUG shouldn’t run by default in prod. and it certainly shouldn’t be enabled by default for users. but hey, what do i know! just my 2 cents. > On Mar 17, 2018, at 10:55 AM, J. D. Jordan

Re: Action Required: We are sunsetting CircleCI 1.0 on August 31, 2018

and 2.2 anymore, but is this also true > for those branches? > > On 27 February 2018 at 22:58, Michael Kjellman <kjell...@apple.com> wrote: > >> FYI: we're already fully on circleci 2.0 for the 3.0, 3.11, and trunk >> branches so no action required for us here! >>

Re: Timeout unit tests in trunk

ny objections if I split it into two or multiple tests? > > On Tue, Feb 27, 2018 at 1:32 PM, Michael Kjellman <kjell...@apple.com> > wrote: > >> well, turns out we already have a jira tracking the MV tests being broken >> on trunk. they are legit broken :) thanks j

Fwd: Action Required: We are sunsetting CircleCI 1.0 on August 31, 2018

FYI: we're already fully on circleci 2.0 for the 3.0, 3.11, and trunk branches so no action required for us here! best, kjellman Begin forwarded message: From: The CircleCI Team > Subject: Action Required: We are sunsetting CircleCI 1.0 on

Re: Timeout unit tests in trunk

, Michael Kjellman <kjell...@apple.com<mailto:kjell...@apple.com>> wrote: hey dikang: just chatted a little bit about this. proposal: let's add the equivalent of @resource_intensive to unit tests too.. and the first one is to stop from running the MV unit tests in the free circlec

Re: Timeout unit tests in trunk

hey dikang: just chatted a little bit about this. proposal: let's add the equivalent of @resource_intensive to unit tests too.. and the first one is to stop from running the MV unit tests in the free circleci containers. thoughts? also, might want to bug your management to see if you can get

Re: Why isn't there a separate JVM per table?

it's an interesting idea. i'd wonder how much overhead you'd end up with message parsing and negate any potential GC wins. rick branson had played around a bunch with running storage nodes and doubling down on the old "fat client" model. if you had 1 tables (yes, barely works but we don't

Re: Cassandra Needs to Grow Up by Version Five!

Please do send them! There was a *lot* of really hard great work by a lot of people over the past year to significantly improve the documentation in tree. http://cassandra.apache.org/doc/latest/ https://github.com/apache/cassandra/tree/trunk/doc I still didn't see a reply from you re: my

Re: Cassandra Needs to Grow Up by Version Five!

kenneth: could you please send your jira information? i'm unable to even find an account on http://issues.apache.org with your name despite multiple attempts. thanks! best, kjellman > On Feb 21, 2018, at 2:20 PM, Kenneth Brotman > wrote: > > Jon, > > Very

Re: Cassandra Needs to Grow Up by Version Five!

coder. It's not for me to do Michael. > 5) I'm an individual. I am not working at a big company at the moment > Michael. > > Best, > Kenneth Brotman > > > -Original Message- > From: Michael Kjellman [mailto:kjell...@apple.com] > Sent: Sunday, February 1

Re: Cassandra Needs to Grow Up by Version Five!

hi ken, sorry you don’t like the database. some thoughts: 1) please file actionable jiras for places you feel need to be improved in the database... this is the best way to make and encourage the change you’re looking for. it seems you have quite a few ideas from your post that could be broken

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

o:mich...@pbandjelly.org>> wrote: I apologize for being naive. The test runs do not come from the in-tree circle.yml file and I need to do something different? On 02/14/2018 12:21 PM, Michael Kjellman wrote: please use the latest circleci config that is in trunk. looking at the config you

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

nd this test > cannot bind. > > I'm fine with cutting a new release set from 890f319 and chalking this > up to test flakiness. > > -- > Kind regards, > Michael > >> On 02/14/2018 11:50 AM, Michael Kjellman wrote: >> the tests are writing somethin

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

o run - launch a scratch machine, check > out, build, run tests. > > I'll see if I can repro locally. > > Michael > >> On 02/14/2018 11:44 AM, Michael Kjellman wrote: >> i looked at this a few weeks back. this is asf jenkins right? if so, it’s a >> permissions

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

i looked at this a few weeks back. this is asf jenkins right? if so, it’s a permissions issue on the build executors > On Feb 14, 2018, at 9:40 AM, Michael Shuler wrote: > > Thanks for the feedback on 3.0.16 tentative release. > > Commit 890f319 (current cassandra-3.0

Re: URGENT: CASSANDRA-14092 causes Data Loss

why are people inserting data with a 15+ year TTL? sorta curious about the actual use case for that. > On Jan 25, 2018, at 12:36 PM, horschi wrote: > > The assertion was working fine until yesterday 03:14 UTC. > > The long term solution would be to work with a long instead

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

use 3.6 as well locally and do we have > to do the same for jenkins? > > >> On 02.01.2018 22:42, Michael Kjellman wrote: >> I reproduced the NOTSET log issue locally... got a fix.. i'll push a commit >> up in a moment. >> >>> On Jan 2, 2018,

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

I reproduced the NOTSET log issue locally... got a fix.. i'll push a commit up in a moment. > On Jan 2, 2018, at 11:24 AM, Michael Kjellman <mkjell...@internalcircle.com> > wrote: > > Comments Inline: Thanks for giving this a go!! > >> On Jan 2, 2018, at 6:1

Re: [Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

in parallel. yes, i didn't touch cassandra-builds yet.. focused on getting circleci and local runs working first... once we're happy with that and stable we can make the changes to jenkins configs pretty easily... > > > > On 21.12.2017 11:13, Michael Kjellman wrote: >> I just c

Re: Test patch to Cassandra.3.0.15 using dtests

casual contributor make a change and run the unit and dtests against their branch in circleci (using just a free circleci OSS account) without any end user effort! best, kjellman On Dec 13, 2017, at 12:28 PM, Michael Kjellman <mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com&g

Re: Cassandra Dtests: skip upgrade tests

As part of the work i did for https://issues.apache.org/jira/browse/CASSANDRA-14134, one of the things I did was add a new command line argument “--execute-upgrade-tests”. all the upgrade tests are now annotated with an upgrade_test pytest annotation. by default they aren’t run. adding a

[Patch Available for Review!] CASSANDRA-14134: Migrate dtests to use pytest and python3

I just created https://issues.apache.org/jira/browse/CASSANDRA-14134 which includes tons of details (and a patch available for review) with my efforts to migrate dtests from nosetest to pytest (which ultimately ended up also including porting the ode from python 2.7 to python 3). I'd love if

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

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

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

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

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

? when do ccm releases get published to pypy? On Nov 17, 2017, at 12:18 AM, Michael Kjellman <mkjell...@internalcircle.com<mailto:mkjell...@internalcircle.com>> wrote: I see a ton of upgrade tests right now failing for: Unexpected error in node1 log, error: ERROR [main] 2017-11-17

Re: Flakey Dtests

broken... Do we have any volunteers to fix the broken Materialized Views and CDC DTests? best, kjellman > On Nov 15, 2017, at 5:59 PM, Michael Kjellman <mkjell...@internalcircle.com> > wrote: > > yes - true- some are flaky, but almost all of the ones i filed fail 100% () >

Re: Flakey Dtests

yes - true- some are flaky, but almost all of the ones i filed fail 100% () of the time. i look forward to triaging just the remaining flaky ones (hopefully - without powers combined - by the end of this month!!) appreciate everyone’s help - no matter how small... i already personally did a

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

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

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

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:

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

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

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

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

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

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

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

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

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-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: 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!

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

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

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

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

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

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

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

  1   2   >