Re: Riak-CS Node.js client

Hi, thanks for your help Uenishi. I'm using Riak 1.5.2, and AWS Node.js SDK 2.1.14 and the example code I'm running is bellow. I have beed trying with and without forcing a singing version. With some debug I found that the default is the use the s3 signer If I force v2 I have another error, "

Re: Riak-CS Node.js client

> The s3 signer uses the signs the "canonicalizedResource" and that have the > query parameters already encoded, so I tried to replace the "%3D" by the "=" > and it already works. Yey! The culprit is here. Most client mistakenly encodes Multipart uploadId although it is already supposed to be ur

repair-2i fails: Error: index_scan_timeout

We have a 5 node cluster running 2.0.0beta1. Our 2i indexes seem to return different responses depending on which node you hit, so I'm trying to rebuild them. I'm trying to run riak-admin repair-2i and it fails with Error: index_scan_timeout An example: # riak-admin repair-2i 0 Will repair 2i on

Using Riak for Data with many Entities and Relationships

I am designing a web application that, for the purpose of this conversation, deals with three main entities: - Users - Groups - Tasks Users are members of groups, and tasks belong to groups. Early in the development of the application, Neo4j was used to store the data. Users would have