Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of 0x6e6562@gmail.com designates
 209.85.214.44 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Batch mutation streaming 
From: Ben Hood <0x6e6562@gmail.com>
Message-Id: <DEED7B73-1471-46EE-BF76-3EFEE1580E26@gmail.com>
Date: Fri, 7 Dec 2012 13:34:43 +0000
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Mime-Version: 1.0 (1.0)

Hi,

I'd like my app to stream a large number of events into Cassandra that origi=
nate from the same network input stream. If I create one batch mutation, can=
 I just keep appending events to the Cassandra batch until I'm done, or are t=
here some practical considerations about doing this (e.g. too much stuff buf=
fering up on the client or server side, visibility of the data within the ba=
tch that hasn't been closed by the client yet)? Barring any discussion about=
 atomicity, if I were able to stream a largish source into Cassandra, what w=
ould happen if the client crashed and didn't close the batch? Or is this kin=
d of thing just a normal occurrence that Cassandra has to be aware of anyway=
?

Cheers,

Ben=