On Fri, 2011-01-14 at 13:11 -0600, Eric Evans wrote:
> > Everyone on chrome commits to trunk first. I think the important
> > change we could make is to keep everyone closer to trunk. We spend a
> > good deal of effort back-porting patches between major versions. I
> > think we should make the majo
On Jan 17, 2011, at 9:01 PM, Eric Evans wrote:
> On Mon, 2011-01-17 at 12:12 -0500, Jake Luciani wrote:
>> Some context: We have begun the process of removing Avro from the
>> service layer CASSANDRA-926. We currently use Avro for schema
>> migrations internally, and we have two open items that a
On 18 January 2011 14:30, Eric Evans wrote:
> On Tue, 2011-01-18 at 13:13 +, Stephen Connolly wrote:
>> Is this something that people are OK with?
>
> Why? What are the advantages?
1. It will make deploying to central easier (as ivy does not deploy
correct poms, and maven-ant-tasks can gener
On Tue, 2011-01-18 at 13:13 +, Stephen Connolly wrote:
> Is this something that people are OK with?
Why? What are the advantages?
--
Eric Evans
eev...@rackspace.com
Is this something that people are OK with?
It will result in the version details being specified from the
build.xml and not a separate ivy.xml
Which branch shall I target first... My preference is to target 0.7
and then when the modularization takes place in trunk/0.8 it will be
on top of the mav
Have a read about JVM heap sizing here
http://wiki.apache.org/cassandra/MemtableThresholds
If you let people create keyspaces with a mouse click you will soon run out of
memory.
I use Cassandra to provide a self service "storage service" at my organisation.
All virtual databases operate in the
