[jira] [Comment Edited] (CASSANDRA-9754) Make index info heap friendly for large CQL partitions

[Michael Kjellman (JIRA)]

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

Michael Kjellman edited comment on CASSANDRA-9754 at 8/24/16 5:58 AM:
--

So, I'm mostly done with a trunk version of the patch, however, I'm currently 
focusing on finishing and polishing the 2.1 based version. Although the 
abstraction of the index is almost a total rewrite between 2.1 and trunk, the 
tree itself (aka the Birch implementation) should remain almost identical   so 
this certainly isn't wasted time for anyone. :) I've cleaned up the 
implementation a bunch, taken care of a bunch of todos and low hanging fruit, 
added more documentation, and pushed it to Github to make it a bit easier to 
make sure the changes apply cleanly.

https://github.com/mkjellman/cassandra/commit/e5389378b19eb03de7dd4d50d6df110c68057985

The following 4 unit tests (out of 1184) are still failing (so close!):
 * org.apache.cassandra.cql3.KeyCacheCqlTest (2 of 2). Need to talk to 
[~aweisberg] to understand exactly what these unit tests are testing.
 * org.apache.cassandra.db.ColumnFamilyStoreTest (2 of 38, both related to 
secondary indexes)

Tomorrow, I hope to push a patch addressing the feedback from [~barnie] (see 
above comment) above along with any changes that come out of the code review 
currently underway by [~jasobrown] and [~kohlisankalp]. I also need/want to do 
some work on feeling more comfortable on the upgrade/backwards compatibility 
story and make sure there is a good unit test story around that.

[~jjirsa] if you get a chance to take a look please let me know if you have any 
initial feedback that would be awesome!


was (Author: mkjellman):
So, I'm mostly done with a trunk version of the patch, however, I'm currently 
focusing on finishing and polishing the 2.1 based version. Although the 
abstraction of the index is almost a total rewrite between 2.1 and trunk the 
tree itself and the Birch implementation should remain the same so this 
certainly isn't wasted time for anyone. :) I've cleaned up the implementation a 
bunch, taken care of a bunch of todos and low hanging fruit, added more 
documentation, and pushed it to Github to make it a bit easier to make sure the 
changes apply cleanly.

https://github.com/mkjellman/cassandra/commit/e5389378b19eb03de7dd4d50d6df110c68057985

The following 4 unit tests (out of 1184) are still failing (so close!):
 * org.apache.cassandra.cql3.KeyCacheCqlTest (2 of 2). Need to talk to 
[~aweisberg] to understand exactly what these unit tests are testing.
 * org.apache.cassandra.db.ColumnFamilyStoreTest (2 of 38, both related to 
secondary indexes)

Tomorrow, I hope to push a patch addressing the feedback from [~barnie] (see 
above comment) above along with any changes that come out of the code review 
currently underway by [~jasobrown] and [~kohlisankalp]. I also need/want to do 
some work on feeling more comfortable on the upgrade/backwards compatibility 
story and make sure there is a good unit test story around that.

[~jjirsa] if you get a chance to take a look please let me know if you have any 
initial feedback that would be awesome!

> Make index info heap friendly for large CQL partitions
> --
>
> Key: CASSANDRA-9754
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9754
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: Michael Kjellman
>Priority: Minor
> Fix For: 4.x
>
> Attachments: 9754_part1-v1.diff, 9754_part2-v1.diff
>
>
>  Looking at a heap dump of 2.0 cluster, I found that majority of the objects 
> are IndexInfo and its ByteBuffers. This is specially bad in endpoints with 
> large CQL partitions. If a CQL partition is say 6,4GB, it will have 100K 
> IndexInfo objects and 200K ByteBuffers. This will create a lot of churn for 
> GC. Can this be improved by not creating so many objects?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-9754) Make index info heap friendly for large CQL partitions

[Michael Kjellman (JIRA)]

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

Michael Kjellman commented on CASSANDRA-9754:
-

So, I'm mostly done with a trunk version of the patch, however, I'm currently 
focusing on finishing and polishing the 2.1 based version. Although the 
abstraction of the index is almost a total rewrite between 2.1 and trunk the 
tree itself and the Birch implementation should remain the same so this 
certainly isn't wasted time for anyone. :) I've cleaned up the implementation a 
bunch, taken care of a bunch of todos and low hanging fruit, added more 
documentation, and pushed it to Github to make it a bit easier to make sure the 
changes apply cleanly.

https://github.com/mkjellman/cassandra/commit/e5389378b19eb03de7dd4d50d6df110c68057985

The following 4 unit tests (out of 1184) are still failing (so close!):
 * org.apache.cassandra.cql3.KeyCacheCqlTest (2 of 2). Need to talk to 
[~aweisberg] to understand exactly what these unit tests are testing.
 * org.apache.cassandra.db.ColumnFamilyStoreTest (2 of 38, both related to 
secondary indexes)

Tomorrow, I hope to push a patch addressing the feedback from [~barnie] (see 
above comment) above along with any changes that come out of the code review 
currently underway by [~jasobrown] and [~kohlisankalp]. I also need/want to do 
some work on feeling more comfortable on the upgrade/backwards compatibility 
story and make sure there is a good unit test story around that.

[~jjirsa] if you get a chance to take a look please let me know if you have any 
initial feedback that would be awesome!

> Make index info heap friendly for large CQL partitions
> --
>
> Key: CASSANDRA-9754
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9754
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: Michael Kjellman
>Priority: Minor
> Fix For: 4.x
>
> Attachments: 9754_part1-v1.diff, 9754_part2-v1.diff
>
>
>  Looking at a heap dump of 2.0 cluster, I found that majority of the objects 
> are IndexInfo and its ByteBuffers. This is specially bad in endpoints with 
> large CQL partitions. If a CQL partition is say 6,4GB, it will have 100K 
> IndexInfo objects and 200K ByteBuffers. This will create a lot of churn for 
> GC. Can this be improved by not creating so many objects?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12527) Stack Overflow returned to queries while upgrading

[Steve Severance (JIRA)]

Steve Severance created CASSANDRA-12527:
---

 Summary: Stack Overflow returned to queries while upgrading
 Key: CASSANDRA-12527
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12527
 Project: Cassandra
  Issue Type: Bug
 Environment: Centos 7 x64
Reporter: Steve Severance


I am currently upgrading our cluster from 2.2.5 to 3.0.8.

Some queries (not sure which) appear to be triggering a stack overflow:

ERROR [SharedPool-Worker-2] 2016-08-24 04:34:52,464 Message.java:611 - 
Unexpected exception during request; channel = [id: 0x5ccb2627, /10.0.2.5:42925 
=> /10.0.2.10:9042]
java.lang.StackOverflowError: null
at 
org.apache.cassandra.db.ClusteringComparator.compare(ClusteringComparator.java:131)
 ~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$LegacyBoundComparator.compare(LegacyLayout.java:1761)
 ~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$LegacyRangeTombstoneList.add(LegacyLayout.java:1835)
 ~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$LegacyRangeTombstoneList.addAll(LegacyLayout.java:1900)
 ~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:709) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]
at 
org.apache.cassandra.db.LegacyLayout$3.computeNext(LegacyLayout.java:711) 
~[apache-cassandra-3.0.8.jar:3.0.8]

cassandra git commit: close files/resources in tests

[dbrosius]

Repository: cassandra
Updated Branches:
  refs/heads/trunk 5a249362e -> 9484783a8


close files/resources in tests


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

Branch: refs/heads/trunk
Commit: 9484783a868279439e8d5a658b27a7c63a0482b7
Parents: 5a24936
Author: Dave Brosius 
Authored: Tue Aug 23 23:47:24 2016 -0400
Committer: Dave Brosius 
Committed: Tue Aug 23 23:47:24 2016 -0400

--
 .../org/apache/cassandra/db/VerifyTest.java |  25 +++--
 .../io/util/BufferedRandomAccessFileTest.java   |  89 
 .../io/util/FileSegmentInputStreamTest.java |  40 +---
 .../apache/cassandra/io/util/FileUtilsTest.java |   3 +-
 .../service/ProtocolBetaVersionTest.java|   3 +-
 .../apache/cassandra/utils/KeyGenerator.java| 101 +--
 6 files changed, 156 insertions(+), 105 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/9484783a/test/unit/org/apache/cassandra/db/VerifyTest.java
--
diff --git a/test/unit/org/apache/cassandra/db/VerifyTest.java 
b/test/unit/org/apache/cassandra/db/VerifyTest.java
index 53bf655..4e55a60 100644
--- a/test/unit/org/apache/cassandra/db/VerifyTest.java
+++ b/test/unit/org/apache/cassandra/db/VerifyTest.java
@@ -275,11 +275,12 @@ public class VerifyTest
 SSTableReader sstable = cfs.getLiveSSTables().iterator().next();
 
 
-RandomAccessFile file = new 
RandomAccessFile(sstable.descriptor.filenameFor(sstable.descriptor.digestComponent),
 "rw");
-Long correctChecksum = Long.parseLong(file.readLine());
-file.close();
-
-writeChecksum(++correctChecksum, 
sstable.descriptor.filenameFor(sstable.descriptor.digestComponent));
+try (RandomAccessFile file = new 
RandomAccessFile(sstable.descriptor.filenameFor(sstable.descriptor.digestComponent),
 "rw"))
+{
+Long correctChecksum = Long.valueOf(file.readLine());
+
+writeChecksum(++correctChecksum, 
sstable.descriptor.filenameFor(sstable.descriptor.digestComponent));
+}
 
 try (Verifier verifier = new Verifier(cfs, sstable, false))
 {
@@ -373,13 +374,15 @@ public class VerifyTest
 
 protected long simpleFullChecksum(String filename) throws IOException
 {
-FileInputStream inputStream = new FileInputStream(filename);
-CRC32 checksum = new CRC32();
-CheckedInputStream cinStream = new CheckedInputStream(inputStream, 
checksum);
-byte[] b = new byte[128];
-while (cinStream.read(b) >= 0) {
+try (FileInputStream inputStream = new FileInputStream(filename))
+{
+CRC32 checksum = new CRC32();
+CheckedInputStream cinStream = new CheckedInputStream(inputStream, 
checksum);
+byte[] b = new byte[128];
+while (cinStream.read(b) >= 0) {
+}
+return cinStream.getChecksum().getValue();
 }
-return cinStream.getChecksum().getValue();
 }
 
 protected void writeChecksum(long checksum, String filePath)

http://git-wip-us.apache.org/repos/asf/cassandra/blob/9484783a/test/unit/org/apache/cassandra/io/util/BufferedRandomAccessFileTest.java
--
diff --git 
a/test/unit/org/apache/cassandra/io/util/BufferedRandomAccessFileTest.java 
b/test/unit/org/apache/cassandra/io/util/BufferedRandomAccessFileTest.java
index 44be53d..2386160 100644
--- a/test/unit/org/apache/cassandra/io/util/BufferedRandomAccessFileTest.java
+++ b/test/unit/org/apache/cassandra/io/util/BufferedRandomAccessFileTest.java
@@ -144,25 +144,26 @@ public class BufferedRandomAccessFileTest
 public void testReadAndWriteOnCapacity() throws IOException
 {
 File tmpFile = File.createTempFile("readtest", "bin");
-SequentialWriter w = new SequentialWriter(tmpFile);
-
-// Fully write the file and sync..
-byte[] in = generateByteArray(RandomAccessReader.DEFAULT_BUFFER_SIZE);
-w.write(in);
-
-try (FileHandle.Builder builder = new FileHandle.Builder(w.getPath());
- FileHandle fh = builder.complete();
- RandomAccessReader r = fh.createReader())
+try (SequentialWriter w = new SequentialWriter(tmpFile))
 {
-// Read it into a same size array.
-byte[] out = new byte[RandomAccessReader.DEFAULT_BUFFER_SIZE];
-r.read(out);
-
-// Cannot read any more.
-int negone = r.read();
-assert negone == -1 : "We 

[jira] [Commented] (CASSANDRA-11550) Make the fanout size for LeveledCompactionStrategy to be configurable

[Dikang Gu (JIRA)]

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

Dikang Gu commented on CASSANDRA-11550:
---

[~krummas] I got some time to test it in one of our cluster, I think the result 
looks promising, after I change the fanout size from 10 to 6, I see ~40% drop 
of the original data size, and the disk io dropped as well.

Take one node for example, before the change, the levels look like this:
SSTables in each level: [0, 12/10, 112/100, 98, 0, 0, 0, 0, 0]
SSTables in each level: [1, 11/10, 114/100, 99, 0, 0, 0, 0, 0]

After I change the fanout size to 6, it becomes:
SSTables in each level: [0, 6, 41/36, 120, 0, 0, 0, 0, 0]
SSTables in each level: [0, 6, 39/36, 123, 0, 0, 0, 0, 0]

which is more efficient, in terms of space amplification and write 
amplification.

[~krummas] what do you think? Thanks!

> Make the fanout size for LeveledCompactionStrategy to be configurable
> -
>
> Key: CASSANDRA-11550
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11550
> Project: Cassandra
>  Issue Type: New Feature
>  Components: Compaction
>Reporter: Dikang Gu
>Assignee: Dikang Gu
>  Labels: lcs
> Fix For: 3.x
>
> Attachments: 
> 0001-make-fanout-size-for-leveledcompactionstrategy-to-be.patch
>
>
> Currently, the fanout size for LeveledCompactionStrategy is hard coded in the 
> system (10). It would be useful to make the fanout size to be tunable, so 
> that we can change it according to different use cases.
> Further more, we can change the size dynamically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

cassandra git commit: don't repeatedly inverve the tokenToEndpointMap

[dbrosius]

Repository: cassandra
Updated Branches:
  refs/heads/trunk e4f604580 -> 5a249362e


don't repeatedly inverve the tokenToEndpointMap


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

Branch: refs/heads/trunk
Commit: 5a249362e2160bd54064756304f14f17b7c05d9f
Parents: e4f6045
Author: Dave Brosius 
Authored: Tue Aug 23 23:08:23 2016 -0400
Committer: Dave Brosius 
Committed: Tue Aug 23 23:08:58 2016 -0400

--
 src/java/org/apache/cassandra/locator/TokenMetadata.java | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/5a249362/src/java/org/apache/cassandra/locator/TokenMetadata.java
--
diff --git a/src/java/org/apache/cassandra/locator/TokenMetadata.java 
b/src/java/org/apache/cassandra/locator/TokenMetadata.java
index 8e43016..5057c2a 100644
--- a/src/java/org/apache/cassandra/locator/TokenMetadata.java
+++ b/src/java/org/apache/cassandra/locator/TokenMetadata.java
@@ -1029,7 +1029,8 @@ public class TokenMetadata
 lock.readLock().lock();
 try
 {
-Set eps = tokenToEndpointMap.inverse().keySet();
+Multimap endpointToTokenMap = 
tokenToEndpointMap.inverse();
+Set eps = endpointToTokenMap.keySet();
 
 if (!eps.isEmpty())
 {
@@ -1039,7 +1040,7 @@ public class TokenMetadata
 {
 sb.append(ep);
 sb.append(':');
-sb.append(tokenToEndpointMap.inverse().get(ep));
+sb.append(endpointToTokenMap.get(ep));
 sb.append(System.getProperty("line.separator"));
 }
 }

[jira] [Comment Edited] (CASSANDRA-6151) CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated

[nicerobot (JIRA)]

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

nicerobot edited comment on CASSANDRA-6151 at 8/24/16 2:42 AM:
---

Hypothetically, i can create lots of single-node results, join them, and 
hopefully the partitioning is retained for processing the data further.

Also, what if my partition key clusters millions of rows? I want to iterate 
those millions of rows on each node.


was (Author: nicerobot):
Hypothetically, i can create lots of single-node results, join them, and 
hopefully the partitioning is retained for processing the data further.

> CqlPagingRecorderReader Used when Partition Key Is Explicitly Stated
> 
>
> Key: CASSANDRA-6151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6151
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Russell Spitzer
>Assignee: Alex Liu
>Priority: Minor
> Attachments: 6151-1.2-branch.txt, 6151-v2-1.2-branch.txt, 
> 6151-v3-1.2-branch.txt, 6151-v4-1.2.10-branch.txt
>
>
> From 
> http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig/19211546#19211546
> The user was attempting to load a single partition using a where clause in a 
> pig load statement. 
> CQL Table
> {code}
> CREATE table data (
>   occurday  text,
>   seqnumber int,
>   occurtimems bigint,
>   unique bigint,
>   fields map,
>   primary key ((occurday, seqnumber), occurtimems, unique)
> )
> {code}
> Pig Load statement Query
> {code}
> data = LOAD 
> 'cql://ks/data?where_clause=seqnumber%3D10%20AND%20occurday%3D%272013-10-01%27'
>  USING CqlStorage();
> {code}
> This results in an exception when processed by the the CqlPagingRecordReader 
> which attempts to page this query even though it contains at most one 
> partition key. This leads to an invalid CQL statement. 
> CqlPagingRecordReader Query
> {code}
> SELECT * FROM "data" WHERE token("occurday","seqnumber") > ? AND
> token("occurday","seqnumber") <= ? AND occurday='A Great Day' 
> AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
> {code}
> Exception
> {code}
>  InvalidRequestException(why:occurday cannot be restricted by more than one 
> relation if it includes an Equal)
> {code}
> I'm not sure it is worth the special case but, a modification to not use the 
> paging record reader when the entire partition key is specified would solve 
> this issue. 
> h3. Solution
>  If it have EQUAL clauses for all the partitioning keys, we use Query 
> {code}
>   SELECT * FROM "data" 
>   WHERE occurday='A Great Day' 
>AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
> {code}
> instead of 
> {code}
>   SELECT * FROM "data" 
>   WHERE token("occurday","seqnumber") > ? 
>AND token("occurday","seqnumber") <= ? 
>AND occurday='A Great Day' 
>AND seqnumber=1 LIMIT 1000 ALLOW FILTERING
> {code}
> The base line implementation is to retrieve all data of all rows around the 
> ring. This new feature is to retrieve all data of a wide row. It's a one 
> level lower than the base line. It helps for the use case where user is only 
> interested in a specific wide row, so the user doesn't spend whole job to 
> retrieve all the rows around the ring.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12490) Add sequence distribution type to cassandra stress

[Stefania (JIRA)]

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

Stefania commented on CASSANDRA-12490:
--

Thanks, can this override the distributions specified in the stress profiles?

> Add sequence distribution type to cassandra stress
> --
>
> Key: CASSANDRA-12490
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12490
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tools
>Reporter: Ben Slater
>Assignee: Ben Slater
>Priority: Minor
> Fix For: 3.10
>
> Attachments: 12490-trunk.patch, cqlstress-seq-example.yaml
>
>
> When using the write command, cassandra stress sequentially generates seeds. 
> This ensures generated values don't overlap (unless the sequence wraps) 
> providing more predictable number of inserted records (and generating a base 
> set of data without wasted writes).
> When using a yaml stress spec there is no sequenced distribution available. 
> It think it would be useful to have this for doing initial load of data for 
> testing 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12490) Add sequence distribution type to cassandra stress

[T Jake Luciani (JIRA)]

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

T Jake Luciani commented on CASSANDRA-12490:


FYI we do support this on the command line via -pop seq=1..100

> Add sequence distribution type to cassandra stress
> --
>
> Key: CASSANDRA-12490
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12490
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tools
>Reporter: Ben Slater
>Assignee: Ben Slater
>Priority: Minor
> Fix For: 3.10
>
> Attachments: 12490-trunk.patch, cqlstress-seq-example.yaml
>
>
> When using the write command, cassandra stress sequentially generates seeds. 
> This ensures generated values don't overlap (unless the sequence wraps) 
> providing more predictable number of inserted records (and generating a base 
> set of data without wasted writes).
> When using a yaml stress spec there is no sequenced distribution available. 
> It think it would be useful to have this for doing initial load of data for 
> testing 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12490) Add sequence distribution type to cassandra stress

[Stefania (JIRA)]

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

Stefania updated CASSANDRA-12490:
-
   Resolution: Fixed
Fix Version/s: (was: 3.x)
   3.10
   Status: Resolved  (was: Patch Available)

> Add sequence distribution type to cassandra stress
> --
>
> Key: CASSANDRA-12490
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12490
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tools
>Reporter: Ben Slater
>Assignee: Ben Slater
>Priority: Minor
> Fix For: 3.10
>
> Attachments: 12490-trunk.patch, cqlstress-seq-example.yaml
>
>
> When using the write command, cassandra stress sequentially generates seeds. 
> This ensures generated values don't overlap (unless the sequence wraps) 
> providing more predictable number of inserted records (and generating a base 
> set of data without wasted writes).
> When using a yaml stress spec there is no sequenced distribution available. 
> It think it would be useful to have this for doing initial load of data for 
> testing 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12490) Add sequence distribution type to cassandra stress

[Stefania (JIRA)]

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

Stefania commented on CASSANDRA-12490:
--

CI results are good, the failed testall build is due to a recent change in that 
build that now counts Eclipse warnings as failures. They are not new warnings. 

Committed to trunk as e4f6045806906332b6c1ed3cf2ceece8f5bb922b, thank you for 
the patch!

> Add sequence distribution type to cassandra stress
> --
>
> Key: CASSANDRA-12490
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12490
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Tools
>Reporter: Ben Slater
>Assignee: Ben Slater
>Priority: Minor
> Fix For: 3.x
>
> Attachments: 12490-trunk.patch, cqlstress-seq-example.yaml
>
>
> When using the write command, cassandra stress sequentially generates seeds. 
> This ensures generated values don't overlap (unless the sequence wraps) 
> providing more predictable number of inserted records (and generating a base 
> set of data without wasted writes).
> When using a yaml stress spec there is no sequenced distribution available. 
> It think it would be useful to have this for doing initial load of data for 
> testing 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

cassandra git commit: Add sequence distribution type to cassandra stress

[stefania]

Repository: cassandra
Updated Branches:
  refs/heads/trunk 94df2a9c8 -> e4f604580


Add sequence distribution type to cassandra stress

patch by Ben Slater; reviewed by Stefania Alborghetti for CASSANDRA-12490


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

Branch: refs/heads/trunk
Commit: e4f6045806906332b6c1ed3cf2ceece8f5bb922b
Parents: 94df2a9
Author: Ben Slater 
Authored: Tue Aug 23 10:23:50 2016 +0800
Committer: Stefania Alborghetti 
Committed: Wed Aug 24 09:45:41 2016 +0800

--
 CHANGES.txt |  1 +
 tools/cqlstress-counter-example.yaml|  1 +
 tools/cqlstress-example.yaml|  1 +
 tools/cqlstress-insanity-example.yaml   |  1 +
 .../stress/generate/DistributionSequence.java   | 69 ++
 .../stress/settings/OptionDistribution.java | 60 +++-
 .../generate/DistributionSequenceTest.java  | 99 
 7 files changed, 230 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/e4f60458/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index fd843dd..12bedfa 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,4 +1,5 @@
 3.10
+ * Add sequence distribution type to cassandra stress (CASSANDRA-12490)
  * "SELECT * FROM foo LIMIT ;" does not error out (CASSANDRA-12154)
  * Define executeLocally() at the ReadQuery Level (CASSANDRA-12474)
  * Extend read/write failure messages with a map of replica addresses

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e4f60458/tools/cqlstress-counter-example.yaml
--
diff --git a/tools/cqlstress-counter-example.yaml 
b/tools/cqlstress-counter-example.yaml
index f8f70ea..9084e84 100644
--- a/tools/cqlstress-counter-example.yaml
+++ b/tools/cqlstress-counter-example.yaml
@@ -48,6 +48,7 @@ table_definition: |
 #  GAUSSIAN(min..max,mean,stdev)A gaussian/normal distribution, 
with explicitly defined mean and stdev
 #  UNIFORM(min..max)A uniform distribution over the 
range [min, max]
 #  FIXED(val)   A fixed distribution, always 
returning the same value
+#  SEQ(min..max)A fixed sequence, returning values 
from min to max sequentially, wrapping if necessary.
 #  Aliases: extr, gauss, normal, norm, weibull
 #
 #  If preceded by ~, the distribution is inverted

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e4f60458/tools/cqlstress-example.yaml
--
diff --git a/tools/cqlstress-example.yaml b/tools/cqlstress-example.yaml
index 835a4cb..b2b915d 100644
--- a/tools/cqlstress-example.yaml
+++ b/tools/cqlstress-example.yaml
@@ -59,6 +59,7 @@ table_definition: |
 #  GAUSSIAN(min..max,mean,stdev)A gaussian/normal distribution, 
with explicitly defined mean and stdev
 #  UNIFORM(min..max)A uniform distribution over the 
range [min, max]
 #  FIXED(val)   A fixed distribution, always 
returning the same value
+#  SEQ(min..max)A fixed sequence, returning values 
from min to max sequentially, wrapping if necessary.
 #  Aliases: extr, gauss, normal, norm, weibull
 #
 #  If preceded by ~, the distribution is inverted

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e4f60458/tools/cqlstress-insanity-example.yaml
--
diff --git a/tools/cqlstress-insanity-example.yaml 
b/tools/cqlstress-insanity-example.yaml
index a286625..35bcd4a 100644
--- a/tools/cqlstress-insanity-example.yaml
+++ b/tools/cqlstress-insanity-example.yaml
@@ -58,6 +58,7 @@ table_definition: |
 #  GAUSSIAN(min..max,mean,stdev)A gaussian/normal distribution, 
with explicitly defined mean and stdev
 #  UNIFORM(min..max)A uniform distribution over the 
range [min, max]
 #  FIXED(val)   A fixed distribution, always 
returning the same value
+#  SEQ(min..max)A fixed sequence, returning values 
from min to max sequentially, wrapping if necessary.
 #  Aliases: extr, gauss, normal, norm, weibull
 #
 #  If preceded by ~, the distribution is inverted

http://git-wip-us.apache.org/repos/asf/cassandra/blob/e4f60458/tools/stress/src/org/apache/cassandra/stress/generate/DistributionSequence.java

[jira] [Commented] (CASSANDRA-12423) Cells missing from compact storage table after upgrading from 2.1.9 to 3.7

[Tyler Hobbs (JIRA)]

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

Tyler Hobbs commented on CASSANDRA-12423:
-

Regarding the patch, it took me a while to convince myself this was the correct 
behavior, so I'll write out some comments for posterity.

In the 2.x world, a range tombstone with a final EOC of 0 results in a 
exclusive deletion _except_ for cells that exactly match the tombstone bound.  
I made a 
[dtest|https://github.com/thobbs/cassandra-dtest/commit/e76250a4471a81a1ece93cc954f42d4a61aa8c2d]
 to double check this (which we should commit, I guess).  This is why we can't 
just use {{EXCL_END_BOUND}} in 3.0 -- in the case where the range tombstone 
bound exactly matches a {{ClusteringPrefix}}, we want that to be included in 
the deletion.

I think we should change the new enum name from {{INCL_END_BOUND_EOC_0}} to 
{{END_BOUND_EOC_0}} for clarity.  It's sort of both inclusive and exclusive, so 
having either one in the name is confusing, I think.  Regarding the code 
comment:

bq.  This value compares as an inclusive end bound but before any clustering 
values. It can be removed once support for thrift and legacy sstables is 
removed.

I find the first half of that confusing.  Maybe rephrase it as "This value is 
inclusive of any exact matches, but does not include any clusterings that it is 
merely a prefix of."  I believe the second half of the comment is incorrect, as 
we'll need to continue treating those range tombstones correctly as long as 
they exist.  Furthermore, once we've serialized tombstones with that enum 
value, we'll always need it for deserialization.

My last concern is around compatibility in a mixed-version cluster.  It seems 
like there could be problems if you did something like this:
* Have a 2.x cluster with range tombstones with an eoc=0 end bound
* Upgrade to some 3.x that doesn't include this fix
* Then, upgrade some nodes to a 3.y that _does_ include this fix while there 
are still legacy sstables

It seems like the 3.y nodes could send results with the new enum value to the 
3.x nodes which would then error while deserializing the results.  I'm not sure 
what to do about that yet.  We could require all sstables to be upgraded before 
upgrading to 3.10 from 3.x, but that would also force any remaining legacy 
tombstones like this to be permanently treated incorrectly, which kind of sucks.

> Cells missing from compact storage table after upgrading from 2.1.9 to 3.7
> --
>
> Key: CASSANDRA-12423
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12423
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Tomasz Grabiec
>Assignee: Stefania
> Attachments: 12423.tar.gz
>
>
> Schema:
> {code}
> create table ks1.test ( id int, c1 text, c2 text, v int, primary key (id, c1, 
> c2)) with compact storage and compression = {'sstable_compression': ''};
> {code}
> sstable2json before upgrading:
> {code}
> [
> {"key": "1",
>  "cells": [["","0",1470761440040513],
>["a","asd",2470761440040513,"t",1470764842],
>["asd:","0",1470761451368658],
>["asd:asd","0",1470761449416613]]}
> ]
> {code}
> Query result with 2.1.9:
> {code}
> cqlsh> select * from ks1.test;
>  id | c1  | c2   | v
> +-+--+---
>   1 | | null | 0
>   1 | asd |  | 0
>   1 | asd |  asd | 0
> (3 rows)
> {code}
> Query result with 3.7:
> {code}
> cqlsh> select * from ks1.test;
>  id | 6331 | 6332 | v
> +--+--+---
>   1 |  | null | 0
> (1 rows)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12526) For LCS, single SSTable up-level is handled inefficiently

[Wei Deng (JIRA)]

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

Wei Deng updated CASSANDRA-12526:
-
Description: 
I'm using the latest trunk (as of August 2016, which probably is going to be 
3.10) to run some experiments on LeveledCompactionStrategy and noticed this 
inefficiency.

The test data is generated using cassandra-stress default parameters 
(keyspace1.standard1), so as you can imagine, it consists of a ton of newly 
inserted partitions that will never merge in compactions, which is probably the 
worst kind of workload for LCS (however, I'll detail later why this scenario 
should not be ignored as a corner case; for now, let's just assume we still 
want to handle this scenario efficiently).

After the compaction test is done, I scrubbed debug.log for patterns that match 
 the "Compacted" summary so that I can see how long each individual compaction 
took and how many bytes they processed. The search pattern is like the 
following:

{noformat}
grep 'Compacted.*standard1' debug.log
{noformat}

Interestingly, I noticed a lot of the finished compactions are marked as having 
*only one* SSTable involved. With the workload mentioned above, the "single 
SSTable" compactions actually consist of the majority of all compactions (as 
shown below), so its efficiency can affect the overall compaction throughput 
quite a bit.

{noformat}
automaton@0ce59d338-1:~/cassandra-trunk/logs$ grep 'Compacted.*standard1' 
debug.log-test1 | wc -l
243
automaton@0ce59d338-1:~/cassandra-trunk/logs$ grep 'Compacted.*standard1' 
debug.log-test1 | grep ") 1 sstable" | wc -l
218
{noformat}

By looking at the code, it appears that there's a way to directly edit the 
level of a particular SSTable like the following:

{code}
sstable.descriptor.getMetadataSerializer().mutateLevel(sstable.descriptor, 
targetLevel);
sstable.reloadSSTableMetadata();
{code}

To be exact, I summed up the time spent for these single-SSTable compactions 
(the total data size is 60GB) and found that if each compaction only needs to 
spend 100ms for only the metadata change (instead of the 10+ second they're 
doing now), it can already achieve 22.75% saving on total compaction time.

Compared to what we have now (reading the whole single-SSTable from old level 
and writing out the same single-SSTable at the new level), the only difference 
I could think of by using this approach is that the new SSTable will have the 
same file name (sequence number) as the old one's, which could break some 
assumptions on some other part of the code. However, not having to go through 
the full read/write IO, and not having to bear the overhead of cleaning up the 
old file, creating the new file, creating more churns in heap and file buffer, 
it seems the benefits outweigh the inconvenience. So I'd argue this JIRA 
belongs to LHF and should be made available in 3.0.x as well.

As mentioned in the 2nd paragraph, I'm also going to address why this kind of 
all-new-partition workload should not be ignored as a corner case. Basically, 
for the main use case of LCS where you need to frequently merge partitions to 
optimize read and eliminate tombstones and expired data sooner, LCS can be 
perfectly happy and efficiently perform the partition merge and tombstone 
elimination for a long time. However, as soon as the node becomes a bit 
unhealthy for various reasons (could be a bad disk so it's missing a whole 
bunch of mutations and need repair, could be the user chooses to ingest way 
more data than it usually takes and exceeds its capability, or god-forbidden, 
some DBA chooses to run offline sstablelevelreset), you will have to handle 
this kind of "all-new-partition with a lot of SSTables in L0" scenario, and 
once all L0 SSTables finally gets up-leveled to L1, you will likely see a lot 
of such single-SSTable compactions, which is the situation this JIRA is 
intended to address.

  was:
I'm using the latest trunk (as of August 2016, which probably is going to be 
3.10) to run some experiments on LeveledCompactionStrategy and noticed this 
inefficiency.

The test data is generated using cassandra-stress default parameters 
(keyspace1.standard1), so as you can imagine, it consists of a ton of newly 
inserted partitions that will never merge in compactions, which is probably the 
worst kind of workload for LCS (however, I'll detail later why this scenario 
should not be ignored as a corner case; for now, let's just assume we still 
want to handle this scenario efficiently).

After the compaction test is done, I scrubbed debug.log for patterns that match 
 the "Compacted" summary so that I can see how long each individual compaction 
took and how many bytes they processed. The search pattern is like the 
following:

{noformat}
grep 'Compacted.*standard1' debug.log
{noformat}

Interestingly, I noticed a lot of the finished compactions are marked as having 
*only one* SSTable 

[jira] [Updated] (CASSANDRA-12526) For LCS, single SSTable up-level is handled inefficiently

[Wei Deng (JIRA)]

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

Wei Deng updated CASSANDRA-12526:
-
Description: 
I'm using the latest trunk (as of August 2016, which probably is going to be 
3.10) to run some experiments on LeveledCompactionStrategy and noticed this 
inefficiency.

The test data is generated using cassandra-stress default parameters 
(keyspace1.standard1), so as you can imagine, it consists of a ton of newly 
inserted partitions that will never merge in compactions, which is probably the 
worst kind of workload for LCS (however, I'll detail later why this scenario 
should not be ignored as a corner case; for now, let's just assume we still 
want to handle this scenario efficiently).

After the compaction test is done, I scrubbed debug.log for patterns that match 
 the "Compacted" summary so that I can see how long each individual compaction 
took and how many bytes they processed. The search pattern is like the 
following:

{noformat}
grep 'Compacted.*standard1' debug.log
{noformat}

Interestingly, I noticed a lot of the finished compactions are marked as having 
*only one* SSTable involved. With the workload mentioned above, the "single 
SSTable" compactions actually consist of the majority of all compactions (as 
shown below), so its efficiency can affect the overall compaction throughput 
quite a bit.

{noformat}
automaton@0ce59d338-1:~/cassandra-trunk/logs$ grep 'Compacted.*standard1' 
debug.log-test1 | wc -l
243
automaton@0ce59d338-1:~/cassandra-trunk/logs$ grep 'Compacted.*standard1' 
debug.log-test1 | grep ") 1 sstable" | wc -l
218
{noformat}

By looking at the code, it appears that there's a way to directly edit the 
level of a particular SSTable like the following:

{code}
sstable.descriptor.getMetadataSerializer().mutateLevel(sstable.descriptor, 
targetLevel);
sstable.reloadSSTableMetadata();
{code}

Compared to what we have now (reading the whole single-SSTable from old level 
and writing out the same single-SSTable at the new level), the only difference 
I could think of by using this approach is that the new SSTable will have the 
same file name (sequence number) as the old one's, which could break some 
assumptions on some other part of the code. However, not having to go through 
the full read/write IO, and not having to bear the overhead of cleaning up the 
old file, creating the new file, creating more churns in heap and file buffer, 
it seems the benefits outweigh the inconvenience. So I'd argue this JIRA 
belongs to LHF and should be made available in 3.0.x as well.

As mentioned in the 2nd paragraph, I'm also going to address why this kind of 
all-new-partition workload should not be ignored as a corner case. Basically, 
for the main use case of LCS where you need to frequently merge partitions to 
optimize read and eliminate tombstones and expired data sooner, LCS can be 
perfectly happy and efficiently perform the partition merge and tombstone 
elimination for a long time. However, as soon as the node becomes a bit 
unhealthy for various reasons (could be a bad disk so it's missing a whole 
bunch of mutations and need repair, could be the user chooses to ingest way 
more data than it usually takes and exceeds its capability, or god-forbidden, 
some DBA chooses to run offline sstablelevelreset), you will have to handle 
this kind of "all-new-partition with a lot of SSTables in L0" scenario, and 
once all L0 SSTables finally gets up-leveled to L1, you will likely see a lot 
of such single-SSTable compactions, which is the situation this JIRA is 
intended to address.

  was:
I'm using the latest trunk (as of August 2016, which probably is going to be 
3.10) to run some experiments on LeveledCompactionStrategy and noticed this 
inefficiency.

The test data is generated using cassandra-stress default parameters 
(keyspace1.standard1), so as you can imagine, it consists of a ton of newly 
inserted partitions that will never merge in compactions, which is probably the 
worst kind of workload for LCS (however, I'll detail later why this scenario 
should not be ignored as a corner case; for now, let's just assume we still 
want to handle this scenario efficiently).

After the compaction test is done, I scrubbed debug.log for patterns that match 
 the "Compacted" summary so that I can see how long each individual compaction 
took and how many bytes they processed. The search pattern is like the 
following:

{noformat}
grep 'Compacted.*standard1' debug.log
{noformat}

Interestingly, I noticed a lot of the finished compactions are marked as having 
*only one* SSTable involved. With the workload mentioned above, the "single 
SSTable" compactions actually consist of the majority of all compactions (as 
shown below), so its efficiency can affect the overall compaction throughput 
quite a bit.

{noformat}
automaton@0ce59d338-1:~/cassandra-trunk/logs$ grep 'Compacted.*standard1' 

[jira] [Commented] (CASSANDRA-12279) nodetool repair hangs on non-existant table

[Paulo Motta (JIRA)]

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

Paulo Motta commented on CASSANDRA-12279:
-

It seems 
[scrub_test.TestScrubIndexes|https://github.com/riptano/cassandra-dtest/blob/master/scrub_test.py#L180]
 is 
[failing|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-2.2-12279-dtest/lastCompletedBuild/testReport/scrub_test/TestScrubIndexes/]
 because {{parseOptionalTables}} does not include indexes. 

One way to fix this is to modify {{parseOptionalTables}} to support indexes,but 
 there are some operations that allow index (such as scrub), and some other 
that don't allow like repair, so you need to account for that when doing the 
check. Another option is to perform the validation only for repair on 
{{StorageService.forceRepairAsync}} (see 
{{StorageService.getValidColumnFamilies}}). The best option, but a bit more 
involved is to fix the root cause of the issue on {{RepairRunnable}}, which is 
to catch any {{RuntimeException}} that happens in the initial phase (setup 
tracing, {{getValidColumnFamilies}}, etc) and send a notification to 
{{RepairRunner}} via {{fireErrorAndComplete}}.

> nodetool repair hangs on non-existant table
> ---
>
> Key: CASSANDRA-12279
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12279
> Project: Cassandra
>  Issue Type: Bug
> Environment: Linux Ubuntu, Openjdk
>Reporter: Benjamin Roth
>Assignee: Masataka Yamaguchi
>Priority: Minor
>  Labels: lhf
> Attachments: 0001-CASSANDRA-12279-2.2.patch, 
> 0001-CASSANDRA-12279-3.0.patch, 0001-CASSANDRA-12279-trunk.patch, 
> CASSANDRA-12279-trunk.patch, new_result_example.txt, org_result_example.txt
>
>
> If nodetool repair is called with a table that does not exist, ist hangs 
> infinitely without any error message or logs.
> E.g.
> nodetool repair foo bar
> Keyspace foo exists but table bar does not



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12279) nodetool repair hangs on non-existant table

[Paulo Motta (JIRA)]

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

Paulo Motta updated CASSANDRA-12279:

Status: Open  (was: Patch Available)

> nodetool repair hangs on non-existant table
> ---
>
> Key: CASSANDRA-12279
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12279
> Project: Cassandra
>  Issue Type: Bug
> Environment: Linux Ubuntu, Openjdk
>Reporter: Benjamin Roth
>Assignee: Masataka Yamaguchi
>Priority: Minor
>  Labels: lhf
> Attachments: 0001-CASSANDRA-12279-2.2.patch, 
> 0001-CASSANDRA-12279-3.0.patch, 0001-CASSANDRA-12279-trunk.patch, 
> CASSANDRA-12279-trunk.patch, new_result_example.txt, org_result_example.txt
>
>
> If nodetool repair is called with a table that does not exist, ist hangs 
> infinitely without any error message or logs.
> E.g.
> nodetool repair foo bar
> Keyspace foo exists but table bar does not



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12526) For LCS, single SSTable up-level is handled inefficiently

[Wei Deng (JIRA)]

Wei Deng created CASSANDRA-12526:


 Summary: For LCS, single SSTable up-level is handled inefficiently
 Key: CASSANDRA-12526
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12526
 Project: Cassandra
  Issue Type: Bug
  Components: Compaction
Reporter: Wei Deng


I'm using the latest trunk (as of August 2016, which probably is going to be 
3.10) to run some experiments on LeveledCompactionStrategy and noticed this 
inefficiency.

The test data is generated using cassandra-stress default parameters 
(keyspace1.standard1), so as you can imagine, it consists of a ton of newly 
inserted partitions that will never merge in compactions, which is probably the 
worst kind of workload for LCS (however, I'll detail later why this scenario 
should not be ignored as a corner case; for now, let's just assume we still 
want to handle this scenario efficiently).

After the compaction test is done, I scrubbed debug.log for patterns that match 
 the "Compacted" summary so that I can see how long each individual compaction 
took and how many bytes they processed. The search pattern is like the 
following:

{noformat}
grep 'Compacted.*standard1' debug.log
{noformat}

Interestingly, I noticed a lot of the finished compactions are marked as having 
*only one* SSTable involved. With the workload mentioned above, the "single 
SSTable" compactions actually consist of the majority of all compactions (as 
shown below), so its efficiency can affect the overall compaction throughput 
quite a bit.

{noformat}
automaton@0ce59d338-1:~/cassandra-trunk/logs$ grep 'Compacted.*standard1' 
debug.log-test1 | wc -l
243
automaton@0ce59d338-1:~/cassandra-trunk/logs$ grep 'Compacted.*standard1' 
debug.log-test1 | grep ") 1 sstable" | wc -l
218
{noformat}

By looking at the code, it appears that there's a way to directly edit the 
level of a particular SSTable like the following:

{code}
sstable.descriptor.getMetadataSerializer().mutateLevel(sstable.descriptor, 
targetLevel);
sstable.reloadSSTableMetadata();
{code}

Compared to what we have now (reading the whole single-SSTable from old level 
and writing out the same single-SSTable at the new level), the only difference 
I could think of by using this approach is that the new SSTable will have the 
same file name (sequence number) as the old one's, which could break some 
assumptions on some other part of the code. However, not having to go through 
the full read/write IO, and not having to bear the overhead of cleaning up the 
old file, creating the new file, creating more churns in heap and file buffer, 
it seems the benefits outweigh the inconvenience. So I'd argue this JIRA 
belongs to LHF and should be made available in 3.0.x as well.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12526) For LCS, single SSTable up-level is handled inefficiently

[Wei Deng (JIRA)]

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

Wei Deng updated CASSANDRA-12526:
-
Labels: compaction lcs performance  (was: )

> For LCS, single SSTable up-level is handled inefficiently
> -
>
> Key: CASSANDRA-12526
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12526
> Project: Cassandra
>  Issue Type: Bug
>  Components: Compaction
>Reporter: Wei Deng
>  Labels: compaction, lcs, performance
>
> I'm using the latest trunk (as of August 2016, which probably is going to be 
> 3.10) to run some experiments on LeveledCompactionStrategy and noticed this 
> inefficiency.
> The test data is generated using cassandra-stress default parameters 
> (keyspace1.standard1), so as you can imagine, it consists of a ton of newly 
> inserted partitions that will never merge in compactions, which is probably 
> the worst kind of workload for LCS (however, I'll detail later why this 
> scenario should not be ignored as a corner case; for now, let's just assume 
> we still want to handle this scenario efficiently).
> After the compaction test is done, I scrubbed debug.log for patterns that 
> match  the "Compacted" summary so that I can see how long each individual 
> compaction took and how many bytes they processed. The search pattern is like 
> the following:
> {noformat}
> grep 'Compacted.*standard1' debug.log
> {noformat}
> Interestingly, I noticed a lot of the finished compactions are marked as 
> having *only one* SSTable involved. With the workload mentioned above, the 
> "single SSTable" compactions actually consist of the majority of all 
> compactions (as shown below), so its efficiency can affect the overall 
> compaction throughput quite a bit.
> {noformat}
> automaton@0ce59d338-1:~/cassandra-trunk/logs$ grep 'Compacted.*standard1' 
> debug.log-test1 | wc -l
> 243
> automaton@0ce59d338-1:~/cassandra-trunk/logs$ grep 'Compacted.*standard1' 
> debug.log-test1 | grep ") 1 sstable" | wc -l
> 218
> {noformat}
> By looking at the code, it appears that there's a way to directly edit the 
> level of a particular SSTable like the following:
> {code}
> sstable.descriptor.getMetadataSerializer().mutateLevel(sstable.descriptor, 
> targetLevel);
> sstable.reloadSSTableMetadata();
> {code}
> Compared to what we have now (reading the whole single-SSTable from old level 
> and writing out the same single-SSTable at the new level), the only 
> difference I could think of by using this approach is that the new SSTable 
> will have the same file name (sequence number) as the old one's, which could 
> break some assumptions on some other part of the code. However, not having to 
> go through the full read/write IO, and not having to bear the overhead of 
> cleaning up the old file, creating the new file, creating more churns in heap 
> and file buffer, it seems the benefits outweigh the inconvenience. So I'd 
> argue this JIRA belongs to LHF and should be made available in 3.0.x as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (CASSANDRA-12075) Include whether or not the client should retry the request when throwing a RequestExecutionException

[Geoffrey Yu (JIRA)]

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

Geoffrey Yu resolved CASSANDRA-12075.
-
Resolution: Won't Fix

> Include whether or not the client should retry the request when throwing a 
> RequestExecutionException
> 
>
> Key: CASSANDRA-12075
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12075
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Geoffrey Yu
>Assignee: Geoffrey Yu
>Priority: Minor
>
> Some requests that result in an error should not be retried by the client. 
> Right now if the client gets an error, it has no way of knowing whether or 
> not it should retry. We can include an extra field in each 
> {{RequestExecutionException}} that will indicate whether the client should 
> retry, retry on a different host, or not retry at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-12525) When adding new nodes to a cluster which has authentication enabled, we end up losing cassandra user's current crendentials and they get reverted back to default cas

[Philip Thompson (JIRA)]

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

Philip Thompson updated CASSANDRA-12525:

Summary: When adding new nodes to a cluster which has authentication 
enabled, we end up losing cassandra user's current crendentials and they get 
reverted back to default cassandra/cassandra crendetials  (was: When adding new 
nodes to a cluster which has authentication enabled, we end up loosing 
cassandra user's current crendentials and they get reverted back to default 
cassandra/cassandra crendetials)

> When adding new nodes to a cluster which has authentication enabled, we end 
> up losing cassandra user's current crendentials and they get reverted back to 
> default cassandra/cassandra crendetials
> -
>
> Key: CASSANDRA-12525
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12525
> Project: Cassandra
>  Issue Type: Bug
>  Components: Configuration
>Reporter: Atin Sood
>Priority: Minor
>
> Made the following observation:
> When adding new nodes to an existing C* cluster with authentication enabled 
> we end up loosing password information about `cassandra` user. 
> Initial Setup
> - Create a 5 node cluster with system_auth having RF=5 and 
> NetworkTopologyStrategy
> - Enable PasswordAuthenticator on this cluster and update the password for 
> 'cassandra' user to say 'password' via the alter query
> - Make sure you run nodetool repair on all the nodes
> Test case
> - Now go ahead and add 5 more nodes to this cluster.
> - Run nodetool repair on all the 10 nodes now
> - Decommission the original 5 nodes such that only the new 5 nodes are in the 
> cluster now
> - Run cqlsh and try to connect to this cluster using old user name and 
> password, cassandra/password
> I was unable to connect to the nodes with the original credentials and was 
> only able to connect using the default cassandra/cassandra credentials
> From the conversation over IIRC
> `beobal: sood: that definitely shouldn't happen. The new nodes should only 
> create the default superuser role if there are 0 roles currently defined 
> (including that default one)`



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-9875) Rebuild from targeted replica

[Geoffrey Yu (JIRA)]

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

Geoffrey Yu commented on CASSANDRA-9875:


Thanks! I've opened a PR for the dtests 
[here|https://github.com/riptano/cassandra-dtest/pull/1273]. I'll keep an eye 
on the tests and look in to any failures that come up.

> Rebuild from targeted replica
> -
>
> Key: CASSANDRA-9875
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9875
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: Geoffrey Yu
>Priority: Minor
>  Labels: lhf
> Fix For: 3.x
>
> Attachments: 9875-dtest-master-v2.txt, 9875-dtest-master.txt, 
> 9875-trunk-v2.txt, 9875-trunk.txt
>
>
> Nodetool rebuild command will rebuild all the token ranges handled by the 
> endpoint. Sometimes we want to rebuild only a certain token range. We should 
> add this ability to rebuild command. We should also add the ability to stream 
> from a given replica.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

svn commit: r1757435 [14/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/types.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/types.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/types.html (added)
+++ cassandra/site/publish/doc/3.10/cql/types.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,796 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/types.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+  Data Types
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data Types
+Native Types
+Working with timestamps
+Working with dates
+Working with times
+Collections
+User-Defined Types
+Tuples
+Custom Types
+
+
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Data Types¶
+CQL is a typed language and supports a rich set of data types, including native types,
+collection types, user-defined types, tuple 
types and custom
+types:
+
+cql_type ::=  native_type | collection_type | user_defined_type | tuple_type | custom_type
+
+
+Native Types¶
+The native types supported by CQL are:
+
+native_type ::=  ASCII
+ | BIGINT
+ | BLOB
+ | BOOLEAN
+ | COUNTER
+ | DATE
+ | DECIMAL
+ | DOUBLE
+ | FLOAT
+ | INET
+ | INT
+ | SMALLINT
+ | TEXT
+ | TIME
+ | TIMESTAMP
+ | TIMEUUID
+ | TINYINT
+ | UUID
+ | VARCHAR
+ | VARINT
+
+The following table gives additional informations on the native data types, 
and on which kind of constants each type supports:
+
+
+
+
+
+
+
+type
+constants supported
+description
+
+
+
+ascii
+string
+ASCII character string
+
+bigint
+integer
+64-bit signed long
+
+blob
+blob
+Arbitrary bytes (no validation)
+
+boolean
+boolean
+Either true 
or false
+
+counter
+integer
+Counter column (64-bit signed value). See Counters for details
+
+date
+integer,
+string
+A date (with no corresponding time value). See Working with dates 
below for details
+
+decimal
+integer,
+float
+Variable-precision decimal
+
+double
+integer
+float
+64-bit IEEE-754 floating point
+
+float
+integer,
+float
+32-bit IEEE-754 floating point
+
+inet
+string
+An IP address, either IPv4 (4 bytes long) or IPv6 (16 bytes long). Note 
that
+there is no inet constant, IP address should be input as 
strings
+
+int
+integer
+32-bit signed int
+
+smallint
+integer
+16-bit signed int
+
+text
+string
+UTF8 encoded string
+
+time
+integer,
+string
+A time (with no corresponding date value) with nanosecond precision. See
+Working 
with times below for details
+
+timestamp
+integer,
+string
+A timestamp (date and time) with millisecond precision. See Working 
with timestamps
+below for details
+
+timeuuid
+uuid
+Version 1 https://en.wikipedia.org/wiki/Universally_unique_identifier;>UUID, 
generally used as a “conflict-free” timestamp. Also see
+Timeuuid functions
+
+tinyint

svn commit: r1757435 [17/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/faq/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/faq/index.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/faq/index.html (added)
+++ cassandra/site/publish/doc/3.10/faq/index.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,462 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/faq/;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+  
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+
+  
+  Frequently Asked Questions
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Why
 cant I set listen_address to listen on 0.0.0.0 (all my 
addresses)?
+What ports does Cassandra use?
+What 
happens to existing data in my cluster when I add new nodes?
+I 
delete data from Cassandra, but disk usage stays the same. What gives?
+Why
 does nodetool ring only show one entry, even though my nodes logged that they 
see each other joining the ring?
+Can 
I change the replication factor (a a keyspace) on a live cluster?
+Can I Store (large) BLOBs in 
Cassandra?
+Nodetool
 says Connection refused to host: 127.0.1.1 for any remote host. 
What gives?
+Will batching my 
operations speed up my bulk load?
+On RHEL nodes are unable to 
join the ring
+How do I unsubscribe from the 
email list?
+Why
 does top report that Cassandra is using a lot more memory than the Java heap 
max?
+What are seeds?
+Does single seed mean 
single point of failure?
+Why cant I call jmx 
method X on jconsole?
+Why do I see ... 
messages dropped ... in the logs?
+Cassandra 
dies with java.lang.OutOfMemoryError: Map 
failed
+What 
happens if two updates are made with the same timestamp?
+Why 
bootstrapping a new node fails with a Stream failed 
error?
+
+
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Frequently Asked Questions¶
+
+Why cant I set listen_address to listen on 0.0.0.0 (all my 
addresses)?
+What ports does Cassandra use?
+What happens to existing data in my cluster when I add new 
nodes?
+I delete data from Cassandra, but disk usage stays the same. What 
gives?
+Why does nodetool ring only show one entry, even though my nodes 
logged that they see each other joining the ring?
+Can I Store (large) BLOBs in Cassandra?
+Nodetool says Connection refused to host: 
127.0.1.1 for any remote host. What gives?
+Will batching my operations speed up my bulk 
load?
+On 
RHEL nodes are unable to join the ring
+How do I unsubscribe from the email list?
+Why does top report that Cassandra is using a lot more 
memory than the Java heap max?
+What are seeds?
+Does single seed mean single point of failure?
+Why do I see ... messages dropped ... in the 
logs?
+Cassandra dies with java.lang.OutOfMemoryError: Map 
failed
+What happens if two updates are made with the same 
timestamp?
+Why bootstrapping a new node fails with a Stream 
failed error?
+
+
+Why cant I set listen_address to 
listen on 0.0.0.0 (all my addresses)?¶
+Cassandra is a gossip-based distributed system and listen_address is the address a node 
tells other nodes to reach
+it at. Telling other nodes contact me on any of my addresses is 
a bad idea; if different nodes in the cluster pick
+different addresses for you, Bad Things happen.
+If you dont want to manually specify an IP to listen_address for each node in your 
cluster 

svn commit: r1757435 [12/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/security.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/security.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/security.html (added)
+++ cassandra/site/publish/doc/3.10/cql/security.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,850 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/security.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+  Security
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Database Roles
+Users
+Data 
Control
+
+
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Security¶
+
+Database Roles¶
+CQL uses database roles to represent users and group of users. 
Syntactically, a role is defined by:
+
+role_name ::=  identifier | string
+
+
+CREATE ROLE¶
+Creating a role uses the CREATE ROLE statement:
+
+create_role_statement ::=  
CREATE ROLE [ IF NOT EXISTS ] role_name
+   [ WITH role_options ]
+role_options  ::=  role_option ( AND role_option )*
+role_option   ::=  
PASSWORD '=' string
+  | LOGIN '=' boolean
+  | SUPERUSER '=' boolean
+  | OPTIONS '=' map_literal
+
+For instance:
+CREATE ROLE new_role;
+CREATE ROLE alice WITH PASSWORD = password_a AND LOGIN = true;
+CREATE ROLE bob WITH PASSWORD = password_b AND LOGIN = true 
AND SUPERUSER = true;
+CREATE ROLE carlos WITH OPTIONS = { 
custom_option1 : option1_value, custom_option2 : 99 };
+
+
+By default roles do not possess LOGIN privileges or SUPERUSER status.
+Permissions on database resources are granted to roles; 
types of resources include keyspaces,
+tables, functions and roles themselves. Roles may be granted to other roles to 
create hierarchical permissions
+structures; in these hierarchies, permissions and SUPERUSER status are inherited, but 
the LOGIN 
privilege is
+not.
+If a role has the LOGIN privilege, clients may identify as that role 
when connecting. For the duration of that
+connection, the client will acquire any roles and privileges granted to that 
role.
+Only a client with with the CREATE permission on the database roles resource may 
issue CREATE ROLE requests (see
+the relevant section below), unless the client is a SUPERUSER. Role 
management in Cassandra
+is pluggable and custom implementations may support only a subset of the 
listed options.
+Role names should be quoted if they contain non-alphanumeric characters.
+
+Setting credentials for internal authentication¶
+Use the WITH PASSWORD clause to set a password for internal 
authentication, enclosing the password in single
+quotation marks.
+If internal authentication has not been set up or the role does not have 
LOGIN 
privileges, the WITH 
PASSWORD
+clause is not necessary.
+
+
+Creating a role conditionally¶
+Attempting to create an existing role results in an invalid query condition 
unless the IF NOT EXISTS option is used.
+If the option is used and the role exists, the 

svn commit: r1757435 [6/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operatin

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/ddl.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/ddl.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/ddl.html (added)
+++ cassandra/site/publish/doc/3.10/cql/ddl.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,970 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/ddl.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+  Data Definition
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data Definition
+Common definitions
+CREATE KEYSPACE
+USE
+ALTER KEYSPACE
+DROP KEYSPACE
+CREATE TABLE
+ALTER 
TABLE
+DROP 
TABLE
+TRUNCATE
+
+
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Data Definition¶
+CQL stores data in tables, whose schema defines the layout of said 
data in the table, and those tables are grouped in
+keyspaces. A keyspace defines a number of options that applies to all 
the tables it contains, most prominently of
+which is the replication strategy used by the keyspace. It is generally 
encouraged to use
+one keyspace by application, and thus many cluster may define only 
one keyspace.
+This section describes the statements used to create, modify, and remove 
those keyspace and tables.
+
+Common definitions¶
+The names of the keyspaces and tables are defined by the following 
grammar:
+
+keyspace_name ::=  name
+table_name::=  [ keyspace_name 
'.' ] name
+name  ::=  unquoted_name 
| quoted_name
+unquoted_name ::=  
re('[a-zA-Z_0-9]{1, 48}')
+quoted_name   ::=  '' unquoted_name 
''
+
+Both keyspace and table name should be comprised of only alphanumeric 
characters, cannot be empty and are limited in
+size to 48 characters (that limit exists mostly to avoid filenames (which may 
include the keyspace and table name) to go
+over the limits of certain file systems). By default, keyspace and table names 
are case insensitive (myTable is
+equivalent to mytable) but case sensitivity can be forced by using 
double-quotes (myTable is different from
+mytable).
+Further, a table is always part of a keyspace and a table name can be 
provided fully-qualified by the keyspace it is
+part of. If is is not fully-qualified, the table is assumed to be in the 
current keyspace (see USE statement).
+Further, the valid names for columns is simply defined as:
+
+column_name ::=  identifier
+
+We also define the notion of statement options for use in the following 
section:
+
+options ::=  option ( AND option )*
+option  ::=  identifier '=' ( identifier | constant | map_literal )
+
+
+
+CREATE KEYSPACE¶
+A keyspace is created using a CREATE KEYSPACE 
statement:
+
+create_keyspace_statement 
::=  CREATE KEYSPACE [ IF NOT EXISTS ] keyspace_name WITH options
+
+For instance:
+CREATE KEYSPACE Excelsior
+   WITH replication 
= {class: SimpleStrategy, replication_factor : 3};
+
+CREATE KEYSPACE Excalibur
+   WITH replication 
= {class: NetworkTopologyStrategy, 
DC1 : 1, DC2 : 3}
+AND durable_writes 
= false;
+
+
+The supported options are:
+
+
+
+
+
+
+

svn commit: r1757435 [27/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/latest/development/how_to_commit.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/latest/development/how_to_commit.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/latest/development/how_to_commit.html (added)
+++ cassandra/site/publish/doc/latest/development/how_to_commit.html Tue Aug 23 
20:58:08 2016
@@ -0,0 +1,326 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/latest/development/how_to_commit.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Cassandra Development
+  
+
+  
+  How-to Commit
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Building 
and IDE Integration
+Testing
+Contributing Code Changes
+Code Style
+Review Checklist
+How-to Commit
+
+
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+How-to Commit¶
+If you are a committer, feel free to pick any process that works for you - 
so long as you are planning to commit the work yourself.
+Here is how committing and merging will usually look for merging and 
pushing for tickets that follow the convention (if patch-based):
+Hypothetical CASSANDRA-12345 ticket is a cassandra-3.0 based bug fix that 
requires different code for cassandra-3.3, and trunk. Contributor Jackie 
supplied a patch for the root branch (12345-3.0.patch), and patches for the 
remaining branches (12345-3.3.patch, 12345-trunk.patch).
+
+On cassandra-3.0:
+
+git am -3 12345-3.0.patch (if we have a problem b/c of 
CHANGES.txt not merging anymore, we fix  it ourselves, in place)
+
+
+On cassandra-3.3:
+
+git merge cassandra-3.0 -s ours
+git apply -3 12345-3.3.patch (likely to have an issue with 
CHANGES.txt here: fix it ourselves, then git add CHANGES.txt)
+git commit —amend
+
+
+On trunk:
+
+git merge cassandra-3.3 -s ours
+git apply -3 12345-trunk.patch (likely to have an issue with 
CHANGES.txt here: fix it ourselves, then git add CHANGES.txt)
+git commit —amend
+
+
+On any branch:
+
+git push origin cassandra-3.0 cassandra-3.3 trunk —atomic
+
+
+
+Same scenario, but a branch-based contribution:
+
+On cassandra-3.0:
+
+git cherry-pick sha-of-3.0-commit (if we have a problem b/c 
of CHANGES.txt not merging anymore, we fix it ourselves, in place)
+
+
+On cassandra-3.3:
+
+git merge cassandra-3.0 -s ours
+git format-patch -1 sha-of-3.3-commit
+git apply -3 sha-of-3.3-commit.patch (likely to have an 
issue with CHANGES.txt here: fix it ourselves, then git add CHANGES.txt)
+git commit —amend
+
+
+On trunk:
+
+git merge cassandra-3.3 -s ours
+git format-patch -1 sha-of-trunk-commit
+git apply -3 sha-of-trunk-commit.patch (likely to have an 
issue with CHANGES.txt here: fix it ourselves, then git add CHANGES.txt)
+git commit —amend
+
+
+On any branch:
+
+git push origin cassandra-3.0 cassandra-3.3 trunk —atomic
+
+
+
+
+Tip
+Notes on git flags:
+-3 flag to am 
and apply will instruct git to perform a 3-way merge for you. If a conflict is 
detected, you can either resolve it manually or invoke git mergetool - for both 
am and apply.
+—atomic flag to git push does the obvious thing: 
pushes all or nothing. Without the flag, the command is equivalent to running 
git push once per each branch. This is nifty in case a race condition happens - 
you won’t push half the 

svn commit: r1757435 [20/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/operating/compression.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/operating/compression.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/operating/compression.html (added)
+++ cassandra/site/publish/doc/3.10/operating/compression.html Tue Aug 23 
20:58:08 2016
@@ -0,0 +1,333 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/operating/compression.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Operating Cassandra
+  
+
+  
+  Compression
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Compression
+Configuring Compression
+Benefits and Uses
+Operational Impact
+Advanced Use
+
+
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Security
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Compression¶
+Cassandra offers operators the ability to configure compression on a 
per-table basis. Compression reduces the size of
+data on disk by compressing the SSTable in user-configurable compression chunk_length_in_kb. 
Because Cassandra
+SSTables are immutable, the CPU cost of compressing is only necessary when the 
SSTable is written - subsequent updates
+to data will land in different SSTables, so Cassandra will not need to 
decompress, overwrite, and recompress data when
+UPDATE commands are issued. On reads, Cassandra will locate the relevant 
compressed chunks on disk, decompress the full
+chunk, and then proceed with the remainder of the read path (merging data from 
disks and memtables, read repair, and so
+on).
+
+Configuring Compression¶
+Compression is configured on a per-table basis as an optional argument to 
CREATE TABLE or ALTER TABLE. By
+default, three options are relevant:
+
+class 
specifies the compression class - Cassandra provides three classes (LZ4Compressor,
+SnappyCompressor, and DeflateCompressor ). The default is 
SnappyCompressor.
+chunk_length_in_kb specifies the number of kilobytes 
of data per compression chunk. The default is 64KB.
+crc_check_chance determines how likely Cassandra is 
to verify the checksum on each compression chunk during
+reads. The default is 1.0.
+
+Users can set compression using the following syntax:
+CREATE 
TABLE keyspace.table (id int PRIMARY KEY) WITH compression = {class: 
LZ4Compressor};
+
+
+Or
+ALTER 
TABLE keyspace.table WITH compression = {class: 
SnappyCompressor, chunk_length_in_kb: 128, 
crc_check_chance: 0.5};
+
+
+Once enabled, compression can be disabled with ALTER TABLE 
setting enabled 
to false:
+ALTER 
TABLE keyspace.table WITH compression = {enabled:false};
+
+
+Operators should be aware, however, that changing compression is not 
immediate. The data is compressed when the SSTable
+is written, and as SSTables are immutable, the compression will not be 
modified until the table is compacted. Upon
+issuing a change to the compression options via ALTER TABLE, 
the existing SSTables will not be modified until they
+are compacted - if an operator needs compression changes to take effect 
immediately, the operator can trigger an SSTable
+rewrite using nodetool 
scrub or nodetool 

svn commit: r1757435 [15/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/development/code_style.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/development/code_style.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/development/code_style.html (added)
+++ cassandra/site/publish/doc/3.10/development/code_style.html Tue Aug 23 
20:58:08 2016
@@ -0,0 +1,354 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/development/code_style.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Cassandra Development
+  
+
+  
+  Code Style
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Building 
and IDE Integration
+Testing
+Contributing Code Changes
+Code Style
+General Code Conventions
+Exception handling
+Boilerplate
+Multiline statements
+Whitespace
+Imports
+Format files for IDEs
+
+
+Review Checklist
+How-to Commit
+
+
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Code Style¶
+
+General Code Conventions¶
+
+
+The Cassandra project follows http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html;>Suns 
Java coding conventions with an important exception: { and } are always placed on a new line
+
+
+
+
+Exception handling¶
+
+
+Never ever write catch (...) {} or catch (...) { logger.error() } merely to satisfy Javas compile-time 
exception checking. Always propagate the exception up or throw RuntimeException (or, 
if it cant happen, AssertionError). This makes the exceptions visible to 
automated tests.
+Avoid propagating up checked exceptions that no caller handles. Rethrow as 
RuntimeException 
(or IOError, if 
that is more applicable).
+Similarly, logger.warn() is often a cop-out: is this an error or not? If 
it is dont hide it behind a warn; if it isnt, no need for the 
warning.
+If you genuinely know an exception indicates an expected condition, 
its okay to ignore it BUT this must be explicitly explained in a 
comment.
+
+
+
+
+Boilerplate¶
+
+
+Avoid redundant Override annotations when implementing abstract 
or interface methods.
+Do not implement equals or hashcode methods unless they are actually 
needed.
+Prefer public final fields to private fields with getters. (But prefer 
encapsulating behavior in real methods to either.)
+Prefer requiring initialization in the constructor to setters.
+Avoid redundant this references to member fields or methods.
+Do not extract interfaces (or abstract classes) unless you actually need 
multiple implementations of it.
+Always include braces for nested levels of conditionals and loops. Only 
avoid braces for single level.
+
+
+
+
+Multiline statements¶
+
+
+Try to keep lines under 120 characters, but use good judgement  
its better to exceed 120 by a little, than split a line that has no 
natural splitting points.
+When splitting inside a method call, use one line per parameter and align 
them, like this:
+
+SSTableWriter writer = new 
SSTableWriter(cfs.getTempSSTablePath(),
+ columnFamilies.size(),
+ StorageService.getPartitioner());
+
+
+
+When splitting a ternary, use one line per clause, carry the operator, and 
align like this:
+
+var = bar 
== null
+? doFoo()
+: doBar();
+
+
+
+
+
+Whitespace¶
+
+
+Please make sure to 

svn commit: r1757435 [11/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/mvs.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/mvs.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/mvs.html (added)
+++ cassandra/site/publish/doc/3.10/cql/mvs.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,387 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/mvs.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+  Materialized Views
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+CREATE MATERIALIZED VIEW
+ALTER MATERIALIZED VIEW
+DROP MATERIALIZED VIEW
+
+
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Materialized Views¶
+Materialized views names are defined by:
+
+view_name ::=  
re('[a-zA-Z_0-9]+')
+
+
+CREATE MATERIALIZED 
VIEW¶
+You can create a materialized view on a table using a CREATE MATERIALIZED 
VIEW statement:
+
+create_materialized_view_statement
 ::=  CREATE MATERIALIZED VIEW [ IF NOT EXISTS ] view_name AS
+select_statement
+PRIMARY KEY '(' primary_key 
')'
+WITH table_options
+
+For instance:
+CREATE MATERIALIZED VIEW monkeySpecies_by_population AS
+SELECT * FROM monkeySpecies
+WHERE population IS NOT NULL 
AND species IS NOT NULL
+PRIMARY KEY (population, 
species)
+WITH comment=Allow query by population instead of 
species;
+
+
+The CREATE MATERIALIZED VIEW statement 
creates a new materialized view. Each such view is a set of rows which
+corresponds to rows which are present in the underlying, or base, table 
specified in the SELECT statement. A
+materialized view cannot be directly updated, but updates to the base table 
will cause corresponding updates in the
+view.
+Creating a materialized view has 3 main parts:
+
+The select statement that restrict the data included in the 
view.
+The primary key definition for the view.
+The options for the view.
+
+Attempting to create an already existing materialized view will return an 
error unless the IF 
NOT EXISTS option is
+used. If it is used, the statement will be a no-op if the materialized view 
already exists.
+
+MV select statement¶
+The select statement of a materialized view creation defines which of the 
base table is included in the view. That
+statement is limited in a number of ways:
+
+the selection is limited to those that only select 
columns of the base table. In other
+words, you cant use any function (aggregate or not), casting, term, 
etc. Aliases are also not supported. You can
+however use * as a shortcut of selecting all columns. Further, static columns cannot be
+included in a materialized view (which means SELECT * 
isnt allowed if the base table has static columns).
+the WHERE 
clause have the following restrictions:
+it cannot include any bind_marker.
+the columns that are not part of the base table primary key can 
only be restricted by an IS NOT NULL
+restriction. No other restriction is allowed.
+as the 

svn commit: r1757435 [8/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operatin

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/dml.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/dml.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/dml.html (added)
+++ cassandra/site/publish/doc/3.10/cql/dml.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,703 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/dml.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+  Data Manipulation
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data Manipulation
+SELECT
+INSERT
+UPDATE
+DELETE
+BATCH
+
+
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Data Manipulation¶
+This section describes the statements supported by CQL to insert, update, 
delete and query data.
+
+SELECT¶
+Querying data from data is done using a SELECT statement:
+
+select_statement ::=  
SELECT [ JSON | DISTINCT ] ( select_clause | '*' )
+  FROM table_name
+  [ WHERE where_clause ]
+  [ GROUP BY group_by_clause ]
+  [ ORDER BY ordering_clause ]
+  [ PER PARTITION LIMIT (integer | bind_marker) ]
+  [ LIMIT (integer | bind_marker) ]
+  [ ALLOW FILTERING ]
+select_clause::=  selector [ AS identifier ] ( ',' selector [ AS identifier ] )
+selector ::=  column_name
+  | term
+  | CAST '(' selector AS cql_type ')'
+  | function_name '(' [ selector ( ',' selector )* ] ')'
+  | COUNT '(' '*' ')'
+where_clause ::=  relation ( AND relation )*
+relation ::=  column_name 
operator term
+  '(' column_name ( ',' column_name 
)* ')' operator tuple_literal
+  TOKEN '(' column_name ( ',' column_name 
)* ')' operator term
+operator ::=  '=' | 
'' | '' | '=' | '=' | '!=' | IN | CONTAINS | CONTAINS KEY
+group_by_clause  ::=  column_name ( 
',' column_name )*
+ordering_clause  ::=  column_name [ 
ASC | DESC ] ( ',' column_name [ ASC | DESC ] )*
+
+For instance:
+SELECT name, 
occupation FROM users WHERE userid IN (199, 200, 207);
+SELECT JSON name, occupation 
FROM users WHERE userid = 
199;
+SELECT name AS user_name, 
occupation AS user_occupation FROM users;
+
+SELECT time, value
+FROM events
+WHERE event_type = myEvent
+  AND time  2011-02-03
+  AND time = 2012-01-01
+
+SELECT COUNT (*) AS user_count FROM users;
+
+
+The SELECT 
statements reads one or more columns for one or more rows in a table. It 
returns a result-set of the rows
+matching the request, where each row contains the values for the selection 
corresponding to the query. Additionally,
+functions including aggregation ones can be applied to the result.
+A SELECT 
statement contains at least a selection clause 
and the name of the table on which
+the selection is on (note that CQL does not joins or 
sub-queries and thus a select statement only apply to a single
+table). In most case, a select will also have a where clause and 

svn commit: r1757435 [28/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/latest/development/patches.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/latest/development/patches.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/latest/development/patches.html (added)
+++ cassandra/site/publish/doc/latest/development/patches.html Tue Aug 23 
20:58:08 2016
@@ -0,0 +1,393 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/latest/development/patches.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Cassandra Development
+  
+
+  
+  Contributing Code Changes
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Building 
and IDE Integration
+Testing
+Contributing Code Changes
+Choosing What to Work on
+Before You Start Coding
+Creating a Patch
+
+
+Code Style
+Review Checklist
+How-to Commit
+
+
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Contributing Code Changes¶
+
+Choosing What to Work on¶
+Submitted patches can include bug fixes, changes to the Java code base, 
improvements for tooling (both Java or Python), documentation, testing or any 
other changes that requires changing the code base. Although the process of 
contributing code is always the same, the amount of work and time it takes to 
get a patch accepted also depends on the kind of issue youre 
addressing.
+
+As a general rule of thumb:
+
+Major new features and significant changes to the code based will likely 
not going to be accepted without deeper discussion within the http://cassandra.apache.org/community/;>developer community
+Bug fixes take higher priority compared to features
+The extend to which tests are required depend on how likely your changes 
will effect the stability of Cassandra in production. Tooling changes requires 
fewer tests than storage engine changes.
+Less complex patches will be faster to review: consider breaking up an 
issue into individual tasks and contributions that can be reviewed 
separately
+
+
+
+
+Hint
+Not sure what to work? Just pick an issue tagged with the https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+=+12310865+AND+labels+=+lhf+AND+status+!=+resolved;>low
 hanging fruit label in JIRA, which we use to flag issues that could turn 
out to be good starter tasks for beginners.
+
+
+
+Before You Start Coding¶
+Although contributions are highly appreciated, we do not guarantee that 
each contribution will become a part of Cassandra. Therefor its 
generally a good idea to first get some feedback on the things you plan to work 
on, especially about any new features or major changes to the code base. You 
can reach out to other developers on the mailing list or IRC channel listed on 
our http://cassandra.apache.org/community/;>community page.
+
+You should also
+
+Avoid redundant work by searching for already reported issues in https://issues.apache.org/jira/browse/CASSANDRA;>JIRA
+Create a new issue early in the process describing what youre 
working on - not just after finishing your patch
+Link related JIRA issues with your own ticket to provide a better 
context
+Update your ticket from time to time by giving feedback on your progress 
and link a GitHub WIP branch with your current code
+Ping people who you actively like to ask for advice on 

svn commit: r1757435 [22/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/operating/repair.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/operating/repair.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/operating/repair.html (added)
+++ cassandra/site/publish/doc/3.10/operating/repair.html Tue Aug 23 20:58:08 
2016
@@ -0,0 +1,269 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/operating/repair.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Operating Cassandra
+  
+
+  
+  Repair
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Compression
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Security
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Repair¶
+
+Todo
+todo
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ 
Previous
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+  
+
+  
+https://twitter.com/cassandra;
+   class="twitter-follow-button"
+   data-show-count="false" data-size="large">Follow @cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+https://twitter.com/intent/tweet?button_hashtag=cassandra;
+   class="twitter-hashtag-button"
+   data-size="large"
+   data-related="ApacheCassandra">Tweet #cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+  
+
+
+
+   2016 http://apache.org;>The Apache Software 
Foundation.
+  Apache, the Apache feather logo, and Apache Cassandra are trademarks of 
The Apache Software Foundation.
+  
+
+  
+
+
+
+https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js";>
+
+https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js"; 
integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS"
 crossorigin="anonymous">
+
+
+
+
+
+  var DOCUMENTATION_OPTIONS = { URL_ROOT:
"", VERSION: "", COLLAPSE_INDEX: false, FILE_SUFFIX: ".html", HAS_SOURCE:  
false, SOURCELINK_SUFFIX: "" };  
+
+
+$(function() {
+// Stick the #nav to the top of the window
+var nav = $('.doc-navigation');
+var navHomeY = nav.offset().top;
+var isFixed = false;
+var $w = $(window);
+$w.scroll(function() {
+var scrollTop = $w.scrollTop();
+var shouldBeFixed = $w.width() > 991 && scrollTop >= navHomeY - 10;
+if (shouldBeFixed && !isFixed) {
+nav.css({
+position: 'fixed',
+top: 0,
+left: nav.offset().left,
+width: nav.width(),
+});
+

svn commit: r1757435 [4/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operatin

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/configuration/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/configuration/index.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/configuration/index.html (added)
+++ cassandra/site/publish/doc/3.10/configuration/index.html Tue Aug 23 
20:58:08 2016
@@ -0,0 +1,256 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/configuration/;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+  
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+
+  
+  Configuring Cassandra
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Cassandra Configuration File
+
+
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Configuring Cassandra¶
+This section describes how to configure Apache Cassandra.
+
+
+Cassandra Configuration File
+
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ Previous
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+  
+
+  
+https://twitter.com/cassandra;
+   class="twitter-follow-button"
+   data-show-count="false" data-size="large">Follow @cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+https://twitter.com/intent/tweet?button_hashtag=cassandra;
+   class="twitter-hashtag-button"
+   data-size="large"
+   data-related="ApacheCassandra">Tweet #cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+  
+
+
+
+   2016 http://apache.org;>The Apache Software 
Foundation.
+  Apache, the Apache feather logo, and Apache Cassandra are trademarks of 
The Apache Software Foundation.
+  
+
+  
+
+
+
+https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js";>
+
+https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js"; 
integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS"
 crossorigin="anonymous">
+
+
+
+
+
+  var DOCUMENTATION_OPTIONS = { URL_ROOT:
"", VERSION: "", COLLAPSE_INDEX: false, FILE_SUFFIX: ".html", HAS_SOURCE:  
false, SOURCELINK_SUFFIX: "" };  
+
+
+$(function() {
+// Stick the #nav to the top of the window
+var nav = $('.doc-navigation');
+var navHomeY = nav.offset().top;
+var isFixed = false;
+var $w = $(window);
+$w.scroll(function() {
+var scrollTop = $w.scrollTop();
+var shouldBeFixed = $w.width() > 991 && scrollTop >= navHomeY - 10;
+if (shouldBeFixed && !isFixed) {
+nav.css({
+position: 'fixed',
+top: 0,
+left: nav.offset().left,
+width: nav.width(),
+});
+nav.addClass('fixed-navigation');
+isFixed = true;
+}
+else 

svn commit: r1757435 [10/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/index.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/index.html (added)
+++ cassandra/site/publish/doc/3.10/cql/index.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,383 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+  
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+The Cassandra Query Language (CQL)¶
+This document describes the Cassandra Query Language (CQL) [1]. Note that this 
document describes the last version of
+the languages. However, the changes section provides the diff between the different 
versions of CQL.
+CQL offers a model close to SQL in the sense that data is put in 
tables containing rows of columns. For
+that reason, when used in this document, these terms (tables, rows and 
columns) have the same definition than they have
+in SQL. But please note that as such, they do not refer to 
the concept of rows and columns found in the deprecated
+thrift API (and earlier version 1 and 2 of CQL).
+
+
+Definitions
+Conventions
+Identifiers and keywords
+Constants
+Terms
+Comments
+Statements
+Prepared Statements
+
+
+Data 
Types
+Native Types
+Working with timestamps
+Working with dates
+Working with times
+Collections
+User-Defined Types
+Tuples
+Custom Types
+
+
+Data 
Definition
+Common definitions
+CREATE KEYSPACE
+USE
+ALTER KEYSPACE
+DROP KEYSPACE
+CREATE TABLE
+ALTER TABLE
+DROP TABLE
+TRUNCATE
+
+
+Data 
Manipulation
+SELECT
+INSERT
+UPDATE
+DELETE
+BATCH
+
+
+Secondary Indexes
+CREATE INDEX
+DROP INDEX
+
+
+Materialized Views
+CREATE MATERIALIZED VIEW
+ALTER MATERIALIZED VIEW
+DROP MATERIALIZED VIEW
+
+
+Security
+Database Roles
+Users
+Data Control
+
+
+Functions
+Scalar functions
+Aggregate functions
+
+
+JSON 
Support
+SELECT JSON
+INSERT JSON
+JSON Encoding of 
Cassandra Data Types
+The fromJson() Function
+The toJson() Function
+
+
+Triggers
+CREATE TRIGGER
+DROP TRIGGER
+
+
+Appendices
+Appendix A: CQL Keywords
+Appendix B: CQL Reserved 
Types
+
+
+Changes
+3.4.3
+3.4.2
+3.4.1
+3.4.0
+3.3.1
+3.3.0
+3.2.0
+3.1.7
+3.1.6
+3.1.5
+3.1.4
+3.1.3
+3.1.2
+3.1.1
+3.1.0
+3.0.5
+3.0.4
+3.0.3
+3.0.2
+3.0.1
+Versioning
+
+
+
+
+
+
+
+[1]Technically, this document CQL version 3, which is 
not backward compatible with CQL version 1 and 2 (which have
+been deprecated and remove) and differs from it in numerous ways.
+
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ Previous
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+  
+
+  
+https://twitter.com/cassandra;
+   class="twitter-follow-button"
+   data-show-count="false" data-size="large">Follow @cassandra
+!function(d,s,id){var 

svn commit: r1757435 [21/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/operating/metrics.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/operating/metrics.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/operating/metrics.html (added)
+++ cassandra/site/publish/doc/3.10/operating/metrics.html Tue Aug 23 20:58:08 
2016
@@ -0,0 +1,1858 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/operating/metrics.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+  
 
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Operating Cassandra
+  
+
+  
+  Monitoring
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Compression
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Metric Types
+Table Metrics
+Keyspace Metrics
+ThreadPool Metrics
+Client Request Metrics
+Cache Metrics
+CQL 
Metrics
+DroppedMessage Metrics
+Streaming Metrics
+Compaction Metrics
+CommitLog Metrics
+Storage Metrics
+HintedHandoff Metrics
+SSTable Index Metrics
+BufferPool Metrics
+Client Metrics
+JVM 
Metrics
+JMX
+Metric Reporters
+
+
+Security
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Monitoring¶
+Metrics in Cassandra are managed using the http://metrics.dropwizard.io;>Dropwizard Metrics library. These 
metrics
+can be queried via JMX or pushed to external monitoring systems using a number 
of http://metrics.dropwizard.io/3.1.0/getting-started/#other-reporting;>built
 in and http://metrics.dropwizard.io/3.1.0/manual/third-party/;>third party 
reporter plugins.
+Metrics are collected for a single node. Its up to the operator to 
use an external monitoring system to aggregate them.
+
+Metric Types¶
+All metrics reported by cassandra fit into one of the following types.
+
+Gauge
+An instantaneous measurement of a value.
+Counter
+A gauge for an AtomicLong instance. Typically this is consumed by 
monitoring the change since the last call to
+see if there is a large increase compared to the norm.
+Histogram
+Measures the statistical distribution of values in a 
stream of data.
+In addition to minimum, maximum, mean, etc., it also measures 
median, 75th, 90th, 95th, 98th, 99th, and 99.9th
+percentiles.
+
+Timer
+Measures both the rate that a particular piece of code is called and the 
histogram of its duration.
+Latency
+Special type that tracks latency (in microseconds) with a Timer plus a Counter that tracks 
the total latency
+accrued since starting. The former is useful if you track the change in total 
latency since the last check. Each
+metric name of this type will have Latency and 
TotalLatency appended to it.
+Meter
+A meter metric which measures mean throughput and one-, five-, and 
fifteen-minute exponentially-weighted moving
+average throughputs.
+
+
+
+Table Metrics¶
+Each table in Cassandra has metrics responsible for tracking its state and 
performance.
+The metric names are all appended with the specific Keyspace and Table name.
+Reported name format:
+
+Metric Name
+org.apache.cassandra.metrics.Table.MetricName.Keyspace.Table
+JMX MBean
+org.apache.cassandra.metrics:type=Table keyspace=Keyspace scope=Table name=MetricName
+
+
+Note
+There is a special table called all without a keyspace. 

svn commit: r1757435 [1/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operatin

[tylerhobbs]

Author: tylerhobbs
Date: Tue Aug 23 20:58:08 2016
New Revision: 1757435

URL: http://svn.apache.org/viewvc?rev=1757435=rev
Log:
Publish latest documentation

Added:
cassandra/site/publish/doc/3.10/
cassandra/site/publish/doc/3.10/architecture/
cassandra/site/publish/doc/3.10/architecture/dynamo.html
cassandra/site/publish/doc/3.10/architecture/guarantees.html
cassandra/site/publish/doc/3.10/architecture/index.html
cassandra/site/publish/doc/3.10/architecture/overview.html
cassandra/site/publish/doc/3.10/architecture/storage_engine.html
cassandra/site/publish/doc/3.10/bugs.html
cassandra/site/publish/doc/3.10/configuration/
cassandra/site/publish/doc/3.10/configuration/cassandra_config_file.html
cassandra/site/publish/doc/3.10/configuration/index.html
cassandra/site/publish/doc/3.10/contactus.html
cassandra/site/publish/doc/3.10/cql/
cassandra/site/publish/doc/3.10/cql/appendices.html
cassandra/site/publish/doc/3.10/cql/changes.html
cassandra/site/publish/doc/3.10/cql/ddl.html
cassandra/site/publish/doc/3.10/cql/definitions.html
cassandra/site/publish/doc/3.10/cql/dml.html
cassandra/site/publish/doc/3.10/cql/functions.html
cassandra/site/publish/doc/3.10/cql/index.html
cassandra/site/publish/doc/3.10/cql/indexes.html
cassandra/site/publish/doc/3.10/cql/json.html
cassandra/site/publish/doc/3.10/cql/mvs.html
cassandra/site/publish/doc/3.10/cql/security.html
cassandra/site/publish/doc/3.10/cql/triggers.html
cassandra/site/publish/doc/3.10/cql/types.html
cassandra/site/publish/doc/3.10/data_modeling/
cassandra/site/publish/doc/3.10/data_modeling/index.html
cassandra/site/publish/doc/3.10/development/
cassandra/site/publish/doc/3.10/development/code_style.html
cassandra/site/publish/doc/3.10/development/how_to_commit.html
cassandra/site/publish/doc/3.10/development/how_to_review.html
cassandra/site/publish/doc/3.10/development/ide.html
cassandra/site/publish/doc/3.10/development/index.html
cassandra/site/publish/doc/3.10/development/patches.html
cassandra/site/publish/doc/3.10/development/testing.html
cassandra/site/publish/doc/3.10/faq/
cassandra/site/publish/doc/3.10/faq/index.html
cassandra/site/publish/doc/3.10/genindex.html
cassandra/site/publish/doc/3.10/getting_started/
cassandra/site/publish/doc/3.10/getting_started/configuring.html
cassandra/site/publish/doc/3.10/getting_started/drivers.html
cassandra/site/publish/doc/3.10/getting_started/index.html
cassandra/site/publish/doc/3.10/getting_started/installing.html
cassandra/site/publish/doc/3.10/getting_started/querying.html
cassandra/site/publish/doc/3.10/index.html
cassandra/site/publish/doc/3.10/objects.inv   (with props)
cassandra/site/publish/doc/3.10/operating/
cassandra/site/publish/doc/3.10/operating/backups.html
cassandra/site/publish/doc/3.10/operating/bloom_filters.html
cassandra/site/publish/doc/3.10/operating/bulk_loading.html
cassandra/site/publish/doc/3.10/operating/cdc.html
cassandra/site/publish/doc/3.10/operating/compaction.html
cassandra/site/publish/doc/3.10/operating/compression.html
cassandra/site/publish/doc/3.10/operating/hardware.html
cassandra/site/publish/doc/3.10/operating/hints.html
cassandra/site/publish/doc/3.10/operating/index.html
cassandra/site/publish/doc/3.10/operating/metrics.html
cassandra/site/publish/doc/3.10/operating/read_repair.html
cassandra/site/publish/doc/3.10/operating/repair.html
cassandra/site/publish/doc/3.10/operating/security.html
cassandra/site/publish/doc/3.10/operating/snitch.html
cassandra/site/publish/doc/3.10/operating/topo_changes.html
cassandra/site/publish/doc/3.10/search.html
cassandra/site/publish/doc/3.10/searchindex.js
cassandra/site/publish/doc/3.10/tools/
cassandra/site/publish/doc/3.10/tools/cqlsh.html
cassandra/site/publish/doc/3.10/tools/index.html
cassandra/site/publish/doc/3.10/tools/nodetool.html
cassandra/site/publish/doc/3.10/troubleshooting/
cassandra/site/publish/doc/3.10/troubleshooting/index.html
cassandra/site/publish/doc/latest/development/
cassandra/site/publish/doc/latest/development/code_style.html
cassandra/site/publish/doc/latest/development/how_to_commit.html
cassandra/site/publish/doc/latest/development/how_to_review.html
cassandra/site/publish/doc/latest/development/ide.html
cassandra/site/publish/doc/latest/development/index.html
cassandra/site/publish/doc/latest/development/patches.html
cassandra/site/publish/doc/latest/development/testing.html
Modified:
cassandra/site/publish/doc/latest/architecture/dynamo.html
cassandra/site/publish/doc/latest/architecture/guarantees.html
cassandra/site/publish/doc/latest/architecture/index.html
cassandra/site/publish/doc/latest/architecture/overview.html

svn commit: r1757435 [19/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/operating/bulk_loading.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/operating/bulk_loading.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/operating/bulk_loading.html (added)
+++ cassandra/site/publish/doc/3.10/operating/bulk_loading.html Tue Aug 23 
20:58:08 2016
@@ -0,0 +1,269 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/operating/bulk_loading.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+  
 
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Operating Cassandra
+  
+
+  
+  Bulk Loading
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Compression
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Security
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Bulk Loading¶
+
+Todo
+TODO
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ Previous
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+  
+
+  
+https://twitter.com/cassandra;
+   class="twitter-follow-button"
+   data-show-count="false" data-size="large">Follow @cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+https://twitter.com/intent/tweet?button_hashtag=cassandra;
+   class="twitter-hashtag-button"
+   data-size="large"
+   data-related="ApacheCassandra">Tweet #cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+  
+
+
+
+   2016 http://apache.org;>The Apache Software 
Foundation.
+  Apache, the Apache feather logo, and Apache Cassandra are trademarks of 
The Apache Software Foundation.
+  
+
+  
+
+
+
+https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js";>
+
+https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js"; 
integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS"
 crossorigin="anonymous">
+
+
+
+
+
+  var DOCUMENTATION_OPTIONS = { URL_ROOT:
"", VERSION: "", COLLAPSE_INDEX: false, FILE_SUFFIX: ".html", HAS_SOURCE:  
false, SOURCELINK_SUFFIX: "" };  
+
+
+$(function() {
+// Stick the #nav to the top of the window
+var nav = $('.doc-navigation');
+var navHomeY = nav.offset().top;
+var isFixed = false;
+var $w = $(window);
+$w.scroll(function() {
+var scrollTop = $w.scrollTop();
+var shouldBeFixed = $w.width() > 991 && scrollTop >= navHomeY - 10;
+if (shouldBeFixed && !isFixed) {
+nav.css({
+position: 'fixed',
+top: 0,
+left: nav.offset().left,
+

svn commit: r1757435 [29/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Modified: cassandra/site/publish/doc/latest/operating/metrics.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/latest/operating/metrics.html?rev=1757435=1757434=1757435=diff
==
--- cassandra/site/publish/doc/latest/operating/metrics.html (original)
+++ cassandra/site/publish/doc/latest/operating/metrics.html Tue Aug 23 
20:58:08 2016
@@ -24,7 +24,7 @@
   
   
 
-  
 
+  
 
 
 
   
@@ -152,6 +152,7 @@
 SSTable Index Metrics
 BufferPool Metrics
 Client Metrics
+JVM 
Metrics
 JMX
 Metric Reporters
 
@@ -162,8 +163,9 @@
 
 Cassandra Tools
 Troubleshooting
+Cassandra Development
 Frequently Asked Questions
-Reporting bugs and contributing
+Reporting Bugs and Contributing
 Contact us
 
 
@@ -645,39 +647,63 @@ specific type.
 
 
 
-Name
-Type
-Description
+Name
+
+Type
+
+Description
+
 
 
 
-Timeouts
-Counter
-Number of timeouts encountered.
+Timeouts
+
+Counter
+
+Number of timeouts encountered.
+
 
-Failures
-Counter
-Number of transaction failures encountered.
+Failures
+
+Counter
+
+Number of transaction failures encountered.
+
 
-
-Latency
-Transaction read latency.
+
+
+Latency
+
+Transaction read latency.
+
 
-Unavailables
-Counter
-Number of unavailable exceptions encountered.
+Unavailables
+
+Counter
+
+Number of unavailable exceptions encountered.
+
 
-UnfinishedCommit
-Counter
-Number of transactions that were committed on read.
+UnfinishedCommit
+
+Counter
+
+Number of transactions that were committed on 
read.
+
 
-ConditionNotMet
-Counter
-Number of transaction preconditions did not match current values.
+ConditionNotMet
+
+Counter
+
+Number of transaction preconditions did not match 
current values.
+
 
-ContentionHistogram
-Histogram
-How many contended reads were encountered
+ContentionHistogram
+
+Histogram
+
+How many contended reads were encountered
+
 
 
 
@@ -696,35 +722,56 @@ specific type.
 
 
 
-Name
-Type
-Description
+Name
+
+Type
+
+Description
+
 
 
 
-Timeouts
-Counter
-Number of timeouts encountered.
+Timeouts
+
+Counter
+
+Number of timeouts encountered.
+
 
-Failures
-Counter
-Number of transaction failures encountered.
+Failures
+
+Counter
+
+Number of transaction failures encountered.
+
 
-
-Latency
-Transaction write latency.
+
+
+Latency
+
+Transaction write latency.
+
 
-UnfinishedCommit
-Counter
-Number of transactions that were committed on write.
+UnfinishedCommit
+
+Counter
+
+Number of transactions that were committed on 
write.
+
 
-ConditionNotMet
-Counter
-Number of transaction preconditions did not match current values.
+ConditionNotMet
+
+Counter
+
+Number of transaction preconditions did not match 
current values.
+
 
-ContentionHistogram
-Histogram
-How many contended writes were encountered
+ContentionHistogram
+
+Histogram
+
+How many contended writes were encountered
+
 
 
 
@@ -743,27 +790,42 @@ specific type.
 
 
 
-Name
-Type
-Description
+Name
+
+Type
+
+Description
+
 
 
 
-Timeouts
-Counter
-Number of timeouts encountered.
+Timeouts
+
+Counter
+
+Number of timeouts encountered.
+
 
-Failures
-Counter
-Number of read failures encountered.
+Failures
+
+Counter
+
+Number of read failures encountered.
+
 
-
-Latency
-Read latency.
+
+
+Latency
+
+Read latency.
+
 
-Unavailables
-Counter
-Number of unavailable exceptions encountered.
+Unavailables
+
+Counter
+
+Number of unavailable exceptions encountered.
+
 
 
 
@@ -782,27 +844,42 @@ specific type.
 
 
 
-Name
-Type
-Description
+Name
+
+Type
+
+Description
+
 
 
 
-Timeouts
-Counter
-Number of timeouts encountered.
+Timeouts
+
+Counter
+
+Number of timeouts encountered.
+
 
-Failures
-Counter
-Number of range query failures encountered.
+Failures
+
+Counter
+
+Number of range query failures encountered.
+
 
-
-Latency
-Range query latency.
+
+
+Latency
+
+Range query latency.
+
 
-Unavailables
-Counter
-Number of unavailable exceptions encountered.
+Unavailables
+
+Counter
+
+Number of unavailable exceptions encountered.
+
 
 
 
@@ -821,27 +898,42 @@ specific type.
 
 
 
-Name
-Type
-Description
+Name
+
+Type
+
+Description
+
 
 
 
-Timeouts
-Counter
-Number of timeouts encountered.
+Timeouts
+
+Counter
+
+Number of timeouts encountered.
+
 
-Failures
-Counter
-Number of write failures encountered.
+Failures
+
+Counter
+
+Number of write failures encountered.
+
 
-
-Latency
-Write latency.
+
+
+Latency
+
+Write latency.
+
 
-Unavailables
-Counter
-Number of unavailable exceptions encountered.
+Unavailables
+
+Counter
+
+Number of unavailable exceptions encountered.
+
 
 
 
@@ -860,33 +952,54 @@ specific type.
 
 
 
-Timeouts
-Counter
-Number of timeouts encountered.
+Timeouts
+
+Counter
+
+Number of timeouts encountered.
+
 
-Failures
-Counter
-Number of transaction failures encountered.
+Failures
+
+Counter
+
+Number of transaction failures encountered.
+
 
-Unavailables
-Counter
-Number of unavailable exceptions encountered.
+Unavailables
+
+Counter
+
+Number of unavailable exceptions encountered.
+
 

svn commit: r1757435 [5/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operatin

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/changes.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/changes.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/changes.html (added)
+++ cassandra/site/publish/doc/3.10/cql/changes.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,490 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/changes.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+  Changes
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+3.4.3
+3.4.2
+3.4.1
+3.4.0
+3.3.1
+3.3.0
+3.2.0
+3.1.7
+3.1.6
+3.1.5
+3.1.4
+3.1.3
+3.1.2
+3.1.1
+3.1.0
+3.0.5
+3.0.4
+3.0.3
+3.0.2
+3.0.1
+Versioning
+
+
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Changes¶
+The following describes the changes in each version of CQL.
+
+3.4.3¶
+
+Support for GROUP 
BY (https://issues.apache.org/jira/browse/CASSANDRA-10707;>CASSANDRA-10707).
+Adds a DEFAULT 
UNSET option for INSERT JSON 
to ignore omitted columns (https://issues.apache.org/jira/browse/CASSANDRA-11424;>CASSANDRA-11424).
+Allows null 
as a legal value for TTL on insert and update. It will be treated as equivalent 
to
+
+inserting a 0 (https://issues.apache.org/jira/browse/CASSANDRA-12216;>CASSANDRA-12216).
+
+
+3.4.2¶
+
+If a table has a non zero default_time_to_live, then explicitly specifying a 
TTL of 0 in an INSERT or
+UPDATE 
statement will result in the new writes not having any expiration (that is, an 
explicit TTL of 0 cancels
+the default_time_to_live). This wasnt the case 
before and the default_time_to_live was applied even though a
+TTL had been explicitly set.
+ALTER TABLE ADD and DROP now allow multiple columns to be 
added/removed.
+New PER PARTITION LIMIT option for 
SELECT 
statements (see https://issues.apache.org/jira/browse/CASSANDRA-7017)">CASSANDRA-7017.
+User-defined functions can now instantiate UDTValue and TupleValue instances 
via the
+new UDFContext 
interface (see https://issues.apache.org/jira/browse/CASSANDRA-10818)">CASSANDRA-10818.
+User-defined types may now be stored in a non-frozen form, 
allowing individual fields to be updated and
+deleted in UPDATE statements and DELETE statements, respectively. (https://issues.apache.org/jira/browse/CASSANDRA-7423)">CASSANDRA-7423).
+
+
+
+3.4.1¶
+
+Adds CAST 
functions.
+
+
+
+3.4.0¶
+
+Support for materialized 
views.
+DELETE 
support for inequality expressions and IN restrictions on any primary key columns.
+UPDATE 
support for IN 
restrictions on any primary key columns.
+
+
+
+3.3.1¶
+
+The syntax TRUNCATE TABLE X is now accepted as an alias for TRUNCATE X.
+
+
+
+3.3.0¶
+
+User-defined functions and aggregates are now 
supported.
+Allows double-dollar enclosed strings literals as an alternative to 
single-quote enclosed strings.
+Introduces Roles to supersede user based authentication and access 
control
+New date, 
time, tinyint and smallint data types have been added.
+JSON support has been added
+Adds new time conversion functions and deprecate dateOf and unixTimestampOf.

svn commit: r1757435 [23/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/operating/topo_changes.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/operating/topo_changes.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/operating/topo_changes.html (added)
+++ cassandra/site/publish/doc/3.10/operating/topo_changes.html Tue Aug 23 
20:58:08 2016
@@ -0,0 +1,360 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/operating/topo_changes.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Operating Cassandra
+  
+
+  
+  Adding, replacing, moving and removing nodes
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Bootstrap
+Removing nodes
+Moving nodes
+Replacing a dead node
+Monitoring progress
+Cleanup data after range 
movements
+
+
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Compression
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Security
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Adding, replacing, moving and removing 
nodes¶
+
+Bootstrap¶
+Adding new nodes is called bootstrapping. The num_tokens parameter 
will define the amount of virtual nodes
+(tokens) the joining node will be assigned during bootstrap. The tokens define 
the sections of the ring (token ranges)
+the node will become responsible for.
+
+Token allocation¶
+With the default token allocation algorithm the new node will pick num_tokens random 
tokens to become responsible
+for. Since tokens are distributed randomly, load distribution improves with a 
higher amount of virtual nodes, but it
+also increases token management overhead. The default of 256 virtual nodes 
should provide a reasonable load balance with
+acceptable overhead.
+On 3.0+ a new token allocation algorithm was introduced to allocate tokens 
based on the load of existing virtual nodes
+for a given keyspace, and thus yield an improved load distribution with a 
lower number of tokens. To use this approach,
+the new node must be started with the JVM option -Dcassandra.allocate_tokens_for_keyspace=keyspace,
 where
+keyspace is the keyspace from which the 
algorithm can find the load information to optimize token assignment for.
+
+Manual token assignment¶
+You may specify a comma-separated list of tokens manually with the initial_token cassandra.yaml 
parameter, and
+if that is specified Cassandra will skip the token allocation process. This 
may be useful when doing token assignment
+with an external tool or when restoring a node with its previous tokens.
+
+
+
+Range streaming¶
+After the tokens are allocated, the joining node will pick current replicas 
of the token ranges it will become
+responsible for to stream data from. By default it will stream from the 
primary replica of each token range in order to
+guarantee data in the new node will be consistent with the current state.
+In the case of any unavailable replica, the consistent bootstrap process 
will fail. To override this behavior and
+potentially miss data from an unavailable replica, set the JVM flag -Dcassandra.consistent.rangemovement=false.
+
+
+Resuming failed/hanged bootstrap¶
+On 2.2+, if the bootstrap process fails, its possible to resume 
bootstrap 

svn commit: r1757435 [9/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operatin

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/functions.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/functions.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/functions.html (added)
+++ cassandra/site/publish/doc/3.10/cql/functions.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,812 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/functions.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+  Functions
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+Scalar functions
+Aggregate functions
+
+
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Functions¶
+CQL supports 2 main categories of functions:
+
+the scalar functions, which simply take a number of 
values and produce an output with it.
+the aggregate functions, which are used to aggregate 
multiple rows results from a
+SELECT 
statement.
+
+In both cases, CQL provides a number of native hard-coded 
functions as well as the ability to create new user-defined
+functions.
+
+Note
+By default, the use of user-defined functions is disabled by 
default for security concerns (even when
+enabled, the execution of user-defined functions is sandboxed and a 
rogue function should not be allowed to do
+evil, but no sandbox is perfect so using user-defined functions is opt-in). 
See the enable_user_defined_functions
+in cassandra.yaml to enable them.
+
+A function is identifier by its name:
+
+function_name ::=  [ keyspace_name 
'.' ] name
+
+
+Scalar functions¶
+
+Native functions¶
+
+Cast¶
+The cast 
function can be used to converts one native datatype to another.
+The following table describes the conversions supported by the cast function. 
Cassandra will silently ignore any
+cast converting a datatype into its own datatype.
+
+
+
+
+
+
+From
+To
+
+
+
+ascii
+text, varchar
+
+bigint
+tinyint, 
smallint, int, float, double, decimal, varint, text,
+varchar
+
+boolean
+text, varchar
+
+counter
+tinyint, 
smallint, int, bigint, float, double, decimal, varint,
+text, varchar
+
+date
+timestamp
+
+decimal
+tinyint, 
smallint, int, bigint, float, double, varint, text,
+varchar
+
+double
+tinyint, 
smallint, int, bigint, float, decimal, varint, text,
+varchar
+
+float
+tinyint, 
smallint, int, bigint, double, decimal, varint, text,
+varchar
+
+inet
+text, varchar
+
+int
+tinyint, 
smallint, bigint, float, double, decimal, varint, text,
+varchar
+
+smallint
+tinyint, 
int, bigint, float, double, decimal, varint, text,
+varchar
+
+time
+text, varchar
+
+timestamp
+date, text, varchar
+
+timeuuid
+timestamp, 
date, text, varchar
+
+tinyint
+tinyint, 
smallint, int, bigint, float, double, decimal, varint,
+text, varchar
+
+uuid
+text, varchar
+
+varint
+tinyint, 
smallint, int, bigint, float, double, decimal, text,
+varchar
+
+
+
+The conversions rely strictly on Javas semantics. For example, the 
double value 1 will be converted to the text value
+1.0. For instance:
+SELECT avg(cast(count as double)) 
FROM myTable
+
+
+
+
+Token¶
+The token 
function allows to 

svn commit: r1757435 [16/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/development/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/development/index.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/development/index.html (added)
+++ cassandra/site/publish/doc/3.10/development/index.html Tue Aug 23 20:58:08 
2016
@@ -0,0 +1,289 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/development/;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+  
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+
+  
+  Cassandra Development
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Building 
and IDE Integration
+Testing
+Contributing Code Changes
+Code Style
+Review Checklist
+How-to Commit
+
+
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Cassandra Development¶
+
+
+Building 
and IDE Integration
+Building From Source
+Setting up Cassandra in 
IntelliJ IDEA
+Setting up Cassandra in 
Eclipse
+
+
+Testing
+Unit Testing
+DTests
+Performance Testing
+
+
+Contributing Code Changes
+Choosing What to Work on
+Before You Start Coding
+Creating a Patch
+
+
+Code Style
+General Code 
Conventions
+Exception handling
+Boilerplate
+Multiline statements
+Whitespace
+Imports
+Format files for IDEs
+
+
+Review Checklist
+How-to Commit
+
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ Previous
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+  
+
+  
+https://twitter.com/cassandra;
+   class="twitter-follow-button"
+   data-show-count="false" data-size="large">Follow @cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+https://twitter.com/intent/tweet?button_hashtag=cassandra;
+   class="twitter-hashtag-button"
+   data-size="large"
+   data-related="ApacheCassandra">Tweet #cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+  
+
+
+
+   2016 http://apache.org;>The Apache Software 
Foundation.
+  Apache, the Apache feather logo, and Apache Cassandra are trademarks of 
The Apache Software Foundation.
+  
+
+  
+
+
+
+https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js";>
+
+https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js"; 
integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS"
 crossorigin="anonymous">
+
+
+
+
+
+  var DOCUMENTATION_OPTIONS = { URL_ROOT:
"", VERSION: "", COLLAPSE_INDEX: false, FILE_SUFFIX: ".html", HAS_SOURCE:  
false, SOURCELINK_SUFFIX: "" };  
+
+
+$(function() {
+// Stick the #nav to the top of the window
+var nav = $('.doc-navigation');
+var navHomeY = nav.offset().top;
+var isFixed = false;
+var $w = $(window);
+$w.scroll(function() 

svn commit: r1757435 [26/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Modified: cassandra/site/publish/doc/latest/bugs.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/latest/bugs.html?rev=1757435=1757434=1757435=diff
==
--- cassandra/site/publish/doc/latest/bugs.html (original)
+++ cassandra/site/publish/doc/latest/bugs.html Tue Aug 23 20:58:08 2016
@@ -24,7 +24,7 @@
   
   
 
- 
 
+ 
 
 
 
   
@@ -59,7 +59,7 @@
   
 
   
-  Reporting bugs and contributing
+  Reporting Bugs and Contributing
   
 
   
@@ -124,8 +124,9 @@
 Operating Cassandra
 Cassandra Tools
 Troubleshooting
+Cassandra Development
 Frequently Asked Questions
-Reporting bugs and contributing
+Reporting Bugs and Contributing
 Contact us
 
 
@@ -140,14 +141,14 @@
 
   
   
-Reporting bugs and contributing¶
+Reporting Bugs and Contributing¶
 If you encounter a problem with Cassandra, the first places to ask for help 
are the user mailing list and the #cassandra IRC 
channel.
 If, after having asked for help, you suspect that you have found a bug in 
Cassandra, you should report it by opening a
 ticket through the https://issues.apache.org/jira/browse/CASSANDRA;>Apache Cassandra 
JIRA. Please provide as much
 details as you can on your problem, and dont forget to indicate which 
version of Cassandra you are running and on which
 environment.
-If you would like to contribute, please check https://wiki.apache.org/cassandra/HowToContribute;>the section on 
contributing on the Cassandra wiki. Please note that the source of this
-documentation is part of the Cassandra git repository and hence contributions 
to the documentation should follow the
+Further details on how to contribute can be found at our Cassandra Development section. Please note that the 
source of
+this documentation is part of the Cassandra git repository and hence 
contributions to the documentation should follow the
 same path.
 
 

Modified: 
cassandra/site/publish/doc/latest/configuration/cassandra_config_file.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/latest/configuration/cassandra_config_file.html?rev=1757435=1757434=1757435=diff
==
--- cassandra/site/publish/doc/latest/configuration/cassandra_config_file.html 
(original)
+++ cassandra/site/publish/doc/latest/configuration/cassandra_config_file.html 
Tue Aug 23 20:58:08 2016
@@ -24,7 +24,7 @@
   
   
 
-   
+   
 
 
   
@@ -240,6 +240,7 @@
 cas_contention_timeout_in_ms
 truncate_request_timeout_in_ms
 request_timeout_in_ms
+slow_query_log_timeout_in_ms
 cross_node_timeout
 streaming_socket_timeout_in_ms
 phi_convict_threshold
@@ -276,8 +277,9 @@
 Operating Cassandra
 Cassandra Tools
 Troubleshooting
+Cassandra Development
 Frequently Asked Questions
-Reporting bugs and contributing
+Reporting Bugs and Contributing
 Contact us
 
 
@@ -878,6 +880,9 @@ If omitted, Cassandra will set both to 1
 
 memtable_cleanup_threshold¶
 This option is commented out by default.
+memtable_cleanup_threshold is deprecated. The default calculation
+is the only reasonable choice. See the comments on  memtable_flush_writers
+for more information.
 Ratio of occupied non-flushing memtable size to total permitted size
 that will trigger a flush of the largest memtable. Larger mct will
 mean larger flushes and hence less compaction, but also less concurrent
@@ -914,13 +919,28 @@ of the commitlog volume.
 
 memtable_flush_writers¶
 This option is commented out by default.
-This sets the amount of memtable flush writer threads.  These will
-be blocked by disk io, and each one will hold a memtable in memory
-while blocked.
-memtable_flush_writers defaults to one per data_file_directory.
-If your data directories are backed by SSD, you can increase this, but
-avoid having memtable_flush_writers * data_file_directories  number of 
cores
-Default Value: 1
+This sets the number of memtable flush writer threads per disk
+as well as the total number of memtables that can be flushed concurrently.
+These are generally a combination of compute and IO bound.
+Memtable flushing is more CPU efficient than memtable ingest and a single 
thread
+can keep up with the ingest rate of a whole server on a single fast disk
+until it temporarily becomes IO bound under contention typically with 
compaction.
+At that point you need multiple flush threads. At some point in the future
+it may become CPU bound all the time.
+You can tell if flushing is falling behind using the 
MemtablePool.BlockedOnAllocation
+metric which should be 0, but will be non-zero if threads are blocked waiting 
on flushing
+to free memory.
+memtable_flush_writers defaults to two for a single data directory.
+This means that two  memtables can be flushed concurrently to the single data 
directory.
+If you have multiple data directories the default is one memtable flushing at 
a time
+but the flush will use a thread per data 

svn commit: r1757435 [25/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/tools/cqlsh.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/tools/cqlsh.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/tools/cqlsh.html (added)
+++ cassandra/site/publish/doc/3.10/tools/cqlsh.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,627 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/tools/cqlsh.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+  
 
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Cassandra Tools
+  
+
+  
+  cqlsh: the CQL shell
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+cqlsh: the CQL shell
+Compatibility
+Optional Dependencies
+cqlshrc
+Command Line Options
+Special Commands
+
+
+Nodetool
+
+
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+cqlsh: the CQL shell¶
+cqlsh is a command line shell for interacting with Cassandra through CQL 
(the Cassandra Query Language).  It is shipped
+with every Cassandra package, and can be found in the bin/ directory alongside 
the cassandra executable.  cqlsh utilizes
+the Python native protocol driver, and connects to the single node specified 
on the command line.
+
+Compatibility¶
+cqlsh is compatible with Python 2.7.
+In general, a given version of cqlsh is only guaranteed to work with the 
version of Cassandra that it was released with.
+In some cases, cqlsh make work with older or newer versions of Cassandra, but 
this is not officially supported.
+
+
+Optional Dependencies¶
+cqlsh ships with all essential dependencies.  However, there are some 
optional dependencies that can be installed to
+improve the capabilities of cqlsh.
+
+pytz¶
+By default, cqlsh displays all timestamps with a UTC timezone.  To support 
display of timestamps with another timezone,
+the http://pytz.sourceforge.net/;>pytz 
library must be installed.  See the timezone option in cqlshrc for
+specifying a timezone to use.
+
+
+cython¶
+The performance of cqlshs COPY operations can be improved by installing http://cython.org/;>cython.  This will
+compile the python modules that are central to the performance of COPY.
+
+
+
+cqlshrc¶
+The cqlshrc 
file holds configuration options for cqlsh.  By default this is in the 
users home directory at
+~/.cassandra/cqlsh, but a custom location can be 
specified with the --cqlshrc option.
+Example config values and documentation can be found in the conf/cqlshrc.sample 
file of a tarball installation.  You
+can also view the latest version of https://github.com/apache/cassandra/blob/trunk/conf/cqlshrc.sample;>cqlshrc
 online.
+
+
+Command Line Options¶
+Usage:
+cqlsh [options] [host [port]]
+Options:
+
+-C --color
+Force color output
+--no-color
+Disable color output
+--browser
+Specify the browser to use for displaying cqlsh help.  This can be one of 
the https://docs.python.org/2/library/webbrowser.html;>supported browser 
names (e.g. firefox) or a browser path followed by %s (e.g.
+/usr/bin/google-chrome-stable %s).
+--ssl
+Use SSL when connecting to Cassandra
+-u --user
+Username to authenticate against Cassandra with
+-p --password
+Password to authenticate against Cassandra with, should
+be used in conjunction with --user
+-k --keyspace
+Keyspace to authenticate to, should be used in conjunction
+with --user
+-f --file
+Execute commands from the 

svn commit: r1757435 [18/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/getting_started/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/getting_started/index.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/getting_started/index.html (added)
+++ cassandra/site/publish/doc/3.10/getting_started/index.html Tue Aug 23 
20:58:08 2016
@@ -0,0 +1,293 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/getting_started/;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+  
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+
+  
+  Getting Started
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Installing Cassandra
+Configuring Cassandra
+Inserting and querying
+Client drivers
+
+
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Getting Started¶
+This section covers how to get started using Apache Cassandra and should be 
the first thing to read if you are new to
+Cassandra.
+
+
+Installing Cassandra
+Prerequisites
+Installation from 
binary tarball files
+Installation from 
Debian packages
+
+
+Configuring Cassandra
+Main runtime properties
+Changing the 
location of directories
+Environment variables
+Logging
+
+
+Inserting and querying
+CQLSH
+Client drivers
+
+
+Client drivers
+Java
+Python
+Ruby
+C# / .NET
+Nodejs
+PHP
+C++
+Scala
+Clojure
+Erlang
+Go
+Haskell
+Rust
+
+
+
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ 
Previous
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+  
+
+  
+https://twitter.com/cassandra;
+   class="twitter-follow-button"
+   data-show-count="false" data-size="large">Follow @cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+https://twitter.com/intent/tweet?button_hashtag=cassandra;
+   class="twitter-hashtag-button"
+   data-size="large"
+   data-related="ApacheCassandra">Tweet #cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+  
+
+
+
+   2016 http://apache.org;>The Apache Software 
Foundation.
+  Apache, the Apache feather logo, and Apache Cassandra are trademarks of 
The Apache Software Foundation.
+  
+
+  
+
+
+
+https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js";>
+
+https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js"; 
integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS"
 crossorigin="anonymous">
+
+
+
+
+
+  var DOCUMENTATION_OPTIONS = { URL_ROOT:
"", VERSION: "", COLLAPSE_INDEX: false, FILE_SUFFIX: ".html", HAS_SOURCE:  
false, SOURCELINK_SUFFIX: "" };  
+
+
+$(function() {
+// Stick the #nav to the top of the window
+var nav = $('.doc-navigation');
+var navHomeY = nav.offset().top;
+var isFixed = 

svn commit: r1757435 [7/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operatin

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/definitions.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/definitions.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/definitions.html (added)
+++ cassandra/site/publish/doc/3.10/cql/definitions.html Tue Aug 23 20:58:08 
2016
@@ -0,0 +1,458 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/definitions.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+  Definitions
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Conventions
+Identifiers and keywords
+Constants
+Terms
+Comments
+Statements
+Prepared Statements
+
+
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Definitions¶
+
+Conventions¶
+To aid in specifying the CQL syntax, we will use the following conventions 
in this document:
+
+Language rules will be given in an informal http://en.wikipedia.org/wiki/Backus%E2%80%93Naur_Form#Variants;>BNF 
variant notation. In particular, well use square brakets
+([ item ]) for optional items, 
* and + for repeated items 
(where + imply 
at least one).
+The grammar will also use the following convention for convenience: 
non-terminal term will be lowercase (and link to
+their definition) while terminal keywords will be provided all 
caps. Note however that keywords are
+Identifiers and keywords and are thus case insensitive in 
practice. We will also define some early construction using
+regexp, which well indicate with re(some regular expression).
+The grammar is provided for documentation purposes and leave some minor 
details out.  For instance, the comma on the
+last column definition in a CREATE TABLE statement is 
optional but supported if present even though the grammar in
+this document suggests otherwise. Also, not everything accepted by the grammar 
is necessarily valid CQL.
+References to keywords or pieces of CQL code in running text will be shown 
in a fixed-width font.
+
+
+
+Identifiers and keywords¶
+The CQL language uses identifiers (or names) to identify 
tables, columns and other objects. An identifier is a token
+matching the regular expression [a-zA-Z][a-zA-Z0-9_]*.
+A number of such identifiers, like SELECT or WITH, are keywords. They have a fixed 
meaning for the language
+and most are reserved. The list of those keywords can be found in Appendix A: CQL Keywords.
+Identifiers and (unquoted) keywords are case insensitive. Thus SELECT is the same 
than select or 
sElEcT, and
+myId is the 
same than myid 
or MYID. A 
convention often used (in particular by the samples of this
+documentation) is to use upper case for keywords and lower case for other 
identifiers.
+There is a second kind of identifiers called quoted identifiers 
defined by enclosing an arbitrary sequence of
+characters (non empty) in double-quotes(). Quoted identifiers are never keywords. Thus 
select is not a
+reserved keyword and can be used to refer to a column (note that using this is 
particularly advised), while select
+would raise a parsing error. Also, 

svn commit: r1757435 [3/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operatin

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/configuration/cassandra_config_file.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/configuration/cassandra_config_file.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/configuration/cassandra_config_file.html 
(added)
+++ cassandra/site/publish/doc/3.10/configuration/cassandra_config_file.html 
Tue Aug 23 20:58:08 2016
@@ -0,0 +1,1867 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/configuration/cassandra_config_file.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  Configuring Cassandra
+  
+
+  
+  Cassandra Configuration File
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Cassandra Configuration File
+cluster_name
+num_tokens
+allocate_tokens_for_keyspace
+initial_token
+hinted_handoff_enabled
+hinted_handoff_disabled_datacenters
+max_hint_window_in_ms
+hinted_handoff_throttle_in_kb
+max_hints_delivery_threads
+hints_directory
+hints_flush_period_in_ms
+max_hints_file_size_in_mb
+hints_compression
+batchlog_replay_throttle_in_kb
+authenticator
+authorizer
+role_manager
+roles_validity_in_ms
+roles_update_interval_in_ms
+permissions_validity_in_ms
+permissions_update_interval_in_ms
+credentials_validity_in_ms
+credentials_update_interval_in_ms
+partitioner
+data_file_directories
+commitlog_directory
+cdc_enabled
+cdc_raw_directory
+disk_failure_policy
+commit_failure_policy
+prepared_statements_cache_size_mb
+thrift_prepared_statements_cache_size_mb
+key_cache_size_in_mb
+key_cache_save_period
+key_cache_keys_to_save
+row_cache_class_name
+row_cache_size_in_mb
+row_cache_save_period
+row_cache_keys_to_save
+counter_cache_size_in_mb
+counter_cache_save_period
+counter_cache_keys_to_save
+saved_caches_directory
+commitlog_sync
+commitlog_sync_batch_window_in_ms
+commitlog_sync
+commitlog_sync_period_in_ms
+commitlog_segment_size_in_mb
+commitlog_compression
+seed_provider
+concurrent_reads
+concurrent_writes
+concurrent_counter_writes
+concurrent_materialized_view_writes
+file_cache_size_in_mb
+buffer_pool_use_heap_if_exhausted
+disk_optimization_strategy
+memtable_heap_space_in_mb
+memtable_offheap_space_in_mb
+memtable_cleanup_threshold
+memtable_allocation_type
+commitlog_total_space_in_mb
+memtable_flush_writers
+cdc_total_space_in_mb
+cdc_free_space_check_interval_ms
+index_summary_capacity_in_mb
+index_summary_resize_interval_in_minutes
+trickle_fsync
+trickle_fsync_interval_in_kb
+storage_port
+ssl_storage_port
+listen_address
+listen_interface
+listen_interface_prefer_ipv6
+broadcast_address
+listen_on_broadcast_address
+internode_authenticator
+start_native_transport
+native_transport_port
+native_transport_port_ssl
+native_transport_max_threads
+native_transport_max_frame_size_in_mb
+native_transport_max_concurrent_connections
+native_transport_max_concurrent_connections_per_ip
+start_rpc
+rpc_address
+rpc_interface
+rpc_interface_prefer_ipv6
+rpc_port
+broadcast_rpc_address
+rpc_keepalive
+rpc_server_type
+rpc_min_threads
+rpc_max_threads
+rpc_send_buff_size_in_bytes
+rpc_recv_buff_size_in_bytes
+internode_send_buff_size_in_bytes
+internode_recv_buff_size_in_bytes
+thrift_framed_transport_size_in_mb
+incremental_backups
+snapshot_before_compaction
+auto_snapshot
+column_index_size_in_kb
+column_index_cache_size_in_kb
+concurrent_compactors
+compaction_throughput_mb_per_sec
+sstable_preemptive_open_interval_in_mb
+stream_throughput_outbound_megabits_per_sec

svn commit: r1757435 [13/30] - in /cassandra/site/publish/doc: 3.10/ 3.10/architecture/ 3.10/configuration/ 3.10/cql/ 3.10/data_modeling/ 3.10/development/ 3.10/faq/ 3.10/getting_started/ 3.10/operati

[tylerhobbs]

Added: cassandra/site/publish/doc/3.10/cql/triggers.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/publish/doc/3.10/cql/triggers.html?rev=1757435=auto
==
--- cassandra/site/publish/doc/3.10/cql/triggers.html (added)
+++ cassandra/site/publish/doc/3.10/cql/triggers.html Tue Aug 23 20:58:08 2016
@@ -0,0 +1,299 @@
+
+
+  
+
+
+
+
+  
+  
+  
+  
+  
+  
+
+
+  Documentation
+
+  http://cassandra.apache.org/doc/3.10/cql/triggers.html;>
+
+  https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css; 
integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7"
 crossorigin="anonymous">
+  
+  
+  
+  
+
+   
+
+
+  
+
+
+  
+
+  
+
+  
+  Apache Software Foundation 
+  
+http://www.apache.org;>Apache Homepage
+http://www.apache.org/licenses/;>License
+http://www.apache.org/foundation/sponsorship.html;>Sponsorship
+http://www.apache.org/foundation/thanks.html;>Thanks
+http://www.apache.org/security/;>Security
+  
+
+  
+
+  
+  Apache Cassandra
+  
+
+  
+
+Documentation
+
+  
+
+  
+  The Cassandra Query Language (CQL)
+  
+
+  
+  Triggers
+  
+
+  
+
+  
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+
+  
+
+  
+
+  Home
+  Download
+  Documentation
+  Community
+
+  
+
+  
+
+  
+
+
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+CREATE TRIGGER
+DROP 
TRIGGER
+
+
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Triggers¶
+Triggers are identified by a name defined by:
+
+trigger_name ::=  identifier
+
+
+CREATE TRIGGER¶
+Creating a new trigger uses the CREATE TRIGGER statement:
+
+create_trigger_statement 
::=  CREATE TRIGGER [ IF NOT EXISTS ] trigger_name
+  ON table_name
+  USING string
+
+For instance:
+CREATE TRIGGER myTrigger ON myTable USING org.apache.cassandra.triggers.InvertedIndex;
+
+
+The actual logic that makes up the trigger can be written in any Java (JVM) 
language and exists outside the database.
+You place the trigger code in a lib/triggers subdirectory of the Cassandra 
installation directory, it loads during
+cluster startup, and exists on every node that participates in a cluster. The 
trigger defined on a table fires before a
+requested DML statement occurs, which ensures the atomicity of the 
transaction.
+
+
+DROP TRIGGER¶
+Dropping a trigger uses the DROP TRIGGER statement:
+
+drop_trigger_statement ::=  
DROP TRIGGER [ IF EXISTS ] trigger_name ON table_name
+
+For instance:
+DROP TRIGGER myTrigger ON myTable;
+
+
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ Previous
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+  
+
+  
+https://twitter.com/cassandra;
+   class="twitter-follow-button"
+   data-show-count="false" data-size="large">Follow @cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+https://twitter.com/intent/tweet?button_hashtag=cassandra;
+   class="twitter-hashtag-button"
+   data-size="large"
+   data-related="ApacheCassandra">Tweet #cassandra
+!function(d,s,id){var 
js,fjs=d.getElementsByTagName(s)[0],p=/^http:/.test(d.location)?'http':'https';if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src=p+'://platform.twitter.com/widgets.js';fjs.parentNode.insertBefore(js,fjs);}}(document,
 'script', 'twitter-wjs');
+  
+
+
+
+   2016 http://apache.org;>The Apache Software 
Foundation.
+  Apache, the Apache feather logo, and Apache 

[jira] [Updated] (CASSANDRA-5342) ancestors are not cleared in SSTableMetadata after compactions are done and old SSTables are removed

[Wei Deng (JIRA)]

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

Wei Deng updated CASSANDRA-5342:

Labels: lcs  (was: )

> ancestors are not cleared in SSTableMetadata after compactions are done and 
> old SSTables are removed
> 
>
> Key: CASSANDRA-5342
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5342
> Project: Cassandra
>  Issue Type: Bug
>Affects Versions: 1.1.3
>Reporter: Wei Zhu
>Assignee: Marcus Eriksson
>  Labels: lcs
> Fix For: 1.2.7
>
> Attachments: 0001-CASSANDRA-5342-wip-v2.patch, 
> 0001-CASSANDRA-5342-wip.patch, Screen Shot 2013-03-13 at 12.05.08 PM.png
>
>
> We are using LCS and have total of 38000 SSTables for one CF. During LCS, 
> there could be over a thousand SSTable involved. All those SSTable IDs are 
> stored in ancestors field of SSTableMetatdata for the new table. In our case, 
> it consumes more than 1G of heap memory for those field. Put it in 
> perspective, the ancestors consume 2 - 3 times more memory than bloomfilter 
> (fp = 0.1 by default) in LCS. 
> We should remove those ancestors from SSTableMetadata after the compaction is 
> finished and the old SSTable is removed. It  might be a big deal for Sized 
> Compaction since there are small number of SSTable involved. But it consumes 
> a lot of memory for LCS. 
> At least, we shouldn't load those ancestors to the memory during startup if 
> the files are removed. 
> I would love to contribute and provide patch. Please let me know how to 
> start. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12034) Special handling for Netty's direct memory allocation failure

[Robert Stupp (JIRA)]

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

Robert Stupp commented on CASSANDRA-12034:
--

[~tjake] can you take a look at the merge up to 3.9 & trunk?

> Special handling for Netty's direct memory allocation failure
> -
>
> Key: CASSANDRA-12034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12034
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Robert Stupp
>Assignee: Robert Stupp
>  Labels: doc-impacting
> Fix For: 3.8
>
>
> With CASSANDRA-12032, Netty throws a 
> {{io.netty.util.internal.OutOfDirectMemoryError}} if there's not enough 
> off-heap memory for the response buffer. We can easily handle this situation 
> and return an error. This is not a condition that destabilizes the system and 
> should therefore not passed to {{JVMStabilityInspector}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12523) dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test

[Joel Knighton (JIRA)]

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

Joel Knighton commented on CASSANDRA-12523:
---

I'll kick off a multiplexer run for that PR, and I'm +1 to closing this if that 
shows no problems and the PR is merged. Thanks!

> dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test
> --
>
> Key: CASSANDRA-12523
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12523
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>  Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, 
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/view/cassandra-3.9/job/cassandra-3.9_dtest/46/testReport/junit/upgrade_internal_auth_test/TestAuthUpgrade/upgrade_to_30_test/
> Failed on CassCI build cassandra-3.9_dtest #46
> Relevant error in logs is
> {code}
> Unexpected error in node2 log, error: 
> ERROR [SharedPool-Worker-1] 2016-08-22 17:35:31,108 Message.java:617 - 
> Unexpected exception during request; channel = [id: 0x603c4ef1, 
> /127.0.0.1:46357 => /127.0.0.2:9042]
> java.lang.RuntimeException: 
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - 
> received only 0 responses.
>   at 
> org.apache.cassandra.auth.CassandraRoleManager.getRole(CassandraRoleManager.java:489)
>  ~[main/:na]
>   at 
> org.apache.cassandra.auth.CassandraRoleManager.canLogin(CassandraRoleManager.java:298)
>  ~[main/:na]
>   at org.apache.cassandra.service.ClientState.login(ClientState.java:270) 
> ~[main/:na]
>   at 
> org.apache.cassandra.transport.messages.AuthResponse.execute(AuthResponse.java:79)
>  ~[main/:na]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:513)
>  [main/:na]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:407)
>  [main/:na]
>   at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:333)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext.access$700(AbstractChannelHandlerContext.java:32)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext$8.run(AbstractChannelHandlerContext.java:324)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_45]
>   at 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
>  [main/:na]
>   at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) 
> [main/:na]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45]
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation 
> timed out - received only 0 responses.
>   at 
> org.apache.cassandra.service.ReadCallback.awaitResults(ReadCallback.java:132) 
> ~[main/:na]
>   at org.apache.cassandra.service.ReadCallback.get(ReadCallback.java:137) 
> ~[main/:na]
>   at 
> org.apache.cassandra.service.AbstractReadExecutor.get(AbstractReadExecutor.java:145)
>  ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.awaitResultsAndRetryOnDigestMismatch(StorageProxy.java:1715)
>  ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1664) 
> ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1605) 
> ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1524) 
> ~[main/:na]
>   at 
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:954)
>  ~[main/:na]
>   at 
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:263)
>  ~[main/:na]
>   at 
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:224)
>  ~[main/:na]
>   at 
> org.apache.cassandra.auth.CassandraRoleManager.getRoleFromTable(CassandraRoleManager.java:497)
>  ~[main/:na]
>   at 
> org.apache.cassandra.auth.CassandraRoleManager.getRole(CassandraRoleManager.java:484)
>  ~[main/:na]
>   ... 13 common frames omitted
> {code}
> Note: this is unrelated to CASSANDRA-12518



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12523) dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test

[Sam Tunnicliffe (JIRA)]

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

Sam Tunnicliffe commented on CASSANDRA-12523:
-

Ok, makes sense. I've opened a [dtest 
pr|https://github.com/riptano/cassandra-dtest/pull/1272] with that change to 
the test. The test functionality itself seems unimpaired, so seeing as this is 
the only recorded occurrence of this failure unless there's any objection, I'm 
tempted to resolve this issue if/when that PR is merged. We can re-open if it 
happens again after

> dtest failure in upgrade_internal_auth_test.TestAuthUpgrade.upgrade_to_30_test
> --
>
> Key: CASSANDRA-12523
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12523
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Sam Tunnicliffe
>Assignee: Sam Tunnicliffe
>  Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log, node2.log, 
> node2_debug.log, node2_gc.log, node3.log, node3_debug.log, node3_gc.log
>
>
> example failure:
> http://cassci.datastax.com/view/cassandra-3.9/job/cassandra-3.9_dtest/46/testReport/junit/upgrade_internal_auth_test/TestAuthUpgrade/upgrade_to_30_test/
> Failed on CassCI build cassandra-3.9_dtest #46
> Relevant error in logs is
> {code}
> Unexpected error in node2 log, error: 
> ERROR [SharedPool-Worker-1] 2016-08-22 17:35:31,108 Message.java:617 - 
> Unexpected exception during request; channel = [id: 0x603c4ef1, 
> /127.0.0.1:46357 => /127.0.0.2:9042]
> java.lang.RuntimeException: 
> org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - 
> received only 0 responses.
>   at 
> org.apache.cassandra.auth.CassandraRoleManager.getRole(CassandraRoleManager.java:489)
>  ~[main/:na]
>   at 
> org.apache.cassandra.auth.CassandraRoleManager.canLogin(CassandraRoleManager.java:298)
>  ~[main/:na]
>   at org.apache.cassandra.service.ClientState.login(ClientState.java:270) 
> ~[main/:na]
>   at 
> org.apache.cassandra.transport.messages.AuthResponse.execute(AuthResponse.java:79)
>  ~[main/:na]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:513)
>  [main/:na]
>   at 
> org.apache.cassandra.transport.Message$Dispatcher.channelRead0(Message.java:407)
>  [main/:na]
>   at 
> io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:333)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext.access$700(AbstractChannelHandlerContext.java:32)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> io.netty.channel.AbstractChannelHandlerContext$8.run(AbstractChannelHandlerContext.java:324)
>  [netty-all-4.0.23.Final.jar:4.0.23.Final]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [na:1.8.0_45]
>   at 
> org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:164)
>  [main/:na]
>   at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) 
> [main/:na]
>   at java.lang.Thread.run(Thread.java:745) [na:1.8.0_45]
> Caused by: org.apache.cassandra.exceptions.ReadTimeoutException: Operation 
> timed out - received only 0 responses.
>   at 
> org.apache.cassandra.service.ReadCallback.awaitResults(ReadCallback.java:132) 
> ~[main/:na]
>   at org.apache.cassandra.service.ReadCallback.get(ReadCallback.java:137) 
> ~[main/:na]
>   at 
> org.apache.cassandra.service.AbstractReadExecutor.get(AbstractReadExecutor.java:145)
>  ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy$SinglePartitionReadLifecycle.awaitResultsAndRetryOnDigestMismatch(StorageProxy.java:1715)
>  ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy.fetchRows(StorageProxy.java:1664) 
> ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy.readRegular(StorageProxy.java:1605) 
> ~[main/:na]
>   at 
> org.apache.cassandra.service.StorageProxy.read(StorageProxy.java:1524) 
> ~[main/:na]
>   at 
> org.apache.cassandra.db.SinglePartitionReadCommand$Group.execute(SinglePartitionReadCommand.java:954)
>  ~[main/:na]
>   at 
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:263)
>  ~[main/:na]
>   at 
> org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:224)
>  ~[main/:na]
>   at 
> org.apache.cassandra.auth.CassandraRoleManager.getRoleFromTable(CassandraRoleManager.java:497)
>  ~[main/:na]
>   at 
> 

[jira] [Updated] (CASSANDRA-12522) nodetool repair -pr and -local option rejected

[Paulo Motta (JIRA)]

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

Paulo Motta updated CASSANDRA-12522:

Status: Open  (was: Patch Available)

> nodetool repair -pr and -local option rejected
> --
>
> Key: CASSANDRA-12522
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12522
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: Jérôme Mainaud
> Fix For: 3.9
>
> Attachments: 12522-trunk.patch
>
>
> Repair command refuse to work with both -pr and -local on an 2.2.6 cluster.
> The message is  “You need to run primary range repair on all nodes in the 
> cluster”.
> The compatibility was introduiced in CASSANDRA-7450 but RepairOption 
> validation reject the case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12522) nodetool repair -pr and -local option rejected

[Paulo Motta (JIRA)]

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

Paulo Motta commented on CASSANDRA-12522:
-

The patch looks good, but it doesn't apply cleanly to 2.2. Can you provide a 
version for the cassandra-2.2 branch as well (and check if that merges to 
cassandra-3.0)? Thanks!

I think it shouldn't be a problem to call {{Database.daemonInitialization()}} 
on tests. I submitted a preliminary CI run with the trunk version:

||trunk||
|[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:trunk-12522]|
|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-12522-testall/lastCompletedBuild/testReport/]|
|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-12522-dtest/lastCompletedBuild/testReport/]|


> nodetool repair -pr and -local option rejected
> --
>
> Key: CASSANDRA-12522
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12522
> Project: Cassandra
>  Issue Type: Bug
>  Components: Tools
>Reporter: Jérôme Mainaud
> Fix For: 3.9
>
> Attachments: 12522-trunk.patch
>
>
> Repair command refuse to work with both -pr and -local on an 2.2.6 cluster.
> The message is  “You need to run primary range repair on all nodes in the 
> cluster”.
> The compatibility was introduiced in CASSANDRA-7450 but RepairOption 
> validation reject the case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

svn commit: r1757419 [15/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/cql/ddl.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/cql/ddl.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/cql/ddl.html (added)
+++ cassandra/site/src/doc/3.10/cql/ddl.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,826 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "The Cassandra Query Language (CQL)"
+
+doc-title: "Data Definition"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data Definition
+Common definitions
+CREATE KEYSPACE
+USE
+ALTER KEYSPACE
+DROP KEYSPACE
+CREATE TABLE
+ALTER 
TABLE
+DROP 
TABLE
+TRUNCATE
+
+
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Data Definition¶
+CQL stores data in tables, whose schema defines the layout of said 
data in the table, and those tables are grouped in
+keyspaces. A keyspace defines a number of options that applies to all 
the tables it contains, most prominently of
+which is the replication strategy used by the keyspace. It is generally 
encouraged to use
+one keyspace by application, and thus many cluster may define only 
one keyspace.
+This section describes the statements used to create, modify, and remove 
those keyspace and tables.
+
+Common definitions¶
+The names of the keyspaces and tables are defined by the following 
grammar:
+
+keyspace_name ::=  name
+table_name::=  [ keyspace_name 
'.' ] name
+name  ::=  unquoted_name 
| quoted_name
+unquoted_name ::=  
re('[a-zA-Z_0-9]{1, 48}')
+quoted_name   ::=  '' unquoted_name 
''
+
+Both keyspace and table name should be comprised of only alphanumeric 
characters, cannot be empty and are limited in
+size to 48 characters (that limit exists mostly to avoid filenames (which may 
include the keyspace and table name) to go
+over the limits of certain file systems). By default, keyspace and table names 
are case insensitive (myTable is
+equivalent to mytable) but case sensitivity can be forced by using 
double-quotes (myTable is different from
+mytable).
+Further, a table is always part of a keyspace and a table name can be 
provided fully-qualified by the keyspace it is
+part of. If is is not fully-qualified, the table is assumed to be in the 
current keyspace (see USE statement).
+Further, the valid names for columns is simply defined as:
+
+column_name ::=  identifier
+
+We also define the notion of statement options for use in the following 
section:
+
+options ::=  option ( AND option )*
+option  ::=  identifier '=' ( identifier | constant | map_literal )
+
+
+
+CREATE KEYSPACE¶
+A keyspace is created using a CREATE KEYSPACE 
statement:
+
+create_keyspace_statement 
::=  CREATE KEYSPACE [ IF NOT EXISTS ] keyspace_name WITH options
+
+For instance:
+CREATE KEYSPACE Excelsior
+   WITH replication 
= {class: SimpleStrategy, replication_factor : 3};
+
+CREATE KEYSPACE Excalibur
+   WITH replication 
= {class: NetworkTopologyStrategy, 
DC1 : 1, DC2 : 3}
+AND durable_writes 
= false;
+
+
+The supported options are:
+
+
+
+
+
+
+
+
+
+name
+kind
+mandatory
+default
+description
+
+
+
+replication
+map
+yes
+
+The replication strategy and options to use for the keyspace (see
+details below).
+
+durable_writes
+simple
+no
+true
+Whether to use the commit log for updates on this keyspace
+(disable this option at your own risk!).
+
+
+
+The replication property is mandatory and must at least 
contains the 'class' sub-option which defines the
+replication strategy class to use. The rest of the 
sub-options depends on what replication
+strategy is used. By default, Cassandra support the following 'class':
+
+'SimpleStrategy': A simple strategy that defines a 
replication factor for the whole cluster. The only sub-options
+supported is 'replication_factor' to define that replication 
factor and is 

svn commit: r1757419 [25/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/operating/compression.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/operating/compression.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/operating/compression.html (added)
+++ cassandra/site/src/doc/3.10/operating/compression.html Tue Aug 23 19:25:17 
2016
@@ -0,0 +1,189 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "Operating Cassandra"
+
+doc-title: "Compression"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Compression
+Configuring Compression
+Benefits and Uses
+Operational Impact
+Advanced Use
+
+
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Security
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Compression¶
+Cassandra offers operators the ability to configure compression on a 
per-table basis. Compression reduces the size of
+data on disk by compressing the SSTable in user-configurable compression chunk_length_in_kb. 
Because Cassandra
+SSTables are immutable, the CPU cost of compressing is only necessary when the 
SSTable is written - subsequent updates
+to data will land in different SSTables, so Cassandra will not need to 
decompress, overwrite, and recompress data when
+UPDATE commands are issued. On reads, Cassandra will locate the relevant 
compressed chunks on disk, decompress the full
+chunk, and then proceed with the remainder of the read path (merging data from 
disks and memtables, read repair, and so
+on).
+
+Configuring Compression¶
+Compression is configured on a per-table basis as an optional argument to 
CREATE TABLE or ALTER TABLE. By
+default, three options are relevant:
+
+class 
specifies the compression class - Cassandra provides three classes (LZ4Compressor,
+SnappyCompressor, and DeflateCompressor ). The default is 
SnappyCompressor.
+chunk_length_in_kb specifies the number of kilobytes 
of data per compression chunk. The default is 64KB.
+crc_check_chance determines how likely Cassandra is 
to verify the checksum on each compression chunk during
+reads. The default is 1.0.
+
+Users can set compression using the following syntax:
+CREATE 
TABLE keyspace.table (id int PRIMARY KEY) WITH compression = {class: 
LZ4Compressor};
+
+
+Or
+ALTER 
TABLE keyspace.table WITH compression = {class: 
SnappyCompressor, chunk_length_in_kb: 128, 
crc_check_chance: 0.5};
+
+
+Once enabled, compression can be disabled with ALTER TABLE 
setting enabled 
to false:
+ALTER 
TABLE keyspace.table WITH compression = {enabled:false};
+
+
+Operators should be aware, however, that changing compression is not 
immediate. The data is compressed when the SSTable
+is written, and as SSTables are immutable, the compression will not be 
modified until the table is compacted. Upon
+issuing a change to the compression options via ALTER TABLE, 
the existing SSTables will not be modified until they
+are compacted - if an operator needs compression changes to take effect 
immediately, the operator can trigger an SSTable
+rewrite using nodetool 
scrub or nodetool upgradesstables -a, both of which will rebuild the SSTables on disk,
+re-compressing the data in the process.
+
+
+Benefits and Uses¶
+Compressions primary benefit is that it reduces the amount of data 
written to disk. Not only does the reduced size save
+in storage requirements, it often increases read and write throughput, as the 
CPU overhead of compressing data is faster
+than the time it would take to read or write the larger volume of uncompressed 
data from disk.
+Compression is most useful in tables comprised of many rows, where the rows 
are similar in nature. Tables containing
+similar text columns (such as repeated JSON blobs) often compress very 
well.
+
+
+Operational Impact¶
+
+Compression metadata is stored off-heap and scales with data on disk.  
This often requires 

svn commit: r1757419 [19/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/cql/indexes.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/cql/indexes.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/cql/indexes.html (added)
+++ cassandra/site/src/doc/3.10/cql/indexes.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,170 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "The Cassandra Query Language (CQL)"
+
+doc-title: "Secondary Indexes"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+CREATE INDEX
+DROP 
INDEX
+
+
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Secondary Indexes¶
+CQL supports creating secondary indexes on tables, allowing queries on the 
table to use those indexes. A secondary index
+is identified by a name defined by:
+
+index_name ::=  
re('[a-zA-Z_0-9]+')
+
+
+CREATE INDEX¶
+Creating a secondary index on a table uses the CREATE INDEX 
statement:
+
+create_index_statement ::=  
CREATE [ CUSTOM ] INDEX [ IF NOT EXISTS ] [ index_name ]
+ON table_name '(' index_identifier ')'
+[ USING string [ WITH OPTIONS = map_literal ] 
]
+index_identifier   
::=  column_name
+   | ( KEYS | VALUES | ENTRIES | FULL ) '(' column_name 
')'
+
+For instance:
+CREATE INDEX userIndex ON NerdMovies (user);
+CREATE INDEX ON Mutants (abilityId);
+CREATE INDEX ON users (keys(favs));
+CREATE CUSTOM INDEX ON users 
(email) 
USING path.to.the.IndexClass;
+CREATE CUSTOM INDEX ON users 
(email) 
USING path.to.the.IndexClass WITH 
OPTIONS = {storage: /mnt/ssd/indexes/};
+
+
+The CREATE INDEX statement is used to create a new (automatic) 
secondary index for a given (existing) column in a
+given table. A name for the index itself can be specified before the ON keyword, if 
desired. If data already exists
+for the column, it will be indexed asynchronously. After the index is created, 
new data for the column is indexed
+automatically at insertion time.
+Attempting to create an already existing index will return an error unless 
the IF NOT EXISTS option is used. 
If it
+is used, the statement will be a no-op if the index already exists.
+
+Indexes on Map Keys¶
+When creating an index on a maps, you may index 
either the keys or the values. If the column identifier is
+placed within the keys() function, the index will be on the map keys, 
allowing you to use CONTAINS KEY in
+WHERE clauses. 
Otherwise, the index will be on the map values.
+
+
+
+DROP INDEX¶
+Dropping a secondary index uses the DROP INDEX statement:
+
+drop_index_statement 
::=  DROP INDEX [ IF EXISTS ] index_name
+
+The DROP INDEX statement is used to drop an existing secondary 
index. The argument of the statement is the index
+name, which may optionally specify the keyspace of the index.
+If the index does not exists, the statement will return an error, unless 
IF EXISTS is used in which case the
+operation is a no-op.
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ Previous
+
+  
+  
+
+  
+
+
+
+  
+
\ No newline at end of file

Added: cassandra/site/src/doc/3.10/cql/json.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/cql/json.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/cql/json.html (added)
+++ cassandra/site/src/doc/3.10/cql/json.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,317 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "The Cassandra Query Language (CQL)"
+
+doc-title: "JSON Support"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+

svn commit: r1757419 [1/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling/

[tylerhobbs]

Author: tylerhobbs
Date: Tue Aug 23 19:25:17 2016
New Revision: 1757419

URL: http://svn.apache.org/viewvc?rev=1757419=rev
Log:
Add docs for 3.10

Added:
cassandra/site/src/doc/3.10/
cassandra/site/src/doc/3.10/.buildinfo
cassandra/site/src/doc/3.10/_images/
cassandra/site/src/doc/3.10/_images/eclipse_debug0.png
cassandra/site/src/doc/3.10/_images/eclipse_debug1.png
cassandra/site/src/doc/3.10/_images/eclipse_debug2.png
cassandra/site/src/doc/3.10/_images/eclipse_debug3.png
cassandra/site/src/doc/3.10/_images/eclipse_debug4.png
cassandra/site/src/doc/3.10/_images/eclipse_debug5.png
cassandra/site/src/doc/3.10/_images/eclipse_debug6.png
cassandra/site/src/doc/3.10/_sources/
cassandra/site/src/doc/3.10/_sources/architecture/
cassandra/site/src/doc/3.10/_sources/architecture/dynamo.txt
cassandra/site/src/doc/3.10/_sources/architecture/guarantees.txt
cassandra/site/src/doc/3.10/_sources/architecture/index.txt
cassandra/site/src/doc/3.10/_sources/architecture/overview.txt
cassandra/site/src/doc/3.10/_sources/architecture/storage_engine.txt
cassandra/site/src/doc/3.10/_sources/bugs.txt
cassandra/site/src/doc/3.10/_sources/configuration/
cassandra/site/src/doc/3.10/_sources/configuration/cassandra_config_file.txt
cassandra/site/src/doc/3.10/_sources/configuration/index.txt
cassandra/site/src/doc/3.10/_sources/contactus.txt
cassandra/site/src/doc/3.10/_sources/cql/
cassandra/site/src/doc/3.10/_sources/cql/appendices.txt
cassandra/site/src/doc/3.10/_sources/cql/changes.txt
cassandra/site/src/doc/3.10/_sources/cql/ddl.txt
cassandra/site/src/doc/3.10/_sources/cql/definitions.txt
cassandra/site/src/doc/3.10/_sources/cql/dml.txt
cassandra/site/src/doc/3.10/_sources/cql/functions.txt
cassandra/site/src/doc/3.10/_sources/cql/index.txt
cassandra/site/src/doc/3.10/_sources/cql/indexes.txt
cassandra/site/src/doc/3.10/_sources/cql/json.txt
cassandra/site/src/doc/3.10/_sources/cql/mvs.txt
cassandra/site/src/doc/3.10/_sources/cql/security.txt
cassandra/site/src/doc/3.10/_sources/cql/triggers.txt
cassandra/site/src/doc/3.10/_sources/cql/types.txt
cassandra/site/src/doc/3.10/_sources/data_modeling/
cassandra/site/src/doc/3.10/_sources/data_modeling/index.txt
cassandra/site/src/doc/3.10/_sources/development/
cassandra/site/src/doc/3.10/_sources/development/code_style.txt
cassandra/site/src/doc/3.10/_sources/development/how_to_commit.txt
cassandra/site/src/doc/3.10/_sources/development/how_to_review.txt
cassandra/site/src/doc/3.10/_sources/development/ide.txt
cassandra/site/src/doc/3.10/_sources/development/index.txt
cassandra/site/src/doc/3.10/_sources/development/patches.txt
cassandra/site/src/doc/3.10/_sources/development/testing.txt
cassandra/site/src/doc/3.10/_sources/faq/
cassandra/site/src/doc/3.10/_sources/faq/index.txt
cassandra/site/src/doc/3.10/_sources/getting_started/
cassandra/site/src/doc/3.10/_sources/getting_started/configuring.txt
cassandra/site/src/doc/3.10/_sources/getting_started/drivers.txt
cassandra/site/src/doc/3.10/_sources/getting_started/index.txt
cassandra/site/src/doc/3.10/_sources/getting_started/installing.txt
cassandra/site/src/doc/3.10/_sources/getting_started/querying.txt
cassandra/site/src/doc/3.10/_sources/index.txt
cassandra/site/src/doc/3.10/_sources/operating/
cassandra/site/src/doc/3.10/_sources/operating/backups.txt
cassandra/site/src/doc/3.10/_sources/operating/bloom_filters.txt
cassandra/site/src/doc/3.10/_sources/operating/bulk_loading.txt
cassandra/site/src/doc/3.10/_sources/operating/cdc.txt
cassandra/site/src/doc/3.10/_sources/operating/compaction.txt
cassandra/site/src/doc/3.10/_sources/operating/compression.txt
cassandra/site/src/doc/3.10/_sources/operating/hardware.txt
cassandra/site/src/doc/3.10/_sources/operating/hints.txt
cassandra/site/src/doc/3.10/_sources/operating/index.txt
cassandra/site/src/doc/3.10/_sources/operating/metrics.txt
cassandra/site/src/doc/3.10/_sources/operating/read_repair.txt
cassandra/site/src/doc/3.10/_sources/operating/repair.txt
cassandra/site/src/doc/3.10/_sources/operating/security.txt
cassandra/site/src/doc/3.10/_sources/operating/snitch.txt
cassandra/site/src/doc/3.10/_sources/operating/topo_changes.txt
cassandra/site/src/doc/3.10/_sources/tools/
cassandra/site/src/doc/3.10/_sources/tools/cqlsh.txt
cassandra/site/src/doc/3.10/_sources/tools/index.txt
cassandra/site/src/doc/3.10/_sources/tools/nodetool.txt
cassandra/site/src/doc/3.10/_sources/troubleshooting/
cassandra/site/src/doc/3.10/_sources/troubleshooting/index.txt
cassandra/site/src/doc/3.10/_static/
cassandra/site/src/doc/3.10/_static/ajax-loader.gif   (with props)
cassandra/site/src/doc/3.10/_static/basic.css
cassandra/site/src/doc/3.10/_static/comment-bright.png   (with 

svn commit: r1757419 [26/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/operating/metrics.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/operating/metrics.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/operating/metrics.html (added)
+++ cassandra/site/src/doc/3.10/operating/metrics.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,1714 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "Operating Cassandra"
+
+doc-title: "Monitoring"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Compression
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Metric Types
+Table Metrics
+Keyspace Metrics
+ThreadPool Metrics
+Client Request Metrics
+Cache Metrics
+CQL 
Metrics
+DroppedMessage Metrics
+Streaming Metrics
+Compaction Metrics
+CommitLog Metrics
+Storage Metrics
+HintedHandoff Metrics
+SSTable Index Metrics
+BufferPool Metrics
+Client Metrics
+JVM 
Metrics
+JMX
+Metric Reporters
+
+
+Security
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Monitoring¶
+Metrics in Cassandra are managed using the http://metrics.dropwizard.io;>Dropwizard Metrics library. These 
metrics
+can be queried via JMX or pushed to external monitoring systems using a number 
of http://metrics.dropwizard.io/3.1.0/getting-started/#other-reporting;>built
 in and http://metrics.dropwizard.io/3.1.0/manual/third-party/;>third party 
reporter plugins.
+Metrics are collected for a single node. Its up to the operator to 
use an external monitoring system to aggregate them.
+
+Metric Types¶
+All metrics reported by cassandra fit into one of the following types.
+
+Gauge
+An instantaneous measurement of a value.
+Counter
+A gauge for an AtomicLong instance. Typically this is consumed by 
monitoring the change since the last call to
+see if there is a large increase compared to the norm.
+Histogram
+Measures the statistical distribution of values in a 
stream of data.
+In addition to minimum, maximum, mean, etc., it also measures 
median, 75th, 90th, 95th, 98th, 99th, and 99.9th
+percentiles.
+
+Timer
+Measures both the rate that a particular piece of code is called and the 
histogram of its duration.
+Latency
+Special type that tracks latency (in microseconds) with a Timer plus a Counter that tracks 
the total latency
+accrued since starting. The former is useful if you track the change in total 
latency since the last check. Each
+metric name of this type will have Latency and 
TotalLatency appended to it.
+Meter
+A meter metric which measures mean throughput and one-, five-, and 
fifteen-minute exponentially-weighted moving
+average throughputs.
+
+
+
+Table Metrics¶
+Each table in Cassandra has metrics responsible for tracking its state and 
performance.
+The metric names are all appended with the specific Keyspace and Table name.
+Reported name format:
+
+Metric Name
+org.apache.cassandra.metrics.Table.MetricName.Keyspace.Table
+JMX MBean
+org.apache.cassandra.metrics:type=Table keyspace=Keyspace scope=Table name=MetricName
+
+
+Note
+There is a special table called all without a keyspace. This 
represents the aggregation of metrics across
+all tables and keyspaces on the node.
+
+
+
+
+
+
+
+
+Name
+Type
+Description
+
+
+
+MemtableOnHeapSize
+GaugeLong
+Total amount of data stored in the memtable that resides 
on-heap, including column related overhead and partitions 
overwritten.
+
+MemtableOffHeapSize
+GaugeLong
+Total amount of data stored in the memtable that resides 
off-heap, including column related overhead and partitions 
overwritten.
+
+MemtableLiveDataSize
+GaugeLong
+Total amount of live data stored in the memtable, excluding any data 
structure overhead.
+
+AllMemtablesOnHeapSize
+GaugeLong
+Total amount of data stored in the memtables (2i and pending flush 
memtables included) that resides on-heap.
+
+AllMemtablesOffHeapSize
+GaugeLong
+Total amount of 

svn commit: r1757419 [2/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling/

[tylerhobbs]

Added: 
cassandra/site/src/doc/3.10/_sources/configuration/cassandra_config_file.txt
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_sources/configuration/cassandra_config_file.txt?rev=1757419=auto
==
--- 
cassandra/site/src/doc/3.10/_sources/configuration/cassandra_config_file.txt 
(added)
+++ 
cassandra/site/src/doc/3.10/_sources/configuration/cassandra_config_file.txt 
Tue Aug 23 19:25:17 2016
@@ -0,0 +1,1792 @@
+.. _cassandra-yaml:
+
+Cassandra Configuration File
+
+
+``cluster_name``
+
+The name of the cluster. This is mainly used to prevent machines in
+one logical cluster from joining another.
+
+*Default Value:* 'Test Cluster'
+
+``num_tokens``
+--
+
+This defines the number of tokens randomly assigned to this node on the ring
+The more tokens, relative to other nodes, the larger the proportion of data
+that this node will store. You probably want all nodes to have the same number
+of tokens assuming they have equal hardware capability.
+
+If you leave this unspecified, Cassandra will use the default of 1 token for 
legacy compatibility,
+and will use the initial_token as described below.
+
+Specifying initial_token will override this setting on the node's initial 
start,
+on subsequent starts, this setting will apply even if initial token is set.
+
+If you already have a cluster with 1 token per node, and wish to migrate to 
+multiple tokens per node, see http://wiki.apache.org/cassandra/Operations
+
+*Default Value:* 256
+
+``allocate_tokens_for_keyspace``
+
+*This option is commented out by default.*
+
+Triggers automatic allocation of num_tokens tokens for this node. The 
allocation
+algorithm attempts to choose tokens in a way that optimizes replicated load 
over
+the nodes in the datacenter for the replication strategy used by the specified
+keyspace.
+
+The load assigned to each node will be close to proportional to its number of
+vnodes.
+
+Only supported with the Murmur3Partitioner.
+
+*Default Value:* KEYSPACE
+
+``initial_token``
+-
+*This option is commented out by default.*
+
+initial_token allows you to specify tokens manually.  While you can use it with
+vnodes (num_tokens > 1, above) -- in which case you should provide a 
+comma-separated list -- it's primarily used when adding nodes to legacy 
clusters 
+that do not have vnodes enabled.
+
+``hinted_handoff_enabled``
+--
+
+See http://wiki.apache.org/cassandra/HintedHandoff
+May either be "true" or "false" to enable globally
+
+*Default Value:* true
+
+``hinted_handoff_disabled_datacenters``
+---
+*This option is commented out by default.*
+
+When hinted_handoff_enabled is true, a black list of data centers that will not
+perform hinted handoff
+
+*Default Value (complex option)*::
+
+#- DC1
+#- DC2
+
+``max_hint_window_in_ms``
+-
+this defines the maximum amount of time a dead host will have hints
+generated.  After it has been dead this long, new hints for it will not be
+created until it has been seen alive and gone down again.
+
+*Default Value:* 1080 # 3 hours
+
+``hinted_handoff_throttle_in_kb``
+-
+
+Maximum throttle in KBs per second, per delivery thread.  This will be
+reduced proportionally to the number of nodes in the cluster.  (If there
+are two nodes in the cluster, each delivery thread will use the maximum
+rate; if there are three, each will throttle to half of the maximum,
+since we expect two nodes to be delivering hints simultaneously.)
+
+*Default Value:* 1024
+
+``max_hints_delivery_threads``
+--
+
+Number of threads with which to deliver hints;
+Consider increasing this number when you have multi-dc deployments, since
+cross-dc handoff tends to be slower
+
+*Default Value:* 2
+
+``hints_directory``
+---
+*This option is commented out by default.*
+
+Directory where Cassandra should store hints.
+If not set, the default directory is $CASSANDRA_HOME/data/hints.
+
+*Default Value:*  /var/lib/cassandra/hints
+
+``hints_flush_period_in_ms``
+
+
+How often hints should be flushed from the internal buffers to disk.
+Will *not* trigger fsync.
+
+*Default Value:* 1
+
+``max_hints_file_size_in_mb``
+-
+
+Maximum size for a single hints file, in megabytes.
+
+*Default Value:* 128
+
+``hints_compression``
+-
+*This option is commented out by default.*
+
+Compression to apply to the hint files. If omitted, hints files
+will be written uncompressed. LZ4, Snappy, and Deflate compressors
+are supported.
+
+*Default Value (complex option)*::
+
+#   - class_name: LZ4Compressor
+# parameters:
+# -
+
+``batchlog_replay_throttle_in_kb``

svn commit: r1757419 [10/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_static/jquery.js
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_static/jquery.js?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_static/jquery.js (added)
+++ cassandra/site/src/doc/3.10/_static/jquery.js Tue Aug 23 19:25:17 2016
@@ -0,0 +1,4 @@
+/*! jQuery v1.11.1 | (c) 2005, 2014 jQuery Foundation, Inc. | 
jquery.org/license */
+!function(a,b){"object"==typeof module&&"object"==typeof 
module.exports?module.exports=a.document?b(a,!0):function(a){if(!a.document)throw
 new Error("jQuery requires a window with a document");return 
b(a)}:b(a)}("undefined"!=typeof window?window:this,function(a,b){var 
c=[],d=c.slice,e=c.concat,f=c.push,g=c.indexOf,h={},i=h.toString,j=h.hasOwnProperty,k={},l="1.11.1",m=function(a,b){return
 new 
m.fn.init(a,b)},n=/^[\s\uFEFF\xA0]+|[\s\uFEFF\xA0]+$/g,o=/^-ms-/,p=/-([\da-z])/gi,q=function(a,b){return
 
b.toUpperCase()};m.fn=m.prototype={jquery:l,constructor:m,selector:"",length:0,toArray:function(){return
 d.call(this)},get:function(a){return 
null!=a?0>a?this[a+this.length]:this[a]:d.call(this)},pushStack:function(a){var 
b=m.merge(this.constructor(),a);return 
b.prevObject=this,b.context=this.context,b},each:function(a,b){return 
m.each(this,a,b)},map:function(a){return 
this.pushStack(m.map(this,function(b,c){return 
a.call(b,c,b)}))},slice:function(){return this.pushStack(d.apply(this,argumen
 ts))},first:function(){return this.eq(0)},last:function(){return 
this.eq(-1)},eq:function(a){var b=this.length,c=+a+(0>a?b:0);return 
this.pushStack(c>=0&>c?[this[c]]:[])},end:function(){return 
this.prevObject||this.constructor(null)},push:f,sort:c.sort,splice:c.splice},m.extend=m.fn.extend=function(){var
 
a,b,c,d,e,f,g=arguments[0]||{},h=1,i=arguments.length,j=!1;for("boolean"==typeof
 g&&(j=g,g=arguments[h]||{},h++),"object"==typeof 
g||m.isFunction(g)||(g={}),h===i&&(g=this,h--);i>h;h++)if(null!=(e=arguments[h]))for(d
 in 
e)a=g[d],c=e[d],g!==c&&(j&&&(m.isPlainObject(c)||(b=m.isArray(c)))?(b?(b=!1,f=a&(a)?a:[]):f=a&(a)?a:{},g[d]=m.extend(j,f,c)):void
 0!==c&&(g[d]=c));return 
g},m.extend({expando:"jQuery"+(l+Math.random()).replace(/\D/g,""),isReady:!0,error:function(a){throw
 new 
Error(a)},noop:function(){},isFunction:function(a){return"function"===m.type(a)},isArray:Array.isArray||function(a){return"array"===m.type(a)},isWindow:function(a){return
 null!=a&=
 
=a.window},isNumeric:function(a){return!m.isArray(a)&(a)>=0},isEmptyObject:function(a){var
 b;for(b in a)return!1;return!0},isPlainObject:function(a){var 
b;if(!a||"object"!==m.type(a)||a.nodeType||m.isWindow(a))return!1;try{if(a.constructor&&!j.call(a,"constructor")&&!j.call(a.constructor.prototype,"isPrototypeOf"))return!1}catch(c){return!1}if(k.ownLast)for(b
 in a)return j.call(a,b);for(b in a);return void 
0===b||j.call(a,b)},type:function(a){return null==a?a+"":"object"==typeof 
a||"function"==typeof a?h[i.call(a)]||"object":typeof 
a},globalEval:function(b){b&(b)&&(a.execScript||function(b){a.eval.call(a,b)})(b)},camelCase:function(a){return
 a.replace(o,"ms-").replace(p,q)},nodeName:function(a,b){return 
a.nodeName&()===b.toLowerCase()},each:function(a,b,c){var
 
d,e=0,f=a.length,g=r(a);if(c){if(g){for(;f>e;e++)if(d=b.apply(a[e],c),d===!1)break}else
 for(e in a)if(d=b.apply(a[e],c),d===!1)break}else 
if(g){for(;f>e;e++)if(d=b.call(a[e],e,a[e]),d
 ===!1)break}else for(e in a)if(d=b.call(a[e],e,a[e]),d===!1)break;return 
a},trim:function(a){return 
null==a?"":(a+"").replace(n,"")},makeArray:function(a,b){var c=b||[];return 
null!=a&&(r(Object(a))?m.merge(c,"string"==typeof 
a?[a]:a):f.call(c,a)),c},inArray:function(a,b,c){var d;if(b){if(g)return 
g.call(b,a,c);for(d=b.length,c=c?0>c?Math.max(0,d+c):c:0;d>c;c++)if(c in 
b&[c]===a)return c}return-1},merge:function(a,b){var 
c=+b.length,d=0,e=a.length;while(c>d)a[e++]=b[d++];if(c!==c)while(void 
0!==b[d])a[e++]=b[d++];return a.length=e,a},grep:function(a,b,c){for(var 
d,e=[],f=0,g=a.length,h=!c;g>f;f++)d=!b(a[f],f),d!==h&(a[f]);return 
e},map:function(a,b,c){var 
d,f=0,g=a.length,h=r(a),i=[];if(h)for(;g>f;f++)d=b(a[f],f,c),null!=d&(d);else
 for(f in a)d=b(a[f],f,c),null!=d&(d);return 
e.apply([],i)},guid:1,proxy:function(a,b){var c,e,f;return"string"==typeof 
b&&(f=a[b],b=a,a=f),m.isFunction(a)?(c=d.call(arguments,2),e=function(){return 
a.apply(b||this,c.concat(d.call(ar
 guments)))},e.guid=a.guid=a.guid||m.guid++,e):void 
0},now:function(){return+new Date},support:k}),m.each("Boolean Number String 
Function Array Date RegExp Object Error".split(" "),function(a,b){h["[object 
"+b+"]"]=b.toLowerCase()});function r(a){var 
b=a.length,c=m.type(a);return"function"===c||m.isWindow(a)?!1:1===a.nodeType&?!0:"array"===c||0===b||"number"==typeof
 b&>0& in a}var s=function(a){var 
b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u="sizzle"+-new 
Date,v=a.document,w=0,x=0,y=gb(),z=gb(),A=gb(),B=function(a,b){return 

svn commit: r1757419 [3/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling/

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_sources/cql/changes.txt
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_sources/cql/changes.txt?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_sources/cql/changes.txt (added)
+++ cassandra/site/src/doc/3.10/_sources/cql/changes.txt Tue Aug 23 19:25:17 
2016
@@ -0,0 +1,197 @@
+.. 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.
+
+.. highlight:: cql
+
+Changes
+---
+
+The following describes the changes in each version of CQL.
+
+3.4.3
+^
+
+- Support for ``GROUP BY`` (:jira:`10707`).
+- Adds a ``DEFAULT UNSET`` option for ``INSERT JSON`` to ignore omitted 
columns (:jira:`11424`).
+- Allows ``null`` as a legal value for TTL on insert and update. It will be 
treated as equivalent to
+inserting a 0 (:jira:`12216`).
+
+3.4.2
+^
+
+- If a table has a non zero ``default_time_to_live``, then explicitly 
specifying a TTL of 0 in an ``INSERT`` or
+  ``UPDATE`` statement will result in the new writes not having any expiration 
(that is, an explicit TTL of 0 cancels
+  the ``default_time_to_live``). This wasn't the case before and the 
``default_time_to_live`` was applied even though a
+  TTL had been explicitly set.
+- ``ALTER TABLE`` ``ADD`` and ``DROP`` now allow multiple columns to be 
added/removed.
+- New ``PER PARTITION LIMIT`` option for ``SELECT`` statements (see 
`CASSANDRA-7017
+  `__.
+- :ref:`User-defined functions ` can now instantiate 
``UDTValue`` and ``TupleValue`` instances via the
+  new ``UDFContext`` interface (see `CASSANDRA-10818 
`__.
+- :ref:`User-defined types ` may now be stored in a non-frozen form, 
allowing individual fields to be updated and
+  deleted in ``UPDATE`` statements and ``DELETE`` statements, respectively. 
(`CASSANDRA-7423
+  `__).
+
+3.4.1
+^
+
+- Adds ``CAST`` functions.
+
+3.4.0
+^
+
+- Support for :ref:`materialized views `.
+- ``DELETE`` support for inequality expressions and ``IN`` restrictions on any 
primary key columns.
+- ``UPDATE`` support for ``IN`` restrictions on any primary key columns.
+
+3.3.1
+^
+
+- The syntax ``TRUNCATE TABLE X`` is now accepted as an alias for ``TRUNCATE 
X``.
+
+3.3.0
+^
+
+- :ref:`User-defined functions and aggregates ` are now 
supported.
+- Allows double-dollar enclosed strings literals as an alternative to 
single-quote enclosed strings.
+- Introduces Roles to supersede user based authentication and access control
+- New ``date``, ``time``, ``tinyint`` and ``smallint`` :ref:`data types 
` have been added.
+- :ref:`JSON support ` has been added
+- Adds new time conversion functions and deprecate ``dateOf`` and 
``unixTimestampOf``.
+
+3.2.0
+^
+
+- :ref:`User-defined types ` supported.
+- ``CREATE INDEX`` now supports indexing collection columns, including 
indexing the keys of map collections through the
+  ``keys()`` function
+- Indexes on collections may be queried using the new ``CONTAINS`` and 
``CONTAINS KEY`` operators
+- :ref:`Tuple types ` were added to hold fixed-length sets of typed 
positional fields.
+- ``DROP INDEX`` now supports optionally specifying a keyspace.
+
+3.1.7
+^
+
+- ``SELECT`` statements now support selecting multiple rows in a single 
partition using an ``IN`` clause on combinations
+  of clustering columns.
+- ``IF NOT EXISTS`` and ``IF EXISTS`` syntax is now supported by ``CREATE 
USER`` and ``DROP USER`` statements,
+  respectively.
+
+3.1.6
+^
+
+- A new ``uuid()`` method has been added.
+- Support for ``DELETE ... IF EXISTS`` syntax.
+
+3.1.5
+^
+
+- It is now possible to group clustering columns in a relation, see 
:ref:`WHERE ` clauses.
+- Added support for :ref:`static columns `.
+
+3.1.4
+^
+
+- ``CREATE INDEX`` now allows specifying options when creating CUSTOM indexes.
+
+3.1.3
+^
+
+- Millisecond precision formats have been added to the :ref:`timestamp 
` parser.
+
+3.1.2
+^
+
+- ``NaN`` and ``Infinity`` has been added as valid float constants. They are 
now reserved keywords. In the unlikely 

svn commit: r1757419 [14/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/configuration/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/configuration/index.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/configuration/index.html (added)
+++ cassandra/site/src/doc/3.10/configuration/index.html Tue Aug 23 19:25:17 
2016
@@ -0,0 +1,111 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-title: "Configuring Cassandra"
+doc-header-links: '
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Cassandra Configuration File
+
+
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Configuring Cassandra¶
+This section describes how to configure Apache Cassandra.
+
+
+Cassandra Configuration File
+
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ Previous
+
+  
+  
+
+  
+
+
+
+  
+
\ No newline at end of file

Added: cassandra/site/src/doc/3.10/contactus.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/contactus.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/contactus.html (added)
+++ cassandra/site/src/doc/3.10/contactus.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,129 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-title: "Contact us"
+doc-header-links: '
+  
+  
+'
+doc-search-path: "search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The 
Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+Mailing lists
+IRC
+
+
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Contact us¶
+You can get in touch with the Cassandra community either via the mailing 
lists or the freenode IRC channels.
+
+Mailing lists¶
+The following mailing lists are available:
+
+http://www.mail-archive.com/usercassandra.apache.org/;>Users – 
General discussion list for users - mailto:user-subscribecassandraapacheorg;>Subscribe
+http://www.mail-archive.com/devcassandra.apache.org/;>Developers 
– Development related discussion - mailto:dev-subscribecassandraapacheorg;>Subscribe
+http://www.mail-archive.com/commitscassandra.apache.org/;>Commits
 – Commit notification source repository -
+mailto:commits-subscribecassandraapacheorg;>Subscribe
+http://www.mail-archive.com/client-devcassandra.apache.org/;>Client 
Libraries – Discussion related to the
+development of idiomatic client APIs - mailto:client-dev-subscribecassandraapacheorg;>Subscribe
+
+Subscribe by sending an email to the email address in the Subscribe links 
above. Follow the instructions in the welcome
+email to confirm your subscription. Make sure to keep the welcome email as it 
contains instructions on how to
+unsubscribe.
+
+
+IRC¶
+To chat with developers or users in real-time, join our channels on http://webchat.freenode.net/;>IRC 
freenode. The
+following channels are available:
+
+#cassandra 
- for user questions and general discussions.
+#cassandra-dev - strictly for questions or 
discussions related to Cassandra development.
+#cassandra-builds - results of automated test 
builds.
+
+
+
+
+
+
+  
+ 

svn commit: r1757419 [21/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/cql/types.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/cql/types.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/cql/types.html (added)
+++ cassandra/site/src/doc/3.10/cql/types.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,652 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "The Cassandra Query Language (CQL)"
+
+doc-title: "Data Types"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data Types
+Native Types
+Working with timestamps
+Working with dates
+Working with times
+Collections
+User-Defined Types
+Tuples
+Custom Types
+
+
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Data Types¶
+CQL is a typed language and supports a rich set of data types, including native types,
+collection types, user-defined types, tuple 
types and custom
+types:
+
+cql_type ::=  native_type | collection_type | user_defined_type | tuple_type | custom_type
+
+
+Native Types¶
+The native types supported by CQL are:
+
+native_type ::=  ASCII
+ | BIGINT
+ | BLOB
+ | BOOLEAN
+ | COUNTER
+ | DATE
+ | DECIMAL
+ | DOUBLE
+ | FLOAT
+ | INET
+ | INT
+ | SMALLINT
+ | TEXT
+ | TIME
+ | TIMESTAMP
+ | TIMEUUID
+ | TINYINT
+ | UUID
+ | VARCHAR
+ | VARINT
+
+The following table gives additional informations on the native data types, 
and on which kind of constants each type supports:
+
+
+
+
+
+
+
+type
+constants supported
+description
+
+
+
+ascii
+string
+ASCII character string
+
+bigint
+integer
+64-bit signed long
+
+blob
+blob
+Arbitrary bytes (no validation)
+
+boolean
+boolean
+Either true 
or false
+
+counter
+integer
+Counter column (64-bit signed value). See Counters for details
+
+date
+integer,
+string
+A date (with no corresponding time value). See Working with dates 
below for details
+
+decimal
+integer,
+float
+Variable-precision decimal
+
+double
+integer
+float
+64-bit IEEE-754 floating point
+
+float
+integer,
+float
+32-bit IEEE-754 floating point
+
+inet
+string
+An IP address, either IPv4 (4 bytes long) or IPv6 (16 bytes long). Note 
that
+there is no inet constant, IP address should be input as 
strings
+
+int
+integer
+32-bit signed int
+
+smallint
+integer
+16-bit signed int
+
+text
+string
+UTF8 encoded string
+
+time
+integer,
+string
+A time (with no corresponding date value) with nanosecond precision. See
+Working 
with times below for details
+
+timestamp
+integer,
+string
+A timestamp (date and time) with millisecond precision. See Working 
with timestamps
+below for details
+
+timeuuid
+uuid
+Version 1 https://en.wikipedia.org/wiki/Universally_unique_identifier;>UUID, 
generally used as a “conflict-free” timestamp. Also see
+Timeuuid functions
+
+tinyint
+integer
+8-bit signed int
+
+uuid
+uuid
+A https://en.wikipedia.org/wiki/Universally_unique_identifier;>UUID (of 
any version)
+
+varchar
+string
+UTF8 encoded string
+
+varint
+integer
+Arbitrary-precision integer
+
+
+
+
+Counters¶
+The counter 
type is used to define counter columns. A counter column is a column 
whose value is a 64-bit signed
+integer and on which 2 operations are supported: incrementing and decrementing 
(see the UPDATE statement for syntax). Note that the 
value of a counter cannot be set: a counter does not exist until first
+incremented/decremented, and that first increment/decrement is made as if the 
prior value was 0.
+Counters have a number of important 
limitations:
+
+They cannot be used for columns part of the PRIMARY KEY 
of a table.
+A table 

svn commit: r1757419 [11/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_static/searchtools.js
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_static/searchtools.js?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_static/searchtools.js (added)
+++ cassandra/site/src/doc/3.10/_static/searchtools.js Tue Aug 23 19:25:17 2016
@@ -0,0 +1,651 @@
+/*
+ * searchtools.js_t
+ * 
+ *
+ * Sphinx JavaScript utilities for the full-text search.
+ *
+ * :copyright: Copyright 2007-2016 by the Sphinx team, see AUTHORS.
+ * :license: BSD, see LICENSE for details.
+ *
+ */
+
+
+/* Non-minified version JS is _stemmer.js if file is provided */ 
+/**
+ * Porter Stemmer
+ */
+var Stemmer = function() {
+
+  var step2list = {
+ational: 'ate',
+tional: 'tion',
+enci: 'ence',
+anci: 'ance',
+izer: 'ize',
+bli: 'ble',
+alli: 'al',
+entli: 'ent',
+eli: 'e',
+ousli: 'ous',
+ization: 'ize',
+ation: 'ate',
+ator: 'ate',
+alism: 'al',
+iveness: 'ive',
+fulness: 'ful',
+ousness: 'ous',
+aliti: 'al',
+iviti: 'ive',
+biliti: 'ble',
+logi: 'log'
+  };
+
+  var step3list = {
+icate: 'ic',
+ative: '',
+alize: 'al',
+iciti: 'ic',
+ical: 'ic',
+ful: '',
+ness: ''
+  };
+
+  var c = "[^aeiou]";  // consonant
+  var v = "[aeiouy]";  // vowel
+  var C = c + "[^aeiouy]*";// consonant sequence
+  var V = v + "[aeiou]*";  // vowel sequence
+
+  var mgr0 = "^(" + C + ")?" + V + C;  // [C]VC... is m>0
+  var meq1 = "^(" + C + ")?" + V + C + "(" + V + ")?$";// [C]VC[V] is m=1
+  var mgr1 = "^(" + C + ")?" + V + C + V + C;  // [C]VCVC... is m>1
+  var s_v   = "^(" + C + ")?" + v; // vowel in stem
+
+  this.stemWord = function (w) {
+var stem;
+var suffix;
+var firstch;
+var origword = w;
+
+if (w.length < 3)
+  return w;
+
+var re;
+var re2;
+var re3;
+var re4;
+
+firstch = w.substr(0,1);
+if (firstch == "y")
+  w = firstch.toUpperCase() + w.substr(1);
+
+// Step 1a
+re = /^(.+?)(ss|i)es$/;
+re2 = /^(.+?)([^s])s$/;
+
+if (re.test(w))
+  w = w.replace(re,"$1$2");
+else if (re2.test(w))
+  w = w.replace(re2,"$1$2");
+
+// Step 1b
+re = /^(.+?)eed$/;
+re2 = /^(.+?)(ed|ing)$/;
+if (re.test(w)) {
+  var fp = re.exec(w);
+  re = new RegExp(mgr0);
+  if (re.test(fp[1])) {
+re = /.$/;
+w = w.replace(re,"");
+  }
+}
+else if (re2.test(w)) {
+  var fp = re2.exec(w);
+  stem = fp[1];
+  re2 = new RegExp(s_v);
+  if (re2.test(stem)) {
+w = stem;
+re2 = /(at|bl|iz)$/;
+re3 = new RegExp("([^aeiouylsz])\\1$");
+re4 = new RegExp("^" + C + v + "[^aeiouwxy]$");
+if (re2.test(w))
+  w = w + "e";
+else if (re3.test(w)) {
+  re = /.$/;
+  w = w.replace(re,"");
+}
+else if (re4.test(w))
+  w = w + "e";
+  }
+}
+
+// Step 1c
+re = /^(.+?)y$/;
+if (re.test(w)) {
+  var fp = re.exec(w);
+  stem = fp[1];
+  re = new RegExp(s_v);
+  if (re.test(stem))
+w = stem + "i";
+}
+
+// Step 2
+re = 
/^(.+?)(ational|tional|enci|anci|izer|bli|alli|entli|eli|ousli|ization|ation|ator|alism|iveness|fulness|ousness|aliti|iviti|biliti|logi)$/;
+if (re.test(w)) {
+  var fp = re.exec(w);
+  stem = fp[1];
+  suffix = fp[2];
+  re = new RegExp(mgr0);
+  if (re.test(stem))
+w = stem + step2list[suffix];
+}
+
+// Step 3
+re = /^(.+?)(icate|ative|alize|iciti|ical|ful|ness)$/;
+if (re.test(w)) {
+  var fp = re.exec(w);
+  stem = fp[1];
+  suffix = fp[2];
+  re = new RegExp(mgr0);
+  if (re.test(stem))
+w = stem + step3list[suffix];
+}
+
+// Step 4
+re = 
/^(.+?)(al|ance|ence|er|ic|able|ible|ant|ement|ment|ent|ou|ism|ate|iti|ous|ive|ize)$/;
+re2 = /^(.+?)(s|t)(ion)$/;
+if (re.test(w)) {
+  var fp = re.exec(w);
+  stem = fp[1];
+  re = new RegExp(mgr1);
+  if (re.test(stem))
+w = stem;
+}
+else if (re2.test(w)) {
+  var fp = re2.exec(w);
+  stem = fp[1] + fp[2];
+  re2 = new RegExp(mgr1);
+  if (re2.test(stem))
+w = stem;
+}
+
+// Step 5
+re = /^(.+?)e$/;
+if (re.test(w)) {
+  var fp = re.exec(w);
+  stem = fp[1];
+  re = new RegExp(mgr1);
+  re2 = new RegExp(meq1);
+  re3 = new RegExp("^" + C + v + "[^aeiouwxy]$");
+  if (re.test(stem) || (re2.test(stem) && !(re3.test(stem
+w = stem;
+}
+re = /ll$/;
+re2 = new RegExp(mgr1);
+if (re.test(w) && re2.test(w)) {
+  re = /.$/;
+  w = w.replace(re,"");
+}
+
+// and turn initial Y back to y
+if (firstch == "y")
+  w = firstch.toLowerCase() + w.substr(1);
+

svn commit: r1757419 [4/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling/

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_sources/cql/functions.txt
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_sources/cql/functions.txt?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_sources/cql/functions.txt (added)
+++ cassandra/site/src/doc/3.10/_sources/cql/functions.txt Tue Aug 23 19:25:17 
2016
@@ -0,0 +1,558 @@
+.. 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.
+
+.. highlight:: cql
+
+.. _cql-functions:
+
+.. Need some intro for UDF and native functions in general and point those to 
it.
+.. _udfs:
+.. _native-functions:
+
+Functions
+-
+
+CQL supports 2 main categories of functions:
+
+- the :ref:`scalar functions `, which simply take a number 
of values and produce an output with it.
+- the :ref:`aggregate functions `, which are used to 
aggregate multiple rows results from a
+  ``SELECT`` statement.
+
+In both cases, CQL provides a number of native "hard-coded" functions as well 
as the ability to create new user-defined
+functions.
+
+.. note:: By default, the use of user-defined functions is disabled by default 
for security concerns (even when
+   enabled, the execution of user-defined functions is sandboxed and a "rogue" 
function should not be allowed to do
+   evil, but no sandbox is perfect so using user-defined functions is opt-in). 
See the ``enable_user_defined_functions``
+   in ``cassandra.yaml`` to enable them.
+
+A function is identifier by its name:
+
+.. productionlist::
+   function_name: [ `keyspace_name` '.' ] `name`
+
+.. _scalar-functions:
+
+Scalar functions
+
+
+.. _scalar-native-functions:
+
+Native functions
+
+
+Cast
+
+
+The ``cast`` function can be used to converts one native datatype to another.
+
+The following table describes the conversions supported by the ``cast`` 
function. Cassandra will silently ignore any
+cast converting a datatype into its own datatype.
+
+=== 
===
+ FromTo
+=== 
===
+ ``ascii``   ``text``, ``varchar``
+ ``bigint``  ``tinyint``, ``smallint``, ``int``, ``float``, ``double``, 
``decimal``, ``varint``, ``text``,
+ ``varchar``
+ ``boolean`` ``text``, ``varchar``
+ ``counter`` ``tinyint``, ``smallint``, ``int``, ``bigint``, ``float``, 
``double``, ``decimal``, ``varint``,
+ ``text``, ``varchar``
+ ``date````timestamp``
+ ``decimal`` ``tinyint``, ``smallint``, ``int``, ``bigint``, ``float``, 
``double``, ``varint``, ``text``,
+ ``varchar``
+ ``double``  ``tinyint``, ``smallint``, ``int``, ``bigint``, ``float``, 
``decimal``, ``varint``, ``text``,
+ ``varchar``
+ ``float``   ``tinyint``, ``smallint``, ``int``, ``bigint``, ``double``, 
``decimal``, ``varint``, ``text``,
+ ``varchar``
+ ``inet````text``, ``varchar``
+ ``int`` ``tinyint``, ``smallint``, ``bigint``, ``float``, ``double``, 
``decimal``, ``varint``, ``text``,
+ ``varchar``
+ ``smallint````tinyint``, ``int``, ``bigint``, ``float``, ``double``, 
``decimal``, ``varint``, ``text``,
+ ``varchar``
+ ``time````text``, ``varchar``
+ ``timestamp``   ``date``, ``text``, ``varchar``
+ ``timeuuid````timestamp``, ``date``, ``text``, ``varchar``
+ ``tinyint`` ``tinyint``, ``smallint``, ``int``, ``bigint``, ``float``, 
``double``, ``decimal``, ``varint``,
+ ``text``, ``varchar``
+ ``uuid````text``, ``varchar``
+ ``varint``  ``tinyint``, ``smallint``, ``int``, ``bigint``, ``float``, 
``double``, ``decimal``, ``text``,
+ ``varchar``
+=== 
===
+
+The conversions rely strictly on Java's semantics. For example, the double 
value 1 will be converted to the text value
+'1.0'. For instance::
+
+SELECT avg(cast(count as double)) FROM myTable
+
+Token

svn commit: r1757419 [7/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling/

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_sources/operating/metrics.txt
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_sources/operating/metrics.txt?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_sources/operating/metrics.txt (added)
+++ cassandra/site/src/doc/3.10/_sources/operating/metrics.txt Tue Aug 23 
19:25:17 2016
@@ -0,0 +1,706 @@
+.. 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.
+
+.. highlight:: none
+
+Monitoring
+--
+
+Metrics in Cassandra are managed using the `Dropwizard Metrics 
`__ library. These metrics
+can be queried via JMX or pushed to external monitoring systems using a number 
of `built in
+`__ and 
`third party
+`__ reporter plugins.
+
+Metrics are collected for a single node. It's up to the operator to use an 
external monitoring system to aggregate them.
+
+Metric Types
+
+All metrics reported by cassandra fit into one of the following types.
+
+``Gauge``
+An instantaneous measurement of a value.
+
+``Counter``
+A gauge for an ``AtomicLong`` instance. Typically this is consumed by 
monitoring the change since the last call to
+see if there is a large increase compared to the norm.
+
+``Histogram``
+Measures the statistical distribution of values in a stream of data.
+
+In addition to minimum, maximum, mean, etc., it also measures median, 
75th, 90th, 95th, 98th, 99th, and 99.9th
+percentiles.
+
+``Timer``
+Measures both the rate that a particular piece of code is called and the 
histogram of its duration.
+
+``Latency``
+Special type that tracks latency (in microseconds) with a ``Timer`` plus a 
``Counter`` that tracks the total latency
+accrued since starting. The former is useful if you track the change in 
total latency since the last check. Each
+metric name of this type will have 'Latency' and 'TotalLatency' appended 
to it.
+
+``Meter``
+A meter metric which measures mean throughput and one-, five-, and 
fifteen-minute exponentially-weighted moving
+average throughputs.
+
+Table Metrics
+^
+
+Each table in Cassandra has metrics responsible for tracking its state and 
performance.
+
+The metric names are all appended with the specific ``Keyspace`` and ``Table`` 
name.
+
+Reported name format:
+
+**Metric Name**
+``org.apache.cassandra.metrics.Table...``
+
+**JMX MBean**
+``org.apache.cassandra.metrics:type=Table keyspace= 
scope= name=``
+
+.. NOTE::
+There is a special table called '``all``' without a keyspace. This 
represents the aggregation of metrics across
+**all** tables and keyspaces on the node.
+
+
+=== == ===
+NameType   Description
+=== == ===
+MemtableOnHeapSize  GaugeTotal amount of data 
stored in the memtable that resides **on**-heap, including column related 
overhead and partitions overwritten.
+MemtableOffHeapSize GaugeTotal amount of data 
stored in the memtable that resides **off**-heap, including column related 
overhead and partitions overwritten.
+MemtableLiveDataSizeGaugeTotal amount of live 
data stored in the memtable, excluding any data structure overhead.
+AllMemtablesOnHeapSize  GaugeTotal amount of data 
stored in the memtables (2i and pending flush memtables included) that resides 
**on**-heap.
+AllMemtablesOffHeapSize GaugeTotal amount of data 
stored in the memtables (2i and pending flush memtables included) that resides 
**off**-heap.
+AllMemtablesLiveDataSizeGaugeTotal amount of live 
data stored in the memtables (2i and pending flush memtables included) that 
resides off-heap, excluding any data structure overhead.
+MemtableColumnsCountGaugeTotal number of columns 
present in the memtable.
+MemtableSwitchCount Counter

svn commit: r1757419 [5/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling/

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_sources/cql/types.txt
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_sources/cql/types.txt?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_sources/cql/types.txt (added)
+++ cassandra/site/src/doc/3.10/_sources/cql/types.txt Tue Aug 23 19:25:17 2016
@@ -0,0 +1,518 @@
+.. 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.
+
+.. highlight:: cql
+
+.. _UUID: https://en.wikipedia.org/wiki/Universally_unique_identifier
+
+.. _data-types:
+
+Data Types
+--
+
+CQL is a typed language and supports a rich set of data types, including 
:ref:`native types `,
+:ref:`collection types `, :ref:`user-defined types `, 
:ref:`tuple types ` and :ref:`custom
+types `:
+
+.. productionlist::
+   cql_type: `native_type` | `collection_type` | `user_defined_type` | 
`tuple_type` | `custom_type`
+
+
+.. _native-types:
+
+Native Types
+
+
+The native types supported by CQL are:
+
+.. productionlist::
+   native_type: ASCII
+  : | BIGINT
+  : | BLOB
+  : | BOOLEAN
+  : | COUNTER
+  : | DATE
+  : | DECIMAL
+  : | DOUBLE
+  : | FLOAT
+  : | INET
+  : | INT
+  : | SMALLINT
+  : | TEXT
+  : | TIME
+  : | TIMESTAMP
+  : | TIMEUUID
+  : | TINYINT
+  : | UUID
+  : | VARCHAR
+  : | VARINT
+
+The following table gives additional informations on the native data types, 
and on which kind of :ref:`constants
+` each type supports:
+
+=== = 
==
+ typeconstants supported   description
+=== = 
==
+ ``ascii``   :token:`string`   ASCII character string
+ ``bigint``  :token:`integer`  64-bit signed long
+ ``blob``:token:`blob` Arbitrary bytes (no validation)
+ ``boolean`` :token:`boolean`  Either ``true`` or ``false``
+ ``counter`` :token:`integer`  Counter column (64-bit signed value). 
See :ref:`counters` for details
+ ``date``:token:`integer`, A date (with no corresponding time 
value). See :ref:`dates` below for details
+ :token:`string`
+ ``decimal`` :token:`integer`, Variable-precision decimal
+ :token:`float`
+ ``double``  :token:`integer`  64-bit IEEE-754 floating point
+ :token:`float`
+ ``float``   :token:`integer`, 32-bit IEEE-754 floating point
+ :token:`float`
+ ``inet``:token:`string`   An IP address, either IPv4 (4 bytes 
long) or IPv6 (16 bytes long). Note that
+   there is no ``inet`` constant, IP 
address should be input as strings
+ ``int`` :token:`integer`  32-bit signed int
+ ``smallint``:token:`integer`  16-bit signed int
+ ``text``:token:`string`   UTF8 encoded string
+ ``time``:token:`integer`, A time (with no corresponding date 
value) with nanosecond precision. See
+ :token:`string`   :ref:`times` below for details
+ ``timestamp``   :token:`integer`, A timestamp (date and time) with 
millisecond precision. See :ref:`timestamps`
+ :token:`string`   below for details
+ ``timeuuid``:token:`uuid` Version 1 UUID_, generally used as a 
“conflict-free” timestamp. Also see
+   :ref:`timeuuid-functions`
+ ``tinyint`` :token:`integer`  8-bit signed int
+ ``uuid``:token:`uuid` A UUID_ (of any version)
+ ``varchar`` :token:`string`   UTF8 encoded string
+ ``varint``  :token:`integer`  Arbitrary-precision integer
+=== = 
==
+
+.. _counters:
+
+Counters
+
+
+The ``counter`` type is used to define 

svn commit: r1757419 [22/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/development/how_to_commit.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/development/how_to_commit.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/development/how_to_commit.html (added)
+++ cassandra/site/src/doc/3.10/development/how_to_commit.html Tue Aug 23 
19:25:17 2016
@@ -0,0 +1,182 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "Cassandra Development"
+
+doc-title: "How-to Commit"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Building 
and IDE Integration
+Testing
+Contributing Code Changes
+Code Style
+Review Checklist
+How-to Commit
+
+
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+How-to Commit¶
+If you are a committer, feel free to pick any process that works for you - 
so long as you are planning to commit the work yourself.
+Here is how committing and merging will usually look for merging and 
pushing for tickets that follow the convention (if patch-based):
+Hypothetical CASSANDRA-12345 ticket is a cassandra-3.0 based bug fix that 
requires different code for cassandra-3.3, and trunk. Contributor Jackie 
supplied a patch for the root branch (12345-3.0.patch), and patches for the 
remaining branches (12345-3.3.patch, 12345-trunk.patch).
+
+On cassandra-3.0:
+
+git am -3 12345-3.0.patch (if we have a problem b/c of 
CHANGES.txt not merging anymore, we fix  it ourselves, in place)
+
+
+On cassandra-3.3:
+
+git merge cassandra-3.0 -s ours
+git apply -3 12345-3.3.patch (likely to have an issue with 
CHANGES.txt here: fix it ourselves, then git add CHANGES.txt)
+git commit —amend
+
+
+On trunk:
+
+git merge cassandra-3.3 -s ours
+git apply -3 12345-trunk.patch (likely to have an issue with 
CHANGES.txt here: fix it ourselves, then git add CHANGES.txt)
+git commit —amend
+
+
+On any branch:
+
+git push origin cassandra-3.0 cassandra-3.3 trunk —atomic
+
+
+
+Same scenario, but a branch-based contribution:
+
+On cassandra-3.0:
+
+git cherry-pick sha-of-3.0-commit (if we have a problem b/c 
of CHANGES.txt not merging anymore, we fix it ourselves, in place)
+
+
+On cassandra-3.3:
+
+git merge cassandra-3.0 -s ours
+git format-patch -1 sha-of-3.3-commit
+git apply -3 sha-of-3.3-commit.patch (likely to have an 
issue with CHANGES.txt here: fix it ourselves, then git add CHANGES.txt)
+git commit —amend
+
+
+On trunk:
+
+git merge cassandra-3.3 -s ours
+git format-patch -1 sha-of-trunk-commit
+git apply -3 sha-of-trunk-commit.patch (likely to have an 
issue with CHANGES.txt here: fix it ourselves, then git add CHANGES.txt)
+git commit —amend
+
+
+On any branch:
+
+git push origin cassandra-3.0 cassandra-3.3 trunk —atomic
+
+
+
+
+Tip
+Notes on git flags:
+-3 flag to am 
and apply will instruct git to perform a 3-way merge for you. If a conflict is 
detected, you can either resolve it manually or invoke git mergetool - for both 
am and apply.
+—atomic flag to git push does the obvious thing: 
pushes all or nothing. Without the flag, the command is equivalent to running 
git push once per each branch. This is nifty in case a race condition happens - 
you won’t push half the branches, blocking other committers’ progress while 
you are resolving the issue.
+
+
+Tip
+The fastest way to get a patch from someone’s commit in a 
branch on GH - if you don’t have their repo in remotes -  is to append .patch 
to the commit url, e.g.
+curl -O https://github.com/apache/cassandra/commit/7374e9b5ab08c1f1e612bf72293ea14c959b0c3c.patch;>https://github.com/apache/cassandra/commit/7374e9b5ab08c1f1e612bf72293ea14c959b0c3c.patch
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ Previous
+
+  
+  
+
+  
+
+
+
+  
+
\ No newline at end of file

Added: cassandra/site/src/doc/3.10/development/how_to_review.html
URL: 

svn commit: r1757419 [16/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/cql/definitions.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/cql/definitions.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/cql/definitions.html (added)
+++ cassandra/site/src/doc/3.10/cql/definitions.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,314 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "The Cassandra Query Language (CQL)"
+
+doc-title: "Definitions"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Conventions
+Identifiers and keywords
+Constants
+Terms
+Comments
+Statements
+Prepared Statements
+
+
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Definitions¶
+
+Conventions¶
+To aid in specifying the CQL syntax, we will use the following conventions 
in this document:
+
+Language rules will be given in an informal http://en.wikipedia.org/wiki/Backus%E2%80%93Naur_Form#Variants;>BNF 
variant notation. In particular, well use square brakets
+([ item ]) for optional items, 
* and + for repeated items 
(where + imply 
at least one).
+The grammar will also use the following convention for convenience: 
non-terminal term will be lowercase (and link to
+their definition) while terminal keywords will be provided all 
caps. Note however that keywords are
+Identifiers and keywords and are thus case insensitive in 
practice. We will also define some early construction using
+regexp, which well indicate with re(some regular expression).
+The grammar is provided for documentation purposes and leave some minor 
details out.  For instance, the comma on the
+last column definition in a CREATE TABLE statement is 
optional but supported if present even though the grammar in
+this document suggests otherwise. Also, not everything accepted by the grammar 
is necessarily valid CQL.
+References to keywords or pieces of CQL code in running text will be shown 
in a fixed-width font.
+
+
+
+Identifiers and keywords¶
+The CQL language uses identifiers (or names) to identify 
tables, columns and other objects. An identifier is a token
+matching the regular expression [a-zA-Z][a-zA-Z0-9_]*.
+A number of such identifiers, like SELECT or WITH, are keywords. They have a fixed 
meaning for the language
+and most are reserved. The list of those keywords can be found in Appendix A: CQL Keywords.
+Identifiers and (unquoted) keywords are case insensitive. Thus SELECT is the same 
than select or 
sElEcT, and
+myId is the 
same than myid 
or MYID. A 
convention often used (in particular by the samples of this
+documentation) is to use upper case for keywords and lower case for other 
identifiers.
+There is a second kind of identifiers called quoted identifiers 
defined by enclosing an arbitrary sequence of
+characters (non empty) in double-quotes(). Quoted identifiers are never keywords. Thus 
select is not a
+reserved keyword and can be used to refer to a column (note that using this is 
particularly advised), while select
+would raise a parsing error. Also, contrarily to unquoted identifiers and 
keywords, quoted identifiers are case
+sensitive (My 
Quoted Id is 
different from my quoted id). A fully lowercase quoted identifier that 
matches
+[a-zA-Z][a-zA-Z0-9_]* is however equivalent 
to the unquoted identifier obtained by removing the double-quote (so
+myid is equivalent to myid and to myId but different 
from myId).  Inside a quoted identifier, the
+double-quote character can be repeated to escape it, so foo  bar is a 
valid identifier.
+
+Note
+quoted identifiers allows to declare columns with 
arbitrary names, and those can sometime clash with
+specific names used by the server. For instance, when using conditional 
update, the server will respond with a
+result-set containing a special result named [applied]. If you’ve 
declared a 

svn commit: r1757419 [17/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/cql/dml.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/cql/dml.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/cql/dml.html (added)
+++ cassandra/site/src/doc/3.10/cql/dml.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,559 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "The Cassandra Query Language (CQL)"
+
+doc-title: "Data Manipulation"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data Manipulation
+SELECT
+INSERT
+UPDATE
+DELETE
+BATCH
+
+
+Secondary Indexes
+Materialized Views
+Security
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Data Manipulation¶
+This section describes the statements supported by CQL to insert, update, 
delete and query data.
+
+SELECT¶
+Querying data from data is done using a SELECT statement:
+
+select_statement ::=  
SELECT [ JSON | DISTINCT ] ( select_clause | '*' )
+  FROM table_name
+  [ WHERE where_clause ]
+  [ GROUP BY group_by_clause ]
+  [ ORDER BY ordering_clause ]
+  [ PER PARTITION LIMIT (integer | bind_marker) ]
+  [ LIMIT (integer | bind_marker) ]
+  [ ALLOW FILTERING ]
+select_clause::=  selector [ AS identifier ] ( ',' selector [ AS identifier ] )
+selector ::=  column_name
+  | term
+  | CAST '(' selector AS cql_type ')'
+  | function_name '(' [ selector ( ',' selector )* ] ')'
+  | COUNT '(' '*' ')'
+where_clause ::=  relation ( AND relation )*
+relation ::=  column_name 
operator term
+  '(' column_name ( ',' column_name 
)* ')' operator tuple_literal
+  TOKEN '(' column_name ( ',' column_name 
)* ')' operator term
+operator ::=  '=' | 
'' | '' | '=' | '=' | '!=' | IN | CONTAINS | CONTAINS KEY
+group_by_clause  ::=  column_name ( 
',' column_name )*
+ordering_clause  ::=  column_name [ 
ASC | DESC ] ( ',' column_name [ ASC | DESC ] )*
+
+For instance:
+SELECT name, 
occupation FROM users WHERE userid IN (199, 200, 207);
+SELECT JSON name, occupation 
FROM users WHERE userid = 
199;
+SELECT name AS user_name, 
occupation AS user_occupation FROM users;
+
+SELECT time, value
+FROM events
+WHERE event_type = myEvent
+  AND time  2011-02-03
+  AND time = 2012-01-01
+
+SELECT COUNT (*) AS user_count FROM users;
+
+
+The SELECT 
statements reads one or more columns for one or more rows in a table. It 
returns a result-set of the rows
+matching the request, where each row contains the values for the selection 
corresponding to the query. Additionally,
+functions including aggregation ones can be applied to the result.
+A SELECT 
statement contains at least a selection clause 
and the name of the table on which
+the selection is on (note that CQL does not joins or 
sub-queries and thus a select statement only apply to a single
+table). In most case, a select will also have a where clause and it 
can optionally have additional
+clauses to order or limit the results. 
Lastly, queries that require
+filtering can be allowed if the ALLOW FILTERING flag is provided.
+
+Selection clause¶
+The select_clause determines which columns needs to 
be queried and returned in the result-set, as well as any
+transformation to apply to this result before returning. It consists of a 
comma-separated list of selectors or,
+alternatively, of the wildcard character (*) to select all the columns defined in the table.
+
+Selectors¶
+A selector can be one of:
+
+A column name of the table selected, to retrieve the values for that 
column.
+A term, which is usually used nested inside other selectors like functions 
(if a term is selected directly, then the
+corresponding column 

svn commit: r1757419 [18/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/cql/functions.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/cql/functions.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/cql/functions.html (added)
+++ cassandra/site/src/doc/3.10/cql/functions.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,668 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "The Cassandra Query Language (CQL)"
+
+doc-title: "Functions"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Functions
+Scalar functions
+Aggregate functions
+
+
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Functions¶
+CQL supports 2 main categories of functions:
+
+the scalar functions, which simply take a number of 
values and produce an output with it.
+the aggregate functions, which are used to aggregate 
multiple rows results from a
+SELECT 
statement.
+
+In both cases, CQL provides a number of native hard-coded 
functions as well as the ability to create new user-defined
+functions.
+
+Note
+By default, the use of user-defined functions is disabled by 
default for security concerns (even when
+enabled, the execution of user-defined functions is sandboxed and a 
rogue function should not be allowed to do
+evil, but no sandbox is perfect so using user-defined functions is opt-in). 
See the enable_user_defined_functions
+in cassandra.yaml to enable them.
+
+A function is identifier by its name:
+
+function_name ::=  [ keyspace_name 
'.' ] name
+
+
+Scalar functions¶
+
+Native functions¶
+
+Cast¶
+The cast 
function can be used to converts one native datatype to another.
+The following table describes the conversions supported by the cast function. 
Cassandra will silently ignore any
+cast converting a datatype into its own datatype.
+
+
+
+
+
+
+From
+To
+
+
+
+ascii
+text, varchar
+
+bigint
+tinyint, 
smallint, int, float, double, decimal, varint, text,
+varchar
+
+boolean
+text, varchar
+
+counter
+tinyint, 
smallint, int, bigint, float, double, decimal, varint,
+text, varchar
+
+date
+timestamp
+
+decimal
+tinyint, 
smallint, int, bigint, float, double, varint, text,
+varchar
+
+double
+tinyint, 
smallint, int, bigint, float, decimal, varint, text,
+varchar
+
+float
+tinyint, 
smallint, int, bigint, double, decimal, varint, text,
+varchar
+
+inet
+text, varchar
+
+int
+tinyint, 
smallint, bigint, float, double, decimal, varint, text,
+varchar
+
+smallint
+tinyint, 
int, bigint, float, double, decimal, varint, text,
+varchar
+
+time
+text, varchar
+
+timestamp
+date, text, varchar
+
+timeuuid
+timestamp, 
date, text, varchar
+
+tinyint
+tinyint, 
smallint, int, bigint, float, double, decimal, varint,
+text, varchar
+
+uuid
+text, varchar
+
+varint
+tinyint, 
smallint, int, bigint, float, double, decimal, text,
+varchar
+
+
+
+The conversions rely strictly on Javas semantics. For example, the 
double value 1 will be converted to the text value
+1.0. For instance:
+SELECT avg(cast(count as double)) 
FROM myTable
+
+
+
+
+Token¶
+The token 
function allows to compute the token for a given partition key. The exact 
signature of the token function
+depends on the table concerned and of the partitioner used by the cluster.
+The type of the arguments of the token depend on the type of the partition key 
columns. The return type depend on
+the partitioner in use:
+
+For Murmur3Partitioner, the return type is bigint.
+For RandomPartitioner, the return type is varint.
+For ByteOrderedPartitioner, the return type is blob.
+
+For instance, in a cluster using the default Murmur3Partitioner, if a table 
is defined by:
+CREATE TABLE users (
+userid text PRIMARY KEY,
+username text,
+)
+
+
+then the token function will take a single argument of type 
text (in that 
case, the partition key is userid
+(there is no clustering columns so 

svn commit: r1757419 [23/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/faq/index.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/faq/index.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/faq/index.html (added)
+++ cassandra/site/src/doc/3.10/faq/index.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,317 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-title: "Frequently Asked Questions"
+doc-header-links: '
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Why
 cant I set listen_address to listen on 0.0.0.0 (all my 
addresses)?
+What ports does Cassandra use?
+What 
happens to existing data in my cluster when I add new nodes?
+I 
delete data from Cassandra, but disk usage stays the same. What gives?
+Why
 does nodetool ring only show one entry, even though my nodes logged that they 
see each other joining the ring?
+Can 
I change the replication factor (a a keyspace) on a live cluster?
+Can I Store (large) BLOBs in 
Cassandra?
+Nodetool
 says Connection refused to host: 127.0.1.1 for any remote host. 
What gives?
+Will batching my 
operations speed up my bulk load?
+On RHEL nodes are unable to 
join the ring
+How do I unsubscribe from the 
email list?
+Why
 does top report that Cassandra is using a lot more memory than the Java heap 
max?
+What are seeds?
+Does single seed mean 
single point of failure?
+Why cant I call jmx 
method X on jconsole?
+Why do I see ... 
messages dropped ... in the logs?
+Cassandra 
dies with java.lang.OutOfMemoryError: Map 
failed
+What 
happens if two updates are made with the same timestamp?
+Why 
bootstrapping a new node fails with a Stream failed 
error?
+
+
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Frequently Asked Questions¶
+
+Why cant I set listen_address to listen on 0.0.0.0 (all my 
addresses)?
+What ports does Cassandra use?
+What happens to existing data in my cluster when I add new 
nodes?
+I delete data from Cassandra, but disk usage stays the same. What 
gives?
+Why does nodetool ring only show one entry, even though my nodes 
logged that they see each other joining the ring?
+Can I Store (large) BLOBs in Cassandra?
+Nodetool says Connection refused to host: 
127.0.1.1 for any remote host. What gives?
+Will batching my operations speed up my bulk 
load?
+On 
RHEL nodes are unable to join the ring
+How do I unsubscribe from the email list?
+Why does top report that Cassandra is using a lot more 
memory than the Java heap max?
+What are seeds?
+Does single seed mean single point of failure?
+Why do I see ... messages dropped ... in the 
logs?
+Cassandra dies with java.lang.OutOfMemoryError: Map 
failed
+What happens if two updates are made with the same 
timestamp?
+Why bootstrapping a new node fails with a Stream 
failed error?
+
+
+Why cant I set listen_address to 
listen on 0.0.0.0 (all my addresses)?¶
+Cassandra is a gossip-based distributed system and listen_address is the address a node 
tells other nodes to reach
+it at. Telling other nodes contact me on any of my addresses is 
a bad idea; if different nodes in the cluster pick
+different addresses for you, Bad Things happen.
+If you dont want to manually specify an IP to listen_address for each node in your 
cluster (understandable!), leave
+it blank and Cassandra will use InetAddress.getLocalHost() to pick an address. Then 
its up to you or your ops team
+to make things resolve correctly (/etc/hosts/, dns, etc).
+One exception to this process is JMX, which by default binds to 0.0.0.0 
(Java bug 6425769).
+See https://issues.apache.org/jira/browse/CASSANDRA-256;>CASSANDRA-256 
and https://issues.apache.org/jira/browse/CASSANDRA-43;>CASSANDRA-43 for 
more gory details.
+
+
+What ports does Cassandra use?¶
+By default, Cassandra uses 7000 for cluster communication (7001 if SSL is 
enabled),  9042 for native protocol clients,
+and 7199 for JMX (and 9160 for the deprecated Thrift interface). The internode 
communication and native protocol ports
+are configurable in the Cassandra Configuration 

svn commit: r1757419 [13/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/configuration/cassandra_config_file.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/configuration/cassandra_config_file.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/configuration/cassandra_config_file.html (added)
+++ cassandra/site/src/doc/3.10/configuration/cassandra_config_file.html Tue 
Aug 23 19:25:17 2016
@@ -0,0 +1,1723 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "Configuring Cassandra"
+
+doc-title: "Cassandra Configuration File"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Cassandra Configuration File
+cluster_name
+num_tokens
+allocate_tokens_for_keyspace
+initial_token
+hinted_handoff_enabled
+hinted_handoff_disabled_datacenters
+max_hint_window_in_ms
+hinted_handoff_throttle_in_kb
+max_hints_delivery_threads
+hints_directory
+hints_flush_period_in_ms
+max_hints_file_size_in_mb
+hints_compression
+batchlog_replay_throttle_in_kb
+authenticator
+authorizer
+role_manager
+roles_validity_in_ms
+roles_update_interval_in_ms
+permissions_validity_in_ms
+permissions_update_interval_in_ms
+credentials_validity_in_ms
+credentials_update_interval_in_ms
+partitioner
+data_file_directories
+commitlog_directory
+cdc_enabled
+cdc_raw_directory
+disk_failure_policy
+commit_failure_policy
+prepared_statements_cache_size_mb
+thrift_prepared_statements_cache_size_mb
+key_cache_size_in_mb
+key_cache_save_period
+key_cache_keys_to_save
+row_cache_class_name
+row_cache_size_in_mb
+row_cache_save_period
+row_cache_keys_to_save
+counter_cache_size_in_mb
+counter_cache_save_period
+counter_cache_keys_to_save
+saved_caches_directory
+commitlog_sync
+commitlog_sync_batch_window_in_ms
+commitlog_sync
+commitlog_sync_period_in_ms
+commitlog_segment_size_in_mb
+commitlog_compression
+seed_provider
+concurrent_reads
+concurrent_writes
+concurrent_counter_writes
+concurrent_materialized_view_writes
+file_cache_size_in_mb
+buffer_pool_use_heap_if_exhausted
+disk_optimization_strategy
+memtable_heap_space_in_mb
+memtable_offheap_space_in_mb
+memtable_cleanup_threshold
+memtable_allocation_type
+commitlog_total_space_in_mb
+memtable_flush_writers
+cdc_total_space_in_mb
+cdc_free_space_check_interval_ms
+index_summary_capacity_in_mb
+index_summary_resize_interval_in_minutes
+trickle_fsync
+trickle_fsync_interval_in_kb
+storage_port
+ssl_storage_port
+listen_address
+listen_interface
+listen_interface_prefer_ipv6
+broadcast_address
+listen_on_broadcast_address
+internode_authenticator
+start_native_transport
+native_transport_port
+native_transport_port_ssl
+native_transport_max_threads
+native_transport_max_frame_size_in_mb
+native_transport_max_concurrent_connections
+native_transport_max_concurrent_connections_per_ip
+start_rpc
+rpc_address
+rpc_interface
+rpc_interface_prefer_ipv6
+rpc_port
+broadcast_rpc_address
+rpc_keepalive
+rpc_server_type
+rpc_min_threads
+rpc_max_threads
+rpc_send_buff_size_in_bytes
+rpc_recv_buff_size_in_bytes
+internode_send_buff_size_in_bytes
+internode_recv_buff_size_in_bytes
+thrift_framed_transport_size_in_mb
+incremental_backups
+snapshot_before_compaction
+auto_snapshot
+column_index_size_in_kb
+column_index_cache_size_in_kb
+concurrent_compactors
+compaction_throughput_mb_per_sec
+sstable_preemptive_open_interval_in_mb
+stream_throughput_outbound_megabits_per_sec
+inter_dc_stream_throughput_outbound_megabits_per_sec
+read_request_timeout_in_ms
+range_request_timeout_in_ms
+write_request_timeout_in_ms
+counter_write_request_timeout_in_ms
+cas_contention_timeout_in_ms
+truncate_request_timeout_in_ms
+request_timeout_in_ms
+slow_query_log_timeout_in_ms
+cross_node_timeout
+streaming_socket_timeout_in_ms
+phi_convict_threshold
+endpoint_snitch
+dynamic_snitch_update_interval_in_ms
+dynamic_snitch_reset_interval_in_ms
+dynamic_snitch_badness_threshold
+request_scheduler
+request_scheduler_options
+request_scheduler_id
+server_encryption_options
+client_encryption_options
+internode_compression
+inter_dc_tcp_nodelay
+tracetype_query_ttl
+tracetype_repair_ttl
+gc_log_threshold_in_ms
+enable_user_defined_functions
+enable_scripted_user_defined_functions
+windows_timer_interval

svn commit: r1757419 [8/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling/

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_sources/troubleshooting/index.txt
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_sources/troubleshooting/index.txt?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_sources/troubleshooting/index.txt (added)
+++ cassandra/site/src/doc/3.10/_sources/troubleshooting/index.txt Tue Aug 23 
19:25:17 2016
@@ -0,0 +1,20 @@
+.. 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.
+
+Troubleshooting
+===
+
+.. TODO: todo

Added: cassandra/site/src/doc/3.10/_static/ajax-loader.gif
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_static/ajax-loader.gif?rev=1757419=auto
==
Binary file - no diff available.

Propchange: cassandra/site/src/doc/3.10/_static/ajax-loader.gif
--
svn:mime-type = application/octet-stream

Added: cassandra/site/src/doc/3.10/_static/basic.css
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_static/basic.css?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_static/basic.css (added)
+++ cassandra/site/src/doc/3.10/_static/basic.css Tue Aug 23 19:25:17 2016
@@ -0,0 +1,604 @@
+/*
+ * basic.css
+ * ~
+ *
+ * Sphinx stylesheet -- basic theme.
+ *
+ * :copyright: Copyright 2007-2016 by the Sphinx team, see AUTHORS.
+ * :license: BSD, see LICENSE for details.
+ *
+ */
+
+/* -- main layout --- 
*/
+
+div.clearer {
+clear: both;
+}
+
+/* -- relbar  
*/
+
+div.related {
+width: 100%;
+font-size: 90%;
+}
+
+div.related h3 {
+display: none;
+}
+
+div.related ul {
+margin: 0;
+padding: 0 0 0 10px;
+list-style: none;
+}
+
+div.related li {
+display: inline;
+}
+
+div.related li.right {
+float: right;
+margin-right: 5px;
+}
+
+/* -- sidebar --- 
*/
+
+div.sphinxsidebarwrapper {
+padding: 10px 5px 0 10px;
+}
+
+div.sphinxsidebar {
+float: left;
+width: 230px;
+margin-left: -100%;
+font-size: 90%;
+word-wrap: break-word;
+overflow-wrap : break-word;
+}
+
+div.sphinxsidebar ul {
+list-style: none;
+}
+
+div.sphinxsidebar ul ul,
+div.sphinxsidebar ul.want-points {
+margin-left: 20px;
+list-style: square;
+}
+
+div.sphinxsidebar ul ul {
+margin-top: 0;
+margin-bottom: 0;
+}
+
+div.sphinxsidebar form {
+margin-top: 10px;
+}
+
+div.sphinxsidebar input {
+border: 1px solid #98dbcc;
+font-family: sans-serif;
+font-size: 1em;
+}
+
+div.sphinxsidebar #searchbox input[type="text"] {
+width: 170px;
+}
+
+img {
+border: 0;
+max-width: 100%;
+}
+
+/* -- search page --- 
*/
+
+ul.search {
+margin: 10px 0 0 20px;
+padding: 0;
+}
+
+ul.search li {
+padding: 5px 0 5px 20px;
+background-image: url(file.png);
+background-repeat: no-repeat;
+background-position: 0 7px;
+}
+
+ul.search li a {
+font-weight: bold;
+}
+
+ul.search li div.context {
+color: #888;
+margin: 2px 0 0 30px;
+text-align: left;
+}
+
+ul.keywordmatches li.goodmatch a {
+font-weight: bold;
+}
+
+/* -- index page  
*/
+
+table.contentstable {
+width: 90%;
+}
+
+table.contentstable p.biglink {
+line-height: 150%;
+}
+
+a.biglink {
+font-size: 1.3em;
+}
+
+span.linkdescr {
+font-style: italic;
+padding-top: 5px;
+font-size: 90%;
+}
+
+/* -- general index - 
*/
+
+table.indextable {
+width: 100%;
+}
+
+table.indextable td {
+text-align: left;
+vertical-align: top;
+}
+
+table.indextable dl, table.indextable dd {
+margin-top: 0;
+margin-bottom: 0;
+}
+
+table.indextable tr.pcap {
+height: 10px;
+}
+
+table.indextable tr.cap {
+margin-top: 10px;
+

svn commit: r1757419 [20/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/cql/security.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/cql/security.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/cql/security.html (added)
+++ cassandra/site/src/doc/3.10/cql/security.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,706 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "The Cassandra Query Language (CQL)"
+
+doc-title: "Security"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Definitions
+Data 
Types
+Data 
Definition
+Data 
Manipulation
+Secondary Indexes
+Materialized Views
+Security
+Database Roles
+Users
+Data 
Control
+
+
+Functions
+JSON 
Support
+Triggers
+Appendices
+Changes
+
+
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Security¶
+
+Database Roles¶
+CQL uses database roles to represent users and group of users. 
Syntactically, a role is defined by:
+
+role_name ::=  identifier | string
+
+
+CREATE ROLE¶
+Creating a role uses the CREATE ROLE statement:
+
+create_role_statement ::=  
CREATE ROLE [ IF NOT EXISTS ] role_name
+   [ WITH role_options ]
+role_options  ::=  role_option ( AND role_option )*
+role_option   ::=  
PASSWORD '=' string
+  | LOGIN '=' boolean
+  | SUPERUSER '=' boolean
+  | OPTIONS '=' map_literal
+
+For instance:
+CREATE ROLE new_role;
+CREATE ROLE alice WITH PASSWORD = password_a AND LOGIN = true;
+CREATE ROLE bob WITH PASSWORD = password_b AND LOGIN = true 
AND SUPERUSER = true;
+CREATE ROLE carlos WITH OPTIONS = { 
custom_option1 : option1_value, custom_option2 : 99 };
+
+
+By default roles do not possess LOGIN privileges or SUPERUSER status.
+Permissions on database resources are granted to roles; 
types of resources include keyspaces,
+tables, functions and roles themselves. Roles may be granted to other roles to 
create hierarchical permissions
+structures; in these hierarchies, permissions and SUPERUSER status are inherited, but 
the LOGIN 
privilege is
+not.
+If a role has the LOGIN privilege, clients may identify as that role 
when connecting. For the duration of that
+connection, the client will acquire any roles and privileges granted to that 
role.
+Only a client with with the CREATE permission on the database roles resource may 
issue CREATE ROLE requests (see
+the relevant section below), unless the client is a SUPERUSER. Role 
management in Cassandra
+is pluggable and custom implementations may support only a subset of the 
listed options.
+Role names should be quoted if they contain non-alphanumeric characters.
+
+Setting credentials for internal authentication¶
+Use the WITH PASSWORD clause to set a password for internal 
authentication, enclosing the password in single
+quotation marks.
+If internal authentication has not been set up or the role does not have 
LOGIN 
privileges, the WITH 
PASSWORD
+clause is not necessary.
+
+
+Creating a role conditionally¶
+Attempting to create an existing role results in an invalid query condition 
unless the IF NOT EXISTS option is used.
+If the option is used and the role exists, the statement is a no-op:
+CREATE ROLE other_role;
+CREATE ROLE IF NOT EXISTS 
other_role;
+
+
+
+
+
+ALTER ROLE¶
+Altering a role options uses the ALTER ROLE statement:
+
+alter_role_statement 
::=  ALTER ROLE role_name WITH role_options
+
+For instance:
+ALTER ROLE bob 
WITH PASSWORD = PASSWORD_B AND SUPERUSER = 
false;
+
+
+Conditions on executing ALTER ROLE statements:
+
+A client must have SUPERUSER status to alter the SUPERUSER status of another role
+A client cannot alter the SUPERUSER status of any role it currently holds
+A client can only modify certain properties of the role with which it 
identified at login (e.g. PASSWORD)
+To modify properties of a role, the client must be granted ALTER permission on that role
+
+
+
+DROP ROLE¶
+Dropping a role uses the DROP ROLE 

svn commit: r1757419 [6/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling/

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_sources/getting_started/installing.txt
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_sources/getting_started/installing.txt?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_sources/getting_started/installing.txt (added)
+++ cassandra/site/src/doc/3.10/_sources/getting_started/installing.txt Tue Aug 
23 19:25:17 2016
@@ -0,0 +1,101 @@
+.. 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.
+
+.. highlight:: none
+
+Installing Cassandra
+
+
+Prerequisites
+^
+
+- The latest version of Java 8, either the `Oracle Java Standard Edition 8
+  `__ or 
`OpenJDK 8 `__. To
+  verify that you have the correct version of java installed, type ``java 
-version``.
+
+- For using cqlsh, the latest version of `Python 2.7 
`__. To verify that you have
+  the correct version of Python installed, type ``python --version``.
+
+Installation from binary tarball files
+^^
+
+- Download the latest stable release from the `Apache Cassandra downloads 
website `__.
+
+- Untar the file somewhere, for example:
+
+::
+
+tar -xvf apache-cassandra-3.6-bin.tar.gz cassandra
+
+The files will be extracted into ``apache-cassandra-3.6``, you need to 
substitute 3.6 with the release number that you
+have downloaded.
+
+- Optionally add ``apache-cassandra-3.6\bin`` to your path.
+- Start Cassandra in the foreground by invoking ``bin/cassandra -f`` from the 
command line. Press "Control-C" to stop
+  Cassandra. Start Cassandra in the background by invoking ``bin/cassandra`` 
from the command line. Invoke ``kill pid``
+  or ``pkill -f CassandraDaemon`` to stop Cassandra, where pid is the 
Cassandra process id, which you can find for
+  example by invoking ``pgrep -f CassandraDaemon``.
+- Verify that Cassandra is running by invoking ``bin/nodetool status`` from 
the command line.
+- Configuration files are located in the ``conf`` sub-directory.
+- Since Cassandra 2.1, log and data directories are located in the ``logs`` 
and ``data`` sub-directories respectively.
+  Older versions defaulted to ``/var/log/cassandra`` and 
``/var/lib/cassandra``. Due to this, it is necessary to either
+  start Cassandra with root privileges or change ``conf/cassandra.yaml`` to 
use directories owned by the current user,
+  as explained below in the section on changing the location of directories.
+
+Installation from Debian packages
+^
+
+- Add the Apache repository of Cassandra to 
``/etc/apt/sources.list.d/cassandra.sources.list``, for example for version
+  3.6:
+
+::
+
+echo "deb http://www.apache.org/dist/cassandra/debian 36x main" | sudo tee 
-a /etc/apt/sources.list.d/cassandra.sources.list
+
+- Update the repositories:
+
+::
+
+sudo apt-get update
+
+- If you encounter this error:
+
+::
+
+GPG error: http://www.apache.org 36x InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
749D6EEC0353B12C
+
+Then add the public key 749D6EEC0353B12C as follows:
+
+::
+
+gpg --keyserver pgp.mit.edu --recv-keys 749D6EEC0353B12C
+gpg --export --armor 749D6EEC0353B12C | sudo apt-key add -
+
+and repeat ``sudo apt-get update``. The actual key may be different, you get 
it from the error message itself. For a
+full list of Apache contributors public keys, you can refer to `this link 
`__.
+
+- Install Cassandra:
+
+::
+
+sudo apt-get install cassandra
+
+- You can start Cassandra with ``sudo service cassandra start`` and stop it 
with ``sudo service cassandra stop``.
+  However, normally the service will start automatically. For this reason be 
sure to stop it if you need to make any
+  configuration changes.
+- Verify that Cassandra is running by invoking ``nodetool status`` from the 
command line.
+- The default location of configuration files is ``/etc/cassandra``.
+- The default location of log and data 

svn commit: r1757419 [29/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/tools/cqlsh.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/tools/cqlsh.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/tools/cqlsh.html (added)
+++ cassandra/site/src/doc/3.10/tools/cqlsh.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,483 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "Cassandra Tools"
+
+doc-title: "cqlsh: the CQL shell"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Cassandra Tools
+cqlsh: the CQL shell
+Compatibility
+Optional Dependencies
+cqlshrc
+Command Line Options
+Special Commands
+
+
+Nodetool
+
+
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+cqlsh: the CQL shell¶
+cqlsh is a command line shell for interacting with Cassandra through CQL 
(the Cassandra Query Language).  It is shipped
+with every Cassandra package, and can be found in the bin/ directory alongside 
the cassandra executable.  cqlsh utilizes
+the Python native protocol driver, and connects to the single node specified 
on the command line.
+
+Compatibility¶
+cqlsh is compatible with Python 2.7.
+In general, a given version of cqlsh is only guaranteed to work with the 
version of Cassandra that it was released with.
+In some cases, cqlsh make work with older or newer versions of Cassandra, but 
this is not officially supported.
+
+
+Optional Dependencies¶
+cqlsh ships with all essential dependencies.  However, there are some 
optional dependencies that can be installed to
+improve the capabilities of cqlsh.
+
+pytz¶
+By default, cqlsh displays all timestamps with a UTC timezone.  To support 
display of timestamps with another timezone,
+the http://pytz.sourceforge.net/;>pytz 
library must be installed.  See the timezone option in cqlshrc for
+specifying a timezone to use.
+
+
+cython¶
+The performance of cqlshs COPY operations can be improved by installing http://cython.org/;>cython.  This will
+compile the python modules that are central to the performance of COPY.
+
+
+
+cqlshrc¶
+The cqlshrc 
file holds configuration options for cqlsh.  By default this is in the 
users home directory at
+~/.cassandra/cqlsh, but a custom location can be 
specified with the --cqlshrc option.
+Example config values and documentation can be found in the conf/cqlshrc.sample 
file of a tarball installation.  You
+can also view the latest version of https://github.com/apache/cassandra/blob/trunk/conf/cqlshrc.sample;>cqlshrc
 online.
+
+
+Command Line Options¶
+Usage:
+cqlsh [options] [host [port]]
+Options:
+
+-C --color
+Force color output
+--no-color
+Disable color output
+--browser
+Specify the browser to use for displaying cqlsh help.  This can be one of 
the https://docs.python.org/2/library/webbrowser.html;>supported browser 
names (e.g. firefox) or a browser path followed by %s (e.g.
+/usr/bin/google-chrome-stable %s).
+--ssl
+Use SSL when connecting to Cassandra
+-u --user
+Username to authenticate against Cassandra with
+-p --password
+Password to authenticate against Cassandra with, should
+be used in conjunction with --user
+-k --keyspace
+Keyspace to authenticate to, should be used in conjunction
+with --user
+-f --file
+Execute commands from the given file, then exit
+--debug
+Print additional debugging information
+--encoding
+Specify a non-default encoding for output (defaults to UTF-8)
+--cqlshrc
+Specify a non-default location for the cqlshrc file
+-e --execute
+Execute the given statement, then exit
+--connect-timeout
+Specify the connection timeout in seconds (defaults to 2s)
+--request-timeout
+Specify the request timeout in seconds (defaults to 10s)
+-t --tty
+Force tty mode (command prompt)
+
+
+
+Special Commands¶
+In addition to supporting regular CQL statements, cqlsh also supports a 
number of special commands that are not part of
+CQL.  These are detailed below.
+
+CONSISTENCY¶
+Usage: CONSISTENCY consistency level
+Sets the consistency level for operations to follow.  Valid arguments 
include:
+

svn commit: r1757419 [27/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/operating/security.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/operating/security.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/operating/security.html (added)
+++ cassandra/site/src/doc/3.10/operating/security.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,448 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "Operating Cassandra"
+
+doc-title: "Security"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Compression
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Security
+TLS/SSL Encryption
+Roles
+Authentication
+Authorization
+Caching
+JMX 
access
+
+
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Security¶
+There are three main components to the security features provided by 
Cassandra:
+
+TLS/SSL encryption for client and inter-node communication
+Client authentication
+Authorization
+
+
+TLS/SSL Encryption¶
+Cassandra provides secure communication between a client machine and a 
database cluster and between nodes within a
+cluster. Enabling encryption ensures that data in flight is not compromised 
and is transferred securely. The options for
+client-to-node and node-to-node encryption are managed separately and may be 
configured independently.
+In both cases, the JVM defaults for supported protocols and cipher suites 
are used when encryption is enabled. These can
+be overidden using the settings in cassandra.yaml, but this is not recommended unless 
there are policies in place
+which dictate certain settings or a need to disable vulnerable ciphers or 
protocols in cases where the JVM cannot be
+updated.
+FIPS compliant settings can be configured at the JVM level and should not 
involve changing encryption settings in
+cassandra.yaml. See https://docs.oracle.com/javase/8/docs/technotes/guides/security/jsse/FIPS.html;>the
 java document on FIPS
+for more details.
+For information on generating the keystore and truststore files used in SSL 
communications, see the
+http://download.oracle.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html#CreateKeystore;>java
 documentation on creating keystores
+
+Inter-node Encryption¶
+The settings for managing inter-node encryption are found in cassandra.yaml in the 
server_encryption_options
+section. To enable inter-node encryption, change the internode_encryption setting from its 
default value of none
+to one value from: rack, dc or all.
+
+
+Client to Node Encryption¶
+The settings for managing client to node encryption are found in cassandra.yaml in the 
client_encryption_options
+section. There are two primary toggles here for enabling encryption, enabled and optional.
+
+If neither is set to true, client connections are entirely 
unencrypted.
+If enabled 
is set to true 
and optional is 
set to false, 
all client connections must be secured.
+If both options are set to true, both encrypted and unencrypted connections are 
supported using the same port.
+Client connections using encryption with this configuration will be 
automatically detected and handled by the server.
+
+As an alternative to the optional setting, separate ports can also be 
configured for secure and unsecure connections
+where operational requirements demand it. To do so, set optional to false and use the native_transport_port_ssl
+setting in cassandra.yaml to specify the port to be used for 
secure client communication.
+
+
+
+Roles¶
+Cassandra uses database roles, which may represent either a single user or 
a group of users, in both authentication and
+permissions management. Role management is an extension point in Cassandra and 
may be configured using the
+role_manager 
setting in cassandra.yaml. The default setting uses CassandraRoleManager, 
an implementation
+which stores role information in the 

svn commit: r1757419 [12/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_static/websupport.js
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_static/websupport.js?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_static/websupport.js (added)
+++ cassandra/site/src/doc/3.10/_static/websupport.js Tue Aug 23 19:25:17 2016
@@ -0,0 +1,808 @@
+/*
+ * websupport.js
+ * ~
+ *
+ * sphinx.websupport utilities for all documentation.
+ *
+ * :copyright: Copyright 2007-2016 by the Sphinx team, see AUTHORS.
+ * :license: BSD, see LICENSE for details.
+ *
+ */
+
+(function($) {
+  $.fn.autogrow = function() {
+return this.each(function() {
+var textarea = this;
+
+$.fn.autogrow.resize(textarea);
+
+$(textarea)
+  .focus(function() {
+textarea.interval = setInterval(function() {
+  $.fn.autogrow.resize(textarea);
+}, 500);
+  })
+  .blur(function() {
+clearInterval(textarea.interval);
+  });
+});
+  };
+
+  $.fn.autogrow.resize = function(textarea) {
+var lineHeight = parseInt($(textarea).css('line-height'), 10);
+var lines = textarea.value.split('\n');
+var columns = textarea.cols;
+var lineCount = 0;
+$.each(lines, function() {
+  lineCount += Math.ceil(this.length / columns) || 1;
+});
+var height = lineHeight * (lineCount + 1);
+$(textarea).css('height', height);
+  };
+})(jQuery);
+
+(function($) {
+  var comp, by;
+
+  function init() {
+initEvents();
+initComparator();
+  }
+
+  function initEvents() {
+$(document).on("click", 'a.comment-close', function(event) {
+  event.preventDefault();
+  hide($(this).attr('id').substring(2));
+});
+$(document).on("click", 'a.vote', function(event) {
+  event.preventDefault();
+  handleVote($(this));
+});
+$(document).on("click", 'a.reply', function(event) {
+  event.preventDefault();
+  openReply($(this).attr('id').substring(2));
+});
+$(document).on("click", 'a.close-reply', function(event) {
+  event.preventDefault();
+  closeReply($(this).attr('id').substring(2));
+});
+$(document).on("click", 'a.sort-option', function(event) {
+  event.preventDefault();
+  handleReSort($(this));
+});
+$(document).on("click", 'a.show-proposal', function(event) {
+  event.preventDefault();
+  showProposal($(this).attr('id').substring(2));
+});
+$(document).on("click", 'a.hide-proposal', function(event) {
+  event.preventDefault();
+  hideProposal($(this).attr('id').substring(2));
+});
+$(document).on("click", 'a.show-propose-change', function(event) {
+  event.preventDefault();
+  showProposeChange($(this).attr('id').substring(2));
+});
+$(document).on("click", 'a.hide-propose-change', function(event) {
+  event.preventDefault();
+  hideProposeChange($(this).attr('id').substring(2));
+});
+$(document).on("click", 'a.accept-comment', function(event) {
+  event.preventDefault();
+  acceptComment($(this).attr('id').substring(2));
+});
+$(document).on("click", 'a.delete-comment', function(event) {
+  event.preventDefault();
+  deleteComment($(this).attr('id').substring(2));
+});
+$(document).on("click", 'a.comment-markup', function(event) {
+  event.preventDefault();
+  toggleCommentMarkupBox($(this).attr('id').substring(2));
+});
+  }
+
+  /**
+   * Set comp, which is a comparator function used for sorting and
+   * inserting comments into the list.
+   */
+  function setComparator() {
+// If the first three letters are "asc", sort in ascending order
+// and remove the prefix.
+if (by.substring(0,3) == 'asc') {
+  var i = by.substring(3);
+  comp = function(a, b) { return a[i] - b[i]; };
+} else {
+  // Otherwise sort in descending order.
+  comp = function(a, b) { return b[by] - a[by]; };
+}
+
+// Reset link styles and format the selected sort option.
+$('a.sel').attr('href', '#').removeClass('sel');
+$('a.by' + by).removeAttr('href').addClass('sel');
+  }
+
+  /**
+   * Create a comp function. If the user has preferences stored in
+   * the sortBy cookie, use those, otherwise use the default.
+   */
+  function initComparator() {
+by = 'rating'; // Default to sort by rating.
+// If the sortBy cookie is set, use that instead.
+if (document.cookie.length > 0) {
+  var start = document.cookie.indexOf('sortBy=');
+  if (start != -1) {
+start = start + 7;
+var end = document.cookie.indexOf(";", start);
+if (end == -1) {
+  end = document.cookie.length;
+  by = unescape(document.cookie.substring(start, end));
+}
+  }
+}
+setComparator();
+  }
+
+  /**
+   * Show a comment div.
+   */
+  function show(id) {
+$('#ao' + id).hide();
+$('#ah' + id).show();
+var context = $.extend({id: id}, opts);
+ 

svn commit: r1757419 [24/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling

[tylerhobbs]

Propchange: cassandra/site/src/doc/3.10/objects.inv
--
svn:mime-type = application/octet-stream

Added: cassandra/site/src/doc/3.10/operating/backups.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/operating/backups.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/operating/backups.html (added)
+++ cassandra/site/src/doc/3.10/operating/backups.html Tue Aug 23 19:25:17 2016
@@ -0,0 +1,125 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "Operating Cassandra"
+
+doc-title: "Backups"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Compression
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Security
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Backups¶
+
+Todo
+TODO
+
+
+
+
+
+  
+  
+
+Next 
+
+
+ Previous
+
+  
+  
+
+  
+
+
+
+  
+
\ No newline at end of file

Added: cassandra/site/src/doc/3.10/operating/bloom_filters.html
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/operating/bloom_filters.html?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/operating/bloom_filters.html (added)
+++ cassandra/site/src/doc/3.10/operating/bloom_filters.html Tue Aug 23 
19:25:17 2016
@@ -0,0 +1,162 @@
+---
+layout: docpage
+
+title: "Documentation"
+
+is_homepage: false
+is_sphinx_doc: true
+
+doc-parent: "Operating Cassandra"
+
+doc-title: "Bloom Filters"
+doc-header-links: '
+  
+  
+  
+  
+'
+doc-search-path: "../search.html"
+
+extra-footer: '
+
+var DOCUMENTATION_OPTIONS = {
+  URL_ROOT:"",
+  VERSION: "",
+  COLLAPSE_INDEX: false,
+  FILE_SUFFIX: ".html",
+  HAS_SOURCE:  false,
+  SOURCELINK_SUFFIX: ""
+};
+
+'
+
+---
+
+  
+
+  
+
+  
+
+  Toggle navigation
+  
+  
+  
+
+  
+  
+
+  
+
+
+
+  
+
+
+
+
+
+Getting Started
+Architecture
+Data Modeling
+The Cassandra Query Language (CQL)
+Configuring Cassandra
+Operating Cassandra
+Snitch
+Adding, replacing, moving and removing nodes
+Repair
+Read repair
+Hints
+Compaction
+Bloom Filters
+Changing
+
+
+Compression
+Change 
Data Capture
+Backups
+Bulk Loading
+Monitoring
+Security
+Hardware Choices
+
+
+Cassandra Tools
+Troubleshooting
+Cassandra Development
+Frequently Asked Questions
+Reporting Bugs and Contributing
+Contact us
+
+
+
+
+  
+
+  
+
+
+  
+
+  
+  
+Bloom Filters¶
+In the read path, Cassandra merges data on disk (in SSTables) with data in 
RAM (in memtables). To avoid checking every
+SSTable data file for the partition being requested, Cassandra employs a data 
structure known as a bloom filter.
+Bloom filters are a probabilistic data structure that allows Cassandra to 
determine one of two possible states: - The
+data definitely does not exist in the given file, or - The data probably 
exists in the given file.
+While bloom filters can not guarantee that the data exists in a given 
SSTable, bloom filters can be made more accurate
+by allowing them to consume more RAM. Operators have the opportunity to tune 
this behavior per table by adjusting the
+the bloom_filter_fp_chance to a float between 0 and 1.
+The default value for bloom_filter_fp_chance is 0.1 for tables using 
LeveledCompactionStrategy and 0.01 for all
+other cases.
+Bloom filters are stored 

svn commit: r1757419 [9/29] - in /cassandra/site/src/doc: ./ 3.10/ 3.10/_images/ 3.10/_sources/ 3.10/_sources/architecture/ 3.10/_sources/configuration/ 3.10/_sources/cql/ 3.10/_sources/data_modeling/

[tylerhobbs]

Added: cassandra/site/src/doc/3.10/_static/jquery-1.11.1.js
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/doc/3.10/_static/jquery-1.11.1.js?rev=1757419=auto
==
--- cassandra/site/src/doc/3.10/_static/jquery-1.11.1.js (added)
+++ cassandra/site/src/doc/3.10/_static/jquery-1.11.1.js Tue Aug 23 19:25:17 
2016
@@ -0,0 +1,10308 @@
+/*!
+ * jQuery JavaScript Library v1.11.1
+ * http://jquery.com/
+ *
+ * Includes Sizzle.js
+ * http://sizzlejs.com/
+ *
+ * Copyright 2005, 2014 jQuery Foundation, Inc. and other contributors
+ * Released under the MIT license
+ * http://jquery.org/license
+ *
+ * Date: 2014-05-01T17:42Z
+ */
+
+(function( global, factory ) {
+
+   if ( typeof module === "object" && typeof module.exports === "object" ) 
{
+   // For CommonJS and CommonJS-like environments where a proper 
window is present,
+   // execute the factory and get jQuery
+   // For environments that do not inherently posses a window with 
a document
+   // (such as Node.js), expose a jQuery-making factory as 
module.exports
+   // This accentuates the need for the creation of a real window
+   // e.g. var jQuery = require("jquery")(window);
+   // See ticket #14549 for more info
+   module.exports = global.document ?
+   factory( global, true ) :
+   function( w ) {
+   if ( !w.document ) {
+   throw new Error( "jQuery requires a 
window with a document" );
+   }
+   return factory( w );
+   };
+   } else {
+   factory( global );
+   }
+
+// Pass this if window is not defined yet
+}(typeof window !== "undefined" ? window : this, function( window, noGlobal ) {
+
+// Can't do this because several apps including ASP.NET trace
+// the stack via arguments.caller.callee and Firefox dies if
+// you try to trace through "use strict" call chains. (#13335)
+// Support: Firefox 18+
+//
+
+var deletedIds = [];
+
+var slice = deletedIds.slice;
+
+var concat = deletedIds.concat;
+
+var push = deletedIds.push;
+
+var indexOf = deletedIds.indexOf;
+
+var class2type = {};
+
+var toString = class2type.toString;
+
+var hasOwn = class2type.hasOwnProperty;
+
+var support = {};
+
+
+
+var
+   version = "1.11.1",
+
+   // Define a local copy of jQuery
+   jQuery = function( selector, context ) {
+   // The jQuery object is actually just the init constructor 
'enhanced'
+   // Need init if jQuery is called (just allow error to be thrown 
if not included)
+   return new jQuery.fn.init( selector, context );
+   },
+
+   // Support: Android<4.1, IE<9
+   // Make sure we trim BOM and NBSP
+   rtrim = /^[\s\uFEFF\xA0]+|[\s\uFEFF\xA0]+$/g,
+
+   // Matches dashed string for camelizing
+   rmsPrefix = /^-ms-/,
+   rdashAlpha = /-([\da-z])/gi,
+
+   // Used by jQuery.camelCase as callback to replace()
+   fcamelCase = function( all, letter ) {
+   return letter.toUpperCase();
+   };
+
+jQuery.fn = jQuery.prototype = {
+   // The current version of jQuery being used
+   jquery: version,
+
+   constructor: jQuery,
+
+   // Start with an empty selector
+   selector: "",
+
+   // The default length of a jQuery object is 0
+   length: 0,
+
+   toArray: function() {
+   return slice.call( this );
+   },
+
+   // Get the Nth element in the matched element set OR
+   // Get the whole matched element set as a clean array
+   get: function( num ) {
+   return num != null ?
+
+   // Return just the one element from the set
+   ( num < 0 ? this[ num + this.length ] : this[ num ] ) :
+
+   // Return all the elements in a clean array
+   slice.call( this );
+   },
+
+   // Take an array of elements and push it onto the stack
+   // (returning the new matched element set)
+   pushStack: function( elems ) {
+
+   // Build a new jQuery matched element set
+   var ret = jQuery.merge( this.constructor(), elems );
+
+   // Add the old object onto the stack (as a reference)
+   ret.prevObject = this;
+   ret.context = this.context;
+
+   // Return the newly-formed element set
+   return ret;
+   },
+
+   // Execute a callback for every element in the matched set.
+   // (You can seed the arguments with an array of args, but this is
+   // only used internally.)
+   each: function( callback, args ) {
+   return jQuery.each( this, callback, args );
+   },
+
+   map: function( callback ) {
+   return 

svn commit: r1757418 - /cassandra/site/src/Makefile

[tylerhobbs]

Author: tylerhobbs
Date: Tue Aug 23 19:24:33 2016
New Revision: 1757418

URL: http://svn.apache.org/viewvc?rev=1757418=rev
Log:
Fix auto symlink to latest docs

Modified:
cassandra/site/src/Makefile

Modified: cassandra/site/src/Makefile
URL: 
http://svn.apache.org/viewvc/cassandra/site/src/Makefile?rev=1757418=1757417=1757418=diff
==
--- cassandra/site/src/Makefile (original)
+++ cassandra/site/src/Makefile Tue Aug 23 19:24:33 2016
@@ -26,7 +26,7 @@ endif
@cp -r $(CASSANDRA_DOC_DIR)/build/html $(DOC_DIR)
 
 .latest-doc-link:
-   @ln -s -f $(DOC_VERSION) "doc/latest"
+   @ln -s -f -T $(DOC_VERSION) "doc/latest"
 
 build:
@jekyll build

[jira] [Updated] (CASSANDRA-12449) Docs: Cassandra Development Section

[Tyler Hobbs (JIRA)]

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

Tyler Hobbs updated CASSANDRA-12449:

Resolution: Fixed
Status: Resolved  (was: Awaiting Feedback)

Great.

+1, committed as {{94df2a9c81a58f820141fbd6fe69231d916da868}} to trunk.  I'll 
figure out how to deploy this to the site.  Thanks again!

> Docs: Cassandra Development Section
> ---
>
> Key: CASSANDRA-12449
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12449
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
>
> The new documentation already contains some user specific topics, but details 
> on developing Cassandra are still missing. I'd like to create a new 
> "Cassandra Development" section that would be initially created based on the 
> following content:
> * [How to contribute|https://wiki.apache.org/cassandra/HowToContribute] 
> (should probably be split up into sub pages)
> * [~iamaleksey]'s [On how to submit patches and have Cassandra committers 
> like 
> you|https://docs.google.com/document/d/1d_AzYQo74de9utbbpyXxW2w-b0__sFhC7b24ibiJqjw/edit?pref=2=1]
>  (some overlapping content with "How to contribute" here)
> * [Code Style|https://wiki.apache.org/cassandra/CodeStyle]
> * [Running Cassandra in 
> IDEA|https://wiki.apache.org/cassandra/RunningCassandraInIDEA] / [Running 
> Cassandra in 
> Eclipse|https://wiki.apache.org/cassandra/RunningCassandraInEclipse] (needs 
> to be reviewed for latest IDE versions)
> Additional content would be nice to have as well, e.g. on contributing 
> documentation. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

cassandra git commit: Add Development section to online docs

[tylerhobbs]

Repository: cassandra
Updated Branches:
  refs/heads/trunk a7926b339 -> 94df2a9c8


Add Development section to online docs

Patch by Stefan Podkowinski; reviewed by Tyler Hobbs for CASSANDRA-12449


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

Branch: refs/heads/trunk
Commit: 94df2a9c81a58f820141fbd6fe69231d916da868
Parents: a7926b3
Author: Stefan Podkowinski 
Authored: Tue Aug 23 14:06:42 2016 -0500
Committer: Tyler Hobbs 
Committed: Tue Aug 23 14:06:42 2016 -0500

--
 doc/source/_templates/indexcontent.html |  10 +-
 doc/source/bugs.rst |   7 +-
 doc/source/development/code_style.rst   |  94 +++
 doc/source/development/how_to_commit.rst|  75 +
 doc/source/development/how_to_review.rst|  71 +
 doc/source/development/ide.rst  | 157 +++
 .../development/images/eclipse_debug0.png   |   0
 .../development/images/eclipse_debug1.png   |   0
 .../development/images/eclipse_debug2.png   |   0
 .../development/images/eclipse_debug3.png   |   0
 .../development/images/eclipse_debug4.png   |   0
 .../development/images/eclipse_debug5.png   |   0
 .../development/images/eclipse_debug6.png   |   0
 doc/source/development/index.rst|  28 
 doc/source/development/patches.rst  | 125 +++
 doc/source/development/testing.rst  |  86 ++
 doc/source/index.rst|   1 +
 17 files changed, 646 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/94df2a9c/doc/source/_templates/indexcontent.html
--
diff --git a/doc/source/_templates/indexcontent.html 
b/doc/source/_templates/indexcontent.html
index 60dd454..5d4b485 100644
--- a/doc/source/_templates/indexcontent.html
+++ b/doc/source/_templates/indexcontent.html
@@ -42,16 +42,18 @@
   {% trans %}CQL reference documentation{% 
endtrans %}
 
 
-  {% trans %}FAQs{% endtrans %}
-  {% trans %}Frequently Asked Questions (with 
answers!){% endtrans %}
+  {% trans %}Cassandra Development{% endtrans 
%}
+  {% trans %}Learn how to improve Cassandra and 
contribute patches{% endtrans %}
 
   
   
 
-  {% trans %}Configuration{% endtrans 
%}
-  {% trans %}Cassandra's handles and knobs{% 
endtrans %}
+  {% trans %}FAQs{% endtrans %}
+  {% trans %}Frequently Asked Questions (with 
answers!){% endtrans %}
 
 
+  {% trans %}Configuration{% endtrans 
%}
+  {% trans %}Cassandra's handles and knobs{% 
endtrans %}
 
   
 

http://git-wip-us.apache.org/repos/asf/cassandra/blob/94df2a9c/doc/source/bugs.rst
--
diff --git a/doc/source/bugs.rst b/doc/source/bugs.rst
index 90efb14..240cfd4 100644
--- a/doc/source/bugs.rst
+++ b/doc/source/bugs.rst
@@ -14,7 +14,7 @@
 .. See the License for the specific language governing permissions and
 .. limitations under the License.
 
-Reporting bugs and contributing
+Reporting Bugs and Contributing
 ===
 
 If you encounter a problem with Cassandra, the first places to ask for help 
are the :ref:`user mailing list
@@ -25,7 +25,6 @@ ticket through the `Apache Cassandra JIRA 
`__ on the Cassandra wiki. 
Please note that the source of this
-documentation is part of the Cassandra git repository and hence contributions 
to the documentation should follow the
+Further details on how to contribute can be found at our 
:doc:`development/index` section. Please note that the source of
+this documentation is part of the Cassandra git repository and hence 
contributions to the documentation should follow the
 same path.

http://git-wip-us.apache.org/repos/asf/cassandra/blob/94df2a9c/doc/source/development/code_style.rst
--
diff --git a/doc/source/development/code_style.rst 
b/doc/source/development/code_style.rst
new file mode 100644
index 000..5a486a4
--- /dev/null
+++ b/doc/source/development/code_style.rst
@@ -0,0 +1,94 @@
+.. Licensed to the Apache Software Foundation (ASF) under one
+.. or more 

[jira] [Commented] (CASSANDRA-12367) Add an API to request the size of a CQL partition

[sankalp kohli (JIRA)]

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

sankalp kohli commented on CASSANDRA-12367:
---

Also what if we expose this through CQL as well. There are clients who want to 
know how big the CQL partition is. So something like 
select bytes from table where 

What do you think. This call will be lot cheaper than counting the CQL rows and 
finding out how big the partition is. 

> Add an API to request the size of a CQL partition
> -
>
> Key: CASSANDRA-12367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12367
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Geoffrey Yu
>Assignee: Geoffrey Yu
>Priority: Minor
> Fix For: 3.x
>
> Attachments: 12367-trunk.txt
>
>
> It would be useful to have an API that we could use to get the total 
> serialized size of a CQL partition, scoped by keyspace and table, on disk.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-9875) Rebuild from targeted replica

[Paulo Motta (JIRA)]

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

Paulo Motta commented on CASSANDRA-9875:


Thanks for the quick update, I think this looks great! I prepared the patch for 
commit and submitted CI runs:

||trunk||
|[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:trunk-9875]|
|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-9875-testall/lastCompletedBuild/testReport/]|
|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-9875-dtest/lastCompletedBuild/testReport/]|

I will mark this as ready to commit after CI results look good. Could you 
please open a [cassandra-dtest|https://github.com/riptano/cassandra-dtest] pull 
request?

> Rebuild from targeted replica
> -
>
> Key: CASSANDRA-9875
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9875
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: Geoffrey Yu
>Priority: Minor
>  Labels: lhf
> Fix For: 3.x
>
> Attachments: 9875-dtest-master-v2.txt, 9875-dtest-master.txt, 
> 9875-trunk-v2.txt, 9875-trunk.txt
>
>
> Nodetool rebuild command will rebuild all the token ranges handled by the 
> endpoint. Sometimes we want to rebuild only a certain token range. We should 
> add this ability to rebuild command. We should also add the ability to stream 
> from a given replica.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12367) Add an API to request the size of a CQL partition

[sankalp kohli (JIRA)]

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

sankalp kohli commented on CASSANDRA-12367:
---

I dont think we should output more information as it will make this call 
expensive. SO we should stick to size for this JMX call. We can always add more 
JMX calls for the things you are suggesting. 

> Add an API to request the size of a CQL partition
> -
>
> Key: CASSANDRA-12367
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12367
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: Geoffrey Yu
>Assignee: Geoffrey Yu
>Priority: Minor
> Fix For: 3.x
>
> Attachments: 12367-trunk.txt
>
>
> It would be useful to have an API that we could use to get the total 
> serialized size of a CQL partition, scoped by keyspace and table, on disk.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12449) Docs: Cassandra Development Section

[Stefan Podkowinski (JIRA)]

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

Stefan Podkowinski commented on CASSANDRA-12449:


Changes look fine, please go ahead.

> Docs: Cassandra Development Section
> ---
>
> Key: CASSANDRA-12449
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12449
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
>
> The new documentation already contains some user specific topics, but details 
> on developing Cassandra are still missing. I'd like to create a new 
> "Cassandra Development" section that would be initially created based on the 
> following content:
> * [How to contribute|https://wiki.apache.org/cassandra/HowToContribute] 
> (should probably be split up into sub pages)
> * [~iamaleksey]'s [On how to submit patches and have Cassandra committers 
> like 
> you|https://docs.google.com/document/d/1d_AzYQo74de9utbbpyXxW2w-b0__sFhC7b24ibiJqjw/edit?pref=2=1]
>  (some overlapping content with "How to contribute" here)
> * [Code Style|https://wiki.apache.org/cassandra/CodeStyle]
> * [Running Cassandra in 
> IDEA|https://wiki.apache.org/cassandra/RunningCassandraInIDEA] / [Running 
> Cassandra in 
> Eclipse|https://wiki.apache.org/cassandra/RunningCassandraInEclipse] (needs 
> to be reviewed for latest IDE versions)
> Additional content would be nice to have as well, e.g. on contributing 
> documentation. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12454) Unable to start on IPv6-only node with local JMX

[Sam Tunnicliffe (JIRA)]

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

Sam Tunnicliffe commented on CASSANDRA-12454:
-

I believe this has already been addressed as a byproduct of CASSANDRA-12109, 
which will be in the upcoming 3.8 (& 3.9). There, the URL string is still 
incorrectly formatted but it is used only for logging,  not to construct a 
{{JMXServiceURL}}. In my testing, this enables the JMX server to be initialised 
correctly. However, it does still log the incorrectly formatted service URL, 
which doesn't make for a great user experience as it will need modifying to 
include the {{[]}} before use. 

[~incubos] if you're able to build from source, could you confirm that this 
works as expected in your setup with 3.8 please? I'll fix the incorrect log 
message and resolve this ticket if so.

> Unable to start on IPv6-only node with local JMX
> 
>
> Key: CASSANDRA-12454
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12454
> Project: Cassandra
>  Issue Type: Bug
> Environment: Ubuntu Trusty, Oracle JDK 1.8.0_102-b14, IPv6-only host
>Reporter: Vadim Tsesko
>
> A Cassandra node using *default* configuration is unable to start on 
> *IPv6-only* machine with the following error message:
> {code}
> ERROR [main] 2016-08-13 14:38:07,309 CassandraDaemon.java:731 - Bad URL path: 
> :0:0:0:0:0:1/jndi/rmi://0:0:0:0:0:0:0:1:7199/jmxrmi
> {code}
> The problem might be located in {{JMXServerUtils.createJMXServer()}} (I am 
> not sure, because there is no stack trace in {{system.log}}):
> {code:java}
> String urlTemplate = "service:jmx:rmi://%1$s/jndi/rmi://%1$s:%2$d/jmxrmi";
> ...
> String url = String.format(urlTemplate, (serverAddress != null ? 
> serverAddress.getHostAddress() : "0.0.0.0"), port);
> {code}
> IPv6 addresses must be surrounded by square brackets when passed to 
> {{JMXServiceURL}}.
> Disabling {{LOCAL_JMX}} mode in {{cassandra-env.sh}} (and enabling JMX 
> authentication) helps.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-6216) Level Compaction should persist last compacted key per level

[Marcus Eriksson (JIRA)]

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

Marcus Eriksson commented on CASSANDRA-6216:


nice catch, committed, thanks

> Level Compaction should persist last compacted key per level
> 
>
> Key: CASSANDRA-6216
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6216
> Project: Cassandra
>  Issue Type: Sub-task
>Reporter: sankalp kohli
>Assignee: Dikang Gu
>Priority: Minor
>  Labels: compaction, lcs
> Fix For: 3.0.9, 3.10
>
> Attachments: JIRA-6216.diff
>
>
> Level compaction does not persist the last compacted key per level. This is 
> important for higher levels. 
> The sstables with higher token and in higher levels wont get a chance to 
> compact as the last compacted key will get reset after a restart.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[2/3] cassandra git commit: remove the calculatedLastCompactedKeys check

[marcuse]

remove the calculatedLastCompactedKeys check

follow-up to CASSANDRA-6216


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

Branch: refs/heads/trunk
Commit: fe3f3da25912ab6da1dcad26946b74505674257b
Parents: 8bd6299
Author: Dikang Gu 
Authored: Tue Aug 23 09:29:53 2016 -0700
Committer: Marcus Eriksson 
Committed: Tue Aug 23 19:50:46 2016 +0200

--
 .../org/apache/cassandra/db/compaction/LeveledManifest.java| 6 --
 1 file changed, 6 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/fe3f3da2/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
--
diff --git a/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java 
b/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
index cf3ae1a..f3f8935 100644
--- a/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
+++ b/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
@@ -67,7 +67,6 @@ public class LeveledManifest
 @VisibleForTesting
 protected final List[] generations;
 private final PartitionPosition[] lastCompactedKeys;
-private volatile boolean calculatedLastCompactedKeys = false;
 private final long maxSSTableSizeInBytes;
 private final SizeTieredCompactionStrategyOptions options;
 private final int [] compactionCounter;
@@ -338,11 +337,6 @@ public class LeveledManifest
 // This isn't a magic wand -- if you are consistently writing too fast 
for LCS to keep
 // up, you're still screwed.  But if instead you have intermittent 
bursts of activity,
 // it can help a lot.
-if (!calculatedLastCompactedKeys)
-{
-this.calculateLastCompactedKeys();
-}
-
 for (int i = generations.length - 1; i > 0; i--)
 {
 List sstables = getLevel(i);

[1/3] cassandra git commit: remove the calculatedLastCompactedKeys check

[marcuse]

Repository: cassandra
Updated Branches:
  refs/heads/cassandra-3.0 8bd629942 -> fe3f3da25
  refs/heads/trunk bdeef40d4 -> a7926b339


remove the calculatedLastCompactedKeys check

follow-up to CASSANDRA-6216


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

Branch: refs/heads/cassandra-3.0
Commit: fe3f3da25912ab6da1dcad26946b74505674257b
Parents: 8bd6299
Author: Dikang Gu 
Authored: Tue Aug 23 09:29:53 2016 -0700
Committer: Marcus Eriksson 
Committed: Tue Aug 23 19:50:46 2016 +0200

--
 .../org/apache/cassandra/db/compaction/LeveledManifest.java| 6 --
 1 file changed, 6 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/fe3f3da2/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
--
diff --git a/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java 
b/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
index cf3ae1a..f3f8935 100644
--- a/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
+++ b/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
@@ -67,7 +67,6 @@ public class LeveledManifest
 @VisibleForTesting
 protected final List[] generations;
 private final PartitionPosition[] lastCompactedKeys;
-private volatile boolean calculatedLastCompactedKeys = false;
 private final long maxSSTableSizeInBytes;
 private final SizeTieredCompactionStrategyOptions options;
 private final int [] compactionCounter;
@@ -338,11 +337,6 @@ public class LeveledManifest
 // This isn't a magic wand -- if you are consistently writing too fast 
for LCS to keep
 // up, you're still screwed.  But if instead you have intermittent 
bursts of activity,
 // it can help a lot.
-if (!calculatedLastCompactedKeys)
-{
-this.calculateLastCompactedKeys();
-}
-
 for (int i = generations.length - 1; i > 0; i--)
 {
 List sstables = getLevel(i);

[3/3] cassandra git commit: Merge branch 'cassandra-3.0' into trunk

[marcuse]

Merge branch 'cassandra-3.0' into trunk


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

Branch: refs/heads/trunk
Commit: a7926b33968b9b1497fe281547e0cd0c656c7364
Parents: bdeef40 fe3f3da
Author: Marcus Eriksson 
Authored: Tue Aug 23 19:51:17 2016 +0200
Committer: Marcus Eriksson 
Committed: Tue Aug 23 19:51:17 2016 +0200

--
 .../org/apache/cassandra/db/compaction/LeveledManifest.java| 6 --
 1 file changed, 6 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/a7926b33/src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
--

[jira] [Updated] (CASSANDRA-9875) Rebuild from targeted replica

[Geoffrey Yu (JIRA)]

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

Geoffrey Yu updated CASSANDRA-9875:
---
Attachment: 9875-dtest-master-v2.txt

I've attached a new dtest patch with the changes. I ended up just adding a new 
test so we can get more granularity in the reporting. Please let me know how it 
looks!

> Rebuild from targeted replica
> -
>
> Key: CASSANDRA-9875
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9875
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: Geoffrey Yu
>Priority: Minor
>  Labels: lhf
> Fix For: 3.x
>
> Attachments: 9875-dtest-master-v2.txt, 9875-dtest-master.txt, 
> 9875-trunk-v2.txt, 9875-trunk.txt
>
>
> Nodetool rebuild command will rebuild all the token ranges handled by the 
> endpoint. Sometimes we want to rebuild only a certain token range. We should 
> add this ability to rebuild command. We should also add the ability to stream 
> from a given replica.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CASSANDRA-9875) Rebuild from targeted replica

[Geoffrey Yu (JIRA)]

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

Geoffrey Yu updated CASSANDRA-9875:
---
Status: Patch Available  (was: Open)

> Rebuild from targeted replica
> -
>
> Key: CASSANDRA-9875
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9875
> Project: Cassandra
>  Issue Type: Improvement
>Reporter: sankalp kohli
>Assignee: Geoffrey Yu
>Priority: Minor
>  Labels: lhf
> Fix For: 3.x
>
> Attachments: 9875-dtest-master-v2.txt, 9875-dtest-master.txt, 
> 9875-trunk-v2.txt, 9875-trunk.txt
>
>
> Nodetool rebuild command will rebuild all the token ranges handled by the 
> endpoint. Sometimes we want to rebuild only a certain token range. We should 
> add this ability to rebuild command. We should also add the ability to stream 
> from a given replica.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12449) Docs: Cassandra Development Section

[Tyler Hobbs (JIRA)]

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

Tyler Hobbs commented on CASSANDRA-12449:
-

This is great! Thank you _very_ much.

Overall, this looks excellent to me.  I've pushed a few minor fixes and tweaks 
to [a branch|https://github.com/thobbs/cassandra/tree/CASSANDRA-12449-review].  
If you don't have anything else you'd like to add, I'll go ahead and commit 
this with those fixes.

> Docs: Cassandra Development Section
> ---
>
> Key: CASSANDRA-12449
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12449
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Documentation and Website
>Reporter: Stefan Podkowinski
>Assignee: Stefan Podkowinski
>
> The new documentation already contains some user specific topics, but details 
> on developing Cassandra are still missing. I'd like to create a new 
> "Cassandra Development" section that would be initially created based on the 
> following content:
> * [How to contribute|https://wiki.apache.org/cassandra/HowToContribute] 
> (should probably be split up into sub pages)
> * [~iamaleksey]'s [On how to submit patches and have Cassandra committers 
> like 
> you|https://docs.google.com/document/d/1d_AzYQo74de9utbbpyXxW2w-b0__sFhC7b24ibiJqjw/edit?pref=2=1]
>  (some overlapping content with "How to contribute" here)
> * [Code Style|https://wiki.apache.org/cassandra/CodeStyle]
> * [Running Cassandra in 
> IDEA|https://wiki.apache.org/cassandra/RunningCassandraInIDEA] / [Running 
> Cassandra in 
> Eclipse|https://wiki.apache.org/cassandra/RunningCassandraInEclipse] (needs 
> to be reviewed for latest IDE versions)
> Additional content would be nice to have as well, e.g. on contributing 
> documentation. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CASSANDRA-12525) When adding new nodes to a cluster which has authentication enabled, we end up loosing cassandra user's current crendentials and they get reverted back to default ca

[Atin Sood (JIRA)]

Atin Sood created CASSANDRA-12525:
-

 Summary: When adding new nodes to a cluster which has 
authentication enabled, we end up loosing cassandra user's current crendentials 
and they get reverted back to default cassandra/cassandra crendetials
 Key: CASSANDRA-12525
 URL: https://issues.apache.org/jira/browse/CASSANDRA-12525
 Project: Cassandra
  Issue Type: Bug
  Components: Configuration
Reporter: Atin Sood
Priority: Minor


Made the following observation:

When adding new nodes to an existing C* cluster with authentication enabled we 
end up loosing password information about `cassandra` user. 

Initial Setup
- Create a 5 node cluster with system_auth having RF=5 and 
NetworkTopologyStrategy
- Enable PasswordAuthenticator on this cluster and update the password for 
'cassandra' user to say 'password' via the alter query
- Make sure you run nodetool repair on all the nodes

Test case
- Now go ahead and add 5 more nodes to this cluster.
- Run nodetool repair on all the 10 nodes now
- Decommission the original 5 nodes such that only the new 5 nodes are in the 
cluster now

- Run cqlsh and try to connect to this cluster using old user name and 
password, cassandra/password

I was unable to connect to the nodes with the original credentials and was only 
able to connect using the default cassandra/cassandra credentials

>From the conversation over IIRC

`beobal: sood: that definitely shouldn't happen. The new nodes should only 
create the default superuser role if there are 0 roles currently defined 
(including that default one)`



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CASSANDRA-12453) AutoSavingCache does not store required keys making RowCacheTests Flaky

[Joel Knighton (JIRA)]

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

Joel Knighton commented on CASSANDRA-12453:
---

I haven't had much time to look at/think about this yet. Any thoughts here as 
the OHC expert [~snazy]?

> AutoSavingCache does not store required keys making RowCacheTests Flaky
> ---
>
> Key: CASSANDRA-12453
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12453
> Project: Cassandra
>  Issue Type: Bug
>  Components: Core
>Reporter: sankalp kohli
>Priority: Minor
>
> RowCacheTests were flaky and while investigating, I found that it does not 
> store all the keys to disk. 
> The reason is that we use  OHCache and call hotKeyIterator on it. This is not 
> guaranteed to return the number of keys we want. Here is the documentation 
> from OHCache 
> /**
>  * Builds an iterator over the N most recently used keys returning 
> deserialized objects.
>  * You must call {@code close()} on the returned iterator.
>  * 
>  * Note: During a rehash, the implementation might return keys twice 
> or not at all.
>  * 
>  */
> CloseableIterator hotKeyIterator(int n);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)