> Last time I checked, this was not true for batch writes. The row
> mutations were started sequentially (ie, for each mutation check
> availability, then kick off an aynchronous write), so it was possible
> for the first to succeed, and the second to fail with an
> UnavailableException.
>
Thats a
I'am using Java + Tomcat + Spring + Hector on Lunux - I works as always
just great.
It is also not bad idea to mix databases - Cassandra is not always solution
for every problem, Cassandra + Mongo could be ;)
On Fri, Aug 17, 2012 at 7:54 PM, Aaron Turner wrote:
> My stack:
>
> Java + JRuby + R
People are aware of the need, but I don't think it's on any roadmaps yet,
and there are other "necessary features" that have been getting more
attention so far. I hope that I or someone else can get to it fairly soon,
but I don't have any guarantees to give. In the meantime, patches are
welcome!
p
"assume" isn't in CQL, that's right--however, it IS in cqlsh. You're just
using it wrong. Try:
ASSUME KEY values are text;
Remember, in CQL, row keys are just another column, so you need to treat
"KEY" (if that's the name of your key column) as a normal column. "HELP
ASSUME" in cqlsh migh
