(Radim: I'm assuming you mean "do not delete already deleted columns" as
Ross doesn't delete his rows.)
Just to be clear about Ross' situation: he continually inserts columns and
later deletes columns from the same set of rows. As long as he *doesn't* *keep
deleting already-deleted columns* (wh
Has anyone seen this particular NPE before from Cassandra?
This is on 1.0.8. It seems to happen transiently on multiple nodes in my
cluster, every so often, and goes away.
ERROR [Thrift:45] 2012-03-26 19:59:12,024 Cassandra.java (line 3041)
Internal error processing get_slice
java.lang.NullPoin
al representation of the
> denormalized timeline rows" diagram.
> Where your UUID is the "user_id" from the example, and your priority is
> the "tweet_id"
>
> -Jeremiah
>
>
> --
> *From:* John Laban [j...@pagerduty.com
sandra-1-1
>
> Or you can store all the priorities that are valid for an ID in another
> row.
>
> Cheers
>
> -----
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 14/03/2012, at 1:05 PM, John Laban wrote:
>
&
Any help would be appreciated,
John
On Tue, Mar 13, 2012 at 12:15 PM, John Laban wrote:
> Hi,
>
> I have a column family that uses a composite key:
>
> (ID, priority) -> ...
>
> Where the ID is a UUID and the priority is an integer.
>
> I'm trying to perform
uates https://github.com/Netflix/curator? this seems to be a
> versatile package.
>
> On Tue, Dec 13, 2011 at 6:06 AM, John Laban wrote:
>
>> Ok, great. I'll be sure to look into the virtualization-specific NTP
>> guides.
>>
>> Another benefit of using Cass
> Hi John,
>
> On 12 December 2011 19:35, John Laban wrote:
>>
>> So I responded to your algorithm in another part of this thread (very
>> interesting) but this part of the paper caught my attention:
>>
>> > When client application code releases a lock, tha
t;>
>>>> There is a doc describing the algorithm, to which may be added an
>>>> appendix describing a protocol so that locking can be interoperable between
>>>> the clients. That could be extended to describe a protocol for
>>>> transactions. Wo
t; size increases
>
> Best, Dominic
>
> On 11 December 2011 01:53, Guy Incognito wrote:
>
>> you could try writing with the clock of the initial replay entry?
>>
>> On 06/12/2011 20:26, John Laban wrote:
>>
>> Ah, neat. It is similar to what was propo
.fightmymonster.com/Shared/docs/Wait%20Chain%20Algorithm.pdf
>>
>> Final word on this re transactions: if/when transactions are added to
>> locking system in Pelops/Hector/Pycassa, Cassandra will provide better
>> performance than ZooKeeper for storing snapshots, especially a
le data into one column
> - make the job
> - remove (or expire) your column.
>
> if there is a problem during "making the job", you keep the possibility to
> replay and replay and replay (synchronously or in a batch).
>
> Regards
>
> Jérémy
>
>
> 201
Hello,
I'm building a system using Cassandra as a datastore and I have a few
places where I am need of transactions.
I'm using ZooKeeper to provide locking when I'm in need of some concurrency
control or isolation, so that solves that half of the puzzle.
What I need now is to sometimes be able t
12 matches
Mail list logo