Yes, you are correct. Setting allow_mult will not be needed with your
setup. I then assume the clients are guaranteed to use unique key when
creating the objects.
Runar
2013/9/27 Brady Wetherington br...@bespincorp.com
Since I'm doing a write-once, update-never environment - I don't see how
I'm doing the POST/PUT to the bucket thing, where it makes a key for me.
-B.
On Sep 28, 2013, at 3:53 PM, Runar Jordahl runar.jord...@gmail.com wrote:
Yes, you are correct. Setting allow_mult will not be needed with your setup.
I then assume the clients are guaranteed to use unique key
I think that CRDT support in Riak will meet your needs. It pushes garbage
collection down to Riak itself so you don't have to worry about it.
The downside is that it is only in Riak 2.0 and not all clients support it
yet or their support is immature. The current support in the .net client is
very
Oh, I get what the siblings/allow_mult business is for, just wondering if I
can use it off-label a little, and eventually do 'conflict resolution'
which would make the results be much more reasonable.
But it sounds like I shouldn't do that. That's totally fine.
Since I'm doing a write-once,
I've built it a solid proof-of-concept system on leveldb, and use some 2i
indexes in order to search for certain things - usually just for counts of
things.
I have two questions so far:
First off, why is Bitcask the default? Is it just because it is faster? Or
is it considered more 'stable' or
inline.
---
Jeremiah Peschka - Founder, Brent Ozar Unlimited
MCITP: SQL Server 2008, MVP
Cloudera Certified Developer for Apache Hadoop
On Wed, Sep 25, 2013 at 2:47 PM, Brady Wetherington br...@bespincorp.comwrote:
I've built it a solid proof-of-concept system on leveldb, and use some 2i
