[jira] [Updated] (CASSANDRA-13633) Data not loading to keyspace using sstable create via CQLSSTableWriter

2017-06-23 Thread Michael Shuler (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-13633:
---
Fix Version/s: (was: 3.10)
   3.11.x

> Data not loading to keyspace using sstable create via CQLSSTableWriter
> --
>
> Key: CASSANDRA-13633
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13633
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
> Environment: Linux
>Reporter: Arpan Khandelwal
> Fix For: 3.11.x
>
> Attachments: dataloading_result.png
>
>
> Scenario : Need to read CSV, Write SSTable using CQLSSTableWriter and load it 
> to the keyspace. [Explained 
> here|https://stackoverflow.com/questions/44713777/json-cassandra-field-value-parsing-using-antlr4]
>  . That was not working so tried a simple test case available 
> here[https://github.com/apache/cassandra/blob/cassandra-3.11/test/unit/org/apache/cassandra/io/sstable/CQLSSTableWriterTest.java#L378]
> Which did not worked either. Following is what i tried.
> Created cql_keyspace3 with below table and types.
> {code:java}
> CREATE TYPE cql_keyspace3.tuple2 (a int, b int);
> CREATE TYPE cql_keyspace3.tuple3 (a int, b int, c int)
> CREATE TABLE cql_keyspace3.table3 ( k int, v1 list, v2 
> frozen, PRIMARY KEY (k));
> {code}
> ran code 
> {code:java}
> final String KS = "cql_keyspace3";
> final String TABLE = "table3";
> final String schema = "CREATE TABLE " + KS + "." + TABLE + " (" + "  
> k int," + "  v1 list,"
> + "  v2 frozen," + "  PRIMARY KEY (k)" + ")";
> File tempdir = Files.createTempDir();
> File dataDir = new File(tempdir.getAbsolutePath() + File.separator + 
> KS + File.separator + TABLE);
> System.out.println(dataDir);
> assert dataDir.mkdirs();
> CQLSSTableWriter writer = 
> CQLSSTableWriter.builder().inDirectory(dataDir)
> .withType("CREATE TYPE " + KS + ".tuple2 (a int, b int)")
> .withType("CREATE TYPE " + KS + ".tuple3 (a int, b int, c 
> int)").forTable(schema)
> .using("INSERT INTO " + KS + "." + TABLE + " (k, v1, v2) " + 
> "VALUES (?, ?, ?)").build();
> 
> 
> UserType tuple2Type = writer.getUDType("tuple2");
> UserType tuple3Type = writer.getUDType("tuple3");
> for (int i = 0; i < 100; i++) {
> writer.addRow(i,
> 
> ImmutableList.builder().add(tuple2Type.newValue().setInt("a", i * 
> 10).setInt("b", i * 20))
> .add(tuple2Type.newValue().setInt("a", i * 
> 30).setInt("b", i * 40)).build(),
> tuple3Type.newValue().setInt("a", i * 100).setInt("b", i 
> * 200).setInt("c", i * 300));
> }
> writer.close();
> {code}
> It generated sstable in "/tmp/1498224996687-0/cql_keyspace3" dir
> Loaded data using following command 
> {code:java}
> /tmp/1498224996687-0/cql_keyspace3 $ sstableloader -d localhost 
> table3-e6e0fa61581911e78be6a72ebce4c745/
> Established connection to initial hosts
> Opening sstables and calculating sections to stream
> Streaming relevant part of 
> /tmp/1498224996687-0/cql_keyspace3/table3-e6e0fa61581911e78be6a72ebce4c745/mc-2-big-Data.db
>  to [localhost/127.0.0.1]
> progress: [localhost/127.0.0.1]0:1/1 100% total: 100% 1.060KiB/s (avg: 
> 1.060KiB/s)
> progress: [localhost/127.0.0.1]0:1/1 100% total: 100% 0.000KiB/s (avg: 
> 0.984KiB/s)
> Summary statistics: 
>Connections per host: 1 
>Total files transferred : 1 
>Total bytes transferred : 5.572KiB  
>Total duration  : 5668 ms   
>Average transfer rate   : 0.982KiB/s
>Peak transfer rate  : 1.060KiB/s
> {code}
> ||k||v1||v2||
> |92|[{a:920,b:1840}, {a:2760,b:3680}]|
> find full result in attached snapshot.
> Please let me know which version of cassandra I should which can allow me to 
> load  reseverd types, collections, UDT from sstable create using 
> CQLSSTableWriter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Comment Edited] (CASSANDRA-13632) Digest mismatch if row is empty

2017-06-23 Thread Jay Zhuang (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061717#comment-16061717
 ] 

Jay Zhuang edited comment on CASSANDRA-13632 at 6/24/17 2:24 AM:
-

Hi [~whangsf], could you please help me to reproduce the problem locally, here 
is what I did:

{noformat}
CREATE KEYSPACE foo WITH replication = {'class': 'NetworkTopologyStrategy', 
'dc1': '3' };
CREATE TABLE foo.foo ( key int, foo int, col int, PRIMARY KEY (key, foo) ) with 
dclocal_read_repair_chance=0;
CONSISTENCY QUORUM;
INSERT INTO foo.foo (key, foo) VALUES ( 1,1);
TRACING ON;
SELECT key FROM foo.foo WHERE key = 1 and foo =2;
{noformat}

But no Repair event:
{noformat}
cqlsh> SELECT key FROM foo.foo WHERE key = 1 and foo =2;

 key
-

(0 rows)

Tracing session: 2cb5aa80-5884-11e7-be43-dfd5ff1ad595

 activity   
  | timestamp  | source| source_elapsed
--++---+
   Execute 
CQL3 query | 2017-06-24 02:23:56.712000 | 127.0.0.1 |  0
  Parsing SELECT key FROM foo.foo WHERE key = 1 and foo =2; 
[SharedPool-Worker-1] | 2017-06-24 02:23:56.712000 | 127.0.0.1 |187
Preparing statement 
[SharedPool-Worker-1] | 2017-06-24 02:23:56.713000 | 127.0.0.1 |411
 reading digest from /127.0.0.3 
[SharedPool-Worker-1] | 2017-06-24 02:23:56.713000 | 127.0.0.1 |976
Executing single-partition query on foo 
[SharedPool-Worker-2] | 2017-06-24 02:23:56.713000 | 127.0.0.1 |   1004
   Acquiring sstable references 
[SharedPool-Worker-2] | 2017-06-24 02:23:56.713000 | 127.0.0.1 |   1057
  Merging memtable contents 
[SharedPool-Worker-2] | 2017-06-24 02:23:56.713000 | 127.0.0.1 |   1083
Sending READ message to /127.0.0.3 
[MessagingService-Outgoing-/127.0.0.3] | 2017-06-24 02:23:56.713000 | 127.0.0.1 
|   1124
 READ message received from /127.0.0.1 
[MessagingService-Incoming-/127.0.0.1] | 2017-06-24 02:23:56.714000 | 127.0.0.3 
| 21
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-2] | 2017-06-24 02:23:56.714000 | 127.0.0.1 |   1249
Executing single-partition query on foo 
[SharedPool-Worker-1] | 2017-06-24 02:23:56.714000 | 127.0.0.3 |145
 REQUEST_RESPONSE message received from /127.0.0.3 
[MessagingService-Incoming-/127.0.0.3] | 2017-06-24 02:23:56.714000 | 127.0.0.1 
|   2198
   Acquiring sstable references 
[SharedPool-Worker-1] | 2017-06-24 02:23:56.714000 | 127.0.0.3 |214
  Merging memtable contents 
[SharedPool-Worker-1] | 2017-06-24 02:23:56.714000 | 127.0.0.3 |265
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-1] | 2017-06-24 02:23:56.714000 | 127.0.0.3 |466
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-1] | 2017-06-24 02:23:56.714000 | 127.0.0.3 |538
   Enqueuing response to /127.0.0.1 
[SharedPool-Worker-1] | 2017-06-24 02:23:56.714001 | 127.0.0.3 |596
Sending REQUEST_RESPONSE message to /127.0.0.1 
[MessagingService-Outgoing-/127.0.0.1] | 2017-06-24 02:23:56.714001 | 127.0.0.3 
|671
Processing response from /127.0.0.3 
[SharedPool-Worker-2] | 2017-06-24 02:23:56.715000 | 127.0.0.1 |   2324
 
Request complete | 2017-06-24 02:23:56.714453 | 127.0.0.1 |   2453
{noformat}


was (Author: jay.zhuang):
Hi [~whangsf], could you please help me to reproduce the problem locally, here 
is what I did:

{noformat}
CREATE KEYSPACE foo WITH replication = {'class': 'NetworkTopologyStrategy', 
'dc1': '3' };
CREATE TABLE foo.foo ( key int, foo int, col int, PRIMARY KEY (key, foo) ) with 
dclocal_read_repair_chance=0;
CONSISTENCY QUORUM;
INSERT INTO foo.foo (key, foo) VALUES ( 1,1);
TRACING ON;
SELECT * FROM foo.foo WHERE key = 1 and foo =2;
{noformat}

But no Repair event:
{noformat}
cqlsh> SELECT * FROM foo.foo WHERE key = 1 and foo =2;

 key | foo | col
-+-+-

(0 rows)

Tracing session: e9751120-5879-11e7-be43-dfd5ff1ad595

 activity   
  | timestamp  | source   

[jira] [Comment Edited] (CASSANDRA-13632) Digest mismatch if row is empty

2017-06-23 Thread Jay Zhuang (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061717#comment-16061717
 ] 

Jay Zhuang edited comment on CASSANDRA-13632 at 6/24/17 1:16 AM:
-

Hi [~whangsf], could you please help me to reproduce the problem locally, here 
is what I did:

{noformat}
CREATE KEYSPACE foo WITH replication = {'class': 'NetworkTopologyStrategy', 
'dc1': '3' };
CREATE TABLE foo.foo ( key int, foo int, col int, PRIMARY KEY (key, foo) ) with 
dclocal_read_repair_chance=0;
CONSISTENCY QUORUM;
INSERT INTO foo.foo (key, foo) VALUES ( 1,1);
TRACING ON;
SELECT * FROM foo.foo WHERE key = 1 and foo =2;
{noformat}

But no Repair event:
{noformat}
cqlsh> SELECT * FROM foo.foo WHERE key = 1 and foo =2;

 key | foo | col
-+-+-

(0 rows)

Tracing session: e9751120-5879-11e7-be43-dfd5ff1ad595

 activity   
  | timestamp  | source| source_elapsed
--++---+
   Execute 
CQL3 query | 2017-06-24 01:10:28.914000 | 127.0.0.1 |  0
Parsing SELECT * FROM foo.foo WHERE key = 1 and foo =2; 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.914000 | 127.0.0.1 |220
Preparing statement 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.914000 | 127.0.0.1 |423
 READ message received from /127.0.0.1 
[MessagingService-Incoming-/127.0.0.1] | 2017-06-24 01:10:28.915000 | 127.0.0.2 
| 40
 reading digest from /127.0.0.2 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1115
Executing single-partition query on foo 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1123
   Acquiring sstable references 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1189
  Merging memtable contents 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1228
Sending READ message to /127.0.0.2 
[MessagingService-Outgoing-/127.0.0.2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 
|   1326
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1424
Executing single-partition query on foo 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |221
 REQUEST_RESPONSE message received from /127.0.0.2 
[MessagingService-Incoming-/127.0.0.2] | 2017-06-24 01:10:28.916000 | 127.0.0.1 
|   2817
   Acquiring sstable references 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |342
  Merging memtable contents 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |402
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |640
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |714
   Enqueuing response to /127.0.0.1 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |770
Sending REQUEST_RESPONSE message to /127.0.0.1 
[MessagingService-Outgoing-/127.0.0.1] | 2017-06-24 01:10:28.916001 | 127.0.0.2 
|917
Processing response from /127.0.0.2 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.917000 | 127.0.0.1 |   2916
 
Request complete | 2017-06-24 01:10:28.917133 | 127.0.0.1 |   3133
{noformat}


was (Author: jay.zhuang):
Hi [~whangsf], could you please help me to reproduce the problem locally, here 
is what I did:

{noformat}
CREATE KEYSPACE foo WITH replication = {'class': 'NetworkTopologyStrategy', 
'dc1': '3' };
CREATE TABLE foo.foo ( key int, foo int, col int, PRIMARY KEY (key, foo) ) with 
dclocal_read_repair_chance=0;
CONSISTENCY QUORUM;
INSERT INTO foo.foo (key, foo) VALUES ( 1,1);
TRACING ON;
SELECT * FROM foo.foo WHERE key = 1 and foo =2;
{noformat}

But Ino Repair event:
{noformat}
cqlsh> SELECT * FROM foo.foo WHERE key = 1 and foo =2;

 key | foo | col
-+-+-

(0 rows)

Tracing session: e9751120-5879-11e7-be43-dfd5ff1ad595

 activity   
  | timestamp

[jira] [Comment Edited] (CASSANDRA-13632) Digest mismatch if row is empty

2017-06-23 Thread Jay Zhuang (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061717#comment-16061717
 ] 

Jay Zhuang edited comment on CASSANDRA-13632 at 6/24/17 1:15 AM:
-

Hi [~whangsf], could you please help me to reproduce the problem locally, here 
is what I did:

{noformat}
CREATE KEYSPACE foo WITH replication = {'class': 'NetworkTopologyStrategy', 
'dc1': '3' };
CREATE TABLE foo.foo ( key int, foo int, col int, PRIMARY KEY (key, foo) ) with 
dclocal_read_repair_chance=0;
CONSISTENCY QUORUM;
INSERT INTO foo.foo (key, foo) VALUES ( 1,1);
TRACING ON;
SELECT * FROM foo.foo WHERE key = 1 and foo =2;
{noformat}

But Ino Repair event:
{noformat}
cqlsh> SELECT * FROM foo.foo WHERE key = 1 and foo =2;

 key | foo | col
-+-+-

(0 rows)

Tracing session: e9751120-5879-11e7-be43-dfd5ff1ad595

 activity   
  | timestamp  | source| source_elapsed
--++---+
   Execute 
CQL3 query | 2017-06-24 01:10:28.914000 | 127.0.0.1 |  0
Parsing SELECT * FROM foo.foo WHERE key = 1 and foo =2; 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.914000 | 127.0.0.1 |220
Preparing statement 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.914000 | 127.0.0.1 |423
 READ message received from /127.0.0.1 
[MessagingService-Incoming-/127.0.0.1] | 2017-06-24 01:10:28.915000 | 127.0.0.2 
| 40
 reading digest from /127.0.0.2 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1115
Executing single-partition query on foo 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1123
   Acquiring sstable references 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1189
  Merging memtable contents 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1228
Sending READ message to /127.0.0.2 
[MessagingService-Outgoing-/127.0.0.2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 
|   1326
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1424
Executing single-partition query on foo 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |221
 REQUEST_RESPONSE message received from /127.0.0.2 
[MessagingService-Incoming-/127.0.0.2] | 2017-06-24 01:10:28.916000 | 127.0.0.1 
|   2817
   Acquiring sstable references 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |342
  Merging memtable contents 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |402
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |640
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |714
   Enqueuing response to /127.0.0.1 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |770
Sending REQUEST_RESPONSE message to /127.0.0.1 
[MessagingService-Outgoing-/127.0.0.1] | 2017-06-24 01:10:28.916001 | 127.0.0.2 
|917
Processing response from /127.0.0.2 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.917000 | 127.0.0.1 |   2916
 
Request complete | 2017-06-24 01:10:28.917133 | 127.0.0.1 |   3133
{noformat}


was (Author: jay.zhuang):
Hi [~whangsf], could you please help me to reproduce the problem locally, here 
is what I did:

{noformat}
CREATE KEYSPACE foo WITH replication = {'class': 'NetworkTopologyStrategy', 
'dc1': '3' };
CREATE TABLE foo.foo ( key int, foo int, col int, PRIMARY KEY (key, foo) ) with 
dclocal_read_repair_chance=0;
CONSISTENCY QUORUM;
INSERT INTO foo.foo (key, foo) VALUES ( 1,1);
TRACING ON;
SELECT * FROM foo.foo WHERE key = 1 and foo =2;
{noformat}

But I don't see Repair event:
{noformat}
cqlsh> SELECT * FROM foo.foo WHERE key = 1 and foo =2;

 key | foo | col
-+-+-

(0 rows)

Tracing session: e9751120-5879-11e7-be43-dfd5ff1ad595

 activity   
  | 

[jira] [Commented] (CASSANDRA-13632) Digest mismatch if row is empty

2017-06-23 Thread Jay Zhuang (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061717#comment-16061717
 ] 

Jay Zhuang commented on CASSANDRA-13632:


Hi [~whangsf], could you please help me to reproduce the problem locally, here 
is what I did:

{noformat}
CREATE KEYSPACE foo WITH replication = {'class': 'NetworkTopologyStrategy', 
'dc1': '3' };
CREATE TABLE foo.foo ( key int, foo int, col int, PRIMARY KEY (key, foo) ) with 
dclocal_read_repair_chance=0;
CONSISTENCY QUORUM;
INSERT INTO foo.foo (key, foo) VALUES ( 1,1);
TRACING ON;
SELECT * FROM foo.foo WHERE key = 1 and foo =2;
{noformat}

But I don't see Repair event:
{noformat}
cqlsh> SELECT * FROM foo.foo WHERE key = 1 and foo =2;

 key | foo | col
-+-+-

(0 rows)

Tracing session: e9751120-5879-11e7-be43-dfd5ff1ad595

 activity   
  | timestamp  | source| source_elapsed
--++---+
   Execute 
CQL3 query | 2017-06-24 01:10:28.914000 | 127.0.0.1 |  0
Parsing SELECT * FROM foo.foo WHERE key = 1 and foo =2; 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.914000 | 127.0.0.1 |220
Preparing statement 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.914000 | 127.0.0.1 |423
 READ message received from /127.0.0.1 
[MessagingService-Incoming-/127.0.0.1] | 2017-06-24 01:10:28.915000 | 127.0.0.2 
| 40
 reading digest from /127.0.0.2 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1115
Executing single-partition query on foo 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1123
   Acquiring sstable references 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1189
  Merging memtable contents 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1228
Sending READ message to /127.0.0.2 
[MessagingService-Outgoing-/127.0.0.2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 
|   1326
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.915000 | 127.0.0.1 |   1424
Executing single-partition query on foo 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |221
 REQUEST_RESPONSE message received from /127.0.0.2 
[MessagingService-Incoming-/127.0.0.2] | 2017-06-24 01:10:28.916000 | 127.0.0.1 
|   2817
   Acquiring sstable references 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |342
  Merging memtable contents 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |402
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |640
  Read 0 live and 0 tombstone cells 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |714
   Enqueuing response to /127.0.0.1 
[SharedPool-Worker-1] | 2017-06-24 01:10:28.916000 | 127.0.0.2 |770
Sending REQUEST_RESPONSE message to /127.0.0.1 
[MessagingService-Outgoing-/127.0.0.1] | 2017-06-24 01:10:28.916001 | 127.0.0.2 
|917
Processing response from /127.0.0.2 
[SharedPool-Worker-2] | 2017-06-24 01:10:28.917000 | 127.0.0.1 |   2916
 
Request complete | 2017-06-24 01:10:28.917133 | 127.0.0.1 |   3133
{noformat}

> Digest mismatch if row is empty
> ---
>
> Key: CASSANDRA-13632
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13632
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local Write-Read Paths
>Reporter: Andrew Whang
>Assignee: Andrew Whang
> Fix For: 3.0.x
>
>
> This issue is similar to CASSANDRA-12090. Quorum read queries that include a 
> column selector (non-wildcard) result in digest mismatch when the row is 
> empty (key does not exist). It seems the data serialization path checks if 
> rowIterator.isEmpty() and if so ignores column names (by setting IS_EMPTY 
> flag). However, the digest serialization path does not perform this check and 
> includes column names. 

[jira] [Updated] (CASSANDRA-13440) Sign RPM artifacts

2017-06-23 Thread Michael Shuler (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-13440:
---
Fix Version/s: 3.0.14
   3.11.0

> Sign RPM artifacts
> --
>
> Key: CASSANDRA-13440
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13440
> Project: Cassandra
>  Issue Type: Sub-task
>  Components: Packaging
>Reporter: Stefan Podkowinski
>Assignee: Michael Shuler
> Fix For: 3.0.14, 3.11.0
>
>
> RPMs should be gpg signed just as the deb packages. Also add documentation 
> how to verify to download page.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-13433) RPM distribution improvements and known issues

2017-06-23 Thread Michael Shuler (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061682#comment-16061682
 ] 

Michael Shuler commented on CASSANDRA-13433:


3.0.14 and 3.11.0 were both just released with signed packages and repo. 
[~denno] 3.10 will not be re-released, but 3.11.0 is the bug-fix release on top 
of 3.10 and is a long-term release series, so that's the one you want :)

{code:title=/etc/yum.repos.d/cassandra.repo for 3.11 series}
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://www.apache.org/dist/cassandra/KEYS
{code}

{code:title=/etc/yum.repos.d/cassandra.repo for 3.0 series}
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/30x/
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://www.apache.org/dist/cassandra/KEYS
{code}

> RPM distribution improvements and known issues
> --
>
> Key: CASSANDRA-13433
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13433
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Packaging
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
>
> Starting with CASSANDRA-13252, new releases will be provided as both official 
> RPM and Debian packages.  While the Debian packages are already well 
> established with our user base, the RPMs just have been release for the first 
> time and still require some attention. 
> Feel free to discuss RPM related issues in this ticket and open a sub-task to 
> fill a bug report. 
> Please note that native systemd support will be implemented with 
> CASSANDRA-13148 and this is not strictly a RPM specific issue. We still 
> intent to offer non-systemd support based on the already working init scripts 
> that we ship. Therefor the first step is to make use of systemd backward 
> compatibility for SysV/LSB scripts, so we can provide RPMs for both systemd 
> and non-systemd environments.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Comment Edited] (CASSANDRA-13569) Schedule schema pulls just once per endpoint

2017-06-23 Thread Michael Fong (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061094#comment-16061094
 ] 

Michael Fong edited comment on CASSANDRA-13569 at 6/23/17 11:44 PM:


Hi, [~spo...@gmail.com]

I agree w/ you that even ScheduledExecutor on MigrationTask would fail on rare 
cases. 

In CASSANDRA-11748, we had patched our own v2.0 source code with similar idea 
that limits schema pull only once per endpoint. However, we later on have 
observed a corner case that when two nodes with different schema version boot 
up at the same time, one node running slightly - a few seconds - faster than 
the other. The first node requests schema pull and failed since the other node 
has not yet finished initialization. 

There has been a huge difference in v2.0 and 3.x code bases, and I do not know 
if the corner problem still exists. Here is the the problematic code snippet 
for your reference. 
{code:java}
if (epState == null)  {
{code} would probably not prevent this. In your patch, if the state of 
ScheduledFuture return done, things could get much messier since schema 
migration would never happen. 

Sincerely,

Michael Fong



was (Author: mcfongtw):
Hi, [~spo...@gmail.com]

I agree w/ you that even ScheduledExecutor on MigrationTask would fail on rare 
cases. 

In CASSANDRA-11748, we had patched our own v2.0 source code with similar idea 
that limits schema pull only once per endpoint. However, we later on have 
observed a corner case that when two nodes with different schema version boot 
up at the same time, one node running slightly - a few seconds - faster than 
the other. The first node requests schema pull and failed since the other node 
has not yet finished initialization. 

There has been a huge difference in v2.0 and 3.x code bases, and I do not know 
if the corner problem still persists. Here is the the problematic code snippet 
for your reference. 
{code:java}
if (epState == null)  {
{code} would probably not prevent this. In your patch, if the state of 
ScheduledFuture return done, things could get much messier since schema 
migration would never happen. 

Sincerely,

Michael Fong


> Schedule schema pulls just once per endpoint
> 
>
> Key: CASSANDRA-13569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13569
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Distributed Metadata
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> Schema mismatches detected through gossip will get resolved by calling 
> {{MigrationManager.maybeScheduleSchemaPull}}. This method may decide to 
> schedule execution of {{MigrationTask}}, but only after using a 
> {{MIGRATION_DELAY_IN_MS = 6}} delay (for reasons unclear to me). 
> Meanwhile, as long as the migration task hasn't been executed, we'll continue 
> to have schema mismatches reported by gossip and will have corresponding 
> {{maybeScheduleSchemaPull}} calls, which will schedule further tasks with the 
> mentioned delay. Some local testing shows that dozens of tasks for the same 
> endpoint will eventually be executed and causing the same, stormy behavior 
> for this very endpoints.
> My proposal would be to simply not schedule new tasks for the same endpoint, 
> in case we still have pending tasks waiting for execution after 
> {{MIGRATION_DELAY_IN_MS}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Resolved] (CASSANDRA-13440) Sign RPM artifacts

2017-06-23 Thread Michael Shuler (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler resolved CASSANDRA-13440.

Resolution: Fixed

> Sign RPM artifacts
> --
>
> Key: CASSANDRA-13440
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13440
> Project: Cassandra
>  Issue Type: Sub-task
>  Components: Packaging
>Reporter: Stefan Podkowinski
>Assignee: Michael Shuler
>
> RPMs should be gpg signed just as the deb packages. Also add documentation 
> how to verify to download page.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-13440) Sign RPM artifacts

2017-06-23 Thread Michael Shuler (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061642#comment-16061642
 ] 

Michael Shuler commented on CASSANDRA-13440:


{noformat}
[cassandra]
name=Apache Cassandra
baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://www.apache.org/dist/cassandra/KEYS
{noformat}

Yum prompts to import the keys from the KEYS file, and installs everything we 
need beautifully.
{noformat}
[automaton@ip-10-200-178-59 ~]$ sudo yum install cassandra cassandra-tools
cassandra/signature 
  |  819 B  
00:00:00 
Retrieving key from https://www.apache.org/dist/cassandra/KEYS
Importing GPG key 0xF2833C93:
 Userid : "Eric Evans "
 Fingerprint: cec8 6bb4 a0ba 9d0f 9039 7cae f835 8fa2 f283 3c93
 From   : https://www.apache.org/dist/cassandra/KEYS
Is this ok [y/N]: y
cassandra/signature 
  | 2.9 kB  
00:00:07 !!! 
cassandra/primary_db
  | 4.3 kB  
00:00:00 
Resolving Dependencies
--> Running transaction check
---> Package cassandra.noarch 0:3.11.0-1 will be installed
--> Processing Dependency: jre >= 1.8.0 for package: cassandra-3.11.0-1.noarch
---> Package cassandra-tools.noarch 0:3.11.0-1 will be installed
--> Running transaction check
---> Package java-1.8.0-openjdk.x86_64 1:1.8.0.131-3.b12.el7_3 will be installed
--> Processing Dependency: java-1.8.0-openjdk-headless = 
1:1.8.0.131-3.b12.el7_3 for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: xorg-x11-fonts-Type1 for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libpng15.so.15(PNG15_0)(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libjvm.so(SUNWprivate_1.1)(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libjli.so(SUNWprivate_1.1)(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libjava.so(SUNWprivate_1.1)(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libasound.so.2(ALSA_0.9.0rc4)(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libasound.so.2(ALSA_0.9)(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: fontconfig(x86-64) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libpng15.so.15()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libjvm.so()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libjli.so()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libjava.so()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libgif.so.4()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libawt.so()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libasound.so.2()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libXtst.so.6()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libXrender.so.1()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libXi.so.6()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libXext.so.6()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libXcomposite.so.1()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: 
1:java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64
--> Running transaction check
---> Package alsa-lib.x86_64 0:1.1.1-1.el7 will be installed
---> Package fontconfig.x86_64 0:2.10.95-10.el7 will be installed
--> Processing Dependency: fontpackages-filesystem for package: 
fontconfig-2.10.95-10.el7.x86_64
---> Package giflib.x86_64 0:4.1.6-9.el7 will be installed
--> Processing Dependency: libSM.so.6()(64bit) for package: 
giflib-4.1.6-9.el7.x86_64
--> Processing Dependency: libICE.so.6()(64bit) for package: 
giflib-4.1.6-9.el7.x86_64
---> Package java-1.8.0-openjdk-headless.x86_64 1:1.8.0.131-3.b12.el7_3 will be 
installed
--> Processing Dependency: tzdata-java 

[jira] [Assigned] (CASSANDRA-13440) Sign RPM artifacts

2017-06-23 Thread Michael Shuler (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler reassigned CASSANDRA-13440:
--

Assignee: Michael Shuler

> Sign RPM artifacts
> --
>
> Key: CASSANDRA-13440
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13440
> Project: Cassandra
>  Issue Type: Sub-task
>  Components: Packaging
>Reporter: Stefan Podkowinski
>Assignee: Michael Shuler
>
> RPMs should be gpg signed just as the deb packages. Also add documentation 
> how to verify to download page.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



svn commit: r1799720 - in /cassandra/site: publish/download/index.html src/download.md

2017-06-23 Thread mshuler
Author: mshuler
Date: Fri Jun 23 23:32:26 2017
New Revision: 1799720

URL: http://svn.apache.org/viewvc?rev=1799720=rev
Log:
Try to fix text file formatting

Modified:
cassandra/site/publish/download/index.html
cassandra/site/src/download.md

Modified: cassandra/site/publish/download/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/download/index.html?rev=1799720=1799719=1799720=diff
==
--- cassandra/site/publish/download/index.html (original)
+++ cassandra/site/publish/download/index.html Fri Jun 23 23:32:26 2017
@@ -179,26 +179,22 @@ configuration changes.
 
   311x and 30x
   Modify the release series desired in the 
baseurl below.
-  (Not all versions of Apache Cassandra are available, since building RPMs 
is a recent addition to the project.)
-
-
-The following versions are currently available for RPM installation:
-
-
-  latest
   
-3.0
+(Not all versions of Apache Cassandra are available, since building 
RPMs is a recent addition to the project.)
   
   Add the Apache repository of Cassandra to 
/etc/yum.repos.d/cassandra.repo, for example for the latest 3.11 
version:
 
 
-[cassandra]
-name=Apache Cassandra
-baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
-gpgcheck=1
-repo_gpgcheck=1
-gpgkey=https://www.apache.org/dist/cassandra/KEYS
-
+
+  1[cassandra]
+2name=Apache 
Cassandra
+3baseurl=https://www.apache.org/dist/cassandra/redhat/311x/
+4gpgcheck=1
+5repo_gpgcheck=1
+6gpgkey=https://www.apache.org/dist/cassandra/KEYS
+
+
+
 
 Start Cassandra (will not start automatically):
 

Modified: cassandra/site/src/download.md
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/download.md?rev=1799720=1799719=1799720=diff
==
--- cassandra/site/src/download.md (original)
+++ cassandra/site/src/download.md Fri Jun 23 23:32:26 2017
@@ -83,14 +83,9 @@ Cassandra can be installed using RPM pac
 * Modify the `` desired in the `baseurl` below.
 * (Not all versions of Apache Cassandra are available, since building RPMs is 
a recent addition to the project.)
 
-The following versions are currently available for RPM installation:
-
-* {{ "latest" }}
-* {{ "3.0" }}
-
 * Add the Apache repository of Cassandra to `/etc/yum.repos.d/cassandra.repo`, 
for example for the latest 3.11 version:
 
-```
+```text
 [cassandra]
 name=Apache Cassandra
 baseurl=https://www.apache.org/dist/cassandra/redhat/311x/



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



[jira] [Commented] (CASSANDRA-13440) Sign RPM artifacts

2017-06-23 Thread Michael Shuler (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061632#comment-16061632
 ] 

Michael Shuler commented on CASSANDRA-13440:


3.0.14 and 3.11.0 RPMs signed, along with the repos. Test and close! :)

> Sign RPM artifacts
> --
>
> Key: CASSANDRA-13440
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13440
> Project: Cassandra
>  Issue Type: Sub-task
>  Components: Packaging
>Reporter: Stefan Podkowinski
>
> RPMs should be gpg signed just as the deb packages. Also add documentation 
> how to verify to download page.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



svn commit: r1799719 - in /cassandra/site: publish/community/index.html publish/download/index.html publish/index.html src/_data/releases.yaml src/download.md

2017-06-23 Thread mshuler
Author: mshuler
Date: Fri Jun 23 23:19:25 2017
New Revision: 1799719

URL: http://svn.apache.org/viewvc?rev=1799719=rev
Log:
Update download page for 3.0.14 and 3.11.0 releases

Modified:
cassandra/site/publish/community/index.html
cassandra/site/publish/download/index.html
cassandra/site/publish/index.html
cassandra/site/src/_data/releases.yaml
cassandra/site/src/download.md

Modified: cassandra/site/publish/community/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/community/index.html?rev=1799719=1799718=1799719=diff
==
--- cassandra/site/publish/community/index.html (original)
+++ cassandra/site/publish/community/index.html Fri Jun 23 23:19:25 2017
@@ -124,7 +124,7 @@ mostly useful for Cassandra developers a
   #cassandra-builds - results of automated test builds.
 
 
-Communication on the #cassandra-dev 
channel is http://wilderness.apache.org/channels/#logs-#cassandra-dev;>publicly 
archived.
+Communication on the #cassandra-dev channel is http://wilderness.apache.org/channels/#logs-#cassandra-dev;>publicly 
archived.
 
 Stack Overflow
 

Modified: cassandra/site/publish/download/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/download/index.html?rev=1799719=1799718=1799719=diff
==
--- cassandra/site/publish/download/index.html (original)
+++ cassandra/site/publish/download/index.html Fri Jun 23 23:19:25 2017
@@ -99,18 +99,14 @@
 
 Latest version
 
-Cassandra is moving to a monthly release process called Tick-Tock. 
Even-numbered releases (e.g. 3.2) contain new
-features; odd-numbered releases (e.g. 3.3) contain bug fixes 
only. If a critical bug is found, a patch will be
-released against the most recent bug fix release. Read more about http://www.planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/;>tick-tock
 here.
-
-Download the latest Cassandra release: http://www.apache.org/dyn/closer.lua/cassandra/3.10/apache-cassandra-3.10-bin.tar.gz;>3.10
 (http://www.apache.org/dist/cassandra/3.10/apache-cassandra-3.10-bin.tar.gz.asc;>pgp,
 http://www.apache.org/dist/cassandra/3.10/apache-cassandra-3.10-bin.tar.gz.md5;>md5
 and http://www.apache.org/dist/cassandra/3.10/apache-cassandra-3.10-bin.tar.gz.sha1;>sha1),
 released on 2017-02-03.
+Download the latest Apache Cassandra 3.11 release: http://www.apache.org/dyn/closer.lua/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz;>3.11.0
 (http://www.apache.org/dist/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc;>pgp,
 http://www.apache.org/dist/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.md5;>md5
 and http://www.apache.org/dist/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.sha1;>sha1),
 released on 2017-06-23.
 
 Older supported releases
 
 The following older Cassandra releases are still supported:
 
 
-  Apache Cassandra 3.0 is supported until 6 months after 4.0 
release (date TBD). The latest release is http://www.apache.org/dyn/closer.lua/cassandra/3.0.13/apache-cassandra-3.0.13-bin.tar.gz;>3.0.13
 (http://www.apache.org/dist/cassandra/3.0.13/apache-cassandra-3.0.13-bin.tar.gz.asc;>pgp,
 http://www.apache.org/dist/cassandra/3.0.13/apache-cassandra-3.0.13-bin.tar.gz.md5;>md5
 and http://www.apache.org/dist/cassandra/3.0.13/apache-cassandra-3.0.13-bin.tar.gz.sha1;>sha1),
 released on 2017-04-14.
+  Apache Cassandra 3.0 is supported until 6 months after 4.0 
release (date TBD). The latest release is http://www.apache.org/dyn/closer.lua/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz;>3.0.14
 (http://www.apache.org/dist/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc;>pgp,
 http://www.apache.org/dist/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.md5;>md5
 and http://www.apache.org/dist/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.sha1;>sha1),
 released on 2017-06-23.
   Apache Cassandra 2.2 is supported until 4.0 release (date 
TBD). The latest release is http://www.apache.org/dyn/closer.lua/cassandra/2.2.9/apache-cassandra-2.2.9-bin.tar.gz;>2.2.9
 (http://www.apache.org/dist/cassandra/2.2.9/apache-cassandra-2.2.9-bin.tar.gz.asc;>pgp,
 http://www.apache.org/dist/cassandra/2.2.9/apache-cassandra-2.2.9-bin.tar.gz.md5;>md5
 and http://www.apache.org/dist/cassandra/2.2.9/apache-cassandra-2.2.9-bin.tar.gz.sha1;>sha1),
 released on 2017-02-21.
   Apache Cassandra 2.1 is supported until 4.0 release (date 
TBD) with critical fixes only. The latest release is
 http://www.apache.org/dyn/closer.lua/cassandra/2.1.17/apache-cassandra-2.1.17-bin.tar.gz;>2.1.17
 (http://www.apache.org/dist/cassandra/2.1.17/apache-cassandra-2.1.17-bin.tar.gz.asc;>pgp,
 http://www.apache.org/dist/cassandra/2.1.17/apache-cassandra-2.1.17-bin.tar.gz.md5;>md5
 and http://www.apache.org/dist/cassandra/2.1.17/apache-cassandra-2.1.17-bin.tar.gz.sha1;>sha1),
 released on 2017-02-21.
@@ -121,16 +117,15 @@ released against the most recent 

[jira] [Updated] (CASSANDRA-13634) Create repository and do initial import for cassandra-dtest

2017-06-23 Thread Nate McCall (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate McCall updated CASSANDRA-13634:

Description: 
Given the completion of CASSANDRA-13584, it's time to create the repository and 
do the initial import of code. 

Note that this repo will be configured similarly our main one in that pull 
requests will go to {{pr@c.a.o}} address. 

  was:Given the completion of CASSANDRA-13584, it's time to create the 
repository and do the initial import of code. 


> Create repository and do initial import for cassandra-dtest
> ---
>
> Key: CASSANDRA-13634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13634
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Nate McCall
>Assignee: Nate McCall
>
> Given the completion of CASSANDRA-13584, it's time to create the repository 
> and do the initial import of code. 
> Note that this repo will be configured similarly our main one in that pull 
> requests will go to {{pr@c.a.o}} address. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Assigned] (CASSANDRA-13634) Create repository and do initial import for cassandra-dtest

2017-06-23 Thread Nate McCall (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate McCall reassigned CASSANDRA-13634:
---

Assignee: Nate McCall

> Create repository and do initial import for cassandra-dtest
> ---
>
> Key: CASSANDRA-13634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13634
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Nate McCall
>Assignee: Nate McCall
>
> Given the completion of CASSANDRA-13584, it's time to create the repository 
> and do the initial import of code. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-13634) Create repository and do initial import for cassandra-dtest

2017-06-23 Thread Nate McCall (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061601#comment-16061601
 ] 

Nate McCall commented on CASSANDRA-13634:
-

Mirror and repository have both been created. Repository:
https://git-wip-us.apache.org/repos/asf/cassandra-dtest.git

The mirror might take as long as 24 hours.

> Create repository and do initial import for cassandra-dtest
> ---
>
> Key: CASSANDRA-13634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13634
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Nate McCall
>
> Given the completion of CASSANDRA-13584, it's time to create the repository 
> and do the initial import of code. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



svn commit: r20180 - in /release/cassandra/redhat: 30x/ 30x/repodata/ 311x/ 311x/repodata/

2017-06-23 Thread mshuler
Author: mshuler
Date: Fri Jun 23 22:26:35 2017
New Revision: 20180

Log:
Create 311x RPM repo, update 30x RPM repo

Version 3.0.14 signed RPMs added to 30x repo.
Version 3.0.13 RPMS signed.
Version 3.11.0 signed RPMS added to new 311x repo.

Added:
release/cassandra/redhat/30x/cassandra-3.0.14-1.noarch.rpm   (with props)
release/cassandra/redhat/30x/cassandra-3.0.14-1.src.rpm   (with props)
release/cassandra/redhat/30x/cassandra-tools-3.0.14-1.noarch.rpm   (with 
props)

release/cassandra/redhat/30x/repodata/15694150289acc40a31c3f0470858d21960c900f9952dd15bacb9f923dd81454-primary.sqlite.bz2
   (with props)

release/cassandra/redhat/30x/repodata/2d1ae60873c2b52b8f101bc6e55366e02820372c52a2fea3b3a4776738f21f6b-other.sqlite.bz2
   (with props)

release/cassandra/redhat/30x/repodata/586da4f06a17fd4f47a45290f3057c8f8d95dea795e87dba097a91400c2df34d-primary.xml.gz
   (with props)

release/cassandra/redhat/30x/repodata/6b9cde2e2204f1d4dd7e06f61462d2a93820700e8ab40bc750482345e7f98a7c-filelists.sqlite.bz2
   (with props)

release/cassandra/redhat/30x/repodata/c3c80f9ba9cebce0a0f6e6c3c36f7ac626ee1277a4c789d582c265d0683f4f64-other.xml.gz
   (with props)

release/cassandra/redhat/30x/repodata/ca8c8f04dc3deaade77a850ffec5c16189fc723f4f8722c45cd6418d6f4fef06-filelists.xml.gz
   (with props)
release/cassandra/redhat/311x/
release/cassandra/redhat/311x/cassandra-3.11.0-1.noarch.rpm   (with props)
release/cassandra/redhat/311x/cassandra-3.11.0-1.src.rpm   (with props)
release/cassandra/redhat/311x/cassandra-tools-3.11.0-1.noarch.rpm   (with 
props)
release/cassandra/redhat/311x/repodata/

release/cassandra/redhat/311x/repodata/17462f7d5509cf8821adee6dda16e5e0521b7044d2ca018299f5f3e2089761bd-filelists.xml.gz
   (with props)

release/cassandra/redhat/311x/repodata/29629735a8a11c7d080434ea330ace47466dfc80e81dce82d20e6e0e8349d368-primary.sqlite.bz2
   (with props)

release/cassandra/redhat/311x/repodata/4ea2274efcc02ea19f5d97856f04e5141a45791be4d71fc7caa684a71434562d-other.sqlite.bz2
   (with props)

release/cassandra/redhat/311x/repodata/aa0783771bbe5f7a23debe8e84251beb90778a783654c46135c36f5b2f5218e2-filelists.sqlite.bz2
   (with props)

release/cassandra/redhat/311x/repodata/ba1722305bfc1b45431b9ab48172afa159ff660d55f1e24794f392ba4ce3ce69-primary.xml.gz
   (with props)

release/cassandra/redhat/311x/repodata/e5d9a776e9578d3b8ebbdd8ac589e666de0608fce710cedd9c6ddd0340560863-other.xml.gz
   (with props)
release/cassandra/redhat/311x/repodata/repomd.xml
release/cassandra/redhat/311x/repodata/repomd.xml.asc
Removed:

release/cassandra/redhat/30x/repodata/2225eea38b6001788de05ca5eab93f48bc6a9248a261985520bcd7c87cf6cd7c-filelists.xml.gz

release/cassandra/redhat/30x/repodata/3bcf18c0078056067a0d9a8921e90224d1ec90589a3ea2e2b10f68c2fc7fb046-filelists.sqlite.bz2

release/cassandra/redhat/30x/repodata/863c1a058ccac330aa63bf770005a82232a2411e78357c5c5c95dfe9eb472314-primary.xml.gz

release/cassandra/redhat/30x/repodata/867899412feb8f542ccb8b9191fa291a3d1650393c0845d447f06287f4cdc7fd-other.xml.gz

release/cassandra/redhat/30x/repodata/b54d0f422c031602d2b7d20e0d3c639e6abb0611960c6f346b3cd6ca4e7e276a-other.sqlite.bz2

release/cassandra/redhat/30x/repodata/c31d4195ac4ff0cf6f30bf177ab18712b2dffb092a6498189b4d46c8447c0ab5-primary.sqlite.bz2
Modified:
release/cassandra/redhat/30x/cassandra-3.0.13-1.noarch.rpm
release/cassandra/redhat/30x/cassandra-3.0.13-1.src.rpm
release/cassandra/redhat/30x/cassandra-tools-3.0.13-1.noarch.rpm
release/cassandra/redhat/30x/repodata/repomd.xml
release/cassandra/redhat/30x/repodata/repomd.xml.asc

Modified: release/cassandra/redhat/30x/cassandra-3.0.13-1.noarch.rpm
==
Binary files - no diff available.

Modified: release/cassandra/redhat/30x/cassandra-3.0.13-1.src.rpm
==
Binary files - no diff available.

Added: release/cassandra/redhat/30x/cassandra-3.0.14-1.noarch.rpm
==
Binary file - no diff available.

Propchange: release/cassandra/redhat/30x/cassandra-3.0.14-1.noarch.rpm
--
svn:mime-type = application/octet-stream

Added: release/cassandra/redhat/30x/cassandra-3.0.14-1.src.rpm
==
Binary file - no diff available.

Propchange: release/cassandra/redhat/30x/cassandra-3.0.14-1.src.rpm
--
svn:mime-type = application/octet-stream

Modified: release/cassandra/redhat/30x/cassandra-tools-3.0.13-1.noarch.rpm
==
Binary files - no diff available.

Added: 

[jira] [Assigned] (CASSANDRA-13632) Digest mismatch if row is empty

2017-06-23 Thread Jay Zhuang (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jay Zhuang reassigned CASSANDRA-13632:
--

Assignee: Andrew Whang

> Digest mismatch if row is empty
> ---
>
> Key: CASSANDRA-13632
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13632
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local Write-Read Paths
>Reporter: Andrew Whang
>Assignee: Andrew Whang
> Fix For: 3.0.x
>
>
> This issue is similar to CASSANDRA-12090. Quorum read queries that include a 
> column selector (non-wildcard) result in digest mismatch when the row is 
> empty (key does not exist). It seems the data serialization path checks if 
> rowIterator.isEmpty() and if so ignores column names (by setting IS_EMPTY 
> flag). However, the digest serialization path does not perform this check and 
> includes column names. The digest comparison results in a mismatch. The 
> mismatch does not end up issuing a read repair mutation since the underlying 
> data is the same.
> The mismatch on the read path ends up doubling our p99 read latency. We 
> discovered this issue while testing a 2.2.5 to 3.0.13 upgrade.
> One thing to note is that we're using thrift, which ends up handling the 
> ColumnFilter differently than the CQL path. 
> As with CASSANDRA-12090, fixing the digest seems sensible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Created] (CASSANDRA-13635) update dtests to support netty-based internode messaging/streaming

2017-06-23 Thread Jason Brown (JIRA)
Jason Brown created CASSANDRA-13635:
---

 Summary: update dtests to support netty-based internode 
messaging/streaming
 Key: CASSANDRA-13635
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13635
 Project: Cassandra
  Issue Type: Task
  Components: Streaming and Messaging, Testing
Reporter: Jason Brown
Assignee: Jason Brown
 Fix For: 4.0


some dtests need to be updated to work correctly with CASSANDRA-13628



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-13634) Create repository and do initial import for cassandra-dtest

2017-06-23 Thread Nate McCall (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061474#comment-16061474
 ] 

Nate McCall commented on CASSANDRA-13634:
-

Request submitted for the repository creation via:
https://reporeq.apache.org/

Not sure if that is a script or a person at the other end, but anecdotally it 
should not take long. 

> Create repository and do initial import for cassandra-dtest
> ---
>
> Key: CASSANDRA-13634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13634
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Nate McCall
>
> Given the completion of CASSANDRA-13584, it's time to create the repository 
> and do the initial import of code. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Created] (CASSANDRA-13634) Create repository and do initial import for cassandra-dtest

2017-06-23 Thread Nate McCall (JIRA)
Nate McCall created CASSANDRA-13634:
---

 Summary: Create repository and do initial import for 
cassandra-dtest
 Key: CASSANDRA-13634
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13634
 Project: Cassandra
  Issue Type: Bug
Reporter: Nate McCall


Given the completion of CASSANDRA-13584, it's time to create the repository and 
do the initial import of code. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



svn commit: r20176 - in /release/cassandra: 3.0.12/ 3.0.13/ 3.10/

2017-06-23 Thread mshuler
Author: mshuler
Date: Fri Jun 23 20:23:11 2017
New Revision: 20176

Log:
Drop 3.0.12 3.0.13 3.10 releases from dist

Removed:
release/cassandra/3.0.12/
release/cassandra/3.0.13/
release/cassandra/3.10/


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



svn commit: r20175 - in /release/cassandra: 3.11.0/ debian/dists/311x/ debian/dists/311x/main/ debian/dists/311x/main/binary-amd64/ debian/dists/311x/main/binary-i386/ debian/dists/311x/main/source/ d

2017-06-23 Thread mshuler
Author: mshuler
Date: Fri Jun 23 20:11:54 2017
New Revision: 20175

Log:
Apache Cassandra 3.11.0 Release

Added:
release/cassandra/3.11.0/
release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz   (with props)
release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc
release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc.md5
release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc.sha1
release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.md5
release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.sha1
release/cassandra/3.11.0/apache-cassandra-3.11.0-src.tar.gz   (with props)
release/cassandra/3.11.0/apache-cassandra-3.11.0-src.tar.gz.asc
release/cassandra/3.11.0/apache-cassandra-3.11.0-src.tar.gz.asc.md5
release/cassandra/3.11.0/apache-cassandra-3.11.0-src.tar.gz.asc.sha1
release/cassandra/3.11.0/apache-cassandra-3.11.0-src.tar.gz.md5
release/cassandra/3.11.0/apache-cassandra-3.11.0-src.tar.gz.sha1
release/cassandra/debian/dists/311x/
release/cassandra/debian/dists/311x/InRelease
release/cassandra/debian/dists/311x/Release
release/cassandra/debian/dists/311x/Release.gpg
release/cassandra/debian/dists/311x/main/
release/cassandra/debian/dists/311x/main/binary-amd64/
release/cassandra/debian/dists/311x/main/binary-amd64/Packages
release/cassandra/debian/dists/311x/main/binary-amd64/Packages.gz   (with 
props)
release/cassandra/debian/dists/311x/main/binary-amd64/Release
release/cassandra/debian/dists/311x/main/binary-i386/
release/cassandra/debian/dists/311x/main/binary-i386/Packages
release/cassandra/debian/dists/311x/main/binary-i386/Packages.gz   (with 
props)
release/cassandra/debian/dists/311x/main/binary-i386/Release
release/cassandra/debian/dists/311x/main/source/
release/cassandra/debian/dists/311x/main/source/Release
release/cassandra/debian/dists/311x/main/source/Sources.gz   (with props)

release/cassandra/debian/pool/main/c/cassandra/cassandra-tools_3.11.0_all.deb   
(with props)
release/cassandra/debian/pool/main/c/cassandra/cassandra_3.11.0.diff.gz   
(with props)
release/cassandra/debian/pool/main/c/cassandra/cassandra_3.11.0.dsc
release/cassandra/debian/pool/main/c/cassandra/cassandra_3.11.0.orig.tar.gz 
  (with props)

release/cassandra/debian/pool/main/c/cassandra/cassandra_3.11.0.orig.tar.gz.asc
release/cassandra/debian/pool/main/c/cassandra/cassandra_3.11.0_all.deb   
(with props)

Added: release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz
==
Binary file - no diff available.

Propchange: release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz
--
svn:mime-type = application/octet-stream

Added: release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc
==
--- release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc (added)
+++ release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc Fri Jun 23 
20:11:54 2017
@@ -0,0 +1,17 @@
+-BEGIN PGP SIGNATURE-
+Version: GnuPG v1
+
+iQIcBAABCAAGBQJZSFUzAAoJEKJ4t4H+SyvayvgP/A0H4p0vebXph/4lX1Q2A9HP
+Zg2awMpVQcdx3kx7+6n7sLcBrEUjsdjUrogzTZNsIbQH7hIiZqEG7VrvOci8wAkG
+vZnOoCAZm1TQJKD03PgvnmBXkSTMHFWrsZouvxaUY4/2+dYcqxp7RChQI8Ce/etM
+mh7OQOHy9SBpOHpx5LqfIP7ui/pW3sc0LqlzkfggMNaqc777txmKcizfhbM78mmV
+zRPbT8+cqehyDgakoA6YWXiz2xJLRxdL//Ze06vzFHgP57jbd641YXB/FT/bCVLx
+poAzbVSgC+r6SARfivKpb/Wx6IIvN086mySVeFUEum/FUSpn3eYucdNsIluuRTs2
+Hn14q3kOPy6AU3qlTDYddw4dwLCglTimrfC8sM7IB93uMI5VQ7xy70GSfUHvuwHC
+hbATf2ezExAIrhpQlEcB864dcPcXIL2VEChYoODv1X7HDLB0oudZRbM8ZJPvCR8q
+WC5RBXAMI9dLcCxJN1PV92yx8p8Ov61VsiQlJQAmeJ3FLdaCxAwNGO3fC8DiUFWU
+m2t31h8v/z3+6/NCyLgnhvVpHWcFgHOjc6Tqk6myKUBbR+takioqUlaaaqWmQtFQ
+jNAgFwl7gOzvDUIbFoHUusoHTx56R9P3TLEEM1DlYqlz4TMEHFfV0Ry3jV1WD/zn
+QppzJ5m3kVmxzmpcoZWM
+=mr/Q
+-END PGP SIGNATURE-

Added: release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc.md5
==
--- release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc.md5 (added)
+++ release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc.md5 Fri Jun 
23 20:11:54 2017
@@ -0,0 +1 @@
+5768cb05708d384b01df35ab27c005e5
\ No newline at end of file

Added: release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc.sha1
==
--- release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc.sha1 (added)
+++ release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.asc.sha1 Fri 
Jun 23 20:11:54 2017
@@ -0,0 +1 @@
+0e60ee09433f5cbf5707e543c2d8444be7b7f65c
\ No newline at end of file

Added: release/cassandra/3.11.0/apache-cassandra-3.11.0-bin.tar.gz.md5

[cassandra] Git Push Summary

2017-06-23 Thread mshuler
Repository: cassandra
Updated Tags:  refs/tags/3.11.0-tentative [deleted] 88dee7e9d

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



[cassandra] Git Push Summary

2017-06-23 Thread mshuler
Repository: cassandra
Updated Tags:  refs/tags/cassandra-3.11.0 [created] bef80a4a7

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



[jira] [Updated] (CASSANDRA-13632) Digest mismatch if row is empty

2017-06-23 Thread Michael Shuler (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Shuler updated CASSANDRA-13632:
---
Fix Version/s: (was: 3.0.14)
   3.0.x

> Digest mismatch if row is empty
> ---
>
> Key: CASSANDRA-13632
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13632
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local Write-Read Paths
>Reporter: Andrew Whang
> Fix For: 3.0.x
>
>
> This issue is similar to CASSANDRA-12090. Quorum read queries that include a 
> column selector (non-wildcard) result in digest mismatch when the row is 
> empty (key does not exist). It seems the data serialization path checks if 
> rowIterator.isEmpty() and if so ignores column names (by setting IS_EMPTY 
> flag). However, the digest serialization path does not perform this check and 
> includes column names. The digest comparison results in a mismatch. The 
> mismatch does not end up issuing a read repair mutation since the underlying 
> data is the same.
> The mismatch on the read path ends up doubling our p99 read latency. We 
> discovered this issue while testing a 2.2.5 to 3.0.13 upgrade.
> One thing to note is that we're using thrift, which ends up handling the 
> ColumnFilter differently than the CQL path. 
> As with CASSANDRA-12090, fixing the digest seems sensible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



svn commit: r20174 - in /release/cassandra: 3.0.14/ debian/dists/30x/ debian/dists/30x/main/binary-amd64/ debian/dists/30x/main/binary-i386/ debian/dists/30x/main/source/ debian/pool/main/c/cassandra/

2017-06-23 Thread mshuler
Author: mshuler
Date: Fri Jun 23 19:44:51 2017
New Revision: 20174

Log:
Apache Cassandra 3.0.14 Release

Added:
release/cassandra/3.0.14/
release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz   (with props)
release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc
release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc.md5
release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc.sha1
release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.md5
release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.sha1
release/cassandra/3.0.14/apache-cassandra-3.0.14-src.tar.gz   (with props)
release/cassandra/3.0.14/apache-cassandra-3.0.14-src.tar.gz.asc
release/cassandra/3.0.14/apache-cassandra-3.0.14-src.tar.gz.asc.md5
release/cassandra/3.0.14/apache-cassandra-3.0.14-src.tar.gz.asc.sha1
release/cassandra/3.0.14/apache-cassandra-3.0.14-src.tar.gz.md5
release/cassandra/3.0.14/apache-cassandra-3.0.14-src.tar.gz.sha1

release/cassandra/debian/pool/main/c/cassandra/cassandra-tools_3.0.14_all.deb   
(with props)
release/cassandra/debian/pool/main/c/cassandra/cassandra_3.0.14.diff.gz   
(with props)
release/cassandra/debian/pool/main/c/cassandra/cassandra_3.0.14.dsc
release/cassandra/debian/pool/main/c/cassandra/cassandra_3.0.14.orig.tar.gz 
  (with props)

release/cassandra/debian/pool/main/c/cassandra/cassandra_3.0.14.orig.tar.gz.asc
release/cassandra/debian/pool/main/c/cassandra/cassandra_3.0.14_all.deb   
(with props)
Modified:
release/cassandra/debian/dists/30x/InRelease
release/cassandra/debian/dists/30x/Release
release/cassandra/debian/dists/30x/Release.gpg
release/cassandra/debian/dists/30x/main/binary-amd64/Packages
release/cassandra/debian/dists/30x/main/binary-amd64/Packages.gz
release/cassandra/debian/dists/30x/main/binary-i386/Packages
release/cassandra/debian/dists/30x/main/binary-i386/Packages.gz
release/cassandra/debian/dists/30x/main/source/Sources.gz

Added: release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz
==
Binary file - no diff available.

Propchange: release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz
--
svn:mime-type = application/octet-stream

Added: release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc
==
--- release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc (added)
+++ release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc Fri Jun 23 
19:44:51 2017
@@ -0,0 +1,17 @@
+-BEGIN PGP SIGNATURE-
+Version: GnuPG v1
+
+iQIcBAABCAAGBQJZSAJDAAoJEKJ4t4H+Syva24UP/ivCr1qoEhHVtRdnwWADkv9G
+G56APtqllh2g3h45eiAWir3p82dU2TXCf70u6Vwi2kiJssdvR2n8Pj1Rc1OAKkUo
+f2kNybmIucGQV4p0ml+2nsKtfMv+QgOKuEUG6UDreMBX3npmLLbJCIML+1Fk5E69
+bs85CHmt/eP7XkZxA2SdFb2o816TLmROpQO8d1gk14o5RXHl8UUgEcs3psXttemH
+M3fPvUJ/W4eTiAg/hgUQR2exR/IRRmBXTPR5rcBHzJS+nz3RlamZzCr0cpSvmJcT
+joa6uvXeRDjeKg5HMm81kiuHJyZtgkztCdHi/r/QEab3JnvL0bCfs9tryi3ct40s
+T6gslZoiLNiF6W3C+RyJt4MGNAgD4PoXVk7jwy2WZXTRcuL1YYVng/IiYxb3XN87
+F2ZHcIwNH9vx6DuEGgbx/jy4oqXHXlKqd1kkzd6Vw2sBB8xXTfWWrfwIxkZeU4Jp
+ScxJvYmk3vPRFwYI0/gDMUf/bh8WI0qjTt1kQ1r0lRWstTrwkJW+wuOptCXmnSB/
+R/TGrNiuF6TrcVN9k9O8BTpLGV3XqaWHI21t7sinyj38FkZpyoWp1g7CiBxruYY2
+DFXQUQTCnrq1Cu8twboQRx48DxcjLGpEpE42rdDffmFBggifLTHnCD+5416TFXzH
+ybY//ZktKWt8slmdgtKJ
+=GnIm
+-END PGP SIGNATURE-

Added: release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc.md5
==
--- release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc.md5 (added)
+++ release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc.md5 Fri Jun 
23 19:44:51 2017
@@ -0,0 +1 @@
+d4f7d1ec2a1d07b649714c9270fac9ca
\ No newline at end of file

Added: release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc.sha1
==
--- release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc.sha1 (added)
+++ release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.asc.sha1 Fri 
Jun 23 19:44:51 2017
@@ -0,0 +1 @@
+9aa3ec46c26161acc139aebd5a3d09f2b3d45e63
\ No newline at end of file

Added: release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.md5
==
--- release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.md5 (added)
+++ release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.md5 Fri Jun 23 
19:44:51 2017
@@ -0,0 +1 @@
+755fe967d4391ca40690868106875596
\ No newline at end of file

Added: release/cassandra/3.0.14/apache-cassandra-3.0.14-bin.tar.gz.sha1
==
--- 

[cassandra] Git Push Summary

2017-06-23 Thread mshuler
Repository: cassandra
Updated Tags:  refs/tags/3.0.14-tentative [deleted] f3e38cb63

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



[cassandra] Git Push Summary

2017-06-23 Thread mshuler
Repository: cassandra
Updated Tags:  refs/tags/cassandra-3.0.14 [created] 7bf0cd1a4

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



[cassandra] Git Push Summary

2017-06-23 Thread mshuler
Repository: cassandra
Updated Tags:  refs/tags/0.8.10-tentative [deleted] 038b8f212
  refs/tags/1.0.10-tentative [deleted] b2ca7f821
  refs/tags/1.0.11-tentative [deleted] 4f0237acd
  refs/tags/1.0.12-tentative [deleted] 373e5b0d5
  refs/tags/1.0.7-tentative [deleted] 6a1ed6205
  refs/tags/1.0.8-tentative [deleted] fe6980eb7
  refs/tags/1.0.9-tentative [deleted] 3fd0fb6aa
  refs/tags/1.1.0-beta1-tentative [deleted] 271630d58
  refs/tags/1.1.0-beta2-tentative [deleted] 643d18af2
  refs/tags/1.1.0-rc1-tentative [deleted] cbbf54910
  refs/tags/1.1.0-tentative [deleted] c67153282
  refs/tags/1.1.1-tentative [deleted] a788a23ca
  refs/tags/1.1.10-tentative [deleted] 684994215
  refs/tags/1.1.11-tentative [deleted] d939a0c95
  refs/tags/1.1.12-tentative [deleted] 2dd73d171
  refs/tags/1.1.2-tentative [deleted] b94d8d40f
  refs/tags/1.1.3-tentative [deleted] 94bcc6a6f
  refs/tags/1.1.4-tentative [deleted] 94e46ff95
  refs/tags/1.1.6-tentative [deleted] a0900f3d3
  refs/tags/1.1.7-tentative [deleted] 2f4b6d8c6
  refs/tags/1.1.8-tentative [deleted] 4885bfccf
  refs/tags/1.1.9-tentative [deleted] 7eb47c50c
  refs/tags/1.2.0-beta1-tentative [deleted] 60bf68caa
  refs/tags/1.2.0-beta2-tentative [deleted] f04bebfa7
  refs/tags/1.2.0-beta3-tentative [deleted] b86f75dcd
  refs/tags/1.2.0-rc1-tentative [deleted] d791e0b3f
  refs/tags/1.2.0-rc2-tentative [deleted] cfe51fb4f
  refs/tags/1.2.0-tentative [deleted] 69337a436
  refs/tags/1.2.1-tentative [deleted] 8540974db
  refs/tags/1.2.10-tentative [deleted] 937536363
  refs/tags/1.2.2-tentative [deleted] 068b53dd5
  refs/tags/1.2.3-tentative [deleted] f07804e0d
  refs/tags/1.2.4-tentative [deleted] 2e96d0711
  refs/tags/1.2.5-tentative [deleted] 7d4380d66
  refs/tags/1.2.6-tentative [deleted] a6ca5d496
  refs/tags/1.2.7-tentative [deleted] ce4e4b9b5
  refs/tags/1.2.8 [deleted] dd105e6ff
  refs/tags/1.2.8-tentative [deleted] 0291d6960
  refs/tags/1.2.9-tentative [deleted] 6164d011e
  refs/tags/2.0.0-beta1-tentative [deleted] fcdb39384
  refs/tags/2.0.0-beta2-tentative [deleted] e0eacd281
  refs/tags/2.0.0-rc1-tentative [deleted] e8ae6720e
  refs/tags/2.0.0-rc2-tentative [deleted] 3e516a328
  refs/tags/2.0.0-tentative [deleted] 03045ca22
  refs/tags/2.0.1-tentative [deleted] eb96db6c1
  refs/tags/3.0.13-tentative [deleted] 91661ec29
  refs/tags/list [deleted] 03b528aa2
  refs/tags/trunk/3881 [deleted] 602e383d6
  refs/tags/trunk/4120 [deleted] 087f902d6

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



[jira] [Updated] (CASSANDRA-13627) Index queries are rejected on COMPACT tables

2017-06-23 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrés de la Peña updated CASSANDRA-13627:
--
Status: Ready to Commit  (was: Patch Available)

> Index queries are rejected on COMPACT tables
> 
>
> Key: CASSANDRA-13627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13627
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>
> Since {{3.0}}, {{compact}} tables are using under the hood {{static}} 
> columns. Due to that {{SELECT}} queries using secondary indexes get rejected 
> with the following error:
> {{Queries using 2ndary indexes don't support selecting only static columns}}.
> This problem can be reproduced using the following unit test:
> {code}@Test
> public void testIndicesOnCompactTable() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int PRIMARY KEY, v int) WITH COMPACT 
> STORAGE");
> createIndex("CREATE INDEX ON %s(v)");
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 1, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 2, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 3, 3);
> assertRows(execute("SELECT pk, v FROM %s WHERE v = 1"),
>row(1, 1),
>row(2, 1));
> }{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Comment Edited] (CASSANDRA-13627) Index queries are rejected on COMPACT tables

2017-06-23 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061217#comment-16061217
 ] 

Andrés de la Peña edited comment on CASSANDRA-13627 at 6/23/17 5:04 PM:


The patch looks good to me, +1.

Just a couple of trivial comments that you could perfectly ignore or fix during 
commit:
 * It seems that 
[here|https://github.com/blerer/cassandra/blob/26e7ca7b1b0b0c493508cc6565e16d185323763d/test/unit/org/apache/cassandra/cql3/validation/entities/SecondaryIndexTest.java#L1306-L1308]
 there are double spaces which are probably accidental. 
 * The insert statements in the newly created 
{{SecondaryIndexTest#testIndicesOnCompactTable}} use an uppercase "%S" format 
specifier, which will produce the uppercased name of the table. This is not a 
problem at all because the unquoted table name is case insensitive, but I'm 
mentioning it just in case the choice of the uppercased format specifier were 
accidental.


was (Author: adelapena):
The patch looks good to me.

Just a couple of trivial comments:
 * It seems that 
[here|https://github.com/blerer/cassandra/blob/26e7ca7b1b0b0c493508cc6565e16d185323763d/test/unit/org/apache/cassandra/cql3/validation/entities/SecondaryIndexTest.java#L1306-L1308]
 there are double spaces which are probably accidental. 
 * The insert statements in the newly created 
{{SecondaryIndexTest#testIndicesOnCompactTable}} use an uppercase "%S" format 
specifier, which will produce the uppercased name of the table. This is not a 
problem at all because the unquoted table name is case insensitive, but I'm 
mentioning it just in case the choice of the uppercased format specifier were 
accidental.

> Index queries are rejected on COMPACT tables
> 
>
> Key: CASSANDRA-13627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13627
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>
> Since {{3.0}}, {{compact}} tables are using under the hood {{static}} 
> columns. Due to that {{SELECT}} queries using secondary indexes get rejected 
> with the following error:
> {{Queries using 2ndary indexes don't support selecting only static columns}}.
> This problem can be reproduced using the following unit test:
> {code}@Test
> public void testIndicesOnCompactTable() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int PRIMARY KEY, v int) WITH COMPACT 
> STORAGE");
> createIndex("CREATE INDEX ON %s(v)");
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 1, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 2, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 3, 3);
> assertRows(execute("SELECT pk, v FROM %s WHERE v = 1"),
>row(1, 1),
>row(2, 1));
> }{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-13627) Index queries are rejected on COMPACT tables

2017-06-23 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061217#comment-16061217
 ] 

Andrés de la Peña commented on CASSANDRA-13627:
---

The patch looks good to me.

Just a couple of trivial comments:
 * It seems that 
[here|https://github.com/blerer/cassandra/blob/26e7ca7b1b0b0c493508cc6565e16d185323763d/test/unit/org/apache/cassandra/cql3/validation/entities/SecondaryIndexTest.java#L1306-L1308]
 there are double spaces which are probably accidental. 
 * The insert statements in the newly created 
{{SecondaryIndexTest#testIndicesOnCompactTable}} use an uppercase "%S" format 
specifier, which will produce the uppercased name of the table. This is not a 
problem at all because the unquoted table name is case insensitive, but I'm 
mentioning it just in case the choice of the uppercased format specifier were 
accidental.

> Index queries are rejected on COMPACT tables
> 
>
> Key: CASSANDRA-13627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13627
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>
> Since {{3.0}}, {{compact}} tables are using under the hood {{static}} 
> columns. Due to that {{SELECT}} queries using secondary indexes get rejected 
> with the following error:
> {{Queries using 2ndary indexes don't support selecting only static columns}}.
> This problem can be reproduced using the following unit test:
> {code}@Test
> public void testIndicesOnCompactTable() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int PRIMARY KEY, v int) WITH COMPACT 
> STORAGE");
> createIndex("CREATE INDEX ON %s(v)");
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 1, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 2, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 3, 3);
> assertRows(execute("SELECT pk, v FROM %s WHERE v = 1"),
>row(1, 1),
>row(2, 1));
> }{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-13632) Digest mismatch if row is empty

2017-06-23 Thread Andrew Whang (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Whang updated CASSANDRA-13632:
-
Summary: Digest mismatch if row is empty  (was: Digest mismatch if 
(non-static) column is null)

> Digest mismatch if row is empty
> ---
>
> Key: CASSANDRA-13632
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13632
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local Write-Read Paths
>Reporter: Andrew Whang
> Fix For: 3.0.14
>
>
> This issue is similar to CASSANDRA-12090. Quorum read queries that include a 
> column selector (non-wildcard) result in digest mismatch when the row is 
> empty (key does not exist). It seems the data serialization path checks if 
> rowIterator.isEmpty() and if so ignores column names (by setting IS_EMPTY 
> flag). However, the digest serialization path does not perform this check and 
> includes column names. The digest comparison results in a mismatch. The 
> mismatch does not end up issuing a read repair mutation since the underlying 
> data is the same.
> The mismatch on the read path ends up doubling our p99 read latency. We 
> discovered this issue while testing a 2.2.5 to 3.0.13 upgrade.
> One thing to note is that we're using thrift, which ends up handling the 
> ColumnFilter differently than the CQL path. 
> As with CASSANDRA-12090, fixing the digest seems sensible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-13632) Digest mismatch if (non-static) column is null

2017-06-23 Thread Andrew Whang (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Whang updated CASSANDRA-13632:
-
Description: 
This issue is similar to CASSANDRA-12090. Quorum read queries that include a 
column selector (non-wildcard) result in digest mismatch when the row is empty 
(key does not exist). It seems the data serialization path checks if 
rowIterator.isEmpty() and if so ignores column names (by setting IS_EMPTY 
flag). However, the digest serialization path does not perform this check and 
includes column names. The digest comparison results in a mismatch. The 
mismatch does not end up issuing a read repair mutation since the underlying 
data is the same.

The mismatch on the read path ends up doubling our p99 read latency. We 
discovered this issue while testing a 2.2.5 to 3.0.13 upgrade.

One thing to note is that we're using thrift, which ends up handling the 
ColumnFilter differently than the CQL path. 

As with CASSANDRA-12090, fixing the digest seems sensible.

  was:
This issue is similar to CASSANDRA-12090. Quorum read queries that include a 
column selector (non-wildcard) result in digest mismatch when the column value 
is null. It seems the data serialization path checks if rowIterator.isEmpty() 
and if so ignores column names (by setting IS_EMPTY flag). However, the digest 
serialization path does not perform this check and includes column names. The 
digest comparison results in a mismatch. The mismatch does not end up issuing a 
read repair mutation since the underlying data is the same.

Our use case involves frequent deletion of partition columns, so the mismatch 
on the read path ends up doubling our p99 read latency. We discovered this 
issue while testing a 2.2.5 to 3.0.13 upgrade.

One thing to note is that we're using thrift, which ends up handling the 
ColumnFilter differently than the CQL path. 

As with CASSANDRA-12090, fixing the digest seems sensible.


> Digest mismatch if (non-static) column is null
> --
>
> Key: CASSANDRA-13632
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13632
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local Write-Read Paths
>Reporter: Andrew Whang
> Fix For: 3.0.14
>
>
> This issue is similar to CASSANDRA-12090. Quorum read queries that include a 
> column selector (non-wildcard) result in digest mismatch when the row is 
> empty (key does not exist). It seems the data serialization path checks if 
> rowIterator.isEmpty() and if so ignores column names (by setting IS_EMPTY 
> flag). However, the digest serialization path does not perform this check and 
> includes column names. The digest comparison results in a mismatch. The 
> mismatch does not end up issuing a read repair mutation since the underlying 
> data is the same.
> The mismatch on the read path ends up doubling our p99 read latency. We 
> discovered this issue while testing a 2.2.5 to 3.0.13 upgrade.
> One thing to note is that we're using thrift, which ends up handling the 
> ColumnFilter differently than the CQL path. 
> As with CASSANDRA-12090, fixing the digest seems sensible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-13067) Integer overflows with file system size reported by Amazon Elastic File System (EFS)

2017-06-23 Thread Benjamin Lerer (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061192#comment-16061192
 ] 

Benjamin Lerer commented on CASSANDRA-13067:


I pushed some new patches for 
[2.2|https://github.com/apache/cassandra/compare/trunk...blerer:13067-2.2],  
[3.0|https://github.com/apache/cassandra/compare/trunk...blerer:13067-3.0] and 
[3.11|https://github.com/apache/cassandra/compare/trunk...blerer:13067-3.11]. I 
ran the tests for {{2.2}}, {{3.0}}, {{3.11}} and {{trunk}} on our internal CI. 
There are no unit tests failures and the DTests failures are unrelated to the 
changes.

The patch handle the 
[JDK-8162520|https://bugs.openjdk.java.net/browse/JDK-8162520] and 
[JDK-8179320|https://bugs.openjdk.java.net/browse/JDK-8179320] problems by 
providing safe methods within {{FileUtils}} to create a safe {{FileStore}} or 
retrieve the {{totalSpace}}, {{freeSpace}} or {{usableSpace}}.
If one value overflow, {{Long.MAX_VALUE}} will be returned instead of the 
negative value.
I considered returning a {{BigInteger}} but finally decided to keep the changes 
 as small as possible.

[~ifesdjeen] could you review?

> Integer overflows with file system size reported by Amazon Elastic File 
> System (EFS)
> 
>
> Key: CASSANDRA-13067
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13067
> Project: Cassandra
>  Issue Type: Bug
> Environment: Cassandra in OpenShift running on Amazon EC2 instance 
> with EFS mounted for data
>Reporter: Michael Hanselmann
>Assignee: Benjamin Lerer
> Attachments: 0001-Handle-exabyte-sized-filesystems.patch
>
>
> When not explicitly configured Cassandra uses 
> [{{nio.FileStore.getTotalSpace}}|https://docs.oracle.com/javase/7/docs/api/java/nio/file/FileStore.html]
>  to determine the total amount of available space in order to [calculate the 
> preferred commit log 
> size|https://github.com/apache/cassandra/blob/cassandra-3.9/src/java/org/apache/cassandra/config/DatabaseDescriptor.java#L553].
>  [Amazon EFS|https://aws.amazon.com/efs/] instances report a filesystem size 
> of 8 EiB when empty. [{{getTotalSpace}} causes an integer overflow 
> (JDK-8162520)|https://bugs.openjdk.java.net/browse/JDK-8162520] and returns a 
> negative number, resulting in a negative preferred size and causing the 
> checked integer to throw.
> Overriding {{commitlog_total_space_in_mb}} is not sufficient as 
> [{{DataDirectory.getAvailableSpace}}|https://github.com/apache/cassandra/blob/cassandra-3.9/src/java/org/apache/cassandra/db/Directories.java#L550]
>  makes use of {{nio.FileStore.getUsableSpace}}.
> [AMQ-6441] is a comparable issue in ActiveMQ.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-13627) Index queries are rejected on COMPACT tables

2017-06-23 Thread Sergio Bossa (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergio Bossa updated CASSANDRA-13627:
-
Reviewer: Andrés de la Peña  (was: Benjamin Lerer)

> Index queries are rejected on COMPACT tables
> 
>
> Key: CASSANDRA-13627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13627
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>
> Since {{3.0}}, {{compact}} tables are using under the hood {{static}} 
> columns. Due to that {{SELECT}} queries using secondary indexes get rejected 
> with the following error:
> {{Queries using 2ndary indexes don't support selecting only static columns}}.
> This problem can be reproduced using the following unit test:
> {code}@Test
> public void testIndicesOnCompactTable() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int PRIMARY KEY, v int) WITH COMPACT 
> STORAGE");
> createIndex("CREATE INDEX ON %s(v)");
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 1, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 2, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 3, 3);
> assertRows(execute("SELECT pk, v FROM %s WHERE v = 1"),
>row(1, 1),
>row(2, 1));
> }{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-13569) Schedule schema pulls just once per endpoint

2017-06-23 Thread Michael Fong (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16061094#comment-16061094
 ] 

Michael Fong commented on CASSANDRA-13569:
--

Hi, [~spo...@gmail.com]

I agree w/ you that even ScheduledExecutor on MigrationTask would fail on rare 
cases. 

In CASSANDRA-11748, we had patched our own v2.0 source code with similar idea 
that limits schema pull only once per endpoint. However, we later on have 
observed a corner case that when two nodes with different schema version boot 
up at the same time, one node running slightly - a few seconds - faster than 
the other. The first node requests schema pull and failed since the other node 
has not yet finished initialization. 

There has been a huge difference in v2.0 and 3.x code bases, and I do not know 
if the corner problem still persists. Here is the the problematic code snippet 
for your reference. 
{code:java}
if (epState == null)  {
{code} would probably not prevent this. In your patch, if the state of 
ScheduledFuture return done, things could get much messier since schema 
migration would never happen. 

Sincerely,

Michael Fong


> Schedule schema pulls just once per endpoint
> 
>
> Key: CASSANDRA-13569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13569
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Distributed Metadata
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> Schema mismatches detected through gossip will get resolved by calling 
> {{MigrationManager.maybeScheduleSchemaPull}}. This method may decide to 
> schedule execution of {{MigrationTask}}, but only after using a 
> {{MIGRATION_DELAY_IN_MS = 6}} delay (for reasons unclear to me). 
> Meanwhile, as long as the migration task hasn't been executed, we'll continue 
> to have schema mismatches reported by gossip and will have corresponding 
> {{maybeScheduleSchemaPull}} calls, which will schedule further tasks with the 
> mentioned delay. Some local testing shows that dozens of tasks for the same 
> endpoint will eventually be executed and causing the same, stormy behavior 
> for this very endpoints.
> My proposal would be to simply not schedule new tasks for the same endpoint, 
> in case we still have pending tasks waiting for execution after 
> {{MIGRATION_DELAY_IN_MS}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Created] (CASSANDRA-13633) Data not loading to keyspace using sstable create via CQLSSTableWriter

2017-06-23 Thread Arpan Khandelwal (JIRA)
Arpan Khandelwal created CASSANDRA-13633:


 Summary: Data not loading to keyspace using sstable create via 
CQLSSTableWriter
 Key: CASSANDRA-13633
 URL: https://issues.apache.org/jira/browse/CASSANDRA-13633
 Project: Cassandra
  Issue Type: Bug
  Components: Tools
 Environment: Linux
Reporter: Arpan Khandelwal
 Fix For: 3.10
 Attachments: dataloading_result.png

Scenario : Need to read CSV, Write SSTable using CQLSSTableWriter and load it 
to the keyspace. [Explained 
here|https://stackoverflow.com/questions/44713777/json-cassandra-field-value-parsing-using-antlr4]
 . That was not working so tried a simple test case available 
here[https://github.com/apache/cassandra/blob/cassandra-3.11/test/unit/org/apache/cassandra/io/sstable/CQLSSTableWriterTest.java#L378]

Which did not worked either. Following is what i tried.

Created cql_keyspace3 with below table and types.

{code:java}
CREATE TYPE cql_keyspace3.tuple2 (a int, b int);
CREATE TYPE cql_keyspace3.tuple3 (a int, b int, c int)
CREATE TABLE cql_keyspace3.table3 ( k int, v1 list, v2 
frozen, PRIMARY KEY (k));
{code}

ran code 

{code:java}
final String KS = "cql_keyspace3";
final String TABLE = "table3";
final String schema = "CREATE TABLE " + KS + "." + TABLE + " (" + "  k 
int," + "  v1 list,"
+ "  v2 frozen," + "  PRIMARY KEY (k)" + ")";
File tempdir = Files.createTempDir();
File dataDir = new File(tempdir.getAbsolutePath() + File.separator + KS 
+ File.separator + TABLE);
System.out.println(dataDir);
assert dataDir.mkdirs();
CQLSSTableWriter writer = 
CQLSSTableWriter.builder().inDirectory(dataDir)
.withType("CREATE TYPE " + KS + ".tuple2 (a int, b int)")
.withType("CREATE TYPE " + KS + ".tuple3 (a int, b int, c 
int)").forTable(schema)
.using("INSERT INTO " + KS + "." + TABLE + " (k, v1, v2) " + 
"VALUES (?, ?, ?)").build();


UserType tuple2Type = writer.getUDType("tuple2");
UserType tuple3Type = writer.getUDType("tuple3");
for (int i = 0; i < 100; i++) {
writer.addRow(i,

ImmutableList.builder().add(tuple2Type.newValue().setInt("a", i * 
10).setInt("b", i * 20))
.add(tuple2Type.newValue().setInt("a", i * 30).setInt("b", 
i * 40)).build(),
tuple3Type.newValue().setInt("a", i * 100).setInt("b", i * 
200).setInt("c", i * 300));
}
writer.close();
{code}

It generated sstable in "/tmp/1498224996687-0/cql_keyspace3" dir

Loaded data using following command 

{code:java}
/tmp/1498224996687-0/cql_keyspace3 $ sstableloader -d localhost 
table3-e6e0fa61581911e78be6a72ebce4c745/

Established connection to initial hosts
Opening sstables and calculating sections to stream
Streaming relevant part of 
/tmp/1498224996687-0/cql_keyspace3/table3-e6e0fa61581911e78be6a72ebce4c745/mc-2-big-Data.db
 to [localhost/127.0.0.1]
progress: [localhost/127.0.0.1]0:1/1 100% total: 100% 1.060KiB/s (avg: 
1.060KiB/s)
progress: [localhost/127.0.0.1]0:1/1 100% total: 100% 0.000KiB/s (avg: 
0.984KiB/s)

Summary statistics: 
   Connections per host: 1 
   Total files transferred : 1 
   Total bytes transferred : 5.572KiB  
   Total duration  : 5668 ms   
   Average transfer rate   : 0.982KiB/s
   Peak transfer rate  : 1.060KiB/s
{code}


||k||v1||v2||
|92|[{a:920,b:1840}, {a:2760,b:3680}]|

find full result in attached snapshot.

Please let me know which version of cassandra I should which can allow me to 
load  reseverd types, collections, UDT from sstable create using 
CQLSSTableWriter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-13627) Index queries are rejected on COMPACT tables

2017-06-23 Thread Benjamin Lerer (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Lerer updated CASSANDRA-13627:
---
Reviewer: Benjamin Lerer

> Index queries are rejected on COMPACT tables
> 
>
> Key: CASSANDRA-13627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13627
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>
> Since {{3.0}}, {{compact}} tables are using under the hood {{static}} 
> columns. Due to that {{SELECT}} queries using secondary indexes get rejected 
> with the following error:
> {{Queries using 2ndary indexes don't support selecting only static columns}}.
> This problem can be reproduced using the following unit test:
> {code}@Test
> public void testIndicesOnCompactTable() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int PRIMARY KEY, v int) WITH COMPACT 
> STORAGE");
> createIndex("CREATE INDEX ON %s(v)");
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 1, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 2, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 3, 3);
> assertRows(execute("SELECT pk, v FROM %s WHERE v = 1"),
>row(1, 1),
>row(2, 1));
> }{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

2017-06-23 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060684#comment-16060684
 ] 

Andrés de la Peña commented on CASSANDRA-10130:
---

PR for dtests [here|https://github.com/riptano/cassandra-dtest/pull/1486].

> Node failure during 2i update after streaming can have incomplete 2i when 
> restarted
> ---
>
> Key: CASSANDRA-10130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10130
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Yuki Morishita
>Assignee: Andrés de la Peña
>Priority: Minor
> Fix For: 4.x
>
>
> Since MV/2i update happens after SSTables are received, node failure during 
> MV/2i update can leave received SSTables live when restarted while MV/2i are 
> partially up to date.
> We can add some kind of tracking mechanism to automatically rebuild at the 
> startup, or at least warn user when the node restarts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

2017-06-23 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrés de la Peña updated CASSANDRA-10130:
--
   Resolution: Fixed
Fix Version/s: 4.x
   Status: Resolved  (was: Ready to Commit)

> Node failure during 2i update after streaming can have incomplete 2i when 
> restarted
> ---
>
> Key: CASSANDRA-10130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10130
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Yuki Morishita
>Assignee: Andrés de la Peña
>Priority: Minor
> Fix For: 4.x
>
>
> Since MV/2i update happens after SSTables are received, node failure during 
> MV/2i update can leave received SSTables live when restarted while MV/2i are 
> partially up to date.
> We can add some kind of tracking mechanism to automatically rebuild at the 
> startup, or at least warn user when the node restarts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

2017-06-23 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrés de la Peña updated CASSANDRA-10130:
--
Status: Ready to Commit  (was: Patch Available)

> Node failure during 2i update after streaming can have incomplete 2i when 
> restarted
> ---
>
> Key: CASSANDRA-10130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10130
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Yuki Morishita
>Assignee: Andrés de la Peña
>Priority: Minor
>
> Since MV/2i update happens after SSTables are received, node failure during 
> MV/2i update can leave received SSTables live when restarted while MV/2i are 
> partially up to date.
> We can add some kind of tracking mechanism to automatically rebuild at the 
> startup, or at least warn user when the node restarts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

2017-06-23 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060672#comment-16060672
 ] 

Andrés de la Peña commented on CASSANDRA-10130:
---

Committed as 
[679c31718b709f5619bba80eeb6f388484b94c3c|https://github.com/apache/cassandra/commit/679c31718b709f5619bba80eeb6f388484b94c3c]
 :)

Thanks a lot for your help!

> Node failure during 2i update after streaming can have incomplete 2i when 
> restarted
> ---
>
> Key: CASSANDRA-10130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10130
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Yuki Morishita
>Assignee: Andrés de la Peña
>Priority: Minor
>
> Since MV/2i update happens after SSTables are received, node failure during 
> MV/2i update can leave received SSTables live when restarted while MV/2i are 
> partially up to date.
> We can add some kind of tracking mechanism to automatically rebuild at the 
> startup, or at least warn user when the node restarts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[1/2] cassandra git commit: Improve secondary index (re)build failure and concurrency handling

2017-06-23 Thread adelapena
Repository: cassandra
Updated Branches:
  refs/heads/trunk a1c6a623a -> 679c31718
Updated Tags:  refs/tags/0.8.10-tentative [created] 038b8f212
  refs/tags/1.0.10-tentative [created] b2ca7f821
  refs/tags/1.0.11-tentative [created] 4f0237acd
  refs/tags/1.0.12-tentative [created] 373e5b0d5
  refs/tags/1.0.7-tentative [created] 6a1ed6205
  refs/tags/1.0.8-tentative [created] fe6980eb7
  refs/tags/1.0.9-tentative [created] 3fd0fb6aa
  refs/tags/1.1.0-beta1-tentative [created] 271630d58
  refs/tags/1.1.0-beta2-tentative [created] 643d18af2
  refs/tags/1.1.0-rc1-tentative [created] cbbf54910
  refs/tags/1.1.0-tentative [created] c67153282
  refs/tags/1.1.1-tentative [created] a788a23ca
  refs/tags/1.1.10-tentative [created] 684994215
  refs/tags/1.1.11-tentative [created] d939a0c95
  refs/tags/1.1.12-tentative [created] 2dd73d171
  refs/tags/1.1.2-tentative [created] b94d8d40f
  refs/tags/1.1.3-tentative [created] 94bcc6a6f
  refs/tags/1.1.4-tentative [created] 94e46ff95
  refs/tags/1.1.6-tentative [created] a0900f3d3
  refs/tags/1.1.7-tentative [created] 2f4b6d8c6
  refs/tags/1.1.8-tentative [created] 4885bfccf
  refs/tags/1.1.9-tentative [created] 7eb47c50c
  refs/tags/1.2.0-beta1-tentative [created] 60bf68caa
  refs/tags/1.2.0-beta2-tentative [created] f04bebfa7
  refs/tags/1.2.0-beta3-tentative [created] b86f75dcd
  refs/tags/1.2.0-rc1-tentative [created] d791e0b3f
  refs/tags/1.2.0-rc2-tentative [created] cfe51fb4f
  refs/tags/1.2.0-tentative [created] 69337a436
  refs/tags/1.2.1-tentative [created] 8540974db
  refs/tags/1.2.10-tentative [created] 937536363
  refs/tags/1.2.2-tentative [created] 068b53dd5
  refs/tags/1.2.3-tentative [created] f07804e0d
  refs/tags/1.2.4-tentative [created] 2e96d0711
  refs/tags/1.2.5-tentative [created] 7d4380d66
  refs/tags/1.2.6-tentative [created] a6ca5d496
  refs/tags/1.2.7-tentative [created] ce4e4b9b5
  refs/tags/1.2.8 [created] dd105e6ff
  refs/tags/1.2.8-tentative [created] 0291d6960
  refs/tags/1.2.9-tentative [created] 6164d011e
  refs/tags/2.0.0-beta1-tentative [created] fcdb39384
  refs/tags/2.0.0-beta2-tentative [created] e0eacd281
  refs/tags/2.0.0-rc1-tentative [created] e8ae6720e
  refs/tags/2.0.0-rc2-tentative [created] 3e516a328
  refs/tags/2.0.0-tentative [created] 03045ca22
  refs/tags/2.0.1-tentative [created] eb96db6c1
  refs/tags/3.0.13-tentative [created] 91661ec29
  refs/tags/cassandra-1.2.0 [created] 95395aadf
  refs/tags/list [created] 03b528aa2
  refs/tags/trunk/3881 [created] 602e383d6
  refs/tags/trunk/4120 [created] 087f902d6


http://git-wip-us.apache.org/repos/asf/cassandra/blob/679c3171/test/unit/org/apache/cassandra/index/SecondaryIndexManagerTest.java
--
diff --git 
a/test/unit/org/apache/cassandra/index/SecondaryIndexManagerTest.java 
b/test/unit/org/apache/cassandra/index/SecondaryIndexManagerTest.java
new file mode 100644
index 000..9af7072
--- /dev/null
+++ b/test/unit/org/apache/cassandra/index/SecondaryIndexManagerTest.java
@@ -0,0 +1,721 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.cassandra.index;
+
+import java.io.FileNotFoundException;
+import java.net.SocketException;
+import java.util.Collection;
+import java.util.Collections;
+import java.util.Set;
+import java.util.concurrent.Callable;
+import java.util.concurrent.CountDownLatch;
+import java.util.concurrent.atomic.AtomicBoolean;
+
+import org.junit.After;
+import org.junit.Test;
+
+import org.apache.cassandra.cql3.CQLTester;
+import org.apache.cassandra.db.ColumnFamilyStore;
+import org.apache.cassandra.db.SystemKeyspace;
+import org.apache.cassandra.db.compaction.CompactionInfo;
+import org.apache.cassandra.db.lifecycle.SSTableSet;
+import org.apache.cassandra.io.sstable.format.SSTableReader;
+import org.apache.cassandra.notifications.SSTableAddedNotification;
+import org.apache.cassandra.schema.IndexMetadata;
+import org.apache.cassandra.schema.SchemaConstants;
+import org.apache.cassandra.utils.JVMStabilityInspector;
+import org.apache.cassandra.utils.KillerForTests;
+import org.apache.cassandra.utils.concurrent.Refs;
+
+import static org.junit.Assert.assertEquals;
+import static org.junit.Assert.assertFalse;

[2/2] cassandra git commit: Improve secondary index (re)build failure and concurrency handling

2017-06-23 Thread adelapena
Improve secondary index (re)build failure and concurrency handling

patch by Andres de la Peña; reviewed by Paulo Motta and Sergio Bossa for 
CASSANDRA-10130


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/679c3171
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/679c3171
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/679c3171

Branch: refs/heads/trunk
Commit: 679c31718b709f5619bba80eeb6f388484b94c3c
Parents: a1c6a62
Author: Andrés de la Peña 
Authored: Fri Jun 23 09:30:21 2017 +0100
Committer: Andrés de la Peña 
Committed: Fri Jun 23 09:30:21 2017 +0100

--
 CHANGES.txt |   1 +
 .../apache/cassandra/db/ColumnFamilyStore.java  |  17 +-
 .../db/compaction/CompactionManager.java|   2 +-
 .../apache/cassandra/db/lifecycle/Tracker.java  |   8 +-
 .../cassandra/index/SecondaryIndexManager.java  | 597 +++
 .../index/internal/CassandraIndex.java  |   2 -
 .../notifications/SSTableAddedNotification.java |  35 +-
 .../cassandra/streaming/StreamReceiveTask.java  |   4 +-
 ...pactionStrategyManagerPendingRepairTest.java |  10 +-
 .../LeveledCompactionStrategyTest.java  |   2 +-
 .../cassandra/db/lifecycle/TrackerTest.java |   6 +-
 .../apache/cassandra/index/CustomIndexTest.java |   3 +-
 .../index/SecondaryIndexManagerTest.java| 721 +++
 .../index/internal/CassandraIndexTest.java  |   1 +
 .../index/internal/CustomCassandraIndex.java|   2 -
 .../cassandra/index/sasi/SASIIndexTest.java |  12 +-
 .../cassandra/stress/CompactionStress.java  |   4 +
 17 files changed, 1236 insertions(+), 191 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/679c3171/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 82a0bda..ab06e2b 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 4.0
+ * Improve secondary index (re)build failure and concurrency handling 
(CASSANDRA-10130)
  * Improve calculation of available disk space for compaction (CASSANDRA-13068)
  * Change the accessibility of RowCacheSerializer for third party row cache 
plugins (CASSANDRA-13579)
  * Allow sub-range repairs for a preview of repaired data (CASSANDRA-13570)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/679c3171/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
--
diff --git a/src/java/org/apache/cassandra/db/ColumnFamilyStore.java 
b/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
index dceb41d..893d525 100644
--- a/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
+++ b/src/java/org/apache/cassandra/db/ColumnFamilyStore.java
@@ -410,7 +410,6 @@ public class ColumnFamilyStore implements 
ColumnFamilyStoreMBean
 minCompactionThreshold = new 
DefaultValue<>(metadata.get().params.compaction.minCompactionThreshold());
 maxCompactionThreshold = new 
DefaultValue<>(metadata.get().params.compaction.maxCompactionThreshold());
 crcCheckChance = new 
DefaultValue<>(metadata.get().params.crcCheckChance);
-indexManager = new SecondaryIndexManager(this);
 viewManager = keyspace.viewManager.forTable(metadata.id);
 metric = new TableMetrics(this);
 fileIndexGenerator.set(generation);
@@ -455,6 +454,7 @@ public class ColumnFamilyStore implements 
ColumnFamilyStoreMBean
 }
 
 // create the private ColumnFamilyStores for the secondary column 
indexes
+indexManager = new SecondaryIndexManager(this);
 for (IndexMetadata info : metadata.get().indexes)
 indexManager.addIndex(info);
 
@@ -567,7 +567,7 @@ public class ColumnFamilyStore implements 
ColumnFamilyStoreMBean
 
 data.dropSSTables();
 LifecycleTransaction.waitForDeletions();
-indexManager.invalidateAllIndexesBlocking();
+indexManager.dropAllIndexes();
 
 invalidateCaches();
 }
@@ -800,7 +800,6 @@ public class ColumnFamilyStore implements 
ColumnFamilyStoreMBean
 try (Refs refs = Refs.ref(newSSTables))
 {
 data.addSSTables(newSSTables);
-indexManager.buildAllIndexesBlocking(newSSTables);
 }
 
 logger.info("Done loading load new SSTables for {}/{}", 
keyspace.getName(), name);
@@ -815,14 +814,8 @@ public class ColumnFamilyStore implements 
ColumnFamilyStoreMBean
 {
 ColumnFamilyStore cfs = 
Keyspace.open(ksName).getColumnFamilyStore(cfName);
 
-Set indexes = new HashSet(Arrays.asList(idxNames));
-
-Iterable sstables = 
cfs.getSSTables(SSTableSet.CANONICAL);
-try (Refs refs = 

[jira] [Commented] (CASSANDRA-13512) SASI full-text search queries using standard analyzer do not work in multi-node environments

2017-06-23 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060620#comment-16060620
 ] 

Andrés de la Peña commented on CASSANDRA-13512:
---

The patch looks good to me, with some nits about the 
[dtest|https://github.com/ifesdjeen/cassandra-dtest/tree/13512-master]:
* There should be a {{@since('3.11')}} annotation in 
[{{multinode_full_text_search}}|https://github.com/ifesdjeen/cassandra-dtest/blob/55334ebb724eb5224572c7f58c4f6157bf1780cd/cql_tests.py#L1444].
* I seems there is a typo 
[here|https://github.com/ifesdjeen/cassandra-dtest/blob/55334ebb724eb5224572c7f58c4f6157bf1780cd/cql_tests.py#L1442],
 "dests" by "dtests".
* This is only a suggestion, I think it would be nice to break [this 
line|https://github.com/ifesdjeen/cassandra-dtest/blob/55334ebb724eb5224572c7f58c4f6157bf1780cd/cql_tests.py#L1466]
 to satisfy the 120 char width. 

> SASI full-text search queries using standard analyzer do not work in 
> multi-node environments 
> -
>
> Key: CASSANDRA-13512
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13512
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Alex Petrov
>Assignee: Alex Petrov
>
> SASI full-text search queries using standard analyzer do not work in 
> multi-node environments. Standard Analyzer will rewind the buffer and search 
> term will be empty for any node other than coordinator, so will return no 
> results.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

2017-06-23 Thread Sergio Bossa (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060619#comment-16060619
 ] 

Sergio Bossa commented on CASSANDRA-10130:
--

Excellent job everyone! +1

> Node failure during 2i update after streaming can have incomplete 2i when 
> restarted
> ---
>
> Key: CASSANDRA-10130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10130
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Yuki Morishita
>Assignee: Andrés de la Peña
>Priority: Minor
>
> Since MV/2i update happens after SSTables are received, node failure during 
> MV/2i update can leave received SSTables live when restarted while MV/2i are 
> partially up to date.
> We can add some kind of tracking mechanism to automatically rebuild at the 
> startup, or at least warn user when the node restarts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-13627) Index queries are rejected on COMPACT tables

2017-06-23 Thread Benjamin Lerer (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Lerer updated CASSANDRA-13627:
---
Status: Patch Available  (was: Open)

> Index queries are rejected on COMPACT tables
> 
>
> Key: CASSANDRA-13627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13627
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>
> Since {{3.0}}, {{compact}} tables are using under the hood {{static}} 
> columns. Due to that {{SELECT}} queries using secondary indexes get rejected 
> with the following error:
> {{Queries using 2ndary indexes don't support selecting only static columns}}.
> This problem can be reproduced using the following unit test:
> {code}@Test
> public void testIndicesOnCompactTable() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int PRIMARY KEY, v int) WITH COMPACT 
> STORAGE");
> createIndex("CREATE INDEX ON %s(v)");
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 1, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 2, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 3, 3);
> assertRows(execute("SELECT pk, v FROM %s WHERE v = 1"),
>row(1, 1),
>row(2, 1));
> }{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-13627) Index queries are rejected on COMPACT tables

2017-06-23 Thread Benjamin Lerer (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060592#comment-16060592
 ] 

Benjamin Lerer commented on CASSANDRA-13627:


I pushed some patches for 
[3.0|https://github.com/apache/cassandra/compare/trunk...blerer:13627-3.0] and 
[trunk|https://github.com/apache/cassandra/compare/trunk...blerer:13627-trunk]. 
I ran the test on our internal CI for {{3.0}}, {{3.11}} and {{trunk}}. There 
are no unit test failures and the DTests failure are unrelated to the patches.

The patches make make sure that {{Selection::containsStaticColumns}} and 
{{SelectStatement::selectOnlyStaticColumns}} (in trunk) return the correct 
value for static compact tables.

> Index queries are rejected on COMPACT tables
> 
>
> Key: CASSANDRA-13627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13627
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>
> Since {{3.0}}, {{compact}} tables are using under the hood {{static}} 
> columns. Due to that {{SELECT}} queries using secondary indexes get rejected 
> with the following error:
> {{Queries using 2ndary indexes don't support selecting only static columns}}.
> This problem can be reproduced using the following unit test:
> {code}@Test
> public void testIndicesOnCompactTable() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int PRIMARY KEY, v int) WITH COMPACT 
> STORAGE");
> createIndex("CREATE INDEX ON %s(v)");
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 1, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 2, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 3, 3);
> assertRows(execute("SELECT pk, v FROM %s WHERE v = 1"),
>row(1, 1),
>row(2, 1));
> }{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Commented] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted

2017-06-23 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060582#comment-16060582
 ] 

Andrés de la Peña commented on CASSANDRA-10130:
---

I have just updated both the CHANGES.txt and the commit message, 
[here|https://github.com/adelapena/cassandra/commits/10130-trunk-squash]. 
Thanks!

> Node failure during 2i update after streaming can have incomplete 2i when 
> restarted
> ---
>
> Key: CASSANDRA-10130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10130
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Yuki Morishita
>Assignee: Andrés de la Peña
>Priority: Minor
>
> Since MV/2i update happens after SSTables are received, node failure during 
> MV/2i update can leave received SSTables live when restarted while MV/2i are 
> partially up to date.
> We can add some kind of tracking mechanism to automatically rebuild at the 
> startup, or at least warn user when the node restarts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-13627) Index queries are rejected on COMPACT tables

2017-06-23 Thread Benjamin Lerer (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Lerer updated CASSANDRA-13627:
---
Component/s: CQL

> Index queries are rejected on COMPACT tables
> 
>
> Key: CASSANDRA-13627
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13627
> Project: Cassandra
>  Issue Type: Bug
>  Components: CQL
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>
> Since {{3.0}}, {{compact}} tables are using under the hood {{static}} 
> columns. Due to that {{SELECT}} queries using secondary indexes get rejected 
> with the following error:
> {{Queries using 2ndary indexes don't support selecting only static columns}}.
> This problem can be reproduced using the following unit test:
> {code}@Test
> public void testIndicesOnCompactTable() throws Throwable
> {
> createTable("CREATE TABLE %s (pk int PRIMARY KEY, v int) WITH COMPACT 
> STORAGE");
> createIndex("CREATE INDEX ON %s(v)");
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 1, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 2, 1);
> execute("INSERT INTO %S (pk, v) VALUES (?, ?)", 3, 3);
> assertRows(execute("SELECT pk, v FROM %s WHERE v = 1"),
>row(1, 1),
>row(2, 1));
> }{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-11223) Queries with LIMIT filtering on clustering columns can return less row than expected

2017-06-23 Thread Stefania (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-11223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefania updated CASSANDRA-11223:
-
Reviewer: Stefania

> Queries with LIMIT filtering on clustering columns can return less row than 
> expected
> 
>
> Key: CASSANDRA-11223
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11223
> Project: Cassandra
>  Issue Type: Bug
>  Components: Local Write-Read Paths
>Reporter: Benjamin Lerer
>Assignee: Benjamin Lerer
>
> A query like {{SELECT * FROM %s WHERE b = 1 LIMIT 2 ALLOW FILTERING}} can 
> return less row than expected if the table has some static columns and some 
> of the partition have no rows matching b = 1.
> The problem can be reproduced with the following unit test:
> {code}
> public void testFilteringOnClusteringColumnsWithLimitAndStaticColumns() 
> throws Throwable
> {
> createTable("CREATE TABLE %s (a int, b int, s int static, c int, 
> primary key (a, b))");
> for (int i = 0; i < 3; i++)
> {
> execute("INSERT INTO %s (a, s) VALUES (?, ?)", i, i);
> for (int j = 0; j < 3; j++)
> if (!(i == 0 && j == 1))
> execute("INSERT INTO %s (a, b, c) VALUES (?, ?, ?)", 
> i, j, i + j);
> }
> assertRows(execute("SELECT * FROM %s"),
>    row(1, 0, 1, 1),
>    row(1, 1, 1, 2),
>    row(1, 2, 1, 3),
>    row(0, 0, 0, 0),
>    row(0, 2, 0, 2),
>    row(2, 0, 2, 2),
>    row(2, 1, 2, 3),
>    row(2, 2, 2, 4));
> assertRows(execute("SELECT * FROM %s WHERE b = 1 ALLOW FILTERING"),
>    row(1, 1, 1, 2),
>    row(2, 1, 2, 3));
> assertRows(execute("SELECT * FROM %s WHERE b = 1 LIMIT 2 ALLOW 
> FILTERING"),
>    row(1, 1, 1, 2),
>    row(2, 1, 2, 3)); // < FAIL It returns only one 
> row because the static row of partition 0 is counted and filtered out in 
> SELECT statement
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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



[jira] [Updated] (CASSANDRA-13464) Failed to create Materialized view with a specific token range

2017-06-23 Thread Krishna Dattu Koneru (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krishna Dattu Koneru updated CASSANDRA-13464:
-
   Labels: materializedviews  (was: )
Reproduced In: 3.0.13, 3.11.x, 4.x  (was: 3.0.13)
   Status: Patch Available  (was: Open)

> Failed to create Materialized view with a specific token range
> --
>
> Key: CASSANDRA-13464
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13464
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Natsumi Kojima
>Assignee: Krishna Dattu Koneru
>Priority: Minor
>  Labels: materializedviews
>
> Failed to create Materialized view with a specific token range.
> Example :
> {code:java}
> $ ccm create "MaterializedView" -v 3.0.13
> $ ccm populate  -n 3
> $ ccm start
> $ ccm status
> Cluster: 'MaterializedView'
> ---
> node1: UP
> node3: UP
> node2: UP
> $ccm node1 cqlsh
> Connected to MaterializedView at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.0.13 | CQL spec 3.4.0 | Native protocol v4]
> Use HELP for help.
> cqlsh> CREATE KEYSPACE test WITH replication = {'class':'SimpleStrategy', 
> 'replication_factor':3};
> cqlsh> CREATE TABLE test.test ( id text PRIMARY KEY , value1 text , value2 
> text, value3 text);
> $ccm node1 ring test 
> Datacenter: datacenter1
> ==
> AddressRackStatus State   LoadOwns
> Token
>   
> 3074457345618258602
> 127.0.0.1  rack1   Up Normal  64.86 KB100.00% 
> -9223372036854775808
> 127.0.0.2  rack1   Up Normal  86.49 KB100.00% 
> -3074457345618258603
> 127.0.0.3  rack1   Up Normal  89.04 KB100.00% 
> 3074457345618258602
> $ ccm node1 cqlsh
> cqlsh> INSERT INTO test.test (id, value1 , value2, value3 ) VALUES ('aaa', 
> 'aaa', 'aaa' ,'aaa');
> cqlsh> INSERT INTO test.test (id, value1 , value2, value3 ) VALUES ('bbb', 
> 'bbb', 'bbb' ,'bbb');
> cqlsh> SELECT token(id),id,value1 FROM test.test;
>  system.token(id) | id  | value1
> --+-+
>  -4737872923231490581 | aaa |aaa
>  -3071845237020185195 | bbb |bbb
> (2 rows)
> cqlsh> CREATE MATERIALIZED VIEW test.test_view AS SELECT value1, id FROM 
> test.test WHERE id IS NOT NULL AND value1 IS NOT NULL AND TOKEN(id) > 
> -9223372036854775808 AND TOKEN(id) < -3074457345618258603 PRIMARY KEY(value1, 
> id) WITH CLUSTERING ORDER BY (id ASC);
> ServerError: java.lang.ClassCastException: 
> org.apache.cassandra.cql3.TokenRelation cannot be cast to 
> org.apache.cassandra.cql3.SingleColumnRelation
> {code}
> Stacktrace :
> {code:java}
> INFO  [MigrationStage:1] 2017-04-19 18:32:48,131 ColumnFamilyStore.java:389 - 
> Initializing test.test
> WARN  [SharedPool-Worker-1] 2017-04-19 18:44:07,263 FBUtilities.java:337 - 
> Trigger directory doesn't exist, please create it and try again.
> ERROR [SharedPool-Worker-1] 2017-04-19 18:46:10,072 QueryMessage.java:128 - 
> Unexpected error during query
> java.lang.ClassCastException: org.apache.cassandra.cql3.TokenRelation cannot 
> be cast to org.apache.cassandra.cql3.SingleColumnRelation
>   at 
> org.apache.cassandra.db.view.View.relationsToWhereClause(View.java:275) 
> ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.statements.CreateViewStatement.announceMigration(CreateViewStatement.java:219)
>  ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.statements.SchemaAlteringStatement.execute(SchemaAlteringStatement.java:93)
>  ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:206)
>  ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:237) 
> ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:222) 
> ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:115)
>  ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:513)
>  [apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:407)
>  [apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>  [netty-all-4.0.44.Final.jar:4.0.44.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:357)
>  

[jira] [Commented] (CASSANDRA-13464) Failed to create Materialized view with a specific token range

2017-06-23 Thread Krishna Dattu Koneru (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16060483#comment-16060483
 ] 

Krishna Dattu Koneru commented on CASSANDRA-13464:
--

I have triggered tests for the patch on CircleCI .

||Patch||CircleCI||
|[3.0 | 
https://github.com/apache/cassandra/compare/cassandra-3.0...krishna-koneru:CASSANDRA-13464-3.0]
 |[circleci-3.0|https://circleci.com/gh/krishna-koneru/cassandra/4]|
|[3.11 | 
https://github.com/apache/cassandra/compare/cassandra-3.11...krishna-koneru:CASSANDRA-13464-3.11]|
 [circleci-3.11|https://circleci.com/gh/krishna-koneru/cassandra/6]|
|[trunk | 
https://github.com/apache/cassandra/compare/trunk...krishna-koneru:CASSANDRA-13464-trunk]
 |[circleci-trunk|https://circleci.com/gh/krishna-koneru/cassandra/5]|



> Failed to create Materialized view with a specific token range
> --
>
> Key: CASSANDRA-13464
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13464
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Natsumi Kojima
>Assignee: Krishna Dattu Koneru
>Priority: Minor
>
> Failed to create Materialized view with a specific token range.
> Example :
> {code:java}
> $ ccm create "MaterializedView" -v 3.0.13
> $ ccm populate  -n 3
> $ ccm start
> $ ccm status
> Cluster: 'MaterializedView'
> ---
> node1: UP
> node3: UP
> node2: UP
> $ccm node1 cqlsh
> Connected to MaterializedView at 127.0.0.1:9042.
> [cqlsh 5.0.1 | Cassandra 3.0.13 | CQL spec 3.4.0 | Native protocol v4]
> Use HELP for help.
> cqlsh> CREATE KEYSPACE test WITH replication = {'class':'SimpleStrategy', 
> 'replication_factor':3};
> cqlsh> CREATE TABLE test.test ( id text PRIMARY KEY , value1 text , value2 
> text, value3 text);
> $ccm node1 ring test 
> Datacenter: datacenter1
> ==
> AddressRackStatus State   LoadOwns
> Token
>   
> 3074457345618258602
> 127.0.0.1  rack1   Up Normal  64.86 KB100.00% 
> -9223372036854775808
> 127.0.0.2  rack1   Up Normal  86.49 KB100.00% 
> -3074457345618258603
> 127.0.0.3  rack1   Up Normal  89.04 KB100.00% 
> 3074457345618258602
> $ ccm node1 cqlsh
> cqlsh> INSERT INTO test.test (id, value1 , value2, value3 ) VALUES ('aaa', 
> 'aaa', 'aaa' ,'aaa');
> cqlsh> INSERT INTO test.test (id, value1 , value2, value3 ) VALUES ('bbb', 
> 'bbb', 'bbb' ,'bbb');
> cqlsh> SELECT token(id),id,value1 FROM test.test;
>  system.token(id) | id  | value1
> --+-+
>  -4737872923231490581 | aaa |aaa
>  -3071845237020185195 | bbb |bbb
> (2 rows)
> cqlsh> CREATE MATERIALIZED VIEW test.test_view AS SELECT value1, id FROM 
> test.test WHERE id IS NOT NULL AND value1 IS NOT NULL AND TOKEN(id) > 
> -9223372036854775808 AND TOKEN(id) < -3074457345618258603 PRIMARY KEY(value1, 
> id) WITH CLUSTERING ORDER BY (id ASC);
> ServerError: java.lang.ClassCastException: 
> org.apache.cassandra.cql3.TokenRelation cannot be cast to 
> org.apache.cassandra.cql3.SingleColumnRelation
> {code}
> Stacktrace :
> {code:java}
> INFO  [MigrationStage:1] 2017-04-19 18:32:48,131 ColumnFamilyStore.java:389 - 
> Initializing test.test
> WARN  [SharedPool-Worker-1] 2017-04-19 18:44:07,263 FBUtilities.java:337 - 
> Trigger directory doesn't exist, please create it and try again.
> ERROR [SharedPool-Worker-1] 2017-04-19 18:46:10,072 QueryMessage.java:128 - 
> Unexpected error during query
> java.lang.ClassCastException: org.apache.cassandra.cql3.TokenRelation cannot 
> be cast to org.apache.cassandra.cql3.SingleColumnRelation
>   at 
> org.apache.cassandra.db.view.View.relationsToWhereClause(View.java:275) 
> ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.statements.CreateViewStatement.announceMigration(CreateViewStatement.java:219)
>  ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.statements.SchemaAlteringStatement.execute(SchemaAlteringStatement.java:93)
>  ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:206)
>  ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:237) 
> ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.cql3.QueryProcessor.process(QueryProcessor.java:222) 
> ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.transport.messages.QueryMessage.execute(QueryMessage.java:115)
>  ~[apache-cassandra-3.0.13.jar:3.0.13]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:513)
>