[GitHub] cassandra issue #74: fixed typo in select example

2016-09-28 Thread hxzhaoyf 
Github user hxzhaoyf commented on the issue:

https://github.com/apache/cassandra/pull/74
  
hi, I think the definition of address type need to update too, because 
phone are UDT, and it should be frozen.
~~~
CREATE TYPE address (
street text,
city text,
zip int,
phones map
)
~~~


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Get in on the fun!

2016-09-28 Thread Nate McCall 
Folks,
We've made some good efforts growing the committer pool recently and
it would be super cool to start getting more people involved in day to
day reviews and commits. You can find a guide of how to do this here:

http://cassandra.apache.org/doc/latest/development/how_to_commit.html

Honestly, this was intimidating and the git incantations in the above
required me to look up a few things and ask for help. But I asked,
folks answered, and I moved forward. Basically, don't stay on the side
lines because it seems hard or you don't understand the process. It
*is* hard and the process is sophisticated. We learn by doing and it
gets easier each time so jump in and ask if you need help.

The following is a small list of recent "Patch Available" issues that
would be good practice if you are new (or if you are not and have not
done a commit in a while):
https://issues.apache.org/jira/browse/CASSANDRA-12706
https://issues.apache.org/jira/browse/CASSANDRA-12014
https://issues.apache.org/jira/browse/CASSANDRA-12457
https://issues.apache.org/jira/browse/CASSANDRA-12582

(Huge thanks to Stefania who has been all over Jira lately!).

The following has already been reviewed and just needs to be committed:
https://issues.apache.org/jira/browse/CASSANDRA-12632

Per that last issue, if you don't have commit access, feel free to
review a "Patch Available" issue adhering to the following:
http://cassandra.apache.org/doc/latest/development/how_to_review.html

Apply a comment saying you reviewed it and toggle it from "Patch
Available" to "Ready to Commit" via the "Workflow" drop down.

Thanks!
-Nate

[RELEASE] Apache Cassandra 2.2.8 released

2016-09-28 Thread Michael Shuler 
* NOTICE *
This is the first release signed with key 0xA278B781FE4B2BDA by Michael
Shuler. Debian users will need to add the key to `apt-key` and the
process has been updated on
https://wiki.apache.org/cassandra/DebianPackaging and patch created for
source docs.

Either method will work:

curl https://www.apache.org/dist/cassandra/KEYS | sudo apt-key add -

or

sudo apt-key adv --keyserver pool.sks-keyservers.net --recv-key
0xA278B781FE4B2BDA

**

The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.8.

Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.

 http://cassandra.apache.org/

Downloads of source and binary distributions are listed in our download
section:

 http://cassandra.apache.org/download/

This version is a bug fix release[1] on the 2.2 series. As always,
please pay attention to the release notes[2] and Let us know[3] if you
were to encounter any problem.

Enjoy!

[1]: (CHANGES.txt) https://goo.gl/pvdo31
[2]: (NEWS.txt) https://goo.gl/PbDAPY
[3]: https://issues.apache.org/jira/browse/CASSANDRA

Create table with ID - Question

2016-09-28 Thread Roman Bielik 
Hi,

in CQL it is possible to create a table with explicit ID: CREATE TABLE ...
WITH ID='xyz'.

Is something like this possible via Thrift interface?
There is an int32 "id" field in CfDef, but it has no effect on the table ID.

My problem is, that concurrent create table (add_column_family) requests
for the same table name result in clash with somewhat unpredictable
behavior.

This problem was reported in:
https://issues.apache.org/jira/browse/CASSANDRA-9933

and seems to be related to changes from ticket:
https://issues.apache.org/jira/browse/CASSANDRA-5202

A workaround for me could be using the same ID in create table, however I'm
using Thrift interface only.

Thank you.
Regards,
Roman

--

Re: Create table with ID - Question

2016-09-28 Thread Aleksey Yeschenko 
No way to do that via Thrift I’m afraid, nor will there be one. Sorry.

-- 
AY

On 28 September 2016 at 16:43:58, Roman Bielik 
(roman.bie...@openmindnetworks.com) wrote:

Hi,  

in CQL it is possible to create a table with explicit ID: CREATE TABLE ...  
WITH ID='xyz'.  

Is something like this possible via Thrift interface?  
There is an int32 "id" field in CfDef, but it has no effect on the table ID.  

My problem is, that concurrent create table (add_column_family) requests  
for the same table name result in clash with somewhat unpredictable  
behavior.  

This problem was reported in:  
https://issues.apache.org/jira/browse/CASSANDRA-9933  

and seems to be related to changes from ticket:  
https://issues.apache.org/jira/browse/CASSANDRA-5202  

A workaround for me could be using the same ID in create table, however I'm  
using Thrift interface only.  

Thank you.  
Regards,  
Roman  

--

Failing tests 2016-09-28

2016-09-28 Thread Philip Thompson 
Hi All,

cassandra-3.9:
===
testall: All passed!

===
dtest: 4 failures

cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest
 .test_round_trip_with_authentication
Flaky test, needs a Jira ticket


cql_tests.LWTTester
 .conditional_deletes_on_static_columns_with_null_values_test

cql_tests.LWTTeste
 r.conditional_deletes_on_static_columns_with_null_values_batch_test

cql_tests.LWTTester
 .conditional_updates_on_static_columns_with_null_values_test
These three failures are all the same, and need a ticket
===
upgrade: 661 failures

I won't enumerate these here. 12697 should resolve them, and also explains
where they're all coming from

===
novnode: All passed!

===

trunk:

===
testall: 13 failures

org.apache.cassandra.config.DatabaseDescriptorRefTest
 .testDatabaseDescriptorRef

org.apache.cassandra.config.DatabaseDescriptorRefTest
 .testDatabaseDescriptorRef-compression
CASSANDRA-12677 for the two failures above.

org.apache.cassandra.service.RemoveTest
 .testLocalHostId
CASSANDRA-12714

10 unlisted timeouts

===
dtest: 4 failures

materialized_views_test.TestMaterializedViews
 .clustering_column_test

materialized_views_test.TestMaterializedViews
 .insert_test

materialized_views_test.TestMaterializedViews
 .query_all_new_column_test

materialized_views_test.TestMaterializedViews
 .query_new_column_test

No need to file a jira for these, I've fixed them already.

===
upgrade: 662 failures

I won't enumerate these here. 12697 should resolve them, and also explains
where they're all coming from

===
novnode: 9 failures

Same 8 paging failures. CASSANDRA-12666

compaction_test.TestCompaction_with_DateTieredCompactionStrategy
 .bloomfilter_size_test
CASSANDRA-12711

Thanks,
Philip

Re: Create table with ID - Question

2016-09-28 Thread Edward Capriolo 
I have a similar set of problems. I will set the stage: in the past, for a
variety of reasons I had to create tables(column families) by time range
for an event processing system.

The man reason was expiring data (TTL) did not purge easily. It was easier
to simply truncate/drop old column families than two deal with different
evolving compaction strategies.

The main loop of my program looked like this:
public void writeThisStuff(List event ){
  MutationBatch mb;
  for (Event event : events){
mb.add(event)
  }
  maybeCreateNeededTables(mb)
  executeBatch(mb);
}

public void maybeCreateNeededTables(mb){
  Set columnFamilieToCreate =
  for (mutation : batch) {
 columnFamiliesToCreate.add(extractColumnFamilyFromMutation(mutation));
  }
  for (String cf: columnFamiliesToCreate){
 if ! hectorAstyanaxFlavoroftheweekclientDoesCfExist(cf)){
hectorAstyanaxFlavoroftheweekclienCreateCf(cf);
 }
  }
}

The size of the batches were in the 5-10K range. For a given batch the
number of target cfs was typically one, but at most two. That mean worst
case scenario 1 would need to be created. Effectively this meant 1 metadata
read before write. (You could cache the already existing columns as well).
One quick read is not a huge cost when you consider the savings of batching
5K roundtrips.

Even with this type of scenario you can run into a concurrent schema
problem. But you can add whatever gizmo to confirm schema agreement here:

  for (String cf: columnFamiliesToCreate){
*waitForSchemaToSettleGizmo()*
 if ! hectorAstyanaxFlavoroftheweekclientDoesCfExist(cf)){
*waitForSchemaToSettleGizmo()*
hectorAstyanaxFlavoroftheweekclienCreateCf(cf);
 }
  }

On Wed, Sep 28, 2016 at 12:01 PM, Aleksey Yeschenko 
wrote:

> No way to do that via Thrift I’m afraid, nor will there be one. Sorry.
>
> --
> AY
>
> On 28 September 2016 at 16:43:58, Roman Bielik (roman.bielik@
> openmindnetworks.com) wrote:
>
> Hi,
>
> in CQL it is possible to create a table with explicit ID: CREATE TABLE ...
> WITH ID='xyz'.
>
> Is something like this possible via Thrift interface?
> There is an int32 "id" field in CfDef, but it has no effect on the table
> ID.
>
> My problem is, that concurrent create table (add_column_family) requests
> for the same table name result in clash with somewhat unpredictable
> behavior.
>
> This problem was reported in:
> https://issues.apache.org/jira/browse/CASSANDRA-9933
>
> and seems to be related to changes from ticket:
> https://issues.apache.org/jira/browse/CASSANDRA-5202
>
> A workaround for me could be using the same ID in create table, however I'm
> using Thrift interface only.
>
> Thank you.
> Regards,
> Roman
>
> --
>
> 
> 
>  
>

Re: Failing tests 2016-09-28

2016-09-28 Thread Oleksandr Petrov 
LWTTester issues are leftovers from the bad merge in
https://github.com/riptano/cassandra-dtest/pull/1214

I've rebased and currently re-running tests.

On Wed, Sep 28, 2016 at 6:23 PM Philip Thompson <
philip.thomp...@datastax.com> wrote:

> Hi All,
>
> cassandra-3.9:
> ===
> testall: All passed!
>
> ===
> dtest: 4 failures
>
> cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest
>  .test_round_trip_with_authentication
> Flaky test, needs a Jira ticket
>
>
> cql_tests.LWTTester
>  .conditional_deletes_on_static_columns_with_null_values_test
>
> cql_tests.LWTTeste
>  r.conditional_deletes_on_static_columns_with_null_values_batch_test
>
> cql_tests.LWTTester
>  .conditional_updates_on_static_columns_with_null_values_test
> These three failures are all the same, and need a ticket
> ===
> upgrade: 661 failures
>
> I won't enumerate these here. 12697 should resolve them, and also explains
> where they're all coming from
>
> ===
> novnode: All passed!
>
> ===
>
> trunk:
>
> ===
> testall: 13 failures
>
> org.apache.cassandra.config.DatabaseDescriptorRefTest
>  .testDatabaseDescriptorRef
>
> org.apache.cassandra.config.DatabaseDescriptorRefTest
>  .testDatabaseDescriptorRef-compression
> CASSANDRA-12677 for the two failures above.
>
> org.apache.cassandra.service.RemoveTest
>  .testLocalHostId
> CASSANDRA-12714
>
> 10 unlisted timeouts
>
> ===
> dtest: 4 failures
>
> materialized_views_test.TestMaterializedViews
>  .clustering_column_test
>
> materialized_views_test.TestMaterializedViews
>  .insert_test
>
> materialized_views_test.TestMaterializedViews
>  .query_all_new_column_test
>
> materialized_views_test.TestMaterializedViews
>  .query_new_column_test
>
> No need to file a jira for these, I've fixed them already.
>
> ===
> upgrade: 662 failures
>
> I won't enumerate these here. 12697 should resolve them, and also explains
> where they're all coming from
>
> ===
> novnode: 9 failures
>
> Same 8 paging failures. CASSANDRA-12666
>
> compaction_test.TestCompaction_with_DateTieredCompactionStrategy
>  .bloomfilter_size_test
> CASSANDRA-12711
>
> Thanks,
> Philip
>
-- 
Alex Petrov

Re: Create table with ID - Question

2016-09-28 Thread Ken Hancock 
So I confirmed with Aleksey before firmly sticking foot in mouth, but you
CAN do this through Thrift -- Thrift has an API for sending a CQL string
via the Thrift interface..  We used to do something similar through Hector.

Not sure if this strictly fits your "is this possible via Thrift
interface"...


On Wed, Sep 28, 2016 at 12:01 PM, Aleksey Yeschenko 
wrote:

> No way to do that via Thrift I’m afraid, nor will there be one. Sorry.
>
> --
> AY
>
> On 28 September 2016 at 16:43:58, Roman Bielik (roman.bielik@
> openmindnetworks.com) wrote:
>
> Hi,
>
> in CQL it is possible to create a table with explicit ID: CREATE TABLE ...
> WITH ID='xyz'.
>
> Is something like this possible via Thrift interface?
> There is an int32 "id" field in CfDef, but it has no effect on the table
> ID.
>
> My problem is, that concurrent create table (add_column_family) requests
> for the same table name result in clash with somewhat unpredictable
> behavior.
>
> This problem was reported in:
> https://issues.apache.org/jira/browse/CASSANDRA-9933
>
> and seems to be related to changes from ticket:
> https://issues.apache.org/jira/browse/CASSANDRA-5202
>
> A workaround for me could be using the same ID in create table, however I'm
> using Thrift interface only.
>
> Thank you.
> Regards,
> Roman
>
> --
>
> 
> 
>  
>

Re: Failing tests 2016-09-28

2016-09-28 Thread Philip Thompson 
That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it
accidentally also merged into 3.9?

On Wed, Sep 28, 2016 at 12:40 PM, Oleksandr Petrov <
oleksandr.pet...@gmail.com> wrote:

> LWTTester issues are leftovers from the bad merge in
> https://github.com/riptano/cassandra-dtest/pull/1214
>
> I've rebased and currently re-running tests.
>
> On Wed, Sep 28, 2016 at 6:23 PM Philip Thompson <
> philip.thomp...@datastax.com> wrote:
>
> > Hi All,
> >
> > cassandra-3.9:
> > ===
> > testall: All passed!
> >
> > ===
> > dtest: 4 failures
> >
> > cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest
> >  .test_round_trip_with_authentication
> > Flaky test, needs a Jira ticket
> >
> >
> > cql_tests.LWTTester
> >  .conditional_deletes_on_static_columns_with_null_values_test
> >
> > cql_tests.LWTTeste
> >  r.conditional_deletes_on_static_columns_with_null_values_batch_test
> >
> > cql_tests.LWTTester
> >  .conditional_updates_on_static_columns_with_null_values_test
> > These three failures are all the same, and need a ticket
> > ===
> > upgrade: 661 failures
> >
> > I won't enumerate these here. 12697 should resolve them, and also
> explains
> > where they're all coming from
> >
> > ===
> > novnode: All passed!
> >
> > ===
> >
> > trunk:
> >
> > ===
> > testall: 13 failures
> >
> > org.apache.cassandra.config.DatabaseDescriptorRefTest
> >  .testDatabaseDescriptorRef
> >
> > org.apache.cassandra.config.DatabaseDescriptorRefTest
> >  .testDatabaseDescriptorRef-compression
> > CASSANDRA-12677 for the two failures above.
> >
> > org.apache.cassandra.service.RemoveTest
> >  .testLocalHostId
> > CASSANDRA-12714
> >
> > 10 unlisted timeouts
> >
> > ===
> > dtest: 4 failures
> >
> > materialized_views_test.TestMaterializedViews
> >  .clustering_column_test
> >
> > materialized_views_test.TestMaterializedViews
> >  .insert_test
> >
> > materialized_views_test.TestMaterializedViews
> >  .query_all_new_column_test
> >
> > materialized_views_test.TestMaterializedViews
> >  .query_new_column_test
> >
> > No need to file a jira for these, I've fixed them already.
> >
> > ===
> > upgrade: 662 failures
> >
> > I won't enumerate these here. 12697 should resolve them, and also
> explains
> > where they're all coming from
> >
> > ===
> > novnode: 9 failures
> >
> > Same 8 paging failures. CASSANDRA-12666
> >
> > compaction_test.TestCompaction_with_DateTieredCompactionStrategy
> >  .bloomfilter_size_test
> > CASSANDRA-12711
> >
> > Thanks,
> > Philip
> >
> --
> Alex Petrov
>

Re: Failing tests 2016-09-28

2016-09-28 Thread Oleksandr Petrov 
Might be I have only made differentiation for trunk and 2.x.

I'll investigate and report on JIRA. Thanks for assigning.

On Wed, Sep 28, 2016 at 6:48 PM Philip Thompson <
philip.thomp...@datastax.com> wrote:

> That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it
> accidentally also merged into 3.9?
>
> On Wed, Sep 28, 2016 at 12:40 PM, Oleksandr Petrov <
> oleksandr.pet...@gmail.com> wrote:
>
> > LWTTester issues are leftovers from the bad merge in
> > https://github.com/riptano/cassandra-dtest/pull/1214
> >
> > I've rebased and currently re-running tests.
> >
> > On Wed, Sep 28, 2016 at 6:23 PM Philip Thompson <
> > philip.thomp...@datastax.com> wrote:
> >
> > > Hi All,
> > >
> > > cassandra-3.9:
> > > ===
> > > testall: All passed!
> > >
> > > ===
> > > dtest: 4 failures
> > >
> > > cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest
> > >  .test_round_trip_with_authentication
> > > Flaky test, needs a Jira ticket
> > >
> > >
> > > cql_tests.LWTTester
> > >  .conditional_deletes_on_static_columns_with_null_values_test
> > >
> > > cql_tests.LWTTeste
> > >  r.conditional_deletes_on_static_columns_with_null_values_batch_test
> > >
> > > cql_tests.LWTTester
> > >  .conditional_updates_on_static_columns_with_null_values_test
> > > These three failures are all the same, and need a ticket
> > > ===
> > > upgrade: 661 failures
> > >
> > > I won't enumerate these here. 12697 should resolve them, and also
> > explains
> > > where they're all coming from
> > >
> > > ===
> > > novnode: All passed!
> > >
> > > ===
> > >
> > > trunk:
> > >
> > > ===
> > > testall: 13 failures
> > >
> > > org.apache.cassandra.config.DatabaseDescriptorRefTest
> > >  .testDatabaseDescriptorRef
> > >
> > > org.apache.cassandra.config.DatabaseDescriptorRefTest
> > >  .testDatabaseDescriptorRef-compression
> > > CASSANDRA-12677 for the two failures above.
> > >
> > > org.apache.cassandra.service.RemoveTest
> > >  .testLocalHostId
> > > CASSANDRA-12714
> > >
> > > 10 unlisted timeouts
> > >
> > > ===
> > > dtest: 4 failures
> > >
> > > materialized_views_test.TestMaterializedViews
> > >  .clustering_column_test
> > >
> > > materialized_views_test.TestMaterializedViews
> > >  .insert_test
> > >
> > > materialized_views_test.TestMaterializedViews
> > >  .query_all_new_column_test
> > >
> > > materialized_views_test.TestMaterializedViews
> > >  .query_new_column_test
> > >
> > > No need to file a jira for these, I've fixed them already.
> > >
> > > ===
> > > upgrade: 662 failures
> > >
> > > I won't enumerate these here. 12697 should resolve them, and also
> > explains
> > > where they're all coming from
> > >
> > > ===
> > > novnode: 9 failures
> > >
> > > Same 8 paging failures. CASSANDRA-12666
> > >
> > > compaction_test.TestCompaction_with_DateTieredCompactionStrategy
> > >  .bloomfilter_size_test
> > > CASSANDRA-12711
> > >
> > > Thanks,
> > > Philip
> > >
> > --
> > Alex Petrov
> >
>
-- 
Alex Petrov

Re: Failing tests 2016-09-28

2016-09-28 Thread Aleksey Yeschenko 
We had one accidental merge from 3.0 into 3.9 (looking at you, you know who you 
are), so could be.

-- 
AY

On 28 September 2016 at 17:48:27, Philip Thompson 
(philip.thomp...@datastax.com) wrote:

That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it  
accidentally also merged into 3.9?  

On Wed, Sep 28, 2016 at 12:40 PM, Oleksandr Petrov <  
oleksandr.pet...@gmail.com> wrote:  

> LWTTester issues are leftovers from the bad merge in  
> https://github.com/riptano/cassandra-dtest/pull/1214  
>  
> I've rebased and currently re-running tests.  
>  
> On Wed, Sep 28, 2016 at 6:23 PM Philip Thompson <  
> philip.thomp...@datastax.com> wrote:  
>  
> > Hi All,  
> >  
> > cassandra-3.9:  
> > ===  
> > testall: All passed!  
> >  
> > ===  
> > dtest: 4 failures  
> >  
> > cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest  
> > .test_round_trip_with_authentication  
> > Flaky test, needs a Jira ticket  
> >  
> >  
> > cql_tests.LWTTester  
> > .conditional_deletes_on_static_columns_with_null_values_test  
> >  
> > cql_tests.LWTTeste  
> > r.conditional_deletes_on_static_columns_with_null_values_batch_test  
> >  
> > cql_tests.LWTTester  
> > .conditional_updates_on_static_columns_with_null_values_test  
> > These three failures are all the same, and need a ticket  
> > ===  
> > upgrade: 661 failures  
> >  
> > I won't enumerate these here. 12697 should resolve them, and also  
> explains  
> > where they're all coming from  
> >  
> > ===  
> > novnode: All passed!  
> >  
> > ===  
> >  
> > trunk:  
> >  
> > ===  
> > testall: 13 failures  
> >  
> > org.apache.cassandra.config.DatabaseDescriptorRefTest  
> > .testDatabaseDescriptorRef  
> >  
> > org.apache.cassandra.config.DatabaseDescriptorRefTest  
> > .testDatabaseDescriptorRef-compression  
> > CASSANDRA-12677 for the two failures above.  
> >  
> > org.apache.cassandra.service.RemoveTest  
> > .testLocalHostId  
> > CASSANDRA-12714  
> >  
> > 10 unlisted timeouts  
> >  
> > ===  
> > dtest: 4 failures  
> >  
> > materialized_views_test.TestMaterializedViews  
> > .clustering_column_test  
> >  
> > materialized_views_test.TestMaterializedViews  
> > .insert_test  
> >  
> > materialized_views_test.TestMaterializedViews  
> > .query_all_new_column_test  
> >  
> > materialized_views_test.TestMaterializedViews  
> > .query_new_column_test  
> >  
> > No need to file a jira for these, I've fixed them already.  
> >  
> > ===  
> > upgrade: 662 failures  
> >  
> > I won't enumerate these here. 12697 should resolve them, and also  
> explains  
> > where they're all coming from  
> >  
> > ===  
> > novnode: 9 failures  
> >  
> > Same 8 paging failures. CASSANDRA-12666  
> >  
> > compaction_test.TestCompaction_with_DateTieredCompactionStrategy  
> > .bloomfilter_size_test  
> > CASSANDRA-12711  
> >  
> > Thanks,  
> > Philip  
> >  
> --  
> Alex Petrov  
>

Re: Failing tests 2016-09-28

2016-09-28 Thread Oleksandr Petrov 
No, not really. It's just that dtests currently expect same behaviour for
3.x and up.


On Wed, Sep 28, 2016 at 8:41 PM Aleksey Yeschenko 
wrote:

> We had one accidental merge from 3.0 into 3.9 (looking at you, you know
> who you are), so could be.
>
> --
> AY
>
> On 28 September 2016 at 17:48:27, Philip Thompson (
> philip.thomp...@datastax.com) wrote:
>
> That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it
> accidentally also merged into 3.9?
>
> On Wed, Sep 28, 2016 at 12:40 PM, Oleksandr Petrov <
> oleksandr.pet...@gmail.com> wrote:
>
> > LWTTester issues are leftovers from the bad merge in
> > https://github.com/riptano/cassandra-dtest/pull/1214
> >
> > I've rebased and currently re-running tests.
> >
> > On Wed, Sep 28, 2016 at 6:23 PM Philip Thompson <
> > philip.thomp...@datastax.com> wrote:
> >
> > > Hi All,
> > >
> > > cassandra-3.9:
> > > ===
> > > testall: All passed!
> > >
> > > ===
> > > dtest: 4 failures
> > >
> > > cqlsh_tests.cqlsh_copy_tests.CqlshCopyTest
> > > .test_round_trip_with_authentication
> > > Flaky test, needs a Jira ticket
> > >
> > >
> > > cql_tests.LWTTester
> > > .conditional_deletes_on_static_columns_with_null_values_test
> > >
> > > cql_tests.LWTTeste
> > > r.conditional_deletes_on_static_columns_with_null_values_batch_test
> > >
> > > cql_tests.LWTTester
> > > .conditional_updates_on_static_columns_with_null_values_test
> > > These three failures are all the same, and need a ticket
> > > ===
> > > upgrade: 661 failures
> > >
> > > I won't enumerate these here. 12697 should resolve them, and also
> > explains
> > > where they're all coming from
> > >
> > > ===
> > > novnode: All passed!
> > >
> > > ===
> > >
> > > trunk:
> > >
> > > ===
> > > testall: 13 failures
> > >
> > > org.apache.cassandra.config.DatabaseDescriptorRefTest
> > > .testDatabaseDescriptorRef
> > >
> > > org.apache.cassandra.config.DatabaseDescriptorRefTest
> > > .testDatabaseDescriptorRef-compression
> > > CASSANDRA-12677 for the two failures above.
> > >
> > > org.apache.cassandra.service.RemoveTest
> > > .testLocalHostId
> > > CASSANDRA-12714
> > >
> > > 10 unlisted timeouts
> > >
> > > ===
> > > dtest: 4 failures
> > >
> > > materialized_views_test.TestMaterializedViews
> > > .clustering_column_test
> > >
> > > materialized_views_test.TestMaterializedViews
> > > .insert_test
> > >
> > > materialized_views_test.TestMaterializedViews
> > > .query_all_new_column_test
> > >
> > > materialized_views_test.TestMaterializedViews
> > > .query_new_column_test
> > >
> > > No need to file a jira for these, I've fixed them already.
> > >
> > > ===
> > > upgrade: 662 failures
> > >
> > > I won't enumerate these here. 12697 should resolve them, and also
> > explains
> > > where they're all coming from
> > >
> > > ===
> > > novnode: 9 failures
> > >
> > > Same 8 paging failures. CASSANDRA-12666
> > >
> > > compaction_test.TestCompaction_with_DateTieredCompactionStrategy
> > > .bloomfilter_size_test
> > > CASSANDRA-12711
> > >
> > > Thanks,
> > > Philip
> > >
> > --
> > Alex Petrov
> >
>
-- 
Alex Petrov