Yeah i've seen how it's done in CQL3 is just wasn't sure if it was a solid
standard yet. I will probably go the CQL route as right now i am doing each
insert individually.
On Sat, Sep 22, 2012 at 11:34 AM, Tyler Hobbs wrote:
> If there's not already a well-written client in place, you should str
I'm not sure, but I think 1.0.3 is the wrong branch:
http://f.cl.ly/items/2z1q1k3Q402L2z061S3m/Apache%20Hadoop%20Versions.png
I need the branch that goes down .22 to .23
The problem is
"You lose binary backward compatibility
Exception in thread "main" java.lang.IncompatibleClassChangeError: Fou
Hello,
Does CQL's IN(...) predicate have the same meaning as SQL's IN(...)? I'm
asking this, because I get results that I cannot explain:
cqlsh:xpl1> select * from t1 where col2='bar1';
pk | col1 | col2
--+--+--
pk1b | foo1 | bar1
pk1 | foo1 | bar1
pk1a | foo1 | bar1
pk1c | f
If there's not already a well-written client in place, you should strongly
consider using cql3 instead. It will save you a ton of work.
If you want to ignore that advice, you can look at the send() and insert()
methods in phpcassa:
https://github.com/thobbs/phpcassa/blob/master/lib/phpcassa/Batch
