Jenkins build is back to stable : Cassandra-Coverage #36

See

Re: Why is the CQL jar versioned independently?

On Tue, 2011-04-26 at 22:42 +0100, Stephen Connolly wrote: > so will cql get its own tree from which releases well be cut, or will > it get released always at the same time? It would probably make sense at some point to separate the build for the Java client code so that releases could be made in

Re: Why is the CQL jar versioned independently?

so will cql get its own tree from which releases well be cut, or will it get released always at the same time? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 26 Apr 2011 22

Re: Why is the CQL jar versioned independently?

On Tue, 2011-04-26 at 13:31 +0100, Stephen Connolly wrote: > From what I can see, the intent is to always release lock-step in sync > with cassandra, in which case the version number should be the > cassandra version number... > > unless you are implying that this is "CQL version 1.0.0" and there

Jenkins build is back to normal : Cassandra #865

See

Re: [VOTE] Release Apache Cassandra 0.7.5

https://repository.apache.org/content/repositories/orgapachecassandra-115/ contains the missing artifact for deployment to maven central https://issues.apache.org/jira/browse/CASSANDRA-2562 will patch 0.7.x to ensure this works going forward. Unless anyone objects, please consider the 115 stagi

Re: [VOTE] Release Apache Cassandra 0.7.5

I've spotted a minor issue with my CASSANDRA-1851 patch... I'll raise a JIRA to address, and I will have to attach a staging repository to this vote for it to be closed successfully (i.e. we are missing the cassandra-parent pom that all the 0.7.5 poms inherit from) On 22 April 2011 18:17, Sylvain

[VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central

Per the Apache release rules, only artifacts which have been voted on can be released. Thus, as I missed the main release vote, I cannot tag onto the end. The artifacts I want to release are: https://repository.apache.org/content/repositories/orgapachecassandra-114/ Notes: * The tar.gz files a

Re: [VOTE] Release Apache Cassandra 0.7.5

+1 On Fri, Apr 22, 2011 at 12:17, Sylvain Lebresne wrote: > I propose the following artifacts for release as 0.7.5. > > SVN: > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960 > Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-113/org/

hinted handoff should use its own sstables

So maybe this idea has been sent around before but I would like to know what everyone thinks. We have a huge column family called bigdata let's say 200 gb a node. We have used cass* as you would expect we never read before writing and during our bulk loading we can get rates like 2000 inserts per s

Why is the CQL jar versioned independently?

Eric, In looking at the build, I see that the CQL jar gets its own version number... Does that make sense? >From what I can see, the intent is to always release lock-step in sync with cassandra, in which case the version number should be the cassandra version number... unless you are implying t

Build failed in Jenkins: Cassandra #864

See Changes: [slebresne] merge CASSANDRA-2557 from trunk -- [...truncated 2004 lines...] [junit] Testsuite: org.apache.cassandra.db.context.CounterContextTest [junit] Tests run: 6, Failur