David Strauss davidstrauss.net> writes:
>
> You can actually already perform "manual conflict resolution" in
> Cassandra by naming your columns so that they don't squash each other in
> Cassandra's internal replication. Then, ensure the code that accesses
>
#x27;ve made things clearer, feel free to poke holes in my logic
> :)
>
> Hope that helps.
> Aaron
>
>
> On 23 Apr 2011, at 09:02, Edward Capriolo wrote:
>
> On Fri, Apr 22, 2011 at 4:31 PM, Milind Parikh
> wrote:
>
> Is there a chance of getting manual conflict res
On Mon, 2011-04-25 at 03:50 -0700, Milind Parikh wrote:
> I suppose the term 'silently dropped' is a matter of perspective. C
> makes an explicit automated choice of latest-timestamp-wins. In
> certain situations, this is not the appropriate choice.
I would still insist that using Cassandra and ex
I respond @ the
speed of thought
/
On Apr 25, 2011 3:54 AM, "David Strauss" wrote:
On Fri, 2011-04-22 at 13:31 -0700, Milind Parikh wrote:
> Is there a chance of getting manual confli...
You can actually already perform "manual conflict resolution" in
On Fri, 2011-04-22 at 13:31 -0700, Milind Parikh wrote:
> Is there a chance of getting manual conflict resolution in Cassandra?
> Please see attachment for why this is important in some cases.
You can actually already perform "manual conflict resolution" in
Cassandra by naming
1 PM, Milind Parikh wrote:
>> Is there a chance of getting manual conflict resolution in Cassandra?
>> Please see attachment for why this is important in some cases.
>>
>> Regards
>> Milind
>>
>>
>
> I think about this often. LDAP servers like S
On Fri, Apr 22, 2011 at 4:31 PM, Milind Parikh wrote:
> Is there a chance of getting manual conflict resolution in Cassandra?
> Please see attachment for why this is important in some cases.
>
> Regards
> Milind
>
>
I think about this often. LDAP servers like SunOne ha
