Re: Any performance comparison / best practice advice for choosing a riak backend ?

2010-08-29 Thread Neville Burnell
Thanks Sean, Do riak_kv_gb_trees_backend and riak_kv_fs_backend have particular strengths/weaknesses? Kind Regards Neville When would one use On 29 August 2010 01:02, Sean Cribbs wrote: > Your choice should be dictated by your use-case. In most situations, > "riak_kv_bitcask_backend" (the de

map reduce -> JSON.parse error

2010-08-29 Thread Nils Petersohn
hello, when i have a simple json bucket entry like this: http://pastebin.com/XcWcvmYe than i always get an error: {"lineno":483,"message":"JSON.parse","source":"unknown"} the stacktrace is here: http://pastebin.com/EGzUKqps when i try to use a much simpler JSON string than there is no error.

Re: map reduce -> JSON.parse error

2010-08-29 Thread James Sadler
Hi Nils, I ran into a similar problem last week. It seems that certain characters can cause the JSON parser that ships as part of the Spidermonkey JavaScript interpreter that Riak uses to throw an exception. Off the top of my head, I think I managed to make it barf with a \r embedded within a str

Re: Any performance comparison / best practice advice for choosing a riak backend ?

2010-08-29 Thread Sean Cribbs
I'm not certain the purpose of the gb_trees backend as opposed to ets, although I imagine it might have faster lookups (and slower inserts). The fs_backend uses one file per object, meaning that you will need lots of files open on a live system. Sean Cribbs Developer Advocate Basho Technologi

Re: map reduce -> JSON.parse error

2010-08-29 Thread Sean Cribbs
I have found that error comes from json2.js, and in the future we should just use Spidermonkey's builtin. https://issues.basho.com/show_bug.cgi?id=525 Sean Cribbs Developer Advocate Basho Technologies, Inc. http://basho.com/ On Aug 29, 2010, at 10:05 AM, James Sadler wrote: > Hi Nils, > > I

Re: map reduce -> JSON.parse error

2010-08-29 Thread Nils Petersohn
yes :) i removed the comment entry, which indeed had some \r chars in it now i am able to let the mapreduce function run. hope you can fix this issue 525 soon. nils On Aug 29, 2010, at 5:01 PM, Sean Cribbs wrote: > I have found that error comes from json2.js, and in the future we should just