riak

Does anyone have example code for mapreduce for Riak that can be run on a single Riak node. cd ~/riak erl -name zed@127.0.0.1 -setcookie riak -pa apps/riak/ebin In the shell: # connect to the server > {ok, Client} = riak:client_connect('riak@127.0.0.1'). {ok,{riak_client,'riak@127.0.0.1',<<6,201,208,64>>}} # create and insert objects > Client:put(riak_object:new(<<"groceries">>, <<"mine">>, ["eggs", "bacons"]), 1). ok > Client:put(riak_object:new(<<"groceries">>, <<"yours">>, ["eggs", "sausages"]), 1). ok # create Map and Reduce functions > Count = fun(G, 'undefined', 'none') -> [dict:from

I'm using an instanced Amazon EC2 virtual Ubuntu 12.04 server as my single Riak node. I've gone through all the proper stages of setting up Riak on the instance using the guide on the basho website here . Where x.x.x.x is the private IP address of the instance, this included: Installation Using sudo su - to gain root privileges (EC2 logs me in as 'Ubuntu'). Installing the SSL Lib with: sudo apt-get install libssl0.9.8 Downloading the 64-bit package for 12.04: wget http://downloads.basho.com.s3-website-us-east-1.amazonaws.com/riak/CURRENT/ubuntu/precise/riak_1.2.1-1_amd64.deb Then unpacking via

Using Riak I want to append data sequentially in a way that I can obtain all of the data I appended from time to time. Think of logs, if I pick incremented log rows and transfer them to riak, at some point I want to reconstitute all what I have appended. I thought of doing this by creating a new bucket for that purpose, then add keys defined by a sequential number or datetime stamp, and add the content to it, then use the list keys API and reconstitute the data I need. The problem with that is that the list key API is not efficient and production recommended. What I like about this approach is

/home/khorkak> sudo riak-admin bucket-type Usage: riak-admin bucket-type <command> The follow commands can be used to manage bucket types for the cluster: list List all bucket types and their activation status status <type> Display the status and properties of a type activate <type> Activate a type create <type> <json> Create or modify a type before activation update <type> <json> Update a type after activation /home/khorkak> Well I have a set of bucket types I created while trying some things out that I no longer want around - can I get rid of these without reinstalling Riak? Unfortunately

I am looking to store pictures in a NoSQL database (<5MB) and link them to articles in a different bucket. What kind of speed does Riak's link walking feature offer? Is it like a RDBMS join at all? Links are not at all similar to JOINs (which involve a Cartesian product), but they can be used for similar purposes in some senses. They are very similar to links in an HTML document. With link-walking you either start with a single key, or you create a map-reduce job that starts with multiple keys. (Link-walking/traversal is actually a special case of map-reduce.) Those values are fetched, their

I'm looking for one place that summarizes the main properties of the NoSQL databases that I keep seeing referenced - in particular, MongoDB, Riak, Redis, Memcached, Membase, and Cassandra. Types of queries, acid, architecture for/properties of scaling, etc. All in memory, overflow to disk, backup on disk, or mainly only indexes in memory? Probably one of the best source which summarizes basic information (and points you to more detailed source in the first place) about various nosql databases is this website. Other than that you should check out these: Cassandra vs MongoDB vs CouchDB vs Redis

I am looking for a simple way to store and retrieve millions of xml files. Currently everything is done in a filesystem, which has some performance issues. Our requirements are: Ability to store millions of xml-files in a batch-process. XML files may be up to a few megs large, most in the 100KB-range. Very fast random lookup by id (e.g. document URL) Accessible by both Java and Perl Available on the most important Linux-Distros and Windows I did have a look at several NoSQL-Platforms (e.g. CouchDB, Riak and others), and while those systems look great, they seem almost like beeing overkill: No

What are the problems, if any, of storing binary data in Riak? Does it effect the maintainability and performance of the clustering? What would the performance differences be between using Riak for this rather than a distributed file system? Elad Adding to @Oscar-Godson's excellent answer, you're likely to experience problems with values much larger than 50MBs. Bitcask is best suited for values that are up to a few KBs. If you're storing large values, you may want to consider alternative storage backends, such as innostore . I don't have experience with storing binary values, but we've a