zan/orm/layer3/spi/db/cassandra/CassandraSession.java
For how to do with thrift, you could look at astyanax.
I use it on that project for indexing for the ORM layer we use(which is
not listed on the cassandra ORM's page as of yet ;) ).
Later,
Dean
On 8/2/12 9:50 AM, Greg Fausak g
I think I'm having a major brain fart here, I am just not getting something.
I have the following CF declared in CQL -3
create columnfamily testCQL5( ac_event_id int, ac_c text,
ac_mtcreation bigint, ac_action text , ac_id text, PRIMARY KEY (ac_c,
ac_mtcreation));
I can do this:
cqlsh:op2
I've been using the cql3 to create a composite table.
Can I use the thrift interface to accomplish the
same thing? In other words, do I have to use cql 3 to
get a composite table type? (The same behavior as
multiple PRIMARY key columns).
Thanks,
---greg
Hi Ivan,
No Cassandra does not support transactions.
I believe each operation is atomic. If that operation returns
a successful result, then it worked. You can't do things like
bind two operations and guarantee is either fails they both fail.
You will find that Cassandra doesn't do a lot of
Mina,
Thanks for that post. Very interesting :-)
What sort of things are you graphing? Standard *nux stuff
(mem/cpu/etc)? Or do you
have some hooks in to the C* process (I saw somoething about port 1414
in the .yaml file).
Best,
-g
On Thu, Jul 26, 2012 at 9:27 AM, Mina Naguib
I thought I'd give this a try:
create columnfamily
at_event__ac_c
(
ac_c text,
ac_creation bigint,
ac_name text,
ac_value text,
PRIMARY KEY (ac_c, ac_creation)
) with compression_parameters:sstable_compression = '';
Then, insert a few columns:
begin batch using
I did something similar for my installation, but I used ENV variables:
I created a directory on a machine (call this the master) with directories
for all of the distributions (call them slaves). So, consider:
/master/slave1
/master/slave2
...
/master/slaven
then i rdist this to all of my
.
Anyway, I didn't mean to hijack Oleg's thread. I am interested
in the original question about the serialization/deserialization on write.
Does anybody know?
-g
On Wed, Jun 13, 2012 at 11:45 PM, Derek Williams de...@fyrie.net wrote:
On Wed, Jun 13, 2012 at 9:08 PM, Greg Fausak g...@named.com
I have playing around with composite CFs, I have one declared:
create columnfamily
at_event_ac_c
(
ac_event_id int,
ac_creation timestamp,
ac_action text,
ac_addr text,
ac_advisory_id text,
ac_c text,
...
ev_sev text,
...
ev_total text,
ev_url text,
That's a good question. I just went to a class, Ben was saying that
any action on a super column requires de-re-serialization. But, it
would be nice if a write had this sort of efficiency.
I have been playing with the 1.1.1 version, in that one there are
'composite' columns, which I think are
Interesting.
How do you do it?
I have a version 2 CF, that works fine.
A version 3 table won't let me invent columns that
don't exist yet. (for composite tables). What's the trick?
cqlsh -3 cas1
use onplus;
cqlsh:onplus select * from at_event where ac_event_id = 7690254;
ac_event_id |
11 matches
Mail list logo
