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

[Michael Shuler]

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

j8_dtests-with-vnodes + j11_dtests-with-vnodes: 1 failure
- test_remote_query - cql_test.TestCQLSlowQuery

j11_dtests-no-vnodes: 1 failure
- test_13595 - consistency_test.TestConsistency

j8_upgradetests-no-vnodes: 3923 failures

Other than the upgradetests (which afaik nobody has looked at for
4.0), this looks somewhat reasonable to me. I'm launching a multi-dc
cluster to do some light load testing.

-Joey


On Thu, Sep 5, 2019 at 4:03 PM Joseph Lynch  wrote:


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 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/org/apache/cassandra/apache-cassandra/4.0-alpha1/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1177/

The Debian and RPM packages are available here:
http://people.apache.org/~mshuler

The vote will be open for 24 hours (longer if needed).

[1]: CHANGES.txt:

https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative
[2]: NEWS.txt:

https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [DISCUSS] Server side CQL schema

[Chris Lohfink]

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. 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 table?
>
> Dinesh
>
> > On Sep 5, 2019, at 2:57 PM, Chris Lohfink  wrote:
> >
> > In https://issues.apache.org/jira/browse/CASSANDRA-14825 its been
> discussed
> > on how a server side DDL can be provided to clients.
> >
> > The original thought was to use a virtual table to make it less invasive
> of
> > a change while providing access to the TableCQLHelper output (and fixing
> > it).
> >
> > The other is to add a DESCRIBE command to the cql protocol or query
> parser
> > so that the command would act same across all drivers as it does in
> cqlsh.
> >
> > In both cases it would return a ResultSet so from drivers perspective it
> > wont be too much different.
> >
> > Since the original thought was a virtual table the existing PR does that
> so
> > I lean in that direction. The virtual table is only 300 or so lines of
> code
> > too so its also smaller incremental step than changing protocol or
> grammar
> > (which can still happen, as mentioned in ticket "why not both").
> >
> > There is no consensus in ticket after nearly a year, so to get the review
> > moving on Id like to open up here for further/final discussion and or
> vote.
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

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

[Michael Shuler]

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: 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/org/apache/cassandra/apache-cassandra/4.0-alpha1/ 

Staging repository: 
https://repository.apache.org/content/repositories/orgapachecassandra-1177/


The Debian and RPM packages are available here: 
http://people.apache.org/~mshuler


The vote will be open for 24 hours (longer if needed).

[1]: CHANGES.txt: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative 

[2]: NEWS.txt: 
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative 



-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Apache Cassandra Google Season of Docs '19 update

[Dinesh Joshi]

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 have been 
assigned a technical writer, Deepak Vohra. Deepak has written ~20 technical 
books and is going to work with our community to help fix the TODOs and write 
documentation for 4.0. We are excited to be working with him on this. He will 
be creating jiras and reaching out to the dev list for questions and 
clarifications.

Thanks,

Dinesh & Nate
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

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

[Dinesh Joshi]

+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-14747 
>  are great.  These 
> will all improve the quality of the release.
> 
>> On Sep 5, 2019, at 4:03 PM, Joseph Lynch  wrote:
>> 
>> 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 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/org/apache/cassandra/apache-cassandra/4.0-alpha1/
 Staging repository:
 
>>> https://repository.apache.org/content/repositories/orgapachecassandra-1177/
 
 The Debian and RPM packages are available here:
 http://people.apache.org/~mshuler
 
 The vote will be open for 24 hours (longer if needed).
 
 [1]: CHANGES.txt:
 
 
>>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative
 [2]: NEWS.txt:
 
 
>>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
 For additional commands, e-mail: dev-h...@cassandra.apache.org
 
 
>>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

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

[Jeremy Hanna]

(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 great.  These will 
all improve the quality of the release.

> On Sep 5, 2019, at 4:03 PM, Joseph Lynch  wrote:
> 
> 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 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/org/apache/cassandra/apache-cassandra/4.0-alpha1/
>>> Staging repository:
>>> 
>> https://repository.apache.org/content/repositories/orgapachecassandra-1177/
>>> 
>>> The Debian and RPM packages are available here:
>>> http://people.apache.org/~mshuler
>>> 
>>> The vote will be open for 24 hours (longer if needed).
>>> 
>>> [1]: CHANGES.txt:
>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative
>>> [2]: NEWS.txt:
>>> 
>>> 
>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>> 
>>> 
>> 

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

[Joseph Lynch]

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 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/org/apache/cassandra/apache-cassandra/4.0-alpha1/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1177/
> >
> > The Debian and RPM packages are available here:
> > http://people.apache.org/~mshuler
> >
> > The vote will be open for 24 hours (longer if needed).
> >
> > [1]: CHANGES.txt:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative
> > [2]: NEWS.txt:
> >
> >
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

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

[Jon Haddad]

+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:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1177/org/apache/cassandra/apache-cassandra/4.0-alpha1/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1177/
>
> The Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
>
> The vote will be open for 24 hours (longer if needed).
>
> [1]: CHANGES.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative
> [2]: NEWS.txt:
>
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0-alpha1-tentative
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: [DISCUSS] Server side CQL schema

[Dinesh Joshi]

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 table?

Dinesh

> On Sep 5, 2019, at 2:57 PM, Chris Lohfink  wrote:
> 
> In https://issues.apache.org/jira/browse/CASSANDRA-14825 its been discussed
> on how a server side DDL can be provided to clients.
> 
> The original thought was to use a virtual table to make it less invasive of
> a change while providing access to the TableCQLHelper output (and fixing
> it).
> 
> The other is to add a DESCRIBE command to the cql protocol or query parser
> so that the command would act same across all drivers as it does in cqlsh.
> 
> In both cases it would return a ResultSet so from drivers perspective it
> wont be too much different.
> 
> Since the original thought was a virtual table the existing PR does that so
> I lean in that direction. The virtual table is only 300 or so lines of code
> too so its also smaller incremental step than changing protocol or grammar
> (which can still happen, as mentioned in ticket "why not both").
> 
> There is no consensus in ticket after nearly a year, so to get the review
> moving on Id like to open up here for further/final discussion and or vote.


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

[DISCUSS] Server side CQL schema

[Chris Lohfink]

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 to add a DESCRIBE command to the cql protocol or query parser
so that the command would act same across all drivers as it does in cqlsh.

In both cases it would return a ResultSet so from drivers perspective it
wont be too much different.

Since the original thought was a virtual table the existing PR does that so
I lean in that direction. The virtual table is only 300 or so lines of code
too so its also smaller incremental step than changing protocol or grammar
(which can still happen, as mentioned in ticket "why not both").

There is no consensus in ticket after nearly a year, so to get the review
moving on Id like to open up here for further/final discussion and or vote.

Re: Builds email notifications

[mck]

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


Done. Looks good so far.

`Cassandra-2.2-artifacts` has been failing for a while, so a manual rebuild 
there generated the following email: 
https://lists.apache.org/thread.html/7ad7f05786189117ac3fcf62a4b2a6eecd1dcc7f2ce03ca0f126d84f@%3Cbuilds.cassandra.apache.org%3E

(The Cassandra-2.2-artifacts job is failing because of more eclipse-warnings…)

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: How to stop github notification emails?

[Marcus Eriksson]

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 them to pr@ (or commits@) please?
>  
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: How to stop github notification emails?

[Mick Semb Wever]

> 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-mail: dev-h...@cassandra.apache.org

Re: How to stop github notification emails?

[Marcus Eriksson]

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 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 know I have never subscribed to that and I am (in most
> cases) not interested in random pull request comments.
> 
> Could you please let me know if there is some way how to turn this off?
> 
> Thank you a lot and have a nice day
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: How to stop github notification emails?

[Benedict Elliott Smith]

+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 #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 know I have never subscribed to that and I am (in most
cases) not interested in random pull request comments.

Could you please let me know if there is some way how to turn this off?

Thank you a lot and have a nice day

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

How to stop github notification emails?

[Stefan Miklosovic]

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 know I have never subscribed to that and I am (in most
cases) not interested in random pull request comments.

Could you please let me know if there is some way how to turn this off?

Thank you a lot and have a nice day

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

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

[GitBox]

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/


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

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

[GitBox]

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 message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org