Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

Thanks a bunch for the test runs. Most of those upgrade tests show "RuntimeError: You need to set JAVA8_HOME," so it does look like a systemic, generic issue to resolve there somewhere in dtest. Thanks again! Michael On 9/5/19 8:08 PM, Joseph Lynch wrote: Following passed 100%: utest_compress

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

Following passed 100%: utest_compression, utests_stress, utests_long, utests_fqltool, j8_dtests-no-vnodes j8_unit_tests: 1 failure - testAcquireReleaseOutbound - org.apache.cassandra.net.ConnectionTest j11_unit_tests: 1 failure - testIdleDisconnect - org.apache.cassandra.transport.IdleDisconnectT

Re: [DISCUSS] Server side CQL schema

It’s not that complicated and can make any work. There is just no consensus on which of the three options and don’t wanna go back and forth as different people review it. Chris On Thursday, September 5, 2019, Dinesh Joshi wrote: > Reading the ticket, I see 3 options being discussed. > > 1. Impl

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

NEWS.txt link was incorrect (fixed in template for next time). https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-alpha1-tentative -- Michael On 9/5/19 3:44 PM, Michael Shuler wrote: I propose the following artifacts for release as 4.0-alpha1. sha1: fc

Apache Cassandra Google Season of Docs '19 update

Hi all, Nate & I wanted to send a quick update on Google Summer of Docs for Apache Cassandra. As some of you may remember we had requested volunteers to participate in the Google Summer of Docs program a while ago. A few of you responded. One of our proposed projects were selected and now we ha

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

+1 > On Sep 5, 2019, at 4:10 PM, Jeremy Hanna wrote: > > (non-binding) +1 > > Speaking of the testing, thanks all for the different tooling and test runs. > Things like fqltool, cassandra-diff, and the testing that Joey has been doing > with https://issues.apache.org/jira/browse/CASSANDRA-14

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

(non-binding) +1 Speaking of the testing, thanks all for the different tooling and test runs. Things like fqltool, cassandra-diff, and the testing that Joey has been doing with https://issues.apache.org/jira/browse/CASSANDRA-14747 are gre

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

Running all tests at https://circleci.com/workflow-run/79918e2a-ea8e-48a6-a38d-96cf85de27ff Will report back with results shortly, -Joey On Thu, Sep 5, 2019 at 3:55 PM Jon Haddad wrote: > +1 > > On Thu, Sep 5, 2019 at 3:44 PM Michael Shuler > wrote: > > > I propose the following artifacts for

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

+1 On Thu, Sep 5, 2019 at 3:44 PM Michael Shuler wrote: > I propose the following artifacts for release as 4.0-alpha1. > > sha1: fc4381ca89ab39a82c9018e5171975285cc3bfe7 > Git: > > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha1-tentative > Artifacts: > > ht

[VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

I propose the following artifacts for release as 4.0-alpha1. sha1: fc4381ca89ab39a82c9018e5171975285cc3bfe7 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1177/

Re: [DISCUSS] Server side CQL schema

Reading the ticket, I see 3 options being discussed. 1. Implement Server Side DESCRIBE 2. Virtual Table (current patch) 3. Go with Virtual Table now, implement Server Side DESCRIBE later (as it is invasive) Is it complicated to port your current patch to implement DESCRIBE instead of a virtual

[DISCUSS] Server side CQL schema

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

Re: Builds email notifications

> Just committing, watching for > errors in the seed job and fixing them isn't very problematic. The > existing jobs are not touched, if the DSL does not parse correctly, and > the errors are usually pretty clear where the issue might be. Just do it > in prod, once it looks about what we want

Re: How to stop github notification emails?

> Sure, updated the ticket to send them to pr@, but I imagine you would > get them if you "watch" the github repo? It is nice to have an archive somewhere public. And AFAIK (i'm unsure of the latest, but it was a concern with the use of github) ASF likes to keep a copy of everything that hap

Re: How to stop github notification emails?

Sure, updated the ticket to send them to pr@, but I imagine you would get them if you "watch" the github repo? /Marcus On Thu, Sep 05, 2019 at 01:03:11PM +0200, Mick Semb Wever wrote: > > > > https://issues.apache.org/jira/browse/INFRA-18982 > > > Marcus, instead of ignoring them can we send

Re: How to stop github notification emails?

> https://issues.apache.org/jira/browse/INFRA-18982 Marcus, instead of ignoring them can we send them to pr@ (or commits@) please? - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-ma

Re: How to stop github notification emails?

https://issues.apache.org/jira/browse/INFRA-18982 /Marcus On Thu, Sep 05, 2019 at 09:20:01AM +0100, Benedict Elliott Smith wrote: > +1 > > These should be sent to commits@, not dev@ > > On 05/09/2019, 09:19, "Stefan Miklosovic" > wrote: > > Hi, > > maybe I am missing here somet

Re: How to stop github notification emails?

+1 These should be sent to commits@, not dev@ On 05/09/2019, 09:19, "Stefan Miklosovic" wrote: Hi, maybe I am missing here something but how can I get rid of these emails which are polluting my inbox? "[GitHub] [cassandra-builds] michaelsembwever commented on issue #

How to stop github notification emails?

Hi, maybe I am missing here something but how can I get rid of these emails which are polluting my inbox? "[GitHub] [cassandra-builds] michaelsembwever commented on issue #10: Configure so emails are sent when a build fails" It is sent from "g...@apache.org" to dev mailing list. As far as I kno

[GitHub] [cassandra-builds] michaelsembwever commented on issue #10: Configure so emails are sent when a build fails…

michaelsembwever commented on issue #10: Configure so emails are sent when a build fails… URL: https://github.com/apache/cassandra-builds/pull/10#issuecomment-528245197 Watching deployment in https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-Job-DSL/

[GitHub] [cassandra-builds] michaelsembwever merged pull request #10: Configure so emails are sent when a build fails…

michaelsembwever merged pull request #10: Configure so emails are sent when a build fails… URL: https://github.com/apache/cassandra-builds/pull/10 This is an automated message from the Apache Git Service. To respond to the m