Hi Luke,Can you please advice. ?
"I have a production database which is fairly large and uses Secondary Indexes.
I was planning to move away from Secondary Index to RIAK Search(SOLR). Can
someone please let me know if Active Anti-Entropy will take care of ensuring
that all the existing data that
Hello Igor,
Deletions should be a strongly consistent operation, yes. If after a
successful strongly consistent delete a GET of that key returns stale
data something is likely wrong, be it with your application, the
cluster, or Riak itself.
That said, deletions don't actually remove keys from Ria
I disagree with whoever said that. User information (like a profile or
account) is some of the easiest to implement with eventual consistency,
namely because it would be rare to be in conflict (only a single actor
updating), and conflict resolution can be performed trivially without
intervention or
Is deleting a strongly consistent key a consistent operation? I have found in
testing that if I delete a key and then attempt to immediately reuse it,
sometimes the delete completes after I have reused it. Should I expect that
when I get a 204 from a delete that I can immediately create a new
I've heard several times now that key/value stores aren't ideal for storing
user information. Why is this true?
Does this apply to Riak even with strong consistency in 2.0?
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mai
