Build failed in Hudson: Cassandra-0.7 #150

2011-01-11 Thread Apache Hudson Server
See https://hudson.apache.org/hudson/job/Cassandra-0.7/150/changes

Changes:

[jbellis] allow specifying specific SSTables to compact from JMX
patch by slebresne; reviewed by jbellis for CASSANDRA-1963

--
[...truncated 723 lines...]
AUinterface/thrift/gen-java/org/apache/cassandra/thrift/SliceRange.java
AUinterface/thrift/gen-java/org/apache/cassandra/thrift/SuperColumn.java
AU
interface/thrift/gen-java/org/apache/cassandra/thrift/InvalidRequestException.java
A 
interface/thrift/gen-java/org/apache/cassandra/thrift/AuthorizationException.java
AU
interface/thrift/gen-java/org/apache/cassandra/thrift/SlicePredicate.java
A 
interface/thrift/gen-java/org/apache/cassandra/thrift/IndexOperator.java
A 
interface/thrift/gen-java/org/apache/cassandra/thrift/IndexExpression.java
A 
interface/thrift/gen-java/org/apache/cassandra/thrift/AuthenticationRequest.java
A 
interface/thrift/gen-java/org/apache/cassandra/thrift/RowPredicate.java
AU
interface/thrift/gen-java/org/apache/cassandra/thrift/ConsistencyLevel.java
AU
interface/thrift/gen-java/org/apache/cassandra/thrift/ColumnOrSuperColumn.java
A interface/thrift/gen-java/org/apache/cassandra/thrift/KsDef.java
AUinterface/thrift/gen-java/org/apache/cassandra/thrift/Column.java
AUinterface/thrift/gen-java/org/apache/cassandra/thrift/TokenRange.java
A 
interface/thrift/gen-java/org/apache/cassandra/thrift/AuthenticationException.java
AUinterface/cassandra.thrift
A ivy.xml
A lib
A lib/guava-r05.jar
AUlib/concurrentlinkedhashmap-lru-1.1.jar
AUlib/high-scale-lib.jar
A lib/commons-cli-1.1.jar
AUlib/jug-2.0.0.jar
AUlib/antlr-3.1.3.jar
A lib/avro-1.4.0-fixes.jar
AUlib/jetty-6.1.21.jar
A lib/commons-codec-1.2.jar
A lib/jackson-mapper-asl-1.4.0.jar
A lib/snakeyaml-1.6.jar
A lib/commons-collections-3.2.1.jar
A lib/libthrift-0.5.jar
AUlib/servlet-api-2.5-20081211.jar
A lib/jackson-core-asl-1.4.0.jar
A lib/licenses
AUlib/licenses/log4j-1.2.16.txt
A lib/licenses/slf4j-log4j12-1.6.1.txt
AUlib/licenses/guava-r05.txt
AUlib/licenses/concurrentlinkedhashmap-lru-1.1.txt
A lib/licenses/high-scale-lib.txt
AUlib/licenses/commons-cli-1.1.txt
A lib/licenses/antlr-3.1.3.txt
A lib/licenses/jug-2.0.0.txt
AUlib/licenses/avro-1.3.1-dev.txt
A lib/licenses/jetty-6.1.21.txt
AUlib/licenses/commons-codec-1.2.txt
AUlib/licenses/jackson-mapper-asl-1.4.0.txt
A lib/licenses/snakeyaml-1.6.txt
AUlib/licenses/commons-collections-3.2.1.txt
AUlib/licenses/libthrift-0.5.txt
AUlib/licenses/jackson-core-asl-1.4.0.txt
A lib/licenses/servlet-api-2.5-20081211.txt
A lib/licenses/slf4j-api-1.6.1.txt
AUlib/licenses/commons-lang-2.4.txt
AUlib/licenses/json-simple-1.1.txt
A lib/licenses/jetty-util-6.1.21.txt
A lib/licenses/jline-0.9.94.txt
AUlib/slf4j-api-1.6.1.jar
A lib/commons-lang-2.4.jar
A lib/json-simple-1.1.jar
AUlib/jetty-util-6.1.21.jar
A lib/jline-0.9.94.jar
A lib/avro-1.4.0-sources-fixes.jar
A lib/log4j-1.2.16.jar
AUlib/slf4j-log4j12-1.6.1.jar
A redhat
A redhat/cassandra
A redhat/cassandra.conf
A redhat/default
A redhat/apache-cassandra.spec
A redhat/cassandra.in.sh
A bin
AUbin/clustertool
A bin/config-converter.bat
AUbin/nodetool
A bin/clustertool.bat
A bin/nodetool.bat
AUbin/stop-server
AUbin/sstablekeys
A bin/sstablekeys.bat
AUbin/schematool
AUbin/cassandra
A bin/schematool.bat
AUbin/cassandra-cli
AUbin/cassandra.bat
AUbin/cassandra-cli.bat
AUbin/json2sstable
AUbin/sstable2json
A bin/config-converter
AUbin/cassandra.in.sh
A bin/json2sstable.bat
A bin/sstable2json.bat
AUREADME.txt
A .rat-excludes
 U.
At revision 1057729
[cassandra] $ /home/hudson/tools/ant/latest/bin/ant -Dversion=$BUILD_ID 
-Dcobertura.dir=/usr/share/java clean release test
Buildfile: 
https://hudson.apache.org/hudson/job/Cassandra-0.7/ws/cassandra/build.xml

clean:

ivy-download:
 [echo] Downloading Ivy...
[mkdir] Created dir: 
https://hudson.apache.org/hudson/job/Cassandra-0.7/ws/cassandra/build
  [get] Getting: 
http://repo2.maven.org/maven2/org/apache/ivy/ivy/2.1.0/ivy-2.1.0.jar
  [get] To: 
https://hudson.apache.org/hudson/job/Cassandra-0.7/ws/cassandra/build/ivy-2.1.0.jar

ivy-init:
[mkdir] Created dir: 
https://hudson.apache.org/hudson/job/Cassandra-0.7/ws/cassandra/build/lib

ivy-retrieve-build:
No ivy:settings found for the default 

Hudson build is back to normal : Cassandra-0.7 #151

2011-01-11 Thread Apache Hudson Server
See https://hudson.apache.org/hudson/job/Cassandra-0.7/151/changes




Time for 1.0

2011-01-11 Thread Jonathan Ellis
Way back in Nov 09, we did a users survey and asked what features
people wanted to see.  Here was my summary of the responses:
http://www.mail-archive.com/cassandra-user@incubator.apache.org/msg01446.html

Looking at that, we've done essentially all of them.  I think we can
make a strong case that our next release should be 1.0; it's
production ready, it's reasonably feature-complete, it's documented,
and we know what our upgrade path story is.

The list--

Load balancing: basics done;
https://issues.apache.org/jira/browse/CASSANDRA-1427 is open to
improve it

Decommission: done

Map/reduce support: done

ColumnFamily / Keyspace definitions w/o restart: done

Design documentation: started at
http://wiki.apache.org/cassandra/ArchitectureInternals

Insert multiple rows at once: done

Remove_slice_range / remove_key_range: turned out to be a *lot* harder
than it looks at first.  Postponed indefinitely.

Secondary indexing: done

Caching: done (with some enhancements possible such as
https://issues.apache.org/jira/browse/CASSANDRA-1969 and
https://issues.apache.org/jira/browse/CASSANDRA-1956)

Bulk delete (truncate): done

I would add,

User documentation: done (http://www.riptano.com/docs)

Large row support: done

Improved replication strategies and more sophisticated ConsistencyLevels: done

Efficient bootstrap/streaming: done

Flow control: done

Network-level compatibility between releases: scheduled
(https://issues.apache.org/jira/browse/CASSANDRA-1015)

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com


Re: Time for 1.0

2011-01-11 Thread Germán Kondolf
+1 days ago I was wondering about the gap between 0.7 and a future 1.0, the 
answer is just a few more enhancements like you said. :)

Excellent news :)

// Germán Kondolf
http://twitter.com/germanklf
http://code.google.com/p/seide/
// @i4

On 11/01/2011, at 22:35, Jonathan Ellis jbel...@gmail.com wrote:

 Way back in Nov 09, we did a users survey and asked what features
 people wanted to see.  Here was my summary of the responses:
 http://www.mail-archive.com/cassandra-user@incubator.apache.org/msg01446.html
 
 Looking at that, we've done essentially all of them.  I think we can
 make a strong case that our next release should be 1.0; it's
 production ready, it's reasonably feature-complete, it's documented,
 and we know what our upgrade path story is.
 
 The list--
 
 Load balancing: basics done;
 https://issues.apache.org/jira/browse/CASSANDRA-1427 is open to
 improve it
 
 Decommission: done
 
 Map/reduce support: done
 
 ColumnFamily / Keyspace definitions w/o restart: done
 
 Design documentation: started at
 http://wiki.apache.org/cassandra/ArchitectureInternals
 
 Insert multiple rows at once: done
 
 Remove_slice_range / remove_key_range: turned out to be a *lot* harder
 than it looks at first.  Postponed indefinitely.
 
 Secondary indexing: done
 
 Caching: done (with some enhancements possible such as
 https://issues.apache.org/jira/browse/CASSANDRA-1969 and
 https://issues.apache.org/jira/browse/CASSANDRA-1956)
 
 Bulk delete (truncate): done
 
 I would add,
 
 User documentation: done (http://www.riptano.com/docs)
 
 Large row support: done
 
 Improved replication strategies and more sophisticated ConsistencyLevels: done
 
 Efficient bootstrap/streaming: done
 
 Flow control: done
 
 Network-level compatibility between releases: scheduled
 (https://issues.apache.org/jira/browse/CASSANDRA-1015)
 
 -- 
 Jonathan Ellis
 Project Chair, Apache Cassandra
 co-founder of Riptano, the source for professional Cassandra support
 http://riptano.com


Re: Time for 1.0

2011-01-11 Thread Jonathan Ellis
On Tue, Jan 11, 2011 at 7:35 PM, Jonathan Ellis jbel...@gmail.com wrote:
 The list--

Through a copy/paste error I left out the first one:

Increment/decrement: done

:)

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com


Re: CQL status

2011-01-11 Thread Tristan Tarrant
what we need now is a jdbc driver...
On Jan 12, 2011 3:00 AM, Courtney Robinson sa...@live.co.uk wrote:
 ?On Tue, Jan 11, 2011 at 7:27 PM, Courtney Robinson sa...@live.co.uk
 wrote:
 ?Having been pointed to
 https://issues.apache.org/jira/browse/CASSANDRA-1704
 I wanted to know what the state of that was.
 Eric Evans said changes had been pushed to SVN, can I check out the
latest
 head and play with it?

Yes.

 Checking out now to have a look.


 Looking at the comments, if its not too late here's my 2cents.

These were both addressed in the 1704 design, by the time we were done
 with it. :)

 Looking through the rest of the posts on Jira now and saw :-)

 In the proposal there was ASC and DESC on the end of the query template,
 assuming here that this implies being able to sort records.

There is ASC and DESC but not ORDER BY, so it is only taking advantage
 of the natural sort order.

 Makes sense

 Being able to use an SQL like syntax should be a matter of convenience
and
 only where it will not force incompatibilities.

Correct.

 :)
 --
 Jonathan Ellis
 Project Chair, Apache Cassandra
 co-founder of Riptano, the source for professional Cassandra support
 http://riptano.com



Re: Time for 1.0

2011-01-11 Thread Colin Taylor
 User documentation: done (http://www.riptano.com/docs)

Apologies if this has been covered elsewhere but, is this a permanent
home? Is there to be mirror on the official site? Surely if the
project itself doesn't have user documentation then the milestone has
not been reached by the project.

I understand the motivation and it is Riptano's right of course, but
the project still needs its own comprehensive user documentation.

cheers
Colin.


Re: Time for 1.0

2011-01-11 Thread Eric Evans
On Tue, 2011-01-11 at 19:35 -0600, Jonathan Ellis wrote:
 Way back in Nov 09, we did a users survey and asked what features
 people wanted to see.  Here was my summary of the responses:
 http://www.mail-archive.com/cassandra-user@incubator.apache.org/msg01446.html
 
 Looking at that, we've done essentially all of them.  I think we can
 make a strong case that our next release should be 1.0; it's
 production ready, it's reasonably feature-complete, it's documented,
 and we know what our upgrade path story is.

-0

I've said it elsewhere, but the only reason to fuss about a 1.0, is that
it is loaded with special meaning.  To impart some vague notion of
readiness on people who should be paying less attention to a number, and
doing more due diligence.  Feels like pandering to me, or cargo-culting.

I'd rather drop the leading the 0 and continue to number releases
sequentially the way we have.  If our  1 versioning is signaling a lack
of readiness, and if = 1 is a necessary gate, then 8.0 should work
equally as well.  Better in fact, 8 times better!

-- 
Eric Evans
eev...@rackspace.com



Re: CQL status

2011-01-11 Thread Eric Evans
On Wed, 2011-01-12 at 05:21 +0100, Tristan Tarrant wrote:
 what we need now is a jdbc driver...

https://issues.apache.org/jira/browse/CASSANDRA-1710

 On Jan 12, 2011 3:00 AM, Courtney Robinson sa...@live.co.uk wrote:
  ?On Tue, Jan 11, 2011 at 7:27 PM, Courtney Robinson sa...@live.co.uk
  wrote:
  ?Having been pointed to
  https://issues.apache.org/jira/browse/CASSANDRA-1704
  I wanted to know what the state of that was.
  Eric Evans said changes had been pushed to SVN, can I check out the
 latest
  head and play with it?
 
 Yes.
 
  Checking out now to have a look.
 
 
  Looking at the comments, if its not too late here's my 2cents.
 
 These were both addressed in the 1704 design, by the time we were done
  with it. :)
 
  Looking through the rest of the posts on Jira now and saw :-)
 
  In the proposal there was ASC and DESC on the end of the query template,
  assuming here that this implies being able to sort records.
 
 There is ASC and DESC but not ORDER BY, so it is only taking advantage
  of the natural sort order.
 
  Makes sense
 
  Being able to use an SQL like syntax should be a matter of convenience
 and
  only where it will not force incompatibilities.
 
 Correct.


-- 
Eric Evans
eev...@racklabs.com