date:20120713

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The ThirdPartySupport page has been changed by TomWilkie:
http://wiki.apache.org/cassandra/ThirdPartySupport?action=diffrev1=30rev2=31

  
  Companies that employ Apache Cassandra [[Committers]]:
  
- {{http://media.acunu.com/library/logo.png}} [[http://www.acunu.com|Acunu]] 
are world experts in Apache Cassandra and beyond. Some of the most challenging 
Cassandra deployments already rely on Acunu's technology, training and support. 
The Acunu Data Platform supercharges and simplifies Apache Cassandra -- it's 
business-ready, deploys out-of-the box and offers rock-solid performance and 
reliability. [[http://www.acunu.com/products/choosing-cassandra/|Get a 90-day 
free trial]] and [[http://www.acunu.com/products/choosing-cassandra/|find out 
more]].
+ {{http://www.acunu.com/uploads/1/1/5/5/11559475/1335714080.png}} 
[[http://www.acunu.com|Acunu]] are world experts in Apache Cassandra and 
beyond. Some of the most challenging Cassandra deployments already rely on 
Acunu's technology, training and support. The Acunu Data Platform supercharges 
and simplifies Apache Cassandra -- it's business-ready, deploys out-of-the box 
and offers rock-solid performance and reliability. 
[[http://www.acunu.com/products/choosing-cassandra/|Get a 90-day free trial]] 
and [[http://www.acunu.com/products/choosing-cassandra/|find out more]].
  
  {{http://www.datastax.com/sites/all/themes/datastax20110201/logo.png}} 
[[http://datastax.com|Datastax]], the commercial leader in Apache Cassandra™ 
offers products and services that make it easy for customers to build, deploy 
and operate elastically scalable and cloud-optimized applications and data 
services. [[http://datastax.com|DataStax]] has over 100 customers, including 
leaders such as Netflix, Cisco, Rackspace, HP, Constant Contact and 
[[http://www.datastax.com/cassandrausers|more]], and spanning verticals 
including web, financial services, telecommunications, logistics and government.

[jira] [Commented] (CASSANDRA-4414) Ship the exact cause for timeout and unavailable exception back to the client

[
https://issues.apache.org/jira/browse/CASSANDRA-4414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413620#comment-13413620
]

Sylvain Lebresne commented on CASSANDRA-4414:
-

The patch doesn't compile due to missing TimeoutException - TimedOutException
renaming in HintedHandoffManager.

Otherwise the patch lgtm.

nit: Maybe in WriteResponseHandler, we could keep the blockFor value as a field
instead of the table, which would avoid having to care about null checks

Ship the exact cause for timeout and unavailable exception back to the client
--

Key: CASSANDRA-4414
URL: https://issues.apache.org/jira/browse/CASSANDRA-4414
Project: Cassandra
Issue Type: Improvement
Reporter: Sylvain Lebresne
Assignee: Jonathan Ellis
Fix For: 1.2

Currently when a client gets a timeout exception, it doesn't know what
happened. But sever side we usually know a little more than that. For
example, for 99% of the timeouts at CL ONE, we will have some replica that
have acknowlege. I think it could be useful to send that information to the
client with the exception. That could help with monitoring, post-mortem
analysis and debugging.
Unavailable exceptions could also ship which nodes were alive and which ones
where not.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-4144) Pig: Composite column support for row key


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

Dirkjan Bussink updated CASSANDRA-4144:
---

Attachment: (was: 
0001-Add-support-for-composite-row-keys-in-Cassandra-PIG.patch)

 Pig: Composite column support for row key
 -

 Key: CASSANDRA-4144
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4144
 Project: Cassandra
  Issue Type: Improvement
  Components: Contrib
Affects Versions: 1.0.9
Reporter: janwar dinata
Priority: Minor
  Labels: Pig, hadoop
 Attachments: 
 0001-Add-support-for-composite-row-keys-in-Cassandra-PIG.patch, 
 0002-Add-test-and-support-for-writing-composite-values.patch


 Currently Pig only understands composite columns not composite row keys.
 Support for querying column family that has composite type for its 
 key_validation_class will be nice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-4144) Pig: Composite column support for row key


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

Dirkjan Bussink updated CASSANDRA-4144:
---

Attachment: 0002-Add-test-and-support-for-writing-composite-values.patch

Add integration tests and support for writing composite values back into 
Cassandra

 Pig: Composite column support for row key
 -

 Key: CASSANDRA-4144
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4144
 Project: Cassandra
  Issue Type: Improvement
  Components: Contrib
Affects Versions: 1.0.9
Reporter: janwar dinata
Priority: Minor
  Labels: Pig, hadoop
 Attachments: 
 0001-Add-support-for-composite-row-keys-in-Cassandra-PIG.patch, 
 0002-Add-test-and-support-for-writing-composite-values.patch


 Currently Pig only understands composite columns not composite row keys.
 Support for querying column family that has composite type for its 
 key_validation_class will be nice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-4144) Pig: Composite column support for row key


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

Dirkjan Bussink updated CASSANDRA-4144:
---

Attachment: 0001-Add-support-for-composite-row-keys-in-Cassandra-PIG.patch

Support for reading composite row keys and add integration test

 Pig: Composite column support for row key
 -

 Key: CASSANDRA-4144
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4144
 Project: Cassandra
  Issue Type: Improvement
  Components: Contrib
Affects Versions: 1.0.9
Reporter: janwar dinata
Priority: Minor
  Labels: Pig, hadoop
 Attachments: 
 0001-Add-support-for-composite-row-keys-in-Cassandra-PIG.patch, 
 0002-Add-test-and-support-for-writing-composite-values.patch


 Currently Pig only understands composite columns not composite row keys.
 Support for querying column family that has composite type for its 
 key_validation_class will be nice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4144) Pig: Composite column support for row key


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413625#comment-13413625
 ] 

Dirkjan Bussink commented on CASSANDRA-4144:


I've removed the original patch and added two new ones. One implements reading 
composite keys and the other adds support for writing back Pig tuples into 
Cassandra.

 Pig: Composite column support for row key
 -

 Key: CASSANDRA-4144
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4144
 Project: Cassandra
  Issue Type: Improvement
  Components: Contrib
Affects Versions: 1.0.9
Reporter: janwar dinata
Priority: Minor
  Labels: Pig, hadoop
 Attachments: 
 0001-Add-support-for-composite-row-keys-in-Cassandra-PIG.patch, 
 0002-Add-test-and-support-for-writing-composite-values.patch


 Currently Pig only understands composite columns not composite row keys.
 Support for querying column family that has composite type for its 
 key_validation_class will be nice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4295) move checkaccess into statement.prepare


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413649#comment-13413649
 ] 

Sylvain Lebresne commented on CASSANDRA-4295:
-

The current {{IAuthority}} API is:
{noformat}
public EnumSetPermission authorize(AuthenticatedUser user, ListObject 
resource);
{noformat}

What about changing that to something like:
{noformat}
public interface PermissionToken {}

public PairEnumSetPermission, PermissionToken authorize(AuthenticatedUser 
user, ListObject resource);
public boolean isStillValid(PermissionToken token);
{noformat}
The semantic being that authorize would give us a token (every implementation 
could make that be whatever they want) and {{isStillValid}} would validate 
whether the authorization that returned the token is still valid at the time of 
the call to {{isStillValid}}.

Implementations that don't want to get fancy could just return null as the 
token and have {{isStillValid}} return either:
- always true if an authorization is valid indefinitely
- always false to force redoing an authorization every time

And more fancier policy (like authorization is valid for X minutes only, ...) 
can be easily implemented too.

Then in CQL we would call authorize during preparation and keep the token 
around, and during execution we would check the validity of the token and redo 
the authorization only if it's not valid anymore. It does complicate think a 
bit, but not too much either.

Or we just leave things like they are and consider that caching the result of 
authorize should be the business of the {{IAuthority}} (I'm personally not 
against that). But the more I think about it, the more I'm convince that 
forcing users and their access rights to be immutable is A Bad Idea.

 move checkaccess into statement.prepare
 ---

 Key: CASSANDRA-4295
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4295
 Project: Cassandra
  Issue Type: Improvement
  Components: API
Affects Versions: 1.1.0
Reporter: Jonathan Ellis
Assignee: Pavel Yaskevich
Priority: Minor
 Fix For: 1.1.3

 Attachments: CASSANDRA-4295.patch


 there's no need to redo this every execution since the schema, tables, and 
 users involved should all be immutable

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4038) Investigate improving the dynamic snitch with reservoir sampling

2012-07-13 Thread Pavel Yaskevich (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413662#comment-13413662
 ] 

Pavel Yaskevich commented on CASSANDRA-4038:


I think it's worth pursuing as that would remove the work we are doing now by 
restricting sampling to window size and number of updates in the interval, 
calculating age of each response arrival, as well as improve sampling by moving 
to exponential decay function. There is already implementation available by 
Apache 2.0 License 
https://github.com/codahale/metrics/blob/master/metrics-core/src/main/java/com/yammer/metrics/stats/ExponentiallyDecayingSample.java

 Investigate improving the dynamic snitch with reservoir sampling
 

 Key: CASSANDRA-4038
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4038
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Brandon Williams
Assignee: Pavel Yaskevich
 Fix For: 1.2


 Dsnitch's UPDATES_PER_INTERVAL and WINDOW_SIZE are chosen somewhat 
 arbitrarily.  A better fit may be something similar to Metric's 
 ExponentiallyDecayingSample, where more recent information is weighted 
 heavier than past information, and reservoir sampling would also be an 
 efficient way of keeping a statistically significant sample rather than 
 refusing updates after UPDATES_PER_INTERVAL and only keeping WINDOW_SIZE 
 amount.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-4411) Assertion with LCS compaction


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

Sylvain Lebresne updated CASSANDRA-4411:


Attachment: 0001-Add-debugging-info-for-LCS.txt

Unfortunately the log doesn't give us much to chew on.

I've actually be able to reproduce this once (using stress). Unfortunately, I 
hadn't added more debugging yet and since I added more debug info I haven't 
been able to reproduce (despite having retried from scratch like 3 times 
letting it run for multiple hours each time).

So I'm attaching a simple patch that adds more debugging. If you guys can try 
applying the patch and see if you can reproduce. If so, the log file produced 
should be helpful. I'll note that it is preferable to *not* turn DEBUG logging 
with this patch as this is not useful and would only generate awfully large 
logs.


 Assertion with LCS compaction
 -

 Key: CASSANDRA-4411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2
Reporter: Anton Winter
 Fix For: 1.1.3

 Attachments: 0001-Add-debugging-info-for-LCS.txt, 
 assertion.system.log, system.log


 As instructed in CASSANDRA-4321 I have raised this issue as a continuation of 
 that issue as it appears the problem still exists.
 I have repeatedly run sstablescrub across all my nodes after the 1.1.2 
 upgrade until sstablescrub shows no errors.  The exceptions described in 
 CASSANDRA-4321 do not occur as frequently now but the integrity check still 
 throws exceptions on a number of nodes.  Once those exceptions occur 
 compactionstats shows a large number of pending tasks with no progression 
 afterwards.
 {code}
 ERROR [CompactionExecutor:150] 2012-07-05 04:26:15,570 
 AbstractCassandraDaemon.java (line 134) Exception in thread 
 Thread[CompactionExecutor:150,1,main]
 java.lang.AssertionError
 at 
 org.apache.cassandra.db.compaction.LeveledManifest.promote(LeveledManifest.java:214)
 at 
 org.apache.cassandra.db.compaction.LeveledCompactionStrategy.handleNotification(LeveledCompactionStrategy.java:158)
 at 
 org.apache.cassandra.db.DataTracker.notifySSTablesChanged(DataTracker.java:531)
 at 
 org.apache.cassandra.db.DataTracker.replaceCompactedSSTables(DataTracker.java:254)
 at 
 org.apache.cassandra.db.ColumnFamilyStore.replaceCompactedSSTables(ColumnFamilyStore.java:978)
 at 
 org.apache.cassandra.db.compaction.CompactionTask.execute(CompactionTask.java:200)
 at 
 org.apache.cassandra.db.compaction.LeveledCompactionTask.execute(LeveledCompactionTask.java:50)
 at 
 org.apache.cassandra.db.compaction.CompactionManager$1.runMayThrow(CompactionManager.java:150)
 at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:636)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-4411) Assertion with LCS compaction

2012-07-13 Thread Rudolf VanderLeeden (JIRA)


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

Rudolf VanderLeeden updated CASSANDRA-4411:
---

Attachment: (was: assertion.system.log)

 Assertion with LCS compaction
 -

 Key: CASSANDRA-4411
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4411
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2
Reporter: Anton Winter
 Fix For: 1.1.3

 Attachments: 0001-Add-debugging-info-for-LCS.txt, system.log


 As instructed in CASSANDRA-4321 I have raised this issue as a continuation of 
 that issue as it appears the problem still exists.
 I have repeatedly run sstablescrub across all my nodes after the 1.1.2 
 upgrade until sstablescrub shows no errors.  The exceptions described in 
 CASSANDRA-4321 do not occur as frequently now but the integrity check still 
 throws exceptions on a number of nodes.  Once those exceptions occur 
 compactionstats shows a large number of pending tasks with no progression 
 afterwards.
 {code}
 ERROR [CompactionExecutor:150] 2012-07-05 04:26:15,570 
 AbstractCassandraDaemon.java (line 134) Exception in thread 
 Thread[CompactionExecutor:150,1,main]
 java.lang.AssertionError
 at 
 org.apache.cassandra.db.compaction.LeveledManifest.promote(LeveledManifest.java:214)
 at 
 org.apache.cassandra.db.compaction.LeveledCompactionStrategy.handleNotification(LeveledCompactionStrategy.java:158)
 at 
 org.apache.cassandra.db.DataTracker.notifySSTablesChanged(DataTracker.java:531)
 at 
 org.apache.cassandra.db.DataTracker.replaceCompactedSSTables(DataTracker.java:254)
 at 
 org.apache.cassandra.db.ColumnFamilyStore.replaceCompactedSSTables(ColumnFamilyStore.java:978)
 at 
 org.apache.cassandra.db.compaction.CompactionTask.execute(CompactionTask.java:200)
 at 
 org.apache.cassandra.db.compaction.LeveledCompactionTask.execute(LeveledCompactionTask.java:50)
 at 
 org.apache.cassandra.db.compaction.CompactionManager$1.runMayThrow(CompactionManager.java:150)
 at 
 org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:636)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[2/3] git commit: Pig: support for composite row keys, writing composites Patch by Dirkjan Bussink, reviewed by brandonwilliams for CASSANDRA-4144

Pig: support for composite row keys, writing composites
Patch by Dirkjan Bussink, reviewed by brandonwilliams for CASSANDRA-4144


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

Branch: refs/heads/trunk
Commit: 7f6cc5ef6cad831061dc5cb75f5623f949ab7ca2
Parents: 962b23b
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Jul 13 10:38:15 2012 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Jul 13 10:38:15 2012 -0500

--
 examples/pig/test/populate-cli.txt |   20 +++
 examples/pig/test/test_storage.pig |   17 +-
 .../cassandra/hadoop/pig/CassandraStorage.java |   44 +-
 3 files changed, 76 insertions(+), 5 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/7f6cc5ef/examples/pig/test/populate-cli.txt
--
diff --git a/examples/pig/test/populate-cli.txt 
b/examples/pig/test/populate-cli.txt
index 7ec6cd6..1f59642 100644
--- a/examples/pig/test/populate-cli.txt
+++ b/examples/pig/test/populate-cli.txt
@@ -112,3 +112,23 @@ set CompoInt['clock']['1:0'] = 'z';
 set CompoInt['clock']['1:30'] = '';
 set CompoInt['clock']['2:30'] = 'daddy?';
 set CompoInt['clock']['6:30'] = 'coffee...';
+
+create column family CompoIntCopy
+with key_validation_class = UTF8Type
+and default_validation_class = UTF8Type
+and comparator = 'CompositeType(LongType,LongType)';
+
+create column family CompoKey
+with key_validation_class = 'CompositeType(UTF8Type,LongType)'
+and default_validation_class = UTF8Type
+and comparator = LongType;
+
+set CompoKey['clock:10']['1'] = 'z';
+set CompoKey['clock:20']['1'] = '';
+set CompoKey['clock:30']['2'] = 'daddy?';
+set CompoKey['clock:40']['6'] = 'coffee...';
+
+create column family CompoKeyCopy
+with key_validation_class = 'CompositeType(UTF8Type,LongType)'
+and default_validation_class = UTF8Type
+and comparator = LongType;

http://git-wip-us.apache.org/repos/asf/cassandra/blob/7f6cc5ef/examples/pig/test/test_storage.pig
--
diff --git a/examples/pig/test/test_storage.pig 
b/examples/pig/test/test_storage.pig
index a0157f7..026cb02 100644
--- a/examples/pig/test/test_storage.pig
+++ b/examples/pig/test/test_storage.pig
@@ -67,4 +67,19 @@ night = foreach night generate 
(int)columns::name.$0+(double)columns::name.$1/60
 -- What happens at the darkest hour?
 darkest = filter night by hour  2 and hour  5;
 
-dump darkest;
\ No newline at end of file
+dump darkest;
+
+compo_int_rows = LOAD 'cassandra://PigTest/CompoInt' USING CassandraStorage();
+STORE compo_int_rows INTO 'cassandra://PigTest/CompoIntCopy' USING 
CassandraStorage();
+
+--
+--  Test CompositeKey
+--
+
+compokeys = load 'cassandra://PigTest/CompoKey' using CassandraStorage();
+compokeys = filter compokeys by key.$1 == 40;
+
+dump compokeys;
+
+compo_key_rows = LOAD 'cassandra://PigTest/CompoKey' USING CassandraStorage();
+STORE compo_key_rows INTO 'cassandra://PigTest/CompoKeyCopy' USING 
CassandraStorage();

http://git-wip-us.apache.org/repos/asf/cassandra/blob/7f6cc5ef/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
--
diff --git a/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java 
b/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
index 5742cb9..454330c 100644
--- a/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
+++ b/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
@@ -131,7 +131,7 @@ public class CassandraStorage extends LoadFunc implements 
StoreFuncInterface, Lo
 {
 return limit;
 }
-
+
 public Tuple getNextWide() throws IOException
 {
 CfDef cfDef = getCfDef(loadSignature);
@@ -223,10 +223,10 @@ public class CassandraStorage extends LoadFunc implements 
StoreFuncInterface, Lo
 
 // output tuple, will hold the key, each indexed column in a 
tuple, then a bag of the rest
 // NOTE: we're setting the tuple size here only for the key so we 
can use setTupleValue on it
-Tuple tuple = TupleFactory.getInstance().newTuple(1);
+
+Tuple tuple = keyToTuple(key, cfDef, 
parseType(cfDef.getKey_validation_class()));
 DefaultDataBag bag = new DefaultDataBag();
-// set the key
-setTupleValue(tuple, 0, 
getDefaultMarshallers(cfDef).get(2).compose(key));
+
 // we must add all the indexed columns first to match the schema

[3/3] git commit: Pig: support for composite row keys, writing composites Patch by Dirkjan Bussink, reviewed by brandonwilliams for CASSANDRA-4144

Pig: support for composite row keys, writing composites
Patch by Dirkjan Bussink, reviewed by brandonwilliams for CASSANDRA-4144


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

Branch: refs/heads/cassandra-1.1
Commit: 7f6cc5ef6cad831061dc5cb75f5623f949ab7ca2
Parents: 962b23b
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Jul 13 10:38:15 2012 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Jul 13 10:38:15 2012 -0500

--
 examples/pig/test/populate-cli.txt |   20 +++
 examples/pig/test/test_storage.pig |   17 +-
 .../cassandra/hadoop/pig/CassandraStorage.java |   44 +-
 3 files changed, 76 insertions(+), 5 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/7f6cc5ef/examples/pig/test/populate-cli.txt
--
diff --git a/examples/pig/test/populate-cli.txt 
b/examples/pig/test/populate-cli.txt
index 7ec6cd6..1f59642 100644
--- a/examples/pig/test/populate-cli.txt
+++ b/examples/pig/test/populate-cli.txt
@@ -112,3 +112,23 @@ set CompoInt['clock']['1:0'] = 'z';
 set CompoInt['clock']['1:30'] = '';
 set CompoInt['clock']['2:30'] = 'daddy?';
 set CompoInt['clock']['6:30'] = 'coffee...';
+
+create column family CompoIntCopy
+with key_validation_class = UTF8Type
+and default_validation_class = UTF8Type
+and comparator = 'CompositeType(LongType,LongType)';
+
+create column family CompoKey
+with key_validation_class = 'CompositeType(UTF8Type,LongType)'
+and default_validation_class = UTF8Type
+and comparator = LongType;
+
+set CompoKey['clock:10']['1'] = 'z';
+set CompoKey['clock:20']['1'] = '';
+set CompoKey['clock:30']['2'] = 'daddy?';
+set CompoKey['clock:40']['6'] = 'coffee...';
+
+create column family CompoKeyCopy
+with key_validation_class = 'CompositeType(UTF8Type,LongType)'
+and default_validation_class = UTF8Type
+and comparator = LongType;

http://git-wip-us.apache.org/repos/asf/cassandra/blob/7f6cc5ef/examples/pig/test/test_storage.pig
--
diff --git a/examples/pig/test/test_storage.pig 
b/examples/pig/test/test_storage.pig
index a0157f7..026cb02 100644
--- a/examples/pig/test/test_storage.pig
+++ b/examples/pig/test/test_storage.pig
@@ -67,4 +67,19 @@ night = foreach night generate 
(int)columns::name.$0+(double)columns::name.$1/60
 -- What happens at the darkest hour?
 darkest = filter night by hour  2 and hour  5;
 
-dump darkest;
\ No newline at end of file
+dump darkest;
+
+compo_int_rows = LOAD 'cassandra://PigTest/CompoInt' USING CassandraStorage();
+STORE compo_int_rows INTO 'cassandra://PigTest/CompoIntCopy' USING 
CassandraStorage();
+
+--
+--  Test CompositeKey
+--
+
+compokeys = load 'cassandra://PigTest/CompoKey' using CassandraStorage();
+compokeys = filter compokeys by key.$1 == 40;
+
+dump compokeys;
+
+compo_key_rows = LOAD 'cassandra://PigTest/CompoKey' USING CassandraStorage();
+STORE compo_key_rows INTO 'cassandra://PigTest/CompoKeyCopy' USING 
CassandraStorage();

http://git-wip-us.apache.org/repos/asf/cassandra/blob/7f6cc5ef/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
--
diff --git a/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java 
b/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
index 5742cb9..454330c 100644
--- a/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
+++ b/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
@@ -131,7 +131,7 @@ public class CassandraStorage extends LoadFunc implements 
StoreFuncInterface, Lo
 {
 return limit;
 }
-
+
 public Tuple getNextWide() throws IOException
 {
 CfDef cfDef = getCfDef(loadSignature);
@@ -223,10 +223,10 @@ public class CassandraStorage extends LoadFunc implements 
StoreFuncInterface, Lo
 
 // output tuple, will hold the key, each indexed column in a 
tuple, then a bag of the rest
 // NOTE: we're setting the tuple size here only for the key so we 
can use setTupleValue on it
-Tuple tuple = TupleFactory.getInstance().newTuple(1);
+
+Tuple tuple = keyToTuple(key, cfDef, 
parseType(cfDef.getKey_validation_class()));
 DefaultDataBag bag = new DefaultDataBag();
-// set the key
-setTupleValue(tuple, 0, 
getDefaultMarshallers(cfDef).get(2).compose(key));
+
 // we must add all the indexed columns first to match the schema

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

Updated Branches:
  refs/heads/cassandra-1.1 962b23ba0 - 7f6cc5ef6
  refs/heads/trunk e117cbe2b - 2f4c7c4dc


Merge branch 'cassandra-1.1' into trunk


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

Branch: refs/heads/trunk
Commit: 2f4c7c4dc3ab78d1051ec8f445bbb52c6593abf2
Parents: e117cbe 7f6cc5e
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Jul 13 10:39:19 2012 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Jul 13 10:39:19 2012 -0500

--
 examples/pig/test/populate-cli.txt |   20 +++
 examples/pig/test/test_storage.pig |   17 +-
 .../cassandra/hadoop/pig/CassandraStorage.java |   44 +-
 3 files changed, 76 insertions(+), 5 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/2f4c7c4d/src/java/org/apache/cassandra/hadoop/pig/CassandraStorage.java
--

[jira] [Resolved] (CASSANDRA-4144) Pig: Composite column support for row key


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

Brandon Williams resolved CASSANDRA-4144.
-

   Resolution: Fixed
Fix Version/s: 1.1.3
 Assignee: Dirkjan Bussink

Committed, thanks!

I'll note that composite keys aren't supported for wide rows, but the wide row 
logic is quite hairy and relies on key equality to work, where converting it to 
a tuple would be especially troublesome.  So, I'm fine with saying composite 
keys are not supported with wide rows, just like indexes.

 Pig: Composite column support for row key
 -

 Key: CASSANDRA-4144
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4144
 Project: Cassandra
  Issue Type: Improvement
  Components: Contrib
Affects Versions: 1.0.9
Reporter: janwar dinata
Assignee: Dirkjan Bussink
Priority: Minor
  Labels: Pig, hadoop
 Fix For: 1.1.3

 Attachments: 
 0001-Add-support-for-composite-row-keys-in-Cassandra-PIG.patch, 
 0002-Add-test-and-support-for-writing-composite-values.patch


 Currently Pig only understands composite columns not composite row keys.
 Support for querying column family that has composite type for its 
 key_validation_class will be nice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[4/4] git commit: change SP to throw UE when hint queue is full instead of TOE, since we guarantee that no changes are performed patch by jbellis; reviewed by slebresne for CASSANDRA-4414

change SP to throw UE when hint queue is full instead of TOE, since we 
guarantee that no changes are performed
patch by jbellis; reviewed by slebresne for CASSANDRA-4414


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

Branch: refs/heads/trunk
Commit: 200ba86477f49939630b75f989afe07a2d91185a
Parents: 2f4c7c4
Author: Jonathan Ellis jbel...@apache.org
Authored: Wed Jul 11 18:10:02 2012 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Fri Jul 13 11:31:24 2012 -0500

--
 .../org/apache/cassandra/db/CounterColumn.java |3 ++-
 .../org/apache/cassandra/service/StorageProxy.java |   10 +-
 2 files changed, 7 insertions(+), 6 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/200ba864/src/java/org/apache/cassandra/db/CounterColumn.java
--
diff --git a/src/java/org/apache/cassandra/db/CounterColumn.java 
b/src/java/org/apache/cassandra/db/CounterColumn.java
index 4b0bdc2..7ea6514 100644
--- a/src/java/org/apache/cassandra/db/CounterColumn.java
+++ b/src/java/org/apache/cassandra/db/CounterColumn.java
@@ -366,7 +366,8 @@ public class CounterColumn extends Column
 
 StorageProxy.performWrite(rm, ConsistencyLevel.ANY, localDataCenter, 
new StorageProxy.WritePerformer()
 {
-public void apply(IMutation mutation, CollectionInetAddress 
targets, IWriteResponseHandler responseHandler, String localDataCenter, 
ConsistencyLevel consistency_level) throws IOException, TimeoutException
+public void apply(IMutation mutation, CollectionInetAddress 
targets, IWriteResponseHandler responseHandler, String localDataCenter, 
ConsistencyLevel consistency_level)
+throws IOException, TimeoutException, UnavailableException
 {
 // We should only send to the remote replica, not the local one
 targets.remove(local);

http://git-wip-us.apache.org/repos/asf/cassandra/blob/200ba864/src/java/org/apache/cassandra/service/StorageProxy.java
--
diff --git a/src/java/org/apache/cassandra/service/StorageProxy.java 
b/src/java/org/apache/cassandra/service/StorageProxy.java
index 8ae063b..7a79c06 100644
--- a/src/java/org/apache/cassandra/service/StorageProxy.java
+++ b/src/java/org/apache/cassandra/service/StorageProxy.java
@@ -112,7 +112,7 @@ public class StorageProxy implements StorageProxyMBean
   IWriteResponseHandler responseHandler,
   String localDataCenter,
   ConsistencyLevel consistency_level)
-throws IOException, TimeoutException
+throws IOException, TimeoutException, UnavailableException
 {
 assert mutation instanceof RowMutation;
 sendToHintedEndpoints((RowMutation) mutation, targets, 
responseHandler, localDataCenter, consistency_level);
@@ -287,7 +287,7 @@ public class StorageProxy implements StorageProxyMBean
   IWriteResponseHandler 
responseHandler,
   String localDataCenter,
   ConsistencyLevel 
consistency_level)
-throws IOException, TimeoutException
+throws IOException, TimeoutException, UnavailableException
 {
 // Multimap that holds onto all the messages and addresses meant for a 
specific datacenter
 MapString, MultimapMessageOut, InetAddress dcMessages = new 
HashMapString, MultimapMessageOut, InetAddress(targets.size());
@@ -302,7 +302,7 @@ public class StorageProxy implements StorageProxyMBean
 if (totalHintsInProgress.get()  maxHintsInProgress
  (hintsInProgress.get(destination).get()  0  
shouldHint(destination)))
 {
-throw new TimeoutException();
+throw new UnavailableException();
 }
 
 if (FailureDetector.instance.isAlive(destination))
@@ -576,7 +576,7 @@ public class StorageProxy implements StorageProxyMBean
 // and we want to avoid blocking too much the MUTATION 
stage
 
StageManager.getStage(Stage.REPLICATE_ON_WRITE).execute(new 
DroppableRunnable(MessagingService.Verb.READ)
 {
-public void runMayThrow() throws IOException, 
TimeoutException
+public void runMayThrow() throws IOException, 
TimeoutException, UnavailableException
 {

[2/4] git commit: add ack count to TimedOutException on writes patch by jbellis; reviewed by slebresne for CASSANDRA-4414

add ack count to TimedOutException on writes
patch by jbellis; reviewed by slebresne for CASSANDRA-4414


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

Branch: refs/heads/trunk
Commit: c9a13c3c452d3e9e49bca158da93f9a9bbae7379
Parents: 2711548
Author: Jonathan Ellis jbel...@apache.org
Authored: Wed Jul 11 18:13:25 2012 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Fri Jul 13 11:32:12 2012 -0500

--
 interface/cassandra.thrift |8 +-
 .../org/apache/cassandra/thrift/Cassandra.java |4 +
 .../org/apache/cassandra/thrift/Constants.java |2 +-
 .../apache/cassandra/thrift/TimedOutException.java |  118 ++-
 .../org/apache/cassandra/cql/QueryProcessor.java   |   17 +--
 .../cql3/statements/ModificationStatement.java |9 +-
 .../org/apache/cassandra/db/CounterColumn.java |2 +-
 .../cassandra/db/CounterMutationVerbHandler.java   |7 +-
 .../apache/cassandra/db/HintedHandOffManager.java  |4 +-
 .../service/AbstractWriteResponseHandler.java  |7 +-
 .../DatacenterSyncWriteResponseHandler.java|   14 ++-
 .../cassandra/service/IWriteResponseHandler.java   |3 +-
 .../org/apache/cassandra/service/StorageProxy.java |   18 +-
 .../cassandra/service/WriteResponseHandler.java|   10 +-
 .../apache/cassandra/thrift/CassandraServer.java   |   17 +--
 15 files changed, 182 insertions(+), 58 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/c9a13c3c/interface/cassandra.thrift
--
diff --git a/interface/cassandra.thrift b/interface/cassandra.thrift
index 6df9628..1041661 100644
--- a/interface/cassandra.thrift
+++ b/interface/cassandra.thrift
@@ -55,7 +55,7 @@ namespace rb CassandraThrift
 # An effort should be made not to break forward-client-compatibility either
 # (e.g. one should avoid removing obsolete fields from the IDL), but no
 # guarantees in this respect are made by the Cassandra project.
-const string VERSION = 19.32.0
+const string VERSION = 19.33.0
 
 
 #
@@ -140,6 +140,12 @@ exception UnavailableException {
 
 /** RPC timeout was exceeded.  either a node failed mid-operation, or load was 
too high, or the requested op was too large. */
 exception TimedOutException {
+/** 
+ * if a write operation was acknowledged some replicas but not enough to 
+ * satisfy the required ConsistencyLevel, the number of successful 
+ * replies will be given here
+ */
+1: optional i32 acknowledged_by
 }
 
 /** invalid authentication request (invalid keyspace, user does not exist, or 
credentials invalid) */

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c9a13c3c/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java
--
diff --git 
a/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java 
b/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java
index 1c6ec69..ec4982e 100644
--- a/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java
+++ b/interface/thrift/gen-java/org/apache/cassandra/thrift/Cassandra.java
@@ -17817,6 +17817,8 @@ public class Cassandra {
 
 private void readObject(java.io.ObjectInputStream in) throws 
java.io.IOException, ClassNotFoundException {
   try {
+// it doesn't seem like you should have to do this, but java 
serialization is wacky, and doesn't call the default constructor.
+__isset_bit_vector = new BitSet(1);
 read(new org.apache.thrift.protocol.TCompactProtocol(new 
org.apache.thrift.transport.TIOStreamTransport(in)));
   } catch (org.apache.thrift.TException te) {
 throw new java.io.IOException(te);
@@ -34876,6 +34878,8 @@ public class Cassandra {
 
 private void readObject(java.io.ObjectInputStream in) throws 
java.io.IOException, ClassNotFoundException {
   try {
+// it doesn't seem like you should have to do this, but java 
serialization is wacky, and doesn't call the default constructor.
+__isset_bit_vector = new BitSet(1);
 read(new org.apache.thrift.protocol.TCompactProtocol(new 
org.apache.thrift.transport.TIOStreamTransport(in)));
   } catch (org.apache.thrift.TException te) {
 throw new java.io.IOException(te);

http://git-wip-us.apache.org/repos/asf/cassandra/blob/c9a13c3c/interface/thrift/gen-java/org/apache/cassandra/thrift/Constants.java
--
diff --git 
a/interface/thrift/gen-java/org/apache/cassandra/thrift/Constants.java

[1/4] git commit: CS.schedule throws UE instead of TOE patch by jbellis; reviewed by slebresne for CASSANDRA-4414

Updated Branches:
  refs/heads/trunk 2f4c7c4dc - 13f8eee99


CS.schedule throws UE instead of TOE
patch by jbellis; reviewed by slebresne for CASSANDRA-4414


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

Branch: refs/heads/trunk
Commit: 13f8eee99d0acb7063eab5dab7a8980d1b71a3b9
Parents: c9a13c3
Author: Jonathan Ellis jbel...@apache.org
Authored: Wed Jul 11 23:29:37 2012 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Fri Jul 13 11:32:21 2012 -0500

--
 .../apache/cassandra/thrift/CassandraServer.java   |   11 +--
 1 files changed, 9 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/13f8eee9/src/java/org/apache/cassandra/thrift/CassandraServer.java
--
diff --git a/src/java/org/apache/cassandra/thrift/CassandraServer.java 
b/src/java/org/apache/cassandra/thrift/CassandraServer.java
index 15084c6..e594236 100644
--- a/src/java/org/apache/cassandra/thrift/CassandraServer.java
+++ b/src/java/org/apache/cassandra/thrift/CassandraServer.java
@@ -893,9 +893,16 @@ public class CassandraServer implements Cassandra.Iface
 /**
  * Schedule the current thread for access to the required services
  */
-private void schedule(long timeoutMS) throws TimeoutException
+private void schedule(long timeoutMS) throws UnavailableException
 {
-requestScheduler.queue(Thread.currentThread(), 
state().getSchedulingValue(), timeoutMS);
+try
+{
+requestScheduler.queue(Thread.currentThread(), 
state().getSchedulingValue(), timeoutMS);
+}
+catch (TimeoutException e)
+{
+throw new UnavailableException();
+}
 }
 
 /**

[3/4] git commit: formatting

formatting


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

Branch: refs/heads/trunk
Commit: 2711548e00658c44ddf1807f73a872dfad5d709a
Parents: 200ba86
Author: Jonathan Ellis jbel...@apache.org
Authored: Wed Jul 11 18:11:01 2012 -0500
Committer: Jonathan Ellis jbel...@apache.org
Committed: Fri Jul 13 11:32:05 2012 -0500

--
 .../org/apache/cassandra/service/StorageProxy.java |   12 ++--
 1 files changed, 6 insertions(+), 6 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/2711548e/src/java/org/apache/cassandra/service/StorageProxy.java
--
diff --git a/src/java/org/apache/cassandra/service/StorageProxy.java 
b/src/java/org/apache/cassandra/service/StorageProxy.java
index 7a79c06..58cc99d 100644
--- a/src/java/org/apache/cassandra/service/StorageProxy.java
+++ b/src/java/org/apache/cassandra/service/StorageProxy.java
@@ -283,10 +283,10 @@ public class StorageProxy implements StorageProxyMBean
  * @throws TimeoutException if the hints cannot be written/enqueued
  */
 public static void sendToHintedEndpoints(final RowMutation rm,
-  CollectionInetAddress targets,
-  IWriteResponseHandler 
responseHandler,
-  String localDataCenter,
-  ConsistencyLevel 
consistency_level)
+ CollectionInetAddress targets,
+ IWriteResponseHandler 
responseHandler,
+ String localDataCenter,
+ ConsistencyLevel 
consistency_level)
 throws IOException, TimeoutException, UnavailableException
 {
 // Multimap that holds onto all the messages and addresses meant for a 
specific datacenter
@@ -321,8 +321,8 @@ public class StorageProxy implements StorageProxyMBean
 MultimapMessageOut, InetAddress messages = 
dcMessages.get(dc);
 if (messages == null)
 {
-   messages = HashMultimap.create();
-   dcMessages.put(dc, messages);
+messages = HashMultimap.create();
+dcMessages.put(dc, messages);
 }
 
 messages.put(rm.createMessage(), destination);

[jira] [Commented] (CASSANDRA-4436) Counters in columns don't preserve correct values after cluster restart

[
https://issues.apache.org/jira/browse/CASSANDRA-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413881#comment-13413881
]

Sylvain Lebresne commented on CASSANDRA-4436:
-

Can you reproduce every time with those steps? I tried reproducing with those
exact steps (as far as I can tell) a few times on both 1.0 and 1.1 (the counter
code didn't change much between 1.0 and 1.1) and wasn't able to reproduce.

Counters in columns don't preserve correct values after cluster restart
---

Key: CASSANDRA-4436
URL: https://issues.apache.org/jira/browse/CASSANDRA-4436
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.0.10
Reporter: Peter Velas

Similar to #3821. but affecting normal columns.
Set up a 2-node cluster with rf=2.
1. Create a counter column family and increment a 100 keys in loop 5000
times.
2. Then make a rolling restart to cluster.
3. Again increment another 5000 times.
4. Make a rolling restart to cluster.
5. Again increment another 5000 times.
6. Make a rolling restart to cluster.
After step 6 we were able to reproduce bug with bad counter values.
Expected values were 15 000. Values returned from cluster are higher then
15000 + some random number.
Rolling restarts are done with nodetool drain. Always waiting until second
node discover its down then kill java process.

[jira] [Updated] (CASSANDRA-4234) Add tombstone-removal compaction to LCS

2012-07-13 Thread Yuki Morishita (JIRA)


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

Yuki Morishita updated CASSANDRA-4234:
--

Attachment: 4234.txt

Attaching patch with above two points corrected.

 Add tombstone-removal compaction to LCS
 ---

 Key: CASSANDRA-4234
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4234
 Project: Cassandra
  Issue Type: Improvement
Affects Versions: 1.2
Reporter: Jonathan Ellis
Assignee: Yuki Morishita
Priority: Minor
  Labels: compaction
 Fix For: 1.2

 Attachments: 4234.txt, 4234.txt


 CASSANDRA-3442 will recompact sstables with high levels of expired 
 tombstones, but only under SCS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-3647) Support set and map value types in CQL

[
https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413922#comment-13413922
]

Jonathan Ellis commented on CASSANDRA-3647:
---

Pushed some tweaks to https://github.com/jbellis/cassandra/commits/3647-4. In
particular, renamed the position compare/validate overloads to be more clear
what they are for. With that clarified, I think it's worth letting
polymorphism do the branch here, so having them in AbstractType is a good thing.

I agree that superficially isComposite() would be a good addition to
AbstractType... but the way we use instanceof here, I think DCT would have to
return false, which would be pretty confusing. So instanceof looks like the
lesser evil.

I think the current approach for collection representation at the Antlr level
is reasonable. It may be that Pavel's idea is better but I don't think we're
going to make more progress on that w/o actually coding it up. So if you want
to give that a try in a separate ticket Pavel, that's fine, but I don't think
we should block this.

Overall +1 from me.

Support set and map value types in CQL
--

Key: CASSANDRA-3647
URL: https://issues.apache.org/jira/browse/CASSANDRA-3647
Project: Cassandra
Issue Type: New Feature
Components: API, Core
Reporter: Jonathan Ellis
Assignee: Sylvain Lebresne
Labels: cql
Fix For: 1.2

Composite columns introduce the ability to have arbitrarily nested data in a
Cassandra row. We should expose this through CQL.

[jira] [Updated] (CASSANDRA-4427) Restarting a failed bootstrap instajoins the ring


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

Brandon Williams updated CASSANDRA-4427:


Attachment: 4427-v2.txt

v2 takes a different approach that Sylvain kindly suggested, and changes the 
bootstrap flag from a boolean to a 3-way value so that we can detect previous 
attempts that failed, and try again.

 Restarting a failed bootstrap instajoins the ring
 -

 Key: CASSANDRA-4427
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4427
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.0
Reporter: Brandon Williams
Assignee: Brandon Williams
 Fix For: 1.0.11, 1.1.3

 Attachments: 4427-v2.txt, 4427.txt


 I think when we made auto_bootstrap = true the default, we broke the check 
 for the bootstrap flag, creating a dangerous situation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

git commit: Track tombstone for LCS; patch by yukim reviewed by jbellis for CASSANDRA-4234

2012-07-13 Thread yukim

Updated Branches:
  refs/heads/trunk 13f8eee99 - 0091af932


Track tombstone for LCS; patch by yukim reviewed by jbellis for CASSANDRA-4234


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

Branch: refs/heads/trunk
Commit: 0091af932c6ef65a0a5917f123fe24398b79c079
Parents: 13f8eee
Author: Yuki Morishita yu...@apache.org
Authored: Fri Jul 13 13:17:51 2012 -0500
Committer: Yuki Morishita yu...@apache.org
Committed: Fri Jul 13 13:17:51 2012 -0500

--
 CHANGES.txt|2 +-
 .../db/compaction/AbstractCompactionStrategy.java  |   44 
 .../db/compaction/LeveledCompactionStrategy.java   |   45 -
 .../cassandra/db/compaction/LeveledManifest.java   |6 ++
 .../cassandra/db/compaction/OperationType.java |2 +
 .../compaction/SizeTieredCompactionStrategy.java   |   35 +-
 .../cassandra/db/compaction/CompactionsTest.java   |   53 ++-
 7 files changed, 148 insertions(+), 39 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/0091af93/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index 03e3fba..fb66fd6 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -12,7 +12,7 @@
  * add inter-node message compression (CASSANDRA-3127)
  * remove COPP (CASSANDRA-2479)
  * Track tombstone expiration and compact when tombstone content is
-   higher than a configurable threshold, default 20% (CASSANDRA-3442)
+   higher than a configurable threshold, default 20% (CASSANDRA-3442, 4234)
  * update MurmurHash to version 3 (CASSANDRA-2975)
  * (CLI) track elapsed time for `delete' operation (CASSANDRA-4060)
  * (CLI) jline version is bumped to 1.0 to properly  support

http://git-wip-us.apache.org/repos/asf/cassandra/blob/0091af93/src/java/org/apache/cassandra/db/compaction/AbstractCompactionStrategy.java
--
diff --git 
a/src/java/org/apache/cassandra/db/compaction/AbstractCompactionStrategy.java 
b/src/java/org/apache/cassandra/db/compaction/AbstractCompactionStrategy.java
index 41128b0..bf6c87f 100644
--- 
a/src/java/org/apache/cassandra/db/compaction/AbstractCompactionStrategy.java
+++ 
b/src/java/org/apache/cassandra/db/compaction/AbstractCompactionStrategy.java
@@ -38,15 +38,23 @@ import org.apache.cassandra.service.StorageService;
  */
 public abstract class AbstractCompactionStrategy
 {
+protected static final float DEFAULT_TOMBSTONE_THRESHOLD = 0.2f;
+protected static final String TOMBSTONE_THRESHOLD_KEY = 
tombstone_threshold;
+
 protected final ColumnFamilyStore cfs;
 protected final MapString, String options;
 
+protected float tombstoneThreshold;
+
 protected AbstractCompactionStrategy(ColumnFamilyStore cfs, MapString, 
String options)
 {
 assert cfs != null;
 this.cfs = cfs;
 this.options = options;
 
+String optionValue = options.get(TOMBSTONE_THRESHOLD_KEY);
+tombstoneThreshold = (null != optionValue) ? 
Float.parseFloat(optionValue) : DEFAULT_TOMBSTONE_THRESHOLD;
+
 // start compactions in five minutes (if no flushes have occurred by 
then to do so)
 Runnable runnable = new Runnable()
 {
@@ -146,4 +154,40 @@ public abstract class AbstractCompactionStrategy
 {
 return getScanners(toCompact, null);
 }
+
+/**
+ * @param sstable SSTable to check
+ * @param gcBefore time to drop tombstones
+ * @return true if given sstable's tombstones are expected to be removed
+ */
+protected boolean worthDroppingTombstones(SSTableReader sstable, int 
gcBefore)
+{
+double droppableRatio = 
sstable.getEstimatedDroppableTombstoneRatio(gcBefore);
+if (droppableRatio = tombstoneThreshold)
+return false;
+
+SetSSTableReader overlaps = 
cfs.getOverlappingSSTables(Collections.singleton(sstable));
+if (overlaps.isEmpty())
+{
+// there is no overlap, tombstones are safely droppable
+return true;
+}
+else
+{
+// what percentage of columns do we expect to compact outside of 
overlap?
+// first, calculate estimated keys that do not overlap
+long keys = sstable.estimatedKeys();
+SetRangeToken ranges = new HashSetRangeToken();
+for (SSTableReader overlap : overlaps)
+ranges.add(new RangeToken(overlap.first.token, 
overlap.last.token, overlap.partitioner));
+long remainingKeys = keys - sstable.estimatedKeysForRanges(ranges);
+

[jira] [Commented] (CASSANDRA-4427) Restarting a failed bootstrap instajoins the ring


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13413931#comment-13413931
 ] 

Jonathan Ellis commented on CASSANDRA-4427:
---

I think you're misreading the original seed logic...  !(isBootstrapped || 
isSeed) expands to !isBootstrapped  !isSeed.  Still need that so that 
single-node clusters don't try to bootstrap.

 Restarting a failed bootstrap instajoins the ring
 -

 Key: CASSANDRA-4427
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4427
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.0
Reporter: Brandon Williams
Assignee: Brandon Williams
 Fix For: 1.0.11, 1.1.3

 Attachments: 4427-v2.txt, 4427.txt


 I think when we made auto_bootstrap = true the default, we broke the check 
 for the bootstrap flag, creating a dangerous situation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CASSANDRA-3378) Allow configuration of storage protocol socket buffer

2012-07-13 Thread Vladimir Sverzhinsky (JIRA)


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

Vladimir Sverzhinsky reassigned CASSANDRA-3378:
---

Assignee: Vladimir Sverzhinsky  (was: Harish Doddi)

 Allow configuration of storage protocol socket buffer
 -

 Key: CASSANDRA-3378
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3378
 Project: Cassandra
  Issue Type: New Feature
  Components: Core
Reporter: Brandon Williams
Assignee: Vladimir Sverzhinsky
Priority: Minor
  Labels: lhf
 Fix For: 1.2


 Similar to rpc_[send,recv]_buff_size_in_bytes, we should expose this for high 
 latency connections.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CASSANDRA-2666) nodetool repair silently fails (no non-zero exit code) when repair did not happen

2012-07-13 Thread Vladimir Sverzhinsky (JIRA)


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

Vladimir Sverzhinsky reassigned CASSANDRA-2666:
---

Assignee: Vladimir Sverzhinsky

 nodetool repair silently fails (no non-zero exit code) when repair did not 
 happen
 -

 Key: CASSANDRA-2666
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2666
 Project: Cassandra
  Issue Type: Bug
  Components: Tools
Reporter: Peter Schuller
Assignee: Vladimir Sverzhinsky
Priority: Minor
  Labels: lhf

 In this particular example I tested with a neighbor down. system.log 
 correctly reports:
 INFO [manual-repair-65fb7826-77ae-4ad6-99e3-5aa94b03b97d] 2011-05-19 
 14:48:53,476 AntiEntropyService.java (line 767) Could not proceed on repair 
 because a neighbor (/XX.XX.XX.XX) is dead: 
 manual-repair-65fb7826-77ae-4ad6-99e3-5aa94b03b97d failed.
 But nodetool -h localhost repair || echo fail doesn't print fail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-4427) Restarting a failed bootstrap instajoins the ring


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

Brandon Williams updated CASSANDRA-4427:


Attachment: 4427-v3.txt

Oh, I see now.  v3 restores the seed check.

 Restarting a failed bootstrap instajoins the ring
 -

 Key: CASSANDRA-4427
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4427
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.0
Reporter: Brandon Williams
Assignee: Brandon Williams
 Fix For: 1.0.11, 1.1.3

 Attachments: 4427-v2.txt, 4427-v3.txt, 4427.txt


 I think when we made auto_bootstrap = true the default, we broke the check 
 for the bootstrap flag, creating a dangerous situation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Update of DebianPackaging by EricEvans

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The DebianPackaging page has been changed by EricEvans:
http://wiki.apache.org/cassandra/DebianPackaging?action=diffrev1=25rev2=26

- == Official Debian Package ==
+ == Official Package To Install On Debian(tm) (not a product of Debian(tm)) ==
  
  To install on Debian or Debian derivatives, use the following sources:

[jira] [Created] (CASSANDRA-4438) System reboot

2012-07-13 Thread Senthilvel Rangaswamy (JIRA)

Senthilvel Rangaswamy created CASSANDRA-4438:


 Summary: System reboot
 Key: CASSANDRA-4438
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4438
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2
 Environment: EC2, Amazon Linux, Ephemeral Store
Reporter: Senthilvel Rangaswamy


Since we deployed 1.1.2 we have been noticing random nodes in the ring
reboots often. There is no real info in any logs. It is happening on different
ec2 instances. So we can't say it is an instance problem. Any ideas on how to
find out what's causing this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

git commit: Default start_rpc to true in Config

Updated Branches:
  refs/heads/trunk 0091af932 - 1cb0ad5c4


Default start_rpc to true in Config


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

Branch: refs/heads/trunk
Commit: 1cb0ad5c402be4dbfa179f1fc35063c8fc6ef782
Parents: 0091af9
Author: Brandon Williams brandonwilli...@apache.org
Authored: Fri Jul 13 14:53:49 2012 -0500
Committer: Brandon Williams brandonwilli...@apache.org
Committed: Fri Jul 13 14:53:49 2012 -0500

--
 src/java/org/apache/cassandra/config/Config.java |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/1cb0ad5c/src/java/org/apache/cassandra/config/Config.java
--
diff --git a/src/java/org/apache/cassandra/config/Config.java 
b/src/java/org/apache/cassandra/config/Config.java
index afa1c54..f5f4ef6 100644
--- a/src/java/org/apache/cassandra/config/Config.java
+++ b/src/java/org/apache/cassandra/config/Config.java
@@ -65,7 +65,7 @@ public class Config
 public String listen_address;
 public String broadcast_address;
 
-public Boolean start_rpc = false;
+public Boolean start_rpc = true;
 public String rpc_address;
 public Integer rpc_port = 9160;
 public String rpc_server_type = sync;

[jira] [Resolved] (CASSANDRA-4438) System reboot


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

Jonathan Ellis resolved CASSANDRA-4438.
---

Resolution: Invalid

The user mailing list is a more appropriate troubleshooting venue.

 System reboot
 -

 Key: CASSANDRA-4438
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4438
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2
 Environment: EC2, Amazon Linux, Ephemeral Store
Reporter: Senthilvel Rangaswamy

 Since we deployed 1.1.2 we have been noticing random nodes in the ring
 reboots often. There is no real info in any logs. It is happening on different
 ec2 instances. So we can't say it is an instance problem. Any ideas on how to
 find out what's causing this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4438) System reboot

2012-07-13 Thread Rik Schneider (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414005#comment-13414005
 ] 

Rik Schneider commented on CASSANDRA-4438:
--

It appears to be load related. Once a node reboots once, it seems to go into a 
death spiral of bootstrapping causing a high load and the host reboots soon 
reboots again.

We are using the datastax RPM packages with EC2 multi region snitch on 8 nodes 
in each of 2 regions.



 System reboot
 -

 Key: CASSANDRA-4438
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4438
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2
 Environment: EC2, Amazon Linux, Ephemeral Store
Reporter: Senthilvel Rangaswamy

 Since we deployed 1.1.2 we have been noticing random nodes in the ring
 reboots often. There is no real info in any logs. It is happening on different
 ec2 instances. So we can't say it is an instance problem. Any ideas on how to
 find out what's causing this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Comment Edited] (CASSANDRA-4438) System reboot

2012-07-13 Thread Rik Schneider (JIRA)

[
https://issues.apache.org/jira/browse/CASSANDRA-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414005#comment-13414005
]

Rik Schneider edited comment on CASSANDRA-4438 at 7/13/12 8:08 PM:
---

It appears to be load related and is happening on multiple clusters. Once a
node reboots once, it seems to go into a death spiral of bootstrapping causing
a high load and the host reboots soon reboots again.

We are using the datastax RPM packages with EC2 multi region snitch on 8 nodes
in each of 2 regions.

was (Author: dawookie):
It appears to be load related. Once a node reboots once, it seems to go
into a death spiral of bootstrapping causing a high load and the host reboots
soon reboots again.

We are using the datastax RPM packages with EC2 multi region snitch on 8 nodes
in each of 2 regions.

System reboot
-

Key: CASSANDRA-4438
URL: https://issues.apache.org/jira/browse/CASSANDRA-4438
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.1.2
Environment: EC2, Amazon Linux, Ephemeral Store
Reporter: Senthilvel Rangaswamy

Since we deployed 1.1.2 we have been noticing random nodes in the ring
reboots often. There is no real info in any logs. It is happening on different
ec2 instances. So we can't say it is an instance problem. Any ideas on how to
find out what's causing this.

[jira] [Commented] (CASSANDRA-4438) System reboot


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414007#comment-13414007
 ] 

Brandon Williams commented on CASSANDRA-4438:
-

As noted, this belongs on the ML, not jira.

That said, since Amazon Linux is being used, I'll point you to CASSANDRA-4225

 System reboot
 -

 Key: CASSANDRA-4438
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4438
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2
 Environment: EC2, Amazon Linux, Ephemeral Store
Reporter: Senthilvel Rangaswamy

 Since we deployed 1.1.2 we have been noticing random nodes in the ring
 reboots often. There is no real info in any logs. It is happening on different
 ec2 instances. So we can't say it is an instance problem. Any ideas on how to
 find out what's causing this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CASSANDRA-4438) System reboot


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414006#comment-13414006
 ] 

Jonathan Ellis commented on CASSANDRA-4438:
---

Why would a node already part of the ring re-bootstrap?

 System reboot
 -

 Key: CASSANDRA-4438
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4438
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2
 Environment: EC2, Amazon Linux, Ephemeral Store
Reporter: Senthilvel Rangaswamy

 Since we deployed 1.1.2 we have been noticing random nodes in the ring
 reboots often. There is no real info in any logs. It is happening on different
 ec2 instances. So we can't say it is an instance problem. Any ideas on how to
 find out what's causing this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Update of DebianPackaging by EricEvans

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The DebianPackaging page has been changed by EricEvans:
http://wiki.apache.org/cassandra/DebianPackaging?action=diffrev1=26rev2=27

  == Official Package To Install On Debian(tm) (not a product of Debian(tm)) ==
+ 
+ ''Ironically, the ASF is unable to provide the basic HTTP hosting needed to 
support an APT repository.  Therefore, this repo should be considered 
deprecated.''
  
  To install on Debian or Debian derivatives, use the following sources:

[jira] [Updated] (CASSANDRA-4271) Exit status of bin/cassandra without -f is wrong


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

paul cannon updated CASSANDRA-4271:
---

Attachment: 0001-startup-script-returns-0-after-backgrounding.patch

Patch attached; also present in the 4271 branch in my github. Current version 
tagged pending/4271.

https://github.com/thepaul/cassandra/tree/4271

 Exit status of bin/cassandra without -f is wrong
 

 Key: CASSANDRA-4271
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4271
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Reporter: Tyler Hobbs
Assignee: paul cannon
Priority: Minor
 Fix For: 1.1.3

 Attachments: 0001-startup-script-returns-0-after-backgrounding.patch


 The launch_service() function returns {{$?}} after exec'ing java, and the 
 script then exits with that same status.
 The problem is that we do a {{[ ! -z $pidpath]  ...}} conditional 
 statment after exec'ing when the foreground flag isn't set.  The value of 
 {{$?}} then depends on that conditional and the statement, typically 
 returning 1, because {{$pidpath}} isn't set.  So, even if everything appears 
 to execute normally, you will get an exit status of 1 for the whole script.
 I suspect the right thing to do is just return 0 when backgrounding.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Update of DebianPackaging by EricEvans

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The DebianPackaging page has been changed by EricEvans:
http://wiki.apache.org/cassandra/DebianPackaging?action=diffrev1=27rev2=28

  == Official Package To Install On Debian(tm) (not a product of Debian(tm)) ==
  
- ''Ironically, the ASF is unable to provide the basic HTTP hosting needed to 
support an APT repository.  Therefore, this repo should be considered 
deprecated.''
+ ''Ironically, the ASF is unable to provide the basic HTTP hosting needed to 
support an APT repository, therefore this repo should be considered 
deprecated.''
  
  To install on Debian or Debian derivatives, use the following sources:

[jira] [Commented] (CASSANDRA-4234) Add tombstone-removal compaction to LCS

2012-07-13 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/CASSANDRA-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414057#comment-13414057
 ] 

Hudson commented on CASSANDRA-4234:
---

Integrated in Cassandra #1699 (See 
[https://builds.apache.org/job/Cassandra/1699/])
Track tombstone for LCS; patch by yukim reviewed by jbellis for 
CASSANDRA-4234 (Revision 0091af932c6ef65a0a5917f123fe24398b79c079)

 Result = ABORTED
yukim : 
Files : 
* src/java/org/apache/cassandra/db/compaction/SizeTieredCompactionStrategy.java
* src/java/org/apache/cassandra/db/compaction/OperationType.java
* src/java/org/apache/cassandra/db/compaction/LeveledCompactionStrategy.java
* CHANGES.txt
* test/unit/org/apache/cassandra/db/compaction/CompactionsTest.java
* src/java/org/apache/cassandra/db/compaction/LeveledManifest.java
* src/java/org/apache/cassandra/db/compaction/AbstractCompactionStrategy.java


 Add tombstone-removal compaction to LCS
 ---

 Key: CASSANDRA-4234
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4234
 Project: Cassandra
  Issue Type: Improvement
Affects Versions: 1.2
Reporter: Jonathan Ellis
Assignee: Yuki Morishita
Priority: Minor
  Labels: compaction
 Fix For: 1.2

 Attachments: 4234.txt, 4234.txt


 CASSANDRA-3442 will recompact sstables with high levels of expired 
 tombstones, but only under SCS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-4439) Updating column family using cassandra-cli results in Cannot modify index name

2012-07-13 Thread Alex Schultz (JIRA)

Alex Schultz created CASSANDRA-4439:
---

 Summary: Updating column family using cassandra-cli results in 
Cannot modify index name
 Key: CASSANDRA-4439
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4439
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.1.2
 Environment: cassandra 1.1.2, RHEL6.3, running under java-1.6.0-sun
Reporter: Alex Schultz


Using cassandra-cli the following update to a column family worked in 1.1.0:
{code}
create keyspace testing;
use testing;

create column family Album
with comparator = UTF8Type
and default_validation_class = UTF8Type
and column_metadata =
[
{column_name: profileId, validation_class: UTF8Type, index_type: KEYS}
];

update column family Album
and column_metadata =
[
{column_name: profileId, validation_class: UTF8Type, index_type: KEYS},
{column_name: postedDate, validation_class: LongType}
];
{code}

After upgrading to 1.1.2, the update statement fails with the following 
exception in system.log:
{quote}
ERROR [Thrift:16] 2012-07-13 14:51:54,558 CustomTThreadPoolServer.java (line 
204) Error occurred during processing of message.
java.lang.RuntimeException: java.util.concurrent.ExecutionException: 
java.io.IOException: org.apache.cassandra.config.ConfigurationException: Cannot 
modify index name
at 
org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:373)
at 
org.apache.cassandra.service.MigrationManager.announce(MigrationManager.java:188)
at 
org.apache.cassandra.service.MigrationManager.announceColumnFamilyUpdate(MigrationManager.java:161)
at 
org.apache.cassandra.thrift.CassandraServer.system_update_column_family(CassandraServer.java:1063)
at 
org.apache.cassandra.thrift.Cassandra$Processor$system_update_column_family.getResult(Cassandra.java:3520)
at 
org.apache.cassandra.thrift.Cassandra$Processor$system_update_column_family.getResult(Cassandra.java:3508)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:32)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:34)
at 
org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:186)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.util.concurrent.ExecutionException: java.io.IOException: 
org.apache.cassandra.config.ConfigurationException: Cannot modify index name
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at 
org.apache.cassandra.utils.FBUtilities.waitOnFuture(FBUtilities.java:369)
... 11 more
Caused by: java.io.IOException: 
org.apache.cassandra.config.ConfigurationException: Cannot modify index name
at org.apache.cassandra.config.CFMetaData.reload(CFMetaData.java:676)
at 
org.apache.cassandra.db.DefsTable.updateColumnFamily(DefsTable.java:463)
at 
org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:407)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:271)
at 
org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:211)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
... 3 more
Caused by: org.apache.cassandra.config.ConfigurationException: Cannot modify 
index name
at 
org.apache.cassandra.config.ColumnDefinition.apply(ColumnDefinition.java:214)
at org.apache.cassandra.config.CFMetaData.apply(CFMetaData.java:758)
at org.apache.cassandra.config.CFMetaData.reload(CFMetaData.java:672)
... 9 more
ERROR [MigrationStage:1] 2012-07-13 14:51:54,561 AbstractCassandraDaemon.java 
(line 134) Exception in thread Thread[MigrationStage:1,5,main]
java.io.IOException: org.apache.cassandra.config.ConfigurationException: Cannot 
modify index name
at org.apache.cassandra.config.CFMetaData.reload(CFMetaData.java:676)
at 
org.apache.cassandra.db.DefsTable.updateColumnFamily(DefsTable.java:463)
at 
org.apache.cassandra.db.DefsTable.mergeColumnFamilies(DefsTable.java:407)
at org.apache.cassandra.db.DefsTable.mergeSchema(DefsTable.java:271)
at 
org.apache.cassandra.service.MigrationManager$1.call(MigrationManager.java:211)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at

[jira] [Updated] (CASSANDRA-4434) add COPY TO


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

paul cannon updated CASSANDRA-4434:
---

Attachment: 0001-cqlsh-implement-COPY-TO.patch

Patch attached; changes also available in the 4434 branch in my github. Current 
version tagged pending/4434.

https://github.com/thepaul/cassandra/tree/4434

 add COPY TO
 ---

 Key: CASSANDRA-4434
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4434
 Project: Cassandra
  Issue Type: New Feature
Reporter: Jonathan Ellis
Assignee: paul cannon
  Labels: cqlsh
 Fix For: 1.1.3

 Attachments: 0001-cqlsh-implement-COPY-TO.patch


 CASSANDRA-4012 added COPY FROM; this is a ticket to add the inverse.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-4334) cqlsh tab completion error in CREATE KEYSPACE


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

paul cannon updated CASSANDRA-4334:
---

Affects Version/s: 1.1.0
Fix Version/s: 1.1.3

 cqlsh tab completion error in CREATE KEYSPACE
 ---

 Key: CASSANDRA-4334
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4334
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.1.0
 Environment: ubuntu, git:cassandra-1.1. I see the error in cqlsh with 
 cql2 and cql3.
Reporter: Tyler Patterson
Assignee: paul cannon
Priority: Minor
 Fix For: 1.1.3


 The following:
 {code}
 cqlsh CREATE KEYSPACE test WITH strategy_class = 'STAB
 {code}
 will tab complete like this:
 {code}
 cqlsh CREATE KEYSPACE test WITH strategy_class = 'SimpleStrategy '
 {code}
 Note the extra space after SimpleStrategy. Not a big deal to remove, but it 
 could be misleading to people.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-4074) cqlsh: Tab completion should not suggest consistency level ANY for select statements


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

paul cannon updated CASSANDRA-4074:
---

Attachment: 0001-cqlsh-don-t-suggest-CL.ANY-for-SELECT.patch

Patch attached; changes also available in the 4074 branch of my github. Current 
version tagged pending/4074.

https://github.com/thepaul/cassandra/tree/4074

 cqlsh: Tab completion should not suggest consistency level ANY for select 
 statements
 

 Key: CASSANDRA-4074
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4074
 Project: Cassandra
  Issue Type: Bug
Reporter: Tyler Patterson
Assignee: paul cannon
Priority: Trivial
  Labels: cql, cqlsh
 Fix For: 1.1.3

 Attachments: 0001-cqlsh-don-t-suggest-CL.ANY-for-SELECT.patch


 consistency level ANY should not be suggested in tab-completion for SELECT 
 statements

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CASSANDRA-4440) Better output desired to diagnose hung bootstrap due to partial connectivity

2012-07-13 Thread Thomas Whaples (JIRA)

Thomas Whaples created CASSANDRA-4440:
-

 Summary: Better output desired to diagnose hung bootstrap due to 
partial connectivity
 Key: CASSANDRA-4440
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4440
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Reporter: Thomas Whaples
Priority: Trivial
 Fix For: 0.8.10


I was attempting to set up a new node and bootstrap it into my cluster.
Due to an error in my network configuration, this node was able to communicate 
with only a portion of the existing nodes (it could connect to 3 out of 5 
existing nodes). As a result, the node transferred some data, but ultimately 
got stuck in a state of 'Joining' the cluster and not doing anything. 
Unfortunately, it was a little tricky to diagnose. I only figured it out when I 
turned on debug-level monitoring and saw a message about trying to establish an 
outbound connection (not a *failure* to establish it, just a note that it was 
trying to establish one. I'd quote it, but the debug logs got rotated in the 
logspew.)

For posterity, I would like to request that a node in this sort of a situation 
present additional messages or other diagnostics. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CASSANDRA-4440) Better output desired to diagnose hung bootstrap due to partial connectivity

2012-07-13 Thread Thomas Whaples (JIRA)


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

Thomas Whaples updated CASSANDRA-4440:
--

Fix Version/s: (was: 0.8.10)
Affects Version/s: 0.8.10

 Better output desired to diagnose hung bootstrap due to partial connectivity
 

 Key: CASSANDRA-4440
 URL: https://issues.apache.org/jira/browse/CASSANDRA-4440
 Project: Cassandra
  Issue Type: Improvement
  Components: Core
Affects Versions: 0.8.10
Reporter: Thomas Whaples
Priority: Trivial

 I was attempting to set up a new node and bootstrap it into my cluster.
 Due to an error in my network configuration, this node was able to 
 communicate with only a portion of the existing nodes (it could connect to 3 
 out of 5 existing nodes). As a result, the node transferred some data, but 
 ultimately got stuck in a state of 'Joining' the cluster and not doing 
 anything. Unfortunately, it was a little tricky to diagnose. I only figured 
 it out when I turned on debug-level monitoring and saw a message about trying 
 to establish an outbound connection (not a *failure* to establish it, just a 
 note that it was trying to establish one. I'd quote it, but the debug logs 
 got rotated in the logspew.)
 For posterity, I would like to request that a node in this sort of a 
 situation present additional messages or other diagnostics. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[Cassandra Wiki] Update of ThirdPartySupport by alfbaez

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The ThirdPartySupport page has been changed by alfbaez:
http://wiki.apache.org/cassandra/ThirdPartySupport?action=diffrev1=31rev2=32

  {{http://www.datastax.com/sites/all/themes/datastax20110201/logo.png}} 
[[http://datastax.com|Datastax]], the commercial leader in Apache Cassandra™ 
offers products and services that make it easy for customers to build, deploy 
and operate elastically scalable and cloud-optimized applications and data 
services. [[http://datastax.com|DataStax]] has over 100 customers, including 
leaders such as Netflix, Cisco, Rackspace, HP, Constant Contact and 
[[http://www.datastax.com/cassandrausers|more]], and spanning verticals 
including web, financial services, telecommunications, logistics and government.
  
  Other companies:
+ 
+ {{ http://www.urimagnation.com/wp-content/themes/v2.0/images/logo.jpg}}
+ [[http://www.urimagnation.com | URimagination]] , a group of peers, highly 
qualified, dedicated and motivated professionals, and with huge passion for 
open source technologies and projects such OpenSuse, Hadoop, Casandra and more 
offers services to enhance performance of your database applications at quite a 
low cost. Our emphasis is to provide remote database services and 
thereafter-remote database monitoring of your business program. We provide 
competent services in Oracle, PostgreSQL, NoSQL, Hbase, MongoDB, DB2, and many 
more.
  
  {{http://www.impetus.com/sites/impetus.com/impetus/gifs/logo_impetus.png}} 
[[http://www.impetus.com/|Impetus]] provides expertise in Cassandra, Hbase, 
MongoDB, and Other databases like Riak, Redis, Membase, Tokyocabinet, etc 
[[http://bigdata.impetus.com/#|More info about BigData @Impetus]]

[Cassandra Wiki] Update of ThirdPartySupport by alfbaez

Dear Wiki user,

You have subscribed to a wiki page or wiki category on Cassandra Wiki for 
change notification.

The ThirdPartySupport page has been changed by alfbaez:
http://wiki.apache.org/cassandra/ThirdPartySupport?action=diffrev1=32rev2=33

  Other companies:
  
  {{ http://www.urimagnation.com/wp-content/themes/v2.0/images/logo.jpg}}
- [[http://www.urimagnation.com | URimagination]] , a group of peers, highly 
qualified, dedicated and motivated professionals, and with huge passion for 
open source technologies and projects such OpenSuse, Hadoop, Casandra and more 
offers services to enhance performance of your database applications at quite a 
low cost. Our emphasis is to provide remote database services and 
thereafter-remote database monitoring of your business program. We provide 
competent services in Oracle, PostgreSQL, NoSQL, Hbase, MongoDB, DB2, and many 
more.
+ [[http://www.urimagnation.com | URimagination]] , a group of peers, highly 
qualified, dedicated and motivated professionals, and with huge passion for 
open source technologies and projects such Apache Hadoop Big Data Platform, 
OpenSuse, Casandra and more, offers services to enhance performance of your 
applications and databases at quite a low cost. Our emphasis is to provide 
remote database services and thereafter-remote database monitoring of your 
business program. We provide competent services in Oracle, PostgreSQL, NoSQL, 
Hbase, MongoDB, DB2, and many more.
  
  {{http://www.impetus.com/sites/impetus.com/impetus/gifs/logo_impetus.png}} 
[[http://www.impetus.com/|Impetus]] provides expertise in Cassandra, Hbase, 
MongoDB, and Other databases like Riak, Redis, Membase, Tokyocabinet, etc 
[[http://bigdata.impetus.com/#|More info about BigData @Impetus]]

[Cassandra Wiki] Update of ThirdPartySupport by alfbaez