[jira] [Commented] (CASSANDRA-2893) Add row-level isolation

2011-12-29 Thread Radim Kolar (Commented) (JIRA)

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

Radim Kolar commented on CASSANDRA-2893:


what is improvement over cassandra 1.0? Writes to same key in CF were atomic 
already. 

You mean that reader is now waiting until new data are written to row by writer 
instead of returning old data?

 Add row-level isolation
 ---

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

 Attachments: 0001-Move-deletion-infos-into-ISortedColumns-v2.patch, 
 0001-Move-deletion-infos-into-ISortedColumns.patch, 
 0002-Make-memtable-use-CF.addAll-v2.patch, 
 0002-Make-memtable-use-CF.addAll.patch, 
 0003-Add-AtomicSortedColumn-and-snapTree-v2.patch, 
 0003-Add-AtomicSortedColumn-and-snapTree.patch, latency-plain.svg, 
 latency.svg, snaptree-0.1-SNAPSHOT.jar


 This could be done using an the atomic ConcurrentMap operations from the 
 Memtable and something like http://code.google.com/p/pcollections/ to replace 
 the ConcurrentSkipListMap in ThreadSafeSortedColumns.  The trick is that 
 pcollections does not provide a SortedMap, so we probably need to write our 
 own.
 Googling [persistent sortedmap] I found 
 http://code.google.com/p/actord/source/browse/trunk/actord/src/main/scala/ff/collection
  (in scala) and http://clojure.org/data_structures#Data Structures-Maps.

--
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-3682) cassandra hangs during nodetool drain

2011-12-29 Thread Radim Kolar (Created) (JIRA)
cassandra hangs during nodetool drain
-

 Key: CASSANDRA-3682
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3682
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.0.7
Reporter: Radim Kolar


 INFO [RMI TCP Connection(43)-64.6.104.18] 2011-12-29 10:33:23,560 
StorageService.java (line 668) DRAINING: starting drain process
 INFO [RMI TCP Connection(43)-64.6.104.18] 2011-12-29 10:33:23,560 
CassandraDaemon.java (line 219) Stop listening to thrift clients
 INFO [RMI TCP Connection(43)-64.6.104.18] 2011-12-29 10:34:23,614 
MessagingService.java (line 487) Waiting for messaging service to quiesce
-- hangs --

reproducible on all my nodes running 1.0.6-SNAPSHOT


--
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-3677) NPE during HH delivery when gossip turned off on target

2011-12-29 Thread Radim Kolar (Commented) (JIRA)

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

Radim Kolar commented on CASSANDRA-3677:


This error is not related to target node down, i got it today and no nodes down 
are reported.


INFO [HintedHandoff:1] 2011-12-29 10:49:38,993 HintedHandOffManager.java (line 
334) Finished hinted handoff of 0 rows to endpoint /216.17.99.40

 INFO [CompactionExecutor:5] 2011-12-29 10:54:52,465 CompactionTask.java (line 
113) Compacting 
[SSTableReader(path='/usr/local/cassandra/data/system/HintsColumnFamily-hc-963-Data.db'),
 
SSTableReader(path='/usr/local/cassandra/data/system/HintsColumnFamily-hc-962-Data.db')]
 INFO [CompactionExecutor:5] 2011-12-29 10:55:08,744 CompactionTask.java (line 
221) Compacted to 
[/usr/local/cassandra/data/system/HintsColumnFamily-hc-964-Data.db,].  
709,504,640 to 165,449,718 (~23% of original) bytes for 2 keys at 9.692558MB/s. 
 Time: 16,279ms.

ERROR [OptionalTasks:1] 2011-12-29 10:59:06,482 AbstractCassandraDaemon.java 
(line 138) Fatal exception in thread Thread[OptionalTasks:1,5,main]
java.lang.NullPointerException
at 
org.cliffc.high_scale_lib.NonBlockingHashMap.hash(NonBlockingHashMap.java:113)
at 
org.cliffc.high_scale_lib.NonBlockingHashMap.putIfMatch(NonBlockingHashMap.java:553)
at 
org.cliffc.high_scale_lib.NonBlockingHashMap.putIfMatch(NonBlockingHashMap.java:348)
at 
org.cliffc.high_scale_lib.NonBlockingHashMap.putIfAbsent(NonBlockingHashMap.java:319)
at 
org.cliffc.high_scale_lib.NonBlockingHashSet.add(NonBlockingHashSet.java:32)
at 
org.apache.cassandra.db.HintedHandOffManager.scheduleHintDelivery(HintedHandOffManager.java:371)
at 
org.apache.cassandra.db.HintedHandOffManager.scheduleAllDeliveries(HintedHandOffManager.java:356)
at 
org.apache.cassandra.db.HintedHandOffManager.access$000(HintedHandOffManager.java:84)
at 
org.apache.cassandra.db.HintedHandOffManager$1.run(HintedHandOffManager.java:119)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at 
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
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:679)

 NPE during HH delivery when gossip turned off on target
 ---

 Key: CASSANDRA-3677
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3677
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 1.0.7
Reporter: Radim Kolar
Assignee: Brandon Williams
Priority: Trivial
 Fix For: 1.0.7

 Attachments: 3677.txt


 probably not important bug
 ERROR [OptionalTasks:1] 2011-12-27 21:44:25,342 AbstractCassandraDaemon.java 
 (line 138) Fatal exception in thread Thread[OptionalTasks:1,5,main]
 java.lang.NullPointerException
 at 
 org.cliffc.high_scale_lib.NonBlockingHashMap.hash(NonBlockingHashMap.java:113)
 at 
 org.cliffc.high_scale_lib.NonBlockingHashMap.putIfMatch(NonBlockingHashMap.java:553)
 at 
 org.cliffc.high_scale_lib.NonBlockingHashMap.putIfMatch(NonBlockingHashMap.java:348)
 at 
 org.cliffc.high_scale_lib.NonBlockingHashMap.putIfAbsent(NonBlockingHashMap.java:319)
 at 
 org.cliffc.high_scale_lib.NonBlockingHashSet.add(NonBlockingHashSet.java:32)
 at 
 org.apache.cassandra.db.HintedHandOffManager.scheduleHintDelivery(HintedHandOffManager.java:371)
 at 
 org.apache.cassandra.db.HintedHandOffManager.scheduleAllDeliveries(HintedHandOffManager.java:356)
 at 
 org.apache.cassandra.db.HintedHandOffManager.access$000(HintedHandOffManager.java:84)
 at 
 org.apache.cassandra.db.HintedHandOffManager$1.run(HintedHandOffManager.java:119)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
 at 
 

[Cassandra Wiki] Update of Cassandra2474 by JonathanEllis

2011-12-29 Thread Apache Wiki
Dear Wiki user,

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

The Cassandra2474 page has been changed by JonathanEllis:
http://wiki.apache.org/cassandra/Cassandra2474?action=diffrev1=5rev2=6

  
  TableOfContents(100)
  
+ == Background ==
+ 
+ === Supercolumns ===
+ 
+ Cassandra has supported limited nesting of data within a row via SuperColumns 
since its initial release.  A supercolumn is a named container of subcolumns, 
with no other metadata attached to it: unlike data columns, it cannot have a 
timestamp or TTL associated with it.  (The one exception is that supercolumns 
CAN be deleted as a unit, and thus SuperColumns CAN be tombstones.)  Thus, a 
row using supercolumns looks like this:
+ 
+ ||key'''supercolumn1'''  ||'''supercolumn2''' ||
+ ||   ||subcolumn1||subcolumn2|||subcolumn3||subcolumn4||subcolumn5||
+ 
+ The most common use case for SuperColumns is to represent materialized 
views or precomputed resultsets: each object in the resultset maps to a 
single supercolumn.  This usually takes advantage of the sorting-by-column-name 
to give very performant slice lookups for this resultset.  To use a more 
concrete example, we could represent the Twitter timeline as a single 
supercolumn row per user, with the tweets made by that user's friends 
represented as supercolumns within that row.  The supercolumn names will be the 
posted_at information, so this lets us get most recent tweets, in [reverse] 
chronological order easily:
+ 
+ ||tjefferson'''1763'''
   '''1790'''   
   '''1818'''   
||
+ ||  ||body
   ||posted_by ||body   
  ||posted_by  ||body   
 ||posted_by||
+ ||  ||Democracy will soon degenerate into an anarchy  
   ||jadams||To be prepared for war is one of the most effectual 
means of preserving peace||gwashington||Revolution was effected before the war 
commenced||jadams   ||
+ ||bfranklin '''1781'''
   ||   
  ||   ||   
 || ||
+ ||  ||body
   ||posted_by ||   
  ||   ||   
 || ||
+ ||  ||Every government degenerates when trusted to the rulers of the 
people alone||tjefferson||  
   ||   ||  
  || ||
+ 
+ === Composite columns ===
+ 
+ SuperColumns have a number of limitations, most notably
+ 
+  1. there can only ever be a single level of nesting
+  1. to read any subcolumn from supercolumn X, all of X is read into memory
+  1. they add a lot of complexity to the Cassandra implementation and cause a 
fair number of bugs
+ 
+ To address these problems, Cassandra added the CompositeType, which encodes a 
multi-value column name into a single column -- essentially the column name 
becomes a Tuple, for those with a background in Python.  I will use Python 
tuple representation (x, y, z) to denote a composite column with components x, 
y, and z.
+ 
+ Composite columns are flexible enough that there are multiple ways to encode 
the same data.  The most natural ways to encode the above timeline data are, 
first, an encoding where each object becomes a single column:
+ 
+ ||tjefferson||(1763, 'Democracy will soon degenerate into an anarchy', 
'jadams')||(1790, 'To be prepared for war is one of the most effectual means of 
preserving peace', 'gwashington')||(1818, 'Revolution was effected before the 
war commenced', 'jadams')||
+ ||bfranklin ||(1781, 'Every government degenerates when trusted to the rulers 
of the people alone', 'tjefferson')||
+ 
+ Note that a CompositeType definition includes type information -- (int, utf8, 
utf8) here -- but there is no column name information; this is governed purely 
by application convention.
+ 
+ The main drawback to this representation is that like row keys, column names 
are necessarily immutable in Cassandra.  So there is no way to update an object 
using this representation other than by deleting the old and adding the new.  
More subtly, this exposes us to some of the drawbacks of a pure key/value 
approach that normal Cassandra columns avoid: if one client updates field X in 
a result, while another client 

[Cassandra Wiki] Update of Roger Mbiama by Roger Mbiama

2011-12-29 Thread Apache Wiki
Dear Wiki user,

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

The Roger Mbiama page has been changed by Roger Mbiama:
http://wiki.apache.org/cassandra/Roger%20Mbiama?action=diffrev1=4rev2=5

- *title:Roger Mbiama
- *windows winamp or linux xmms
- *Roger Mbiama
+ [[Roger Mbiama]]
- *linkto:WindowsPage title:Linux
- *r:\bdog\b
- *-domain:system
+ [[-domain:system]]
- *category:CategoryHomepage title:thomas
- 
+ ---
+ |category:CategoryHomepage |Mbiama assogo rogerHomepage
+ ---
  Bonjour et une excellente Année 2012
  
- 
- # http://www.apache.org/licenses/LICENSE-2.0/
- Options
- ===
- 
https://svn.wikimedia.org/viewvc/?http://fr.wikipedia.org/wiki/Mbiama%20Assogo%20Roger/?index.php/
- 1?php
- 2 https://svn.wikimedia.org/viewvc/Mbiama Assogo Roger
- 3 if ( !defined( 'MEDIAWIKI' ) ) {
- 4 die( Not a valid entry point\n );
- 5 }
- 6 http://fr.wikipedia.org/wiki/Mbiama Assogo Roger
- 7 $wgExtensionCredits['other'][] = array(
- 8 'path' = __FILE__,
- 9 'name' = 'Cassandra',
- 10'version' = 0.1,
- 11'author' = 'Max Semenik',
- 12'url' = 'https://www.mediawiki.org/wiki/Extension:Cassandra',
- 13'descriptionmsg' = 'cassandra-desc',
- 14);
- 15$dir = dirname( __FILE__ ) . '/';
- 16$wgExtensionMessagesFiles['Cassandra'] =  $dir . 'Cassandra.i18n.php';
- 17
- 18$wgAutoloadClasses['ExternalStoreCassandra'] = 
$wgAutoloadClasses['MWCassandraException']
- 19= $dir . 'Cassandra_body.php';
- 20
- 21if ( is_array( $wgExternalStores ) ) {
- 22$wgExternalStores[] = 'cassandra';
- 23} else {
- 24$wgExternalStores = array( 'cassandra' );
- 25}
- 26
- 27/**
- 28 * Extension settings
- 29 */
- 30
- 31// Directory where Thrift bindings for PHP reside
- 32$wgThriftRoot = '/usr/share/php/Thrift';
- 33
- 34// Port used for communicating with Cassandra. Must match ThriftPort
- 35// in Cassandra's storage-conf.xml
- 36$wgCassandraPort = 9160;
- 37
- 38// Mapping of cluster names to lists of server IPs
- 39// Example:
- 40// $wgCassandraClusters = array( 
- 41// 'foo' = array( '192.168.1.1', '192.168.1.2', ),
- 42// 'bar' = array( 'somehostname' ),
- 43// );
- 44$wgCassandraClusters = array();
- 45
- 46// String prepended to saved key names, can be used to distinct between
- 47// different wikis, etc. Does not affect the already saved revisions.
- 48$wgCassandraKeyPrefix = $wgDBname;
- 49
- 50/**
- 51 * Read and write consistencies, see 
http://wiki.apache.org/cassandra/API#ConsistencyLevel
- 52 * for details.
- 53 * Avoid using cassandra_ConsistencyLevel here to prevent large parts
- 54 * of Cassandra and Thrift from being loaded on every request. Shouldn't
- 55 * matter much for real-world setups with byte code cache though.
- 56 */
- 57$wgCassandraReadConsistency = 1;  // cassandra_ConsistencyLevel::ONE
- 58$wgCassandraWriteConsistency = 1; // cassandra_ConsistencyLevel::ONE
- 59
- 60// Column family to be used for storing data
- 61$wgCassandraColumnFamily = 'Standard1';/
- 


[jira] [Commented] (CASSANDRA-2474) CQL support for compound columns

2011-12-29 Thread Jonathan Ellis (Commented) (JIRA)

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

Jonathan Ellis commented on CASSANDRA-2474:
---

I've updated the wiki page at http://wiki.apache.org/cassandra/Cassandra2474 
with a more in-depth Background section that hopefully clears up where I'm 
going with this sparse/dense business.

Eric mentioned on IRC that he's uneasy about the PRIMARY KEY syntax implicitly 
using the first element of PRIMARY KEY as the row key.  We could make it 
explicit with another WITH option to the TRANSPOSED clause: 

{{{
CREATE TABLE timeline (
user_id int,
posted_at uuid,
column string,
value blob,
PRIMARY KEY(user_id, posted_at)
) TRANSPOSED WITH ROW KEY(user_id)
}}}

This makes things more verbose (this would be a required clause) but I'm okay 
with that if consensus is that being explicit here is better.

 CQL support for compound columns
 

 Key: CASSANDRA-2474
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
 Project: Cassandra
  Issue Type: New Feature
  Components: API, Core
Reporter: Eric Evans
Assignee: Pavel Yaskevich
  Labels: cql
 Fix For: 1.1

 Attachments: 2474-transposed-1.PNG, 2474-transposed-raw.PNG, 
 2474-transposed-select-no-sparse.PNG, 2474-transposed-select.PNG, 
 raw_composite.txt, screenshot-1.jpg, screenshot-2.jpg


 For the most part, this boils down to supporting the specification of 
 compound column names (the CQL syntax is colon-delimted terms), and then 
 teaching the decoders (drivers) to create structures from the results.

--
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-3668) Performance of sstableloader is affected in 1.0.x

2011-12-29 Thread Jonathan Ellis (Commented) (JIRA)

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

Jonathan Ellis commented on CASSANDRA-3668:
---

Are you seeing a bottleneck in i/o?  in CPU?

http://spyced.blogspot.com/2010/01/linux-performance-basics.html

 Performance of sstableloader is affected in 1.0.x
 -

 Key: CASSANDRA-3668
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3668
 Project: Cassandra
  Issue Type: Bug
  Components: API
Affects Versions: 1.0.7
Reporter: Manish Zope
Assignee: Yuki Morishita
 Fix For: 1.0.7

   Original Estimate: 48h
  Remaining Estimate: 48h

 One of my colleague had reported the bug regarding the degraded performance 
 of the sstable generator and sstable loader.
 ISSUE :- https://issues.apache.org/jira/browse/CASSANDRA-3589 
 As stated in above issue generator performance is rectified but performance 
 of the sstableloader is still an issue.
 3589 is marked as duplicate of 3618.Both issues shows resolved status.But the 
 problem with sstableloader still exists.
 So opening other issue so that sstbleloader problem should not go unnoticed.
 FYI : We have tested the generator part with the patch given in 3589.Its 
 Working fine.
 Please let us know if you guys require further inputs from our side.

--
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: clean up streamExecutors map patch by jbellis; reviewed by pschuller for CASSANDRA-3679

2011-12-29 Thread jbellis
Updated Branches:
  refs/heads/trunk 48f5d5716 - 952c6e536


clean up streamExecutors map
patch by jbellis; reviewed by pschuller for CASSANDRA-3679


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

Branch: refs/heads/trunk
Commit: 952c6e536b90abe94874813030033975e33672a4
Parents: 48f5d57
Author: Jonathan Ellis jbel...@apache.org
Authored: Wed Dec 28 12:09:06 2011 -0600
Committer: Jonathan Ellis jbel...@apache.org
Committed: Thu Dec 29 12:16:40 2011 -0600

--
 .../org/apache/cassandra/net/MessagingService.java |   72 +--
 1 files changed, 25 insertions(+), 47 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/952c6e53/src/java/org/apache/cassandra/net/MessagingService.java
--
diff --git a/src/java/org/apache/cassandra/net/MessagingService.java 
b/src/java/org/apache/cassandra/net/MessagingService.java
index 0a072bf..2845495 100644
--- a/src/java/org/apache/cassandra/net/MessagingService.java
+++ b/src/java/org/apache/cassandra/net/MessagingService.java
@@ -26,6 +26,7 @@ import java.nio.ByteBuffer;
 import java.nio.channels.AsynchronousCloseException;
 import java.nio.channels.ServerSocketChannel;
 import java.util.*;
+import java.util.concurrent.ConcurrentMap;
 import java.util.concurrent.ExecutorService;
 import java.util.concurrent.LinkedBlockingQueue;
 import java.util.concurrent.TimeUnit;
@@ -97,9 +98,7 @@ public final class MessagingService implements 
MessagingServiceMBean
  * means the overhead in the degenerate case of having streamed to 
everyone in the ring over time as a ring changes,
  * is not going to be a thread per node - but rather an instance per node. 
That's totally fine.
  */
-private final HashMapInetAddress, DebuggableThreadPoolExecutor 
streamExecutors = new HashMapInetAddress, DebuggableThreadPoolExecutor();
-/** Very rarely acquired lock protecting streamExecutors. */
-private final Lock streamExecutorsLock = new ReentrantLock();
+private final ConcurrentMapInetAddress, DebuggableThreadPoolExecutor 
streamExecutors = new NonBlockingHashMapInetAddress, 
DebuggableThreadPoolExecutor();
 private final AtomicInteger activeStreamsOutbound = new AtomicInteger(0);
 
 private final NonBlockingHashMapInetAddress, OutboundTcpConnectionPool 
connectionManagers_ = new NonBlockingHashMapInetAddress, 
OutboundTcpConnectionPool();
@@ -472,24 +471,25 @@ public final class MessagingService implements 
MessagingServiceMBean
 
 public void stream(StreamHeader header, InetAddress to)
 {
-this.streamExecutorsLock.lock();
-try
+DebuggableThreadPoolExecutor executor = streamExecutors.get(to);
+if (executor == null)
 {
-if (!streamExecutors.containsKey(to))
+// Using a core pool size of 0 is important. See documentation of 
streamExecutors.
+executor = new DebuggableThreadPoolExecutor(0,
+1,
+1,
+TimeUnit.SECONDS,
+new 
LinkedBlockingQueueRunnable(),
+new 
NamedThreadFactory(Streaming to  + to));
+DebuggableThreadPoolExecutor old = streamExecutors.putIfAbsent(to, 
executor);
+if (old != null)
 {
-// Using a core pool size of 0 is important. See documentation 
of streamExecutors.
-streamExecutors.put(to, new DebuggableThreadPoolExecutor(0, 1, 
1, TimeUnit.SECONDS,
-new LinkedBlockingQueueRunnable(),
-new NamedThreadFactory(Streaming to  + to)));
+executor.shutdown();
+executor = old;
 }
-DebuggableThreadPoolExecutor executor = streamExecutors.get(to);
-
-executor.execute(new FileStreamTask(header, to));
-}
-finally
-{
-this.streamExecutorsLock.unlock();
 }
+
+executor.execute(new FileStreamTask(header, to));
 }
 
 public void incrementActiveStreamsOutbound()
@@ -520,37 +520,15 @@ public final class MessagingService implements 
MessagingServiceMBean
 
 public void waitForStreaming() throws InterruptedException
 {
-while (true)
-{
-boolean stillWaiting = false;
+// this does not prevent new streams from beginning after a drain 
begins, but since streams are only
+// 

[jira] [Created] (CASSANDRA-3683) NullPointerException in getTempSSTablePath() with leveled compaction strategy

2011-12-29 Thread Kent Tong (Created) (JIRA)
NullPointerException in getTempSSTablePath() with leveled compaction strategy
-

 Key: CASSANDRA-3683
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3683
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.5
 Environment: Linux
Reporter: Kent Tong


When using the leveled compaction strategy, sometimes a NullPointerException is 
raised during compaction. See the stacktrace below for the details.


INFO [ScheduledTasks:1] 2011-12-29 08:43:52,117 GCInspector.java (line 123) GC 
for ParNew: 1481 ms for 1 collections, 5577352760 used; max is 10171187200
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,117 StatusLogger.java (line 50) 
Pool NameActive   Pending   Blocked
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,118 StatusLogger.java (line 65) 
ReadStage 1 3 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,118 StatusLogger.java (line 65) 
RequestResponseStage  0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,118 StatusLogger.java (line 65) 
ReadRepairStage   0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,118 StatusLogger.java (line 65) 
MutationStage 0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,119 StatusLogger.java (line 65) 
ReplicateOnWriteStage 0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,119 StatusLogger.java (line 65) 
GossipStage   0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,119 StatusLogger.java (line 65) 
AntiEntropyStage  0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,120 StatusLogger.java (line 65) 
MigrationStage0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,120 StatusLogger.java (line 65) 
StreamStage   0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,120 StatusLogger.java (line 65) 
MemtablePostFlusher   1 1 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,120 StatusLogger.java (line 65) 
FlushWriter   1 1 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,121 StatusLogger.java (line 65) 
MiscStage 0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,121 StatusLogger.java (line 65) 
InternalResponseStage 0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,121 StatusLogger.java (line 65) 
HintedHandoff 0 0 0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 69) 
CompactionManager   n/a-3
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 81) 
MessagingServicen/a   0,0
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 85) 
ColumnFamilyMemtable ops,data  Row cache size/cap  Key cache 
size/cap
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 88) 
system.NodeIdInfo 0,0 0/0   
  0/1
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 88) 
system.IndexInfo  0,0 0/0   
  0/1
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
system.LocationInfo   0,0 0/0   
  2/3
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
system.Versions 3,103 0/0   
  0/1
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
system.Migrations 0,0 0/0   
  0/3
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
system.HintsColumnFamily  0,0 0/0   
  0/1
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
system.Schema 0,0 0/0   
  0/3
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,124 StatusLogger.java (line 88) 
mcas.timebasedtoken  2198,1027880 0/0 
700/700
 INFO [ScheduledTasks:1] 2011-12-29 08:43:53,565 GCInspector.java (line 123) GC 
for ParNew: 372 ms for 1 collections, 5582229656 used; max is 10171187200
 INFO [ScheduledTasks:1] 2011-12-29 08:43:55,570 GCInspector.java (line 123) GC 
for ParNew: 405 ms for 1 collections, 6098538760 used; max is 10171187200
 INFO [ScheduledTasks:1] 2011-12-29 08:43:56,572 GCInspector.java (line 123) GC 
for ParNew: 294 ms for 1 collections, 5598626768 used; max is 10171187200
 INFO [ScheduledTasks:1] 2011-12-29 

[jira] [Commented] (CASSANDRA-3668) Performance of sstableloader is affected in 1.0.x

2011-12-29 Thread Manish Zope (Commented) (JIRA)

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

Manish Zope commented on CASSANDRA-3668:


Hi Jonathan,
Sorry for the late reply.

We have created the sstables with 0.8.7 and run the sstableloader from separate 
machine in our test environment.

On same setup we replaced 0.8.7 with 1.0.x (With updated patch as mentioned in 
issue -3589).
Time required for loading data of same size took 2x time as compared to that of 
0.8.7.






 Performance of sstableloader is affected in 1.0.x
 -

 Key: CASSANDRA-3668
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3668
 Project: Cassandra
  Issue Type: Bug
  Components: API
Affects Versions: 1.0.7
Reporter: Manish Zope
Assignee: Yuki Morishita
 Fix For: 1.0.7

   Original Estimate: 48h
  Remaining Estimate: 48h

 One of my colleague had reported the bug regarding the degraded performance 
 of the sstable generator and sstable loader.
 ISSUE :- https://issues.apache.org/jira/browse/CASSANDRA-3589 
 As stated in above issue generator performance is rectified but performance 
 of the sstableloader is still an issue.
 3589 is marked as duplicate of 3618.Both issues shows resolved status.But the 
 problem with sstableloader still exists.
 So opening other issue so that sstbleloader problem should not go unnoticed.
 FYI : We have tested the generator part with the patch given in 3589.Its 
 Working fine.
 Please let us know if you guys require further inputs from our side.

--
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 Roger Mbiama by Roger Mbiama

2011-12-29 Thread Apache Wiki
Dear Wiki user,

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

The Roger Mbiama page has been changed by Roger Mbiama:
http://wiki.apache.org/cassandra/Roger%20Mbiama?action=diffrev1=2rev2=3

- Describe Roger Mbiama here.
+ Roger Mbiama
  
  Roger Mbiama/README.txt
- Required configuration files
+ Configuration files
  
  
  cassandra.yaml: main Cassandra configuration file
@@ -13, +13 @@

  Optional configuration files
  
  
- access.properties: used for authorization
- passwd.properties: used for authentication
  cassandra-rack.properties: used by PropertyFileSnitch
  
- # Licensed to the Apache Software Foundation (ASF) under one
+ # Licensed to the Apache Software Foundation (ASF) under
+ # The ASF licenses this file
- # 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); 
- # 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.
+ Options
+ ===
+ 
https://svn.wikimedia.org/viewvc/?http://fr.wikipedia.org/wiki/Mbiama%20Assogo%20Roger/?index.php
+ 1 ?php
+ 2 https://svn.wikimedia.org/viewvc/Mbiama Assogo Roger
+ 3 if ( !defined( 'MEDIAWIKI' ) ) {
+ 4 die( Not a valid entry point\n );
+ 5 }
+ 6 http://fr.wikipedia.org/wiki/Mbiama Assogo Roger
+ 7 $wgExtensionCredits['other'][] = array(
+ 8 'path' = __FILE__,
+ 9 'name' = 'Cassandra',
+ 10'version' = 0.1,
+ 11'author' = 'Max Semenik',
+ 12'url' = 'https://www.mediawiki.org/wiki/Extension:Cassandra',
+ 13'descriptionmsg' = 'cassandra-desc',
+ 14);
+ 15$dir = dirname( __FILE__ ) . '/';
+ 16$wgExtensionMessagesFiles['Cassandra'] =  $dir . 'Cassandra.i18n.php';
+ 17
+ 18$wgAutoloadClasses['ExternalStoreCassandra'] = 
$wgAutoloadClasses['MWCassandraException']
+ 19= $dir . 'Cassandra_body.php';
+ 20
+ 21if ( is_array( $wgExternalStores ) ) {
+ 22$wgExternalStores[] = 'cassandra';
+ 23} else {
+ 24$wgExternalStores = array( 'cassandra' );
+ 25}
+ 26
+ 27/**
+ 28 * Extension settings
+ 29 */
+ 30
+ 31// Directory where Thrift bindings for PHP reside
+ 32$wgThriftRoot = '/usr/share/php/Thrift';
+ 33
+ 34// Port used for communicating with Cassandra. Must match ThriftPort
+ 35// in Cassandra's storage-conf.xml
+ 36$wgCassandraPort = 9160;
+ 37
+ 38// Mapping of cluster names to lists of server IPs
+ 39// Example:
+ 40// $wgCassandraClusters = array( 
+ 41// 'foo' = array( '192.168.1.1', '192.168.1.2', ),
+ 42// 'bar' = array( 'somehostname' ),
+ 43// );
+ 44$wgCassandraClusters = array();
+ 45
+ 46// String prepended to saved key names, can be used to distinct between
+ 47// different wikis, etc. Does not affect the already saved revisions.
+ 48$wgCassandraKeyPrefix = $wgDBname;
+ 49
+ 50/**
+ 51 * Read and write consistencies, see 
http://wiki.apache.org/cassandra/API#ConsistencyLevel
+ 52 * for details.
+ 53 * Avoid using cassandra_ConsistencyLevel here to prevent large parts
+ 54 * of Cassandra and Thrift from being loaded on every request. Shouldn't
+ 55 * matter much for real-world setups with byte code cache though.
+ 56 */
+ 57$wgCassandraReadConsistency = 1;  // cassandra_ConsistencyLevel::ONE
+ 58$wgCassandraWriteConsistency = 1; // cassandra_ConsistencyLevel::ONE
+ 59
+ 60// Column family to be used for storing data
+ 61$wgCassandraColumnFamily = 'Standard1';
  


[Cassandra Wiki] Update of Roger Mbiama by Roger Mbiama

2011-12-29 Thread Apache Wiki
Dear Wiki user,

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

The Roger Mbiama page has been changed by Roger Mbiama:
http://wiki.apache.org/cassandra/Roger%20Mbiama?action=diffrev1=1rev2=2

  Describe Roger Mbiama here.
  
- conf/README.txt
+ Roger Mbiama/README.txt
  Required configuration files
  
  
@@ -33, +33 @@

  # See the License for the specific language governing permissions and
  # limitations under the License.
  
- calculate_heap_sizes()
- {
- case `uname` in
- Linux)
- system_memory_in_mb=`free -m | awk '/Mem:/ {print $2}'`
- system_cpu_cores=`egrep -c 'processor([[:space:]]+):.*' 
/proc/cpuinfo`
- break
- ;;
- FreeBSD)
- system_memory_in_bytes=`sysctl hw.physmem | awk '{print $2}'`
- system_memory_in_mb=`expr $system_memory_in_bytes / 1024 / 1024`
- system_cpu_cores=`sysctl hw.ncpu | awk '{print $2}'`
- break
- ;;
- SunOS)
- system_memory_in_mb=`prtconf | awk '/Memory size:/ {print $3}'`
- system_cpu_cores=`psrinfo | wc -l`
- break
- ;;
- *)
- # assume reasonable defaults for e.g. a modern desktop or
- # cheap server
- system_memory_in_mb=2048
- system_cpu_cores=2
- ;;
- esac
- max_heap_size_in_mb=`expr $system_memory_in_mb / 2`
- MAX_HEAP_SIZE=${max_heap_size_in_mb}M
- 
- # Young gen: min(max_sensible_per_modern_cpu_core * num_cores, 1/4 * heap 
size)
- max_sensible_yg_per_core_in_mb=100
- max_sensible_yg_in_mb=`expr $max_sensible_yg_per_core_in_mb * 
$system_cpu_cores`
- 
- desired_yg_in_mb=`expr $max_heap_size_in_mb / 4`
- 
- if [ $desired_yg_in_mb -gt $max_sensible_yg_in_mb ]
- then
- HEAP_NEWSIZE=${max_sensible_yg_in_mb}M
- else
- HEAP_NEWSIZE=${desired_yg_in_mb}M
- fi
- }
- 
- # Override these to set the amount of memory to allocate to the JVM at
- # start-up. For production use you almost certainly want to adjust
- # this for your environment. MAX_HEAP_SIZE is the total amount of
- # memory dedicated to the Java heap; HEAP_NEWSIZE refers to the size
- # of the young generation. Both MAX_HEAP_SIZE and HEAP_NEWSIZE should
- # be either set or not (if you set one, set the other).
- #
- # The main trade-off for the young generation is that the larger it
- # is, the longer GC pause times will be. The shorter it is, the more
- # expensive GC will be (usually).
- #
- # The example HEAP_NEWSIZE assumes a modern 8-core+ machine for decent pause
- # times. If in doubt, and if you do not particularly want to tweak, go with
- # 100 MB per physical CPU core.
- 
- #MAX_HEAP_SIZE=4G
- #HEAP_NEWSIZE=800M
- 
- if [ x$MAX_HEAP_SIZE = x ]  [ x$HEAP_NEWSIZE = x ]; then
- calculate_heap_sizes
- else
- if [ x$MAX_HEAP_SIZE = x ] ||  [ x$HEAP_NEWSIZE = x ]; then
- echo please set or unset MAX_HEAP_SIZE and HEAP_NEWSIZE in pairs 
(see cassandra-env.sh)
- exit 1
- fi
- fi
- 
- # Specifies the default port over which Cassandra will be available for
- # JMX connections.
- JMX_PORT=7199
- 
- 
- # Here we create the arguments that will get passed to the jvm when
- # starting cassandra.
- 
- # enable assertions.  disabling this in production will give a modest
- # performance benefit (around 5%).
- JVM_OPTS=$JVM_OPTS -ea
- 
- # add the jamm javaagent
- check_openjdk=`${JAVA:-java} -version 21 | awk '{if (NR == 2) {print 
$1}}'`
- if [ $check_openjdk != OpenJDK ]
- then
- JVM_OPTS=$JVM_OPTS -javaagent:$CASSANDRA_HOME/lib/jamm-0.2.2.jar
- fi
- 
- # enable thread priorities, primarily so we can give periodic tasks
- # a lower priority to avoid interfering with client workload
- JVM_OPTS=$JVM_OPTS -XX:+UseThreadPriorities
- # allows lowering thread priority without being root.  see
- # 
http://tech.stolsvik.com/2010/01/linux-java-thread-priorities-workaround.html
- JVM_OPTS=$JVM_OPTS -XX:ThreadPriorityPolicy=42
- 
- # min and max heap sizes should be set to the same value to avoid
- # stop-the-world GC pauses during resize, and so that we can lock the
- # heap in memory on startup to prevent any of it from being swapped
- # out.
- JVM_OPTS=$JVM_OPTS -Xms${MAX_HEAP_SIZE}
- JVM_OPTS=$JVM_OPTS -Xmx${MAX_HEAP_SIZE}
- JVM_OPTS=$JVM_OPTS -Xmn${HEAP_NEWSIZE}
- JVM_OPTS=$JVM_OPTS -XX:+HeapDumpOnOutOfMemoryError 
- 
- if [ `uname` = Linux ] ; then
- # reduce the per-thread stack size to minimize the impact of Thrift
- # thread-per-client.  (Best practice is for client connections to
- # be pooled anyway.) Only do so on Linux where it is known to be
- # supported.
- JVM_OPTS=$JVM_OPTS -Xss128k
- fi
- 
- # GC tuning options
- JVM_OPTS=$JVM_OPTS -XX:+UseParNewGC 
- JVM_OPTS=$JVM_OPTS -XX:+UseConcMarkSweepGC 
- JVM_OPTS=$JVM_OPTS -XX:+CMSParallelRemarkEnabled 
- JVM_OPTS=$JVM_OPTS -XX:SurvivorRatio=8 
- 

[jira] [Commented] (CASSANDRA-2893) Add row-level isolation

2011-12-29 Thread Jonathan Ellis (Commented) (JIRA)

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

Jonathan Ellis commented on CASSANDRA-2893:
---

Atomic != Isolated

http://en.wikipedia.org/wiki/ACID

 Add row-level isolation
 ---

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

 Attachments: 0001-Move-deletion-infos-into-ISortedColumns-v2.patch, 
 0001-Move-deletion-infos-into-ISortedColumns.patch, 
 0002-Make-memtable-use-CF.addAll-v2.patch, 
 0002-Make-memtable-use-CF.addAll.patch, 
 0003-Add-AtomicSortedColumn-and-snapTree-v2.patch, 
 0003-Add-AtomicSortedColumn-and-snapTree.patch, latency-plain.svg, 
 latency.svg, snaptree-0.1-SNAPSHOT.jar


 This could be done using an the atomic ConcurrentMap operations from the 
 Memtable and something like http://code.google.com/p/pcollections/ to replace 
 the ConcurrentSkipListMap in ThreadSafeSortedColumns.  The trick is that 
 pcollections does not provide a SortedMap, so we probably need to write our 
 own.
 Googling [persistent sortedmap] I found 
 http://code.google.com/p/actord/source/browse/trunk/actord/src/main/scala/ff/collection
  (in scala) and http://clojure.org/data_structures#Data Structures-Maps.

--
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 Roger Mbiama by Roger Mbiama

2011-12-29 Thread Apache Wiki
Dear Wiki user,

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

The Roger Mbiama page has been changed by Roger Mbiama:
http://wiki.apache.org/cassandra/Roger%20Mbiama?action=diffrev1=3rev2=4

+ *title:Roger Mbiama
+ *windows winamp or linux xmms
- Roger Mbiama
+ *Roger Mbiama
+ *linkto:WindowsPage title:Linux
+ *r:\bdog\b
+ *-domain:system
+ *category:CategoryHomepage title:thomas
+ 
+ Bonjour et une excellente Année 2012
- 
- Roger Mbiama/README.txt
- Configuration files
- 
- 
- cassandra.yaml: main Cassandra configuration file
- log4j-server.proprties: log4j configuration file for Cassandra server
  
  
- Optional configuration files
- 
- 
- cassandra-rack.properties: used by PropertyFileSnitch
- 
- # Licensed to the Apache Software Foundation (ASF) under
- # The ASF licenses this file
- # to you under the Apache License, Version 2.0 (the
- # License); 
- #
- # http://www.apache.org/licenses/LICENSE-2.0
+ # http://www.apache.org/licenses/LICENSE-2.0/
  Options
  ===
- 
https://svn.wikimedia.org/viewvc/?http://fr.wikipedia.org/wiki/Mbiama%20Assogo%20Roger/?index.php
+ 
https://svn.wikimedia.org/viewvc/?http://fr.wikipedia.org/wiki/Mbiama%20Assogo%20Roger/?index.php/
- 1 ?php
+ 1?php
  2 https://svn.wikimedia.org/viewvc/Mbiama Assogo Roger
  3 if ( !defined( 'MEDIAWIKI' ) ) {
  4 die( Not a valid entry point\n );
@@ -84, +75 @@

  58$wgCassandraWriteConsistency = 1; // cassandra_ConsistencyLevel::ONE
  59
  60// Column family to be used for storing data
- 61$wgCassandraColumnFamily = 'Standard1';
+ 61$wgCassandraColumnFamily = 'Standard1';/
  


[Cassandra Wiki] Update of Roger Mbiama by Roger Mbiama

2011-12-29 Thread Apache Wiki
Dear Wiki user,

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

The Roger Mbiama page has been changed by Roger Mbiama:
http://wiki.apache.org/cassandra/Roger%20Mbiama?action=diffrev1=5rev2=6

Comment:
listen: [2011: 82422635d672eb7fd0cfd0309e9eaef58a511b23:80; github

  ---
  Bonjour et une excellente Année 2012
  
+ Usage information
+ == 
+ 
+ Usage: Mbiama Roger.html/Cassandra-remote [-h 192.0.2.1:80
+  ,192.0.2.5:8000:] [-u http://wiki.apache.org/Roger Mbiama] [-f[ramed]] 
function [arg1 [arg2...]]
+ 
+ Setting and getting values
+ == 
+ 
+ $ http://wikipedia.org/Roger Mbiama 
Assogo/cassndra/trunk/index.php/Cassandra-remote -h cass-1:9160 insert 
Keyspace1 eevans ColumnPath('dr...@angosso.net', column='Mbiama Assogo 
Roger') apple 1 ConsistencyLevel.QUORUM
+ None
+ $ ./Cassandra-remote -h cass-1:9160 get Keyspace1 eevans 
ColumnPath('dr...@angosso.net', column='Mbiama Assogo Roger') 
ConsistencyLevel.QUORUM
+ ColumnOrSuperColumn(column=Column(timestamp=1, name='Roger Mbiama', 
value='explorer'), super_column=None)
+ 


[jira] [Commented] (CASSANDRA-3213) Upgrade Thrift

2011-12-29 Thread Edward Capriolo (Commented) (JIRA)

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

Edward Capriolo commented on CASSANDRA-3213:


Hive made the jump to 0.7.0 thrift for hive 0.8.0. Currently this makes it hard 
to initialize an embedded C* process inside a hive unit test.

 Upgrade Thrift
 --

 Key: CASSANDRA-3213
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3213
 Project: Cassandra
  Issue Type: Task
  Components: Core
Reporter: Jake Farrell
Assignee: Jake Farrell
Priority: Trivial
  Labels: thrift
 Fix For: 1.2

 Attachments: v1-0001-update-generated-thrift-code.patch, 
 v1-0002-upgrade-thrift-jar-and-license.patch, v1-0003-update-build-xml.patch




--
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-3281) Add an AbstractType anytype which stores meta data on a per column basis

2011-12-29 Thread Jonathan Ellis (Commented) (JIRA)

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

Jonathan Ellis commented on CASSANDRA-3281:
---

Is it accurate to say that conceptually, the main difference between AnyType 
and DynamicCompositeType is that AnyType also includes type information for the 
value?

 Add an AbstractType anytype which stores meta data on a per column basis
 

 Key: CASSANDRA-3281
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3281
 Project: Cassandra
  Issue Type: New Feature
Reporter: Edward Capriolo
Priority: Minor

 A pet project of mine is an AbstractType for Cassandra that stores metadata 
 of the type in the column. https://github.com/edwardcapriolo/Cassandra-AnyType
 I described my use case any my design decisions here. 
 https://github.com/edwardcapriolo/Cassandra-AnyType/blob/master/README . The 
 biggest cases were needing to support null and '' as keys, column names, and 
 column values, however I also think the technique used to serialize Java 
 Objects as JSON but compare as a Java object is novel. 
 Side node: (The AbstractType interface has changed multiple times between 
 0.6.X, 0.7.X, and 1.0.0-beta. I hope it stabilizes! ) 
 If people would like AnyType (or parts of it ) incorporated into Cassandra 
 that would be great. I am willing to tweak change it based on other peoples 
 ideas.

--
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 Cassandra2474 by JonathanEllis

2011-12-29 Thread Apache Wiki
Dear Wiki user,

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

The Cassandra2474 page has been changed by JonathanEllis:
http://wiki.apache.org/cassandra/Cassandra2474?action=diffrev1=6rev2=7

  
  To address these problems, Cassandra added the CompositeType, which encodes a 
multi-value column name into a single column -- essentially the column name 
becomes a Tuple, for those with a background in Python.  I will use Python 
tuple representation (x, y, z) to denote a composite column with components x, 
y, and z.
  
- Composite columns are flexible enough that there are multiple ways to encode 
the same data.  The most natural ways to encode the above timeline data are, 
first, an encoding where each object becomes a single column:
+ Composite columns are flexible enough that there are multiple ways to encode 
the same data.  The most natural ways to encode the above timeline data are, 
first, an encoding where each object becomes a single column, with an empty 
value:
  
  ||tjefferson||(1763, 'Democracy will soon degenerate into an anarchy', 
'jadams')||(1790, 'To be prepared for war is one of the most effectual means of 
preserving peace', 'gwashington')||(1818, 'Revolution was effected before the 
war commenced', 'jadams')||
+ ||  ||[empty] 
  ||[empty] 
  ||[empty] 
||
  ||bfranklin ||(1781, 'Every government degenerates when trusted to the rulers 
of the people alone', 'tjefferson')||
+ ||  ||[empty] 
   ||
  
- Note that a CompositeType definition includes type information -- (int, utf8, 
utf8) here -- but there is no column name information; this is governed purely 
by application convention.
+ (One could arbitrarily pick any column whose sort order is not important to 
be the column value instead, but I think it's more straightforward to treat 
things uniformly.)
  
  The main drawback to this representation is that like row keys, column names 
are necessarily immutable in Cassandra.  So there is no way to update an object 
using this representation other than by deleting the old and adding the new.  
More subtly, this exposes us to some of the drawbacks of a pure key/value 
approach that normal Cassandra columns avoid: if one client updates field X in 
a result, while another client updates field Y, there will be no race when X 
and Y are distinct columns.  But if these fields are stored as part of the same 
composite column then there is a race.
  


[jira] [Commented] (CASSANDRA-3213) Upgrade Thrift

2011-12-29 Thread Jake Farrell (Commented) (JIRA)

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

Jake Farrell commented on CASSANDRA-3213:
-

Edward is there an open Thrift ticket on the problem you are having?

 Upgrade Thrift
 --

 Key: CASSANDRA-3213
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3213
 Project: Cassandra
  Issue Type: Task
  Components: Core
Reporter: Jake Farrell
Assignee: Jake Farrell
Priority: Trivial
  Labels: thrift
 Fix For: 1.2

 Attachments: v1-0001-update-generated-thrift-code.patch, 
 v1-0002-upgrade-thrift-jar-and-license.patch, v1-0003-update-build-xml.patch




--
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-2805) Clean up mbeans that return Internal Cassandra types

2011-12-29 Thread Nick Bailey (Updated) (JIRA)

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

Nick Bailey updated CASSANDRA-2805:
---

Attachment: 0001-Don-t-return-internal-types-over-jmx.patch

Should take care of any instances where internal types are returned over jmx.

 Clean up mbeans that return Internal Cassandra types
 

 Key: CASSANDRA-2805
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2805
 Project: Cassandra
  Issue Type: Bug
Affects Versions: 0.8.1
Reporter: Nick Bailey
Assignee: Nick Bailey
Priority: Minor
  Labels: lhf
 Fix For: 1.1

 Attachments: 0001-Don-t-return-internal-types-over-jmx.patch


 We need to clean up wherever we return internal cassandra objects over jmx. 
 Namely CompactionInfo objects as well as Tokens. There may be a few other 
 examples.
 This is bad for two reasons
 1. You have to load the cassandra jar when querying these mbeans, which sucks.
 2. Stuff breaks between versions when things are moved. For example, 
 CASSANDRA-1610 moves the compaction related classes around. Any code querying 
 those jmx mbeans in 0.8.0 is now broken in 0.8.2. (assuming those moves stay 
 in the 0.8 branch)
 For things like CompactionInfo we should just expose more mbean methods or 
 serialize to something standard like json.
 I'd like to target this for 0.8.2. Since we've already broken compatibility 
 between 0.8.0 and 0.8.1, I'd say just fix this everywhere now.

--
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-3667) We need a way to deactivate row/key caching on a per-cf basis.

2011-12-29 Thread Pavel Yaskevich (Updated) (JIRA)

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

Pavel Yaskevich updated CASSANDRA-3667:
---

Attachment: CASSANDRA-3667.patch

 We need a way to deactivate row/key caching on a per-cf basis.
 --

 Key: CASSANDRA-3667
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3667
 Project: Cassandra
  Issue Type: Improvement
Reporter: Pavel Yaskevich
Assignee: Pavel Yaskevich
 Attachments: CASSANDRA-3667.patch


 Initial idea would be to either have a boolean flag if we only want to allow 
 disabling row cache, or some multi-value caches option that could be none, 
 key_only, row_only or all.

--
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-3486) Node Tool command to stop repair

2011-12-29 Thread Jonathan Ellis (Updated) (JIRA)

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

Jonathan Ellis updated CASSANDRA-3486:
--

 Reviewer: slebresne
Affects Version/s: (was: 1.1)
Fix Version/s: 1.1

 Node Tool command to stop repair
 

 Key: CASSANDRA-3486
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3486
 Project: Cassandra
  Issue Type: Improvement
  Components: Tools
 Environment: JVM
Reporter: Vijay
Assignee: Vijay
Priority: Minor
  Labels: nodetool, repair, stop
 Fix For: 1.1

 Attachments: 0001-stop-repair-3583.patch


 After CASSANDRA-1740, If the validation compaction is stopped then the repair 
 will hang. This ticket will allow users to kill the original repair.

--
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-3684) Composite Column Support for PIG

2011-12-29 Thread Benjamin Coverston (Created) (JIRA)
Composite Column Support for PIG


 Key: CASSANDRA-3684
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3684
 Project: Cassandra
  Issue Type: Bug
Reporter: Benjamin Coverston


It appears that some changes need to be made to support CompositeColumns. Right 
now if you try to load and use a column family that utilizes composite columns 
you get the following exception[1].

It appears to me that we need to modify the storage handler for Pig to support 
this scenario.


[1]


Backend error message
-
java.lang.RuntimeException: Unexpected data type -1 found in stream.
at org.apache.pig.data.BinInterSedes.writeDatum(BinInterSedes.java:478)
at org.apache.pig.data.BinInterSedes.writeTuple(BinInterSedes.java:541)
at org.apache.pig.data.BinInterSedes.writeBag(BinInterSedes.java:522)
at org.apache.pig.data.BinInterSedes.writeDatum(BinInterSedes.java:361)
at org.apache.pig.data.BinInterSedes.writeTuple(BinInterSedes.java:541)
at org.apache.pig.data.BinInterSedes.writeDatum(BinInterSedes.java:357)
at org.apache.pig.data.BinSedesTuple.write(BinSedesTuple.java:57)
at 
org.apache.pig.impl.io.PigNullableWritable.write(PigNullableWritable.java:123)
at 
org.apache.hadoop.io.serializer.WritableSerialization$WritableSerializer.serialize(WritableSerialization.java:90)
at 
org.apache.hadoop.io.serializer.WritableSerialization$WritableSerializer.serialize(WritableSerialization.java:77)
at 
org.apache.hadoop.mapred.MapTask$MapOutputBuffer.collect(MapTask.java:1061)
at 
org.apache.hadoop.mapred.MapTask$NewOutputCollector.write(MapTask.java:691)
at 
org.apache.hadoop.mapreduce.TaskInputOutputContext.write(TaskInputOutputContext.java:80)
at 
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigMapReduce$Map.collect(PigMapReduce.java:116)
at 
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigMapBase.runPipeline(PigMapBase.java:239)
at 
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigMapBase.map(PigMapBase.java:232)
at 
org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigMapBase.map(PigMapBase.java:53)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:370)
at org.apache.hadoop.mapred.Child$4.run(Child.java:272)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1059)
at org.apache.hadoop.mapred.Child.main(Child.java:266)

Backend error message
-
java.lang.Throwable: Child Error
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:271)
Caused by: java.io.IOException: Task process exit with nonzero status of 65.
at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:258)

--
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-3683) NullPointerException in getTempSSTablePath() with leveled compaction strategy

2011-12-29 Thread Jonathan Ellis (Commented) (JIRA)

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

Jonathan Ellis commented on CASSANDRA-3683:
---

This may be caused by CASSANDRA-3536.  Please upgrade to 1.0.6 and re-test.

 NullPointerException in getTempSSTablePath() with leveled compaction strategy
 -

 Key: CASSANDRA-3683
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3683
 Project: Cassandra
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.5
 Environment: Linux
Reporter: Kent Tong

 When using the leveled compaction strategy, sometimes a NullPointerException 
 is raised during compaction. See the stacktrace below for the details.
 INFO [ScheduledTasks:1] 2011-12-29 08:43:52,117 GCInspector.java (line 123) 
 GC for ParNew: 1481 ms for 1 collections, 5577352760 used; max is 10171187200
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,117 StatusLogger.java (line 50) 
 Pool NameActive   Pending   Blocked
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,118 StatusLogger.java (line 65) 
 ReadStage 1 3 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,118 StatusLogger.java (line 65) 
 RequestResponseStage  0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,118 StatusLogger.java (line 65) 
 ReadRepairStage   0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,118 StatusLogger.java (line 65) 
 MutationStage 0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,119 StatusLogger.java (line 65) 
 ReplicateOnWriteStage 0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,119 StatusLogger.java (line 65) 
 GossipStage   0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,119 StatusLogger.java (line 65) 
 AntiEntropyStage  0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,120 StatusLogger.java (line 65) 
 MigrationStage0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,120 StatusLogger.java (line 65) 
 StreamStage   0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,120 StatusLogger.java (line 65) 
 MemtablePostFlusher   1 1 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,120 StatusLogger.java (line 65) 
 FlushWriter   1 1 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,121 StatusLogger.java (line 65) 
 MiscStage 0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,121 StatusLogger.java (line 65) 
 InternalResponseStage 0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,121 StatusLogger.java (line 65) 
 HintedHandoff 0 0 0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 69) 
 CompactionManager   n/a-3
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 81) 
 MessagingServicen/a   0,0
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 85) 
 ColumnFamilyMemtable ops,data  Row cache size/cap  Key cache 
 size/cap
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 88) 
 system.NodeIdInfo 0,0 0/0 
 0/1
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,122 StatusLogger.java (line 88) 
 system.IndexInfo  0,0 0/0 
 0/1
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
 system.LocationInfo   0,0 0/0 
 2/3
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
 system.Versions 3,103 0/0 
 0/1
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
 system.Migrations 0,0 0/0 
 0/3
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
 system.HintsColumnFamily  0,0 0/0 
 0/1
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,123 StatusLogger.java (line 88) 
 system.Schema 0,0 0/0 
 0/3
  INFO [ScheduledTasks:1] 2011-12-29 08:43:52,124 StatusLogger.java (line 88) 
 mcas.timebasedtoken  2198,1027880 0/0 
 700/700
  INFO [ScheduledTasks:1] 2011-12-29 08:43:53,565 GCInspector.java (line 123) 
 

[jira] [Commented] (CASSANDRA-3213) Upgrade Thrift

2011-12-29 Thread Jake Farrell (Commented) (JIRA)

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

Jake Farrell commented on CASSANDRA-3213:
-

Hive issue found to be IncompatibleClassChangeError due to compiling against 
newer version of thrift and then using version within cassandra at runtime.

 Upgrade Thrift
 --

 Key: CASSANDRA-3213
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3213
 Project: Cassandra
  Issue Type: Task
  Components: Core
Reporter: Jake Farrell
Assignee: Jake Farrell
Priority: Trivial
  Labels: thrift
 Fix For: 1.2

 Attachments: v1-0001-update-generated-thrift-code.patch, 
 v1-0002-upgrade-thrift-jar-and-license.patch, v1-0003-update-build-xml.patch




--
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: -javadoc and -sources jars for clientutil

2011-12-29 Thread eevans
Updated Branches:
  refs/heads/trunk 952c6e536 - a7db75f49


-javadoc and -sources jars for clientutil

Patch by satish babu krishnamoorthy w/ minor changes; reviewed by eevans for 
CASSANDRA-3426


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

Branch: refs/heads/trunk
Commit: a7db75f498717a6d957d431f33bd01806d13c6d6
Parents: 952c6e5
Author: Eric Evans eev...@apache.org
Authored: Thu Dec 29 15:33:45 2011 -0600
Committer: Eric Evans eev...@apache.org
Committed: Thu Dec 29 16:35:46 2011 -0600

--
 build.xml |   46 ++
 1 files changed, 38 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/a7db75f4/build.xml
--
diff --git a/build.xml b/build.xml
index 56b25ab..23f69aa 100644
--- a/build.xml
+++ b/build.xml
@@ -788,17 +788,29 @@ url=${svn.entry.url}?pathrev=${svn.entry.commit.revision}
 
   create-javadoc destdir=${javadoc.jars.dir}/main
 filesets
-fileset dir=${build.src.java} defaultexcludes=yes
-  include name=org/apache/**/*.java/
-/fileset
-fileset dir=${build.src.gen-java} defaultexcludes=yes
-  include name=org/apache/**/*.java/
-/fileset
+  fileset dir=${build.src.java} defaultexcludes=yes
+include name=org/apache/**/*.java/
+  /fileset
+  fileset dir=${build.src.gen-java} defaultexcludes=yes
+include name=org/apache/**/*.java/
+  /fileset
 /filesets
   /create-javadoc
   jar jarfile=${build.dir}/${final.name}-javadoc.jar
basedir=${javadoc.jars.dir}/main/
 
+  create-javadoc destdir=${javadoc.jars.dir}/clientutil
+filesets
+  fileset dir=${build.src.java} defaultexcludes=yes
+include name=org/apache/cassandra/cql/jdbc/* /
+include name=org/apache/cassandra/utils/ByteBufferUtil*.java /
+include name=org/apache/cassandra/utils/Hex.java /
+include name=org/apache/cassandra/utils/UUIDGen*.java /
+  /fileset
+/filesets
+  /create-javadoc
+  jar 
jarfile=${build.dir}/${ant.project.name}-clientutil-${version}-javadoc.jar
+   basedir=${javadoc.jars.dir}/clientutil/
   !-- javadoc task always rebuilds so might as well remove the generated 
docs to prevent 
being pulled into the distribution by accident --
   delete quiet=true dir=${javadoc.jars.dir}/
@@ -821,6 +833,14 @@ url=${svn.entry.url}?pathrev=${svn.entry.commit.revision}
   include name=org/apache/**/*.java/
 /fileset
   /jar
+  jar 
jarfile=${build.dir}/${ant.project.name}-clientutil-${version}-sources.jar
+fileset dir=${build.src.java} defaultexcludes=yes
+  include name=org/apache/cassandra/cql/jdbc/* /
+  include name=org/apache/cassandra/utils/ByteBufferUtil*.java /
+  include name=org/apache/cassandra/utils/Hex.java /
+  include name=org/apache/cassandra/utils/UUIDGen*.java /
+/fileset
+  /jar
 /target
 
 !-- creates release tarballs --
@@ -1250,6 +1270,12 @@ url=${svn.entry.url}?pathrev=${svn.entry.commit.revision}
 !-- the cassandra-clientutil jar --  
 install 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
  
file=${build.dir}/${ant.project.name}-clientutil-${version}.jar/
+install 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
+ 
file=${build.dir}/${ant.project.name}-clientutil-${version}-sources.jar
+ classifier=sources/
+install 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
+ 
file=${build.dir}/${ant.project.name}-clientutil-${version}-javadoc.jar
+ classifier=javadoc/
 
 !-- the cassandra-all jar --
 install pomFile=${build.dir}/${final.name}.pom
@@ -1298,7 +1324,12 @@ url=${svn.entry.url}?pathrev=${svn.entry.commit.revision}
 !-- the cassandra-clientutil jar --  
 deploy 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
 file=${build.dir}/${ant.project.name}-clientutil-${version}.jar/
-
+deploy 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
+ 
file=${build.dir}/${ant.project.name}-clientutil-${version}-sources.jar
+ classifier=sources/
+deploy 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
+ 
file=${build.dir}/${ant.project.name}-clientutil-${version}-javadoc.jar
+ classifier=javadoc/
 !-- the cassandra-all jar 

git commit: -javadoc and -sources jars for clientutil

2011-12-29 Thread eevans
Updated Branches:
  refs/heads/cassandra-1.0 02346a1e6 - 8703f745f


-javadoc and -sources jars for clientutil

Patch by satish babu krishnamoorthy w/ minor changes; reviewed by eevans for 
CASSANDRA-3426


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

Branch: refs/heads/cassandra-1.0
Commit: 8703f745fede8705d8e186c0bf6e91a32159701c
Parents: 02346a1
Author: Eric Evans eev...@apache.org
Authored: Thu Dec 29 15:33:45 2011 -0600
Committer: Eric Evans eev...@apache.org
Committed: Thu Dec 29 16:38:24 2011 -0600

--
 build.xml |   46 ++
 1 files changed, 38 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/cassandra/blob/8703f745/build.xml
--
diff --git a/build.xml b/build.xml
index 70aa7e5..0cb7f9e 100644
--- a/build.xml
+++ b/build.xml
@@ -790,17 +790,29 @@ url=${svn.entry.url}?pathrev=${svn.entry.commit.revision}
 
   create-javadoc destdir=${javadoc.jars.dir}/main
 filesets
-fileset dir=${build.src.java} defaultexcludes=yes
-  include name=org/apache/**/*.java/
-/fileset
-fileset dir=${build.src.gen-java} defaultexcludes=yes
-  include name=org/apache/**/*.java/
-/fileset
+  fileset dir=${build.src.java} defaultexcludes=yes
+include name=org/apache/**/*.java/
+  /fileset
+  fileset dir=${build.src.gen-java} defaultexcludes=yes
+include name=org/apache/**/*.java/
+  /fileset
 /filesets
   /create-javadoc
   jar jarfile=${build.dir}/${final.name}-javadoc.jar
basedir=${javadoc.jars.dir}/main/
 
+  create-javadoc destdir=${javadoc.jars.dir}/clientutil
+filesets
+  fileset dir=${build.src.java} defaultexcludes=yes
+include name=org/apache/cassandra/cql/jdbc/* /
+include name=org/apache/cassandra/utils/ByteBufferUtil*.java /
+include name=org/apache/cassandra/utils/Hex.java /
+include name=org/apache/cassandra/utils/UUIDGen*.java /
+  /fileset
+/filesets
+  /create-javadoc
+  jar 
jarfile=${build.dir}/${ant.project.name}-clientutil-${version}-javadoc.jar
+   basedir=${javadoc.jars.dir}/clientutil/
   !-- javadoc task always rebuilds so might as well remove the generated 
docs to prevent 
being pulled into the distribution by accident --
   delete quiet=true dir=${javadoc.jars.dir}/
@@ -823,6 +835,14 @@ url=${svn.entry.url}?pathrev=${svn.entry.commit.revision}
   include name=org/apache/**/*.java/
 /fileset
   /jar
+  jar 
jarfile=${build.dir}/${ant.project.name}-clientutil-${version}-sources.jar
+fileset dir=${build.src.java} defaultexcludes=yes
+  include name=org/apache/cassandra/cql/jdbc/* /
+  include name=org/apache/cassandra/utils/ByteBufferUtil*.java /
+  include name=org/apache/cassandra/utils/Hex.java /
+  include name=org/apache/cassandra/utils/UUIDGen*.java /
+/fileset
+  /jar
 /target
 
 !-- creates release tarballs --
@@ -1253,6 +1273,12 @@ url=${svn.entry.url}?pathrev=${svn.entry.commit.revision}
 !-- the cassandra-clientutil jar --  
 install 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
  
file=${build.dir}/${ant.project.name}-clientutil-${version}.jar/
+install 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
+ 
file=${build.dir}/${ant.project.name}-clientutil-${version}-sources.jar
+ classifier=sources/
+install 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
+ 
file=${build.dir}/${ant.project.name}-clientutil-${version}-javadoc.jar
+ classifier=javadoc/
 
 !-- the cassandra-all jar --
 install pomFile=${build.dir}/${final.name}.pom
@@ -1301,7 +1327,12 @@ url=${svn.entry.url}?pathrev=${svn.entry.commit.revision}
 !-- the cassandra-clientutil jar --  
 deploy 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
 file=${build.dir}/${ant.project.name}-clientutil-${version}.jar/
-
+deploy 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
+ 
file=${build.dir}/${ant.project.name}-clientutil-${version}-sources.jar
+ classifier=sources/
+deploy 
pomFile=${build.dir}/${ant.project.name}-clientutil-${version}.pom
+ 
file=${build.dir}/${ant.project.name}-clientutil-${version}-javadoc.jar
+ classifier=javadoc/
 !-- the 

[jira] [Commented] (CASSANDRA-3583) Add rebuild index JMX command

2011-12-29 Thread Vijay (Commented) (JIRA)

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

Vijay commented on CASSANDRA-3583:
--

BTW: i changed the rebuild index to just be rebuild, because i am going to do 
2392 without saving to filesystem.

Command: nt rebuild Keyspace2 Standard3 Standard3.IdxName,Standard3.IdxName1

 Add rebuild index JMX command
 ---

 Key: CASSANDRA-3583
 URL: https://issues.apache.org/jira/browse/CASSANDRA-3583
 Project: Cassandra
  Issue Type: New Feature
  Components: Core, Tools
Affects Versions: 1.1
Reporter: Jonathan Ellis
Assignee: Vijay
Priority: Minor
 Fix For: 1.1

 Attachments: 0001-3583-v2.patch, 0001-3583.patch


 CASSANDRA-1740 allows aborting an index build, but there is no way to 
 re-attempt the build without restarting the server.
 We've also had requests to allow rebuilding an index that *has* been built, 
 so it would be nice to kill two birds with one stone here.

--
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-2474) CQL support for compound columns

2011-12-29 Thread Jonathan Ellis (Commented) (JIRA)

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

Jonathan Ellis commented on CASSANDRA-2474:
---

Created CASSANDRA-3685 for the WITH COLUMN NAMES feature, which is really 
distinct from compound columns (we have the same problem in standard CFs 
defined with CQL today).

 CQL support for compound columns
 

 Key: CASSANDRA-2474
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
 Project: Cassandra
  Issue Type: New Feature
  Components: API, Core
Reporter: Eric Evans
Assignee: Pavel Yaskevich
  Labels: cql
 Fix For: 1.1

 Attachments: 2474-transposed-1.PNG, 2474-transposed-raw.PNG, 
 2474-transposed-select-no-sparse.PNG, 2474-transposed-select.PNG, 
 raw_composite.txt, screenshot-1.jpg, screenshot-2.jpg


 For the most part, this boils down to supporting the specification of 
 compound column names (the CQL syntax is colon-delimted terms), and then 
 teaching the decoders (drivers) to create structures from the results.

--
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] [Issue Comment Edited] (CASSANDRA-2474) CQL support for compound columns

2011-12-29 Thread Jonathan Ellis (Issue Comment Edited) (JIRA)

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

Jonathan Ellis edited comment on CASSANDRA-2474 at 12/30/11 1:41 AM:
-

I've updated the wiki page at http://wiki.apache.org/cassandra/Cassandra2474 
with a more in-depth Background section that hopefully clears up where I'm 
going with this sparse/dense business.

Eric mentioned on IRC that he's uneasy about the PRIMARY KEY syntax implicitly 
using the first element of PRIMARY KEY as the row key.  We could make it 
explicit with another WITH option to the TRANSPOSED clause: 

{code}
CREATE TABLE timeline (
user_id int,
posted_at uuid,
column string,
value blob,
PRIMARY KEY(user_id, posted_at)
) TRANSPOSED WITH ROW KEY(user_id)
{code}

This makes things more verbose (this would be a required clause) but I'm okay 
with that if consensus is that being explicit here is better.

  was (Author: jbellis):
I've updated the wiki page at 
http://wiki.apache.org/cassandra/Cassandra2474 with a more in-depth Background 
section that hopefully clears up where I'm going with this sparse/dense 
business.

Eric mentioned on IRC that he's uneasy about the PRIMARY KEY syntax implicitly 
using the first element of PRIMARY KEY as the row key.  We could make it 
explicit with another WITH option to the TRANSPOSED clause: 

{{{
CREATE TABLE timeline (
user_id int,
posted_at uuid,
column string,
value blob,
PRIMARY KEY(user_id, posted_at)
) TRANSPOSED WITH ROW KEY(user_id)
}}}

This makes things more verbose (this would be a required clause) but I'm okay 
with that if consensus is that being explicit here is better.
  
 CQL support for compound columns
 

 Key: CASSANDRA-2474
 URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
 Project: Cassandra
  Issue Type: New Feature
  Components: API, Core
Reporter: Eric Evans
Assignee: Pavel Yaskevich
  Labels: cql
 Fix For: 1.1

 Attachments: 2474-transposed-1.PNG, 2474-transposed-raw.PNG, 
 2474-transposed-select-no-sparse.PNG, 2474-transposed-select.PNG, 
 raw_composite.txt, screenshot-1.jpg, screenshot-2.jpg


 For the most part, this boils down to supporting the specification of 
 compound column names (the CQL syntax is colon-delimted terms), and then 
 teaching the decoders (drivers) to create structures from the results.

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