Hi,
In the "atomically updating multiple keys" thread I mentioned the issue of
dirtying the database with orphan keys and thought that topic was worth
starting a new thread.
Say you have an operation that requires creating two keys, A and B, and you
succeed in creating A but fail in creating B
Kelly,
Thank you for the prompt response.
I installed from DEB and it's working just fine now.
Randy
On Nov 2, 2011, at 5:42 PM, Kelly McLaughlin wrote:
> Randy,
>
> Using the DEB package is probably the best way to start out. It'll be quicker
> to get started and you won't have to worry a
Evening, Morning, Afternoon, to All -
Huge Recap for today: new code, new docs, talks, jobs, and more.
Enjoy,
Mark
Community Manager
Basho Technologies
wiki.basho.com
twitter.com/pharkmillups
Riak Recap for October 31 - November 1
==
Randy,
Using the DEB package is probably the best way to start out. It'll be quicker
to get started and you won't have to worry about installing all the tools to
build from source. Last I checked the erlang version of the package that Ubuntu
installs via apt is old and doesn't work with the lat
I'm new to Riak so please forgive a newbie question. I searched the email
archives and did not see a discussion about this...
I will setup several VMWare Ubuntu instances to run a Riak ring so I can
perform some testing and then development.
What are the relative advantages and disadvantages of
Hi Sajithkumar,
Yes, using the LevelDB-based backend you can index long integers. In fact,
you can index integers of arbitrary size, there is no real limit except for
memory / disk space.
In the future, other backends may limit you to 32-bit integers.
Best,
Rusty
On Wed, Nov 2, 2011 at 4:48 PM,
Does secondary integer index support long value. Or it is limited to integer
only?
This message is private and confidential. If you have received it in error,
please notify the sender and remove it from your system.
_
Please add this explanation to the wiki. I'd do it, but i'm working with an
RDBMS right now and I am neither distributed nor eventually consistent.
---
Jeremiah Peschka - Founder, Brent Ozar PLF, LLC
Microsoft SQL Server MVP
On Nov 2, 2011, at 8:18 AM, Ryan Zezeski wrote:
> On Tue, Nov 1, 2011 a
On 11/02/2011 10:40 AM, Justin Karneges wrote:
Thanks everyone for these replies (and also Aphyr, off-list). It has helped me
confirm my suspicions and sounds like I'm on the right track.
For one of my keys, I am doing sort of a manual "last write wins" by having
the reader sort siblings by tim
Thanks everyone for these replies (and also Aphyr, off-list). It has helped me
confirm my suspicions and sounds like I'm on the right track.
For one of my keys, I am doing sort of a manual "last write wins" by having
the reader sort siblings by timestamp, then by vtag, to deterministically
sel
On Wednesday, November 02, 2011 08:18:48 AM Ryan Zezeski wrote:
> No, last_write_wins=true doesn't care about the value of allow_mult. Only
> one should be true at the same time, and the default is to have both set to
> false. Perhaps making an imaginary setting to displace these two would
> help
On Tue, Nov 1, 2011 at 5:51 PM, Justin Karneges wrote:
> Are you saying that allow_mult=false + last_write_win=false is the same as
> allow_mult=false + last_write_win=true ?
>
> False/false may be the default behavior, but I want to know what that
> behavior
> is. :)
>
>
Justin,
No, last_write_
An approach similar to #1 is implemented in statebox
http://github.com/mochi/statebox - basically the trick is to store an
operation queue along with the data, and to put some constraints on how
operations must work so that they can be repeated for conflict resolution.
On Wednesday, November 2, 20
On Nov 1, 2011, at 19:23 , Justin Karneges wrote:
> On Tuesday, November 01, 2011 05:16:43 AM Tuure Laurinolli wrote:
>> Yes, you would get causal consistency with N=3, R=2, W=2. If client A,
>> using some side channel, tells client B that it inserted something, it is
>> guaranteed that client B
I have done some tests with read-your-writes consistency i Riak 1.0.
I am testing with 3 Riak nodes and N=3, W=2 and R=2 (standard config)
I get read-your-writes consistency as long as the client sends write and
read request to one of the three Riak node only. But if I write data with a
connectio
What you'd usually do is somewhere between 2) and 3) - namely, accept that
siblings might occur (although rarely). Also, you'd have a resolution function
with the property (besides being deterministic) that reconciliating two
identical siblings would yield the same - i.e., f(X,X) = X.
__
16 matches
Mail list logo
