On Fri, Nov 2, 2012 at 8:09 PM, Vivek Mishra wrote:
> any idea, how to insert into a column family for a column of type "blob" via
> cql query?
Yes, most of them involve binary data that is hex-encoded ascii. :)
--
Eric Evans
Acunu | http://www.acunu.com | @acunu
Hi,
any idea, how to insert into a column family for a column of type "blob"
via cql query?
-Vivek
Hi all,
I'm using twitter/cassandra ruby client, trying to pool a connection in a
static variable.
@@client = Cassandra.new(keyspace, host, :retries => retries,
:connect_timeout => connect_timeout, :timeout => timeout,
:exception_classes => [])
but the connection returns "stream closed error"
On Fri, Nov 2, 2012 at 12:38 AM, Manu Zhang wrote:
>> It splits into a contiguous range, because truly upgrading to vnode
>> functionality is another step.
>
> That confuses me. As I understand it, there is no point in having 256 tokens
> on same node if I don't commit the shuffle
This isn't exac
> IIRC, tombstone timestamps are written by the server, at compaction
> time. Therefore if you have RF=X, you have X different timestamps
> relative to GCGraceSeconds. I believe there was another thread about
> two weeks ago in which Sylvain detailed the problems with what you are
> proposing, when
On Fri, Nov 2, 2012 at 2:46 AM, horschi wrote:
> might I ask why repair cannot simply ignore anything that is older than
> gc-grace? (like Aaron proposed) I agree that repair should not process any
> tombstones or anything. But in my mind it sounds reasonable to make repair
> ignore timed-out dat
I ran the same cql query against my 3 nodes (after adding the third and
repairing each of them):
On the new node:
cqlsh:mykeyspace> select '20121029#myevent' from 'mycf' where key =
'887#day';
20121029#myevent
---
4983
On the 2 others (old nodes):
cqlsh:mykeyspac
Hi Sylvain,
might I ask why repair cannot simply ignore anything that is older than
gc-grace? (like Aaron proposed) I agree that repair should not process any
tombstones or anything. But in my mind it sounds reasonable to make repair
ignore timed-out data. Because the timestamp is created on the
My guess is that 108 has become a new replica for the streamed data on 103,
104, 107, which is decided by your per-keyspace replica placement strategy.
When we bootstrap, we do not simply stream data from 102 to 108. Rather, we
calculate all the ranges that 108 is responsible for.
So looking from t
