RE: riak.py has been removed?

[Mark Jones]

Turns out my problem was that protocol buffers was not installed.  I modified 
the README and am including it here.

From: riak-users-boun...@lists.basho.com 
[mailto:riak-users-boun...@lists.basho.com] On Behalf Of Jon Meredith
Sent: Thursday, April 22, 2010 9:34 PM
To: riak-users@lists.basho.com
Subject: Re: riak.py has been removed?

Hi Mark,

The python client received a significant refactor today thanks to Silas Sewell. 
 It is now more pythonic and can be installed with a setup.py file.  riak.py 
got moved into riak/__init__.py as part of that.

I'm not sure what bitbucket is up to, but a clean pull worked for me.

Jon

On 4/22/10 12:47 PM, Mark Jones wrote:
http://hg.basho.com/riak-python-client/changeset/5a6372022a1b#chg-riak.py

riak.py appears to have been removed about 9 hours ago.  Bitbucket won't 
display the change set

This changeset can not be displayed, as it is too large (cutoff was at 81.1 KB).

From: Grant Schofield [mailto:gr...@basho.com]
Sent: Thursday, April 22, 2010 1:16 PM
To: Mark Jones
Cc: riak-users@lists.basho.com
Subject: Re: Newbie Questions:


On Apr 22, 2010, at 11:56 AM, Mark Jones wrote:



Are there any speed comparisons between riak and Cassandra?

Tthere aren't any at the moment, but this is something we are interested in 
working on  
(http://blog.basho.com/2010/04/12/toward-a-consistent,-fact-based-comparison-of-emerging-database-technologies/).




How can I get the Python client?

This page: 
https://wiki.basho.com/display/RIAK/Client+Libraries#ClientLibraries-Python 
says to lookhttp://hg.basho.com/riak/src/tip/client_lib/python/riak.py but that 
link returns a 404

Thanks for pointing out the broken link, we will fix that. You can grab the 
most recent Python client here:
http://hg.basho.com/riak-python-client

The client supports both HTTP and protobuffs protocols, but you will need to be 
running the latest tip or .10rc2 release to use the protobuffs protocol.  By 
the end of the week .10 will be released and you should be able to use that 
version as well.



I'm guessing there is no C/C++ client since I didn't see one listed.

No, there isn't currently a C/C++ client, but one is in the works.




Is anyone using this thing to store 30,000   500 byte entries/second?

It is theoretically possible given good infrastructure and application design, 
but those numbers are on the very high end of current usage numbers.

Grant Schofield
Developer Advocate
Basho Technologies




___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com






___

riak-users mailing list

riak-users@lists.basho.com

http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com





README
Description: README
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: one-to-very-many link associations

[Orlin Bozhinov]

Eric Gaumer wrote:
On Thu, Apr 22, 2010 at 4:47 PM, Orlin Bozhinov > wrote:


Eric,

Thanks for the bigdata.com  link.  It's
something I had missed spotting.

The Semantic Web doesn't fit it all either.  I anticipate to much
rather search riak (with its upcoming query language) than rely
entirely on sparql.  Though I've always had the option in mind. 
If you look at my previous reply you'll see I'm considering it.  I

wonder what you think about the combined idea...

If riak won't also become a real graph backend, then I'll likely
go with an additional hosted database.  It could be a relational
db (the most readily available kind), mongodb (i.e. mongohq),
talis, etc.



Given today's landscape, and lessons learned, anyone who isn't 
thinking in terms of diverse storage infrastructures isn't listening. 
There is no single magic solution and in fact, the NoSQL ideology 
frees us from that mentality (directed toward the relational database).


So yes, a combination of diverse components sounds like a reasonable 
architecture.


Is it the ideal architecture? That's something you'll have to work out 
given your technical requirements.


In terms of storage adapters, you're misunderstanding things. What 
they're referring to is the ability to get RDF statements in/out of 
the these backends. This doesn't imply that they transform them into 
graph databases. The graph aspect would actually be something that 
RDF.rb would have to provide on top of the underlying storage 
mechanism (via a SPARQL query engine).


Without such, you have no means of traversal. RDF.rb does not support 
RDFS, OWL, or SPARQL. It's essentially an RDF serializer that can 
retrieve/store RDF statements via storage adapters. Not to imply 
that's a bad thing, you're just not going to get graph like behavior 
from it.


Regards,
-Eric


Good points and correct about RDF.rb - RDF would be useless without 
inference or search.  Perhaps for backup, as it's so portable.  I 
wouldn't mind keeping that in Riak.


Definitely though, the links would need to go into a store that has a 
SPARQL endpoint.  Based on the current list of adapters, I like RedStore 
or the Talis Platform the most.  However, it's a fast growing ecosystem 
and I'm not sure I need a semantic solution for now.  Maybe I'll add RDF 
while my foot is being shot...


Orlin




___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
   
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Riak Recap for 4/21 - 4/22

[Mark Phillips]

Hey All -

Here's the recap for the last several days.

Enjoy -

Mark

-
Community Manager
wiki.basho.com
twitter.com/pharkmillups

-

Riak Recap for 4/21 - 4/22

1) seancribbs and adamhunter had brief but valuable convo in IRC about
removing a node from a cluster. It might be of interest to some of
you. Check it out here:

http://gist.github.com/376558


2) We added some new wiki pages that have in-depth information on a
few 0.10 features:

a. Read up on Pre- and Post- Commit Hooks here:
http://wiki.basho.com/display/RIAK/Pre-+and+Post-Commit+Hooks

b. Info on the Protocols Buffers Client API here:
http://wiki.basho.com/display/RIAK/PBC+API

c. Details on the Protocol Buffers based Erlang client here:
http://wiki.basho.com/pages/viewpage.action?pageId=1245522


3) We also added a new section to the wiki called "Best Practices."
You'll notice that it's sparsely populated at the moment. Don't fret.
There is plenty more to come.

http://wiki.basho.com/display/RIAK/Best+Practices

But before we put some time against it I wanted to ask: What do you
all want to see added here? Which "Best Practices" would help you the
most?


4) chids (aka @martengustafsen) posted a bad-ass picture in IRC made
possible by the top-secret app he is working on:

 Android + GPS -> Riak + CouchDB -> Java Image API = Yesterdays lunch stroll @

http://img693.yfrog.com/img693/4576/screenshot20100421at139.png

--- > Anyone who sends along a picture of their Riak App (or more
specifically, what their Riak app makes possible) will get a fresh
Riak T-shirt.

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Building rel on Debian 2.6.26

[Matthew Pflueger]

I downloaded built Erlang successfully (minus jinterface, odbc, and
wx) then downloaded riak-0.10.  I did a make all and everything built
fine but then doing a make rel I get the following:

==> rel (generate)
ERROR: Unable to generate spec: read file info
/home/mpflueger/riak/rel/../deps/ebloom/.hg/inotify.sock failed

Has anybody else run into this?  Could this be related to my mercurial
install (I'm using 1.51 downloaded and installed normally using
python2.5).

--Matthew

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Building rel on Debian 2.6.26

[Ryan Tilder]

Sounds like you have Mercurial's inotify extension enabled.  hg showconfig
should show it.  Workaround for now would be to following the directions in
the below link for disabling the extension in the riak repo.  In
riak/.hg/hgrc:

[extensions]
inotify = !

http://mercurial.selenic.com/wiki/UsingExtensions#Enabling_an_extension

--Ryan

On Fri, Apr 23, 2010 at 8:48 AM, Matthew Pflueger <
matthew.pflue...@gmail.com> wrote:

> I downloaded built Erlang successfully (minus jinterface, odbc, and
> wx) then downloaded riak-0.10.  I did a make all and everything built
> fine but then doing a make rel I get the following:
>
> ==> rel (generate)
> ERROR: Unable to generate spec: read file info
> /home/mpflueger/riak/rel/../deps/ebloom/.hg/inotify.sock failed
>
> Has anybody else run into this?  Could this be related to my mercurial
> install (I'm using 1.51 downloaded and installed normally using
> python2.5).
>
> --Matthew
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Building rel on Debian 2.6.26

[Matthew Pflueger]

Thanks for the tip.  Unfortunately, disabling doesn't seem to work...
I disabled it in my ~/.hgrc and in ebloom's .hg/hgrc to no avail.  I
downloaded riak-0.10.tar.gz and installed so no .hg directory.  Any
other suggestions?

--Matthew



On Fri, Apr 23, 2010 at 11:56, Ryan Tilder  wrote:
> Sounds like you have Mercurial's inotify extension enabled.  hg showconfig
> should show it.  Workaround for now would be to following the directions in
> the below link for disabling the extension in the riak repo.  In
> riak/.hg/hgrc:
> [extensions]
> inotify = !
> http://mercurial.selenic.com/wiki/UsingExtensions#Enabling_an_extension
>
> --Ryan
>
> On Fri, Apr 23, 2010 at 8:48 AM, Matthew Pflueger
>  wrote:
>>
>> I downloaded built Erlang successfully (minus jinterface, odbc, and
>> wx) then downloaded riak-0.10.  I did a make all and everything built
>> fine but then doing a make rel I get the following:
>>
>> ==> rel (generate)
>> ERROR: Unable to generate spec: read file info
>> /home/mpflueger/riak/rel/../deps/ebloom/.hg/inotify.sock failed
>>
>> Has anybody else run into this?  Could this be related to my mercurial
>> install (I'm using 1.51 downloaded and installed normally using
>> python2.5).
>>
>> --Matthew
>>
>> ___
>> riak-users mailing list
>> riak-users@lists.basho.com
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Building rel on Debian 2.6.26

[Matthew Pflueger]

Cloning the riak repo and building worked fine.  However, not being
able to build from the tarball is a little disconcerting...
--Matthew



On Fri, Apr 23, 2010 at 12:13, Matthew Pflueger
 wrote:
> Thanks for the tip.  Unfortunately, disabling doesn't seem to work...
> I disabled it in my ~/.hgrc and in ebloom's .hg/hgrc to no avail.  I
> downloaded riak-0.10.tar.gz and installed so no .hg directory.  Any
> other suggestions?
>
> --Matthew
>
>
>
> On Fri, Apr 23, 2010 at 11:56, Ryan Tilder  wrote:
>> Sounds like you have Mercurial's inotify extension enabled.  hg showconfig
>> should show it.  Workaround for now would be to following the directions in
>> the below link for disabling the extension in the riak repo.  In
>> riak/.hg/hgrc:
>> [extensions]
>> inotify = !
>> http://mercurial.selenic.com/wiki/UsingExtensions#Enabling_an_extension
>>
>> --Ryan
>>
>> On Fri, Apr 23, 2010 at 8:48 AM, Matthew Pflueger
>>  wrote:
>>>
>>> I downloaded built Erlang successfully (minus jinterface, odbc, and
>>> wx) then downloaded riak-0.10.  I did a make all and everything built
>>> fine but then doing a make rel I get the following:
>>>
>>> ==> rel (generate)
>>> ERROR: Unable to generate spec: read file info
>>> /home/mpflueger/riak/rel/../deps/ebloom/.hg/inotify.sock failed
>>>
>>> Has anybody else run into this?  Could this be related to my mercurial
>>> install (I'm using 1.51 downloaded and installed normally using
>>> python2.5).
>>>
>>> --Matthew
>>>
>>> ___
>>> riak-users mailing list
>>> riak-users@lists.basho.com
>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>>
>

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Building rel on Debian 2.6.26

[Ryan Tilder]

Where did you download an 0.10 tarball from?  We haven't actually published
one yet.  Is it one of the release candidates?

Also, I am assuming that you are attempting to build on a Linux
distribution.  Do you have an /etc/mercurial or /usr/local/etc/mercurial
directory where inotify might be getting enabled?

--Ryan

On Fri, Apr 23, 2010 at 9:19 AM, Matthew Pflueger <
matthew.pflue...@gmail.com> wrote:

> Cloning the riak repo and building worked fine.  However, not being
> able to build from the tarball is a little disconcerting...
> --Matthew
>
>
>
> On Fri, Apr 23, 2010 at 12:13, Matthew Pflueger
>  wrote:
> > Thanks for the tip.  Unfortunately, disabling doesn't seem to work...
> > I disabled it in my ~/.hgrc and in ebloom's .hg/hgrc to no avail.  I
> > downloaded riak-0.10.tar.gz and installed so no .hg directory.  Any
> > other suggestions?
> >
> > --Matthew
> >
> >
> >
> > On Fri, Apr 23, 2010 at 11:56, Ryan Tilder  wrote:
> >> Sounds like you have Mercurial's inotify extension enabled.  hg
> showconfig
> >> should show it.  Workaround for now would be to following the directions
> in
> >> the below link for disabling the extension in the riak repo.  In
> >> riak/.hg/hgrc:
> >> [extensions]
> >> inotify = !
> >> http://mercurial.selenic.com/wiki/UsingExtensions#Enabling_an_extension
> >>
> >> --Ryan
> >>
> >> On Fri, Apr 23, 2010 at 8:48 AM, Matthew Pflueger
> >>  wrote:
> >>>
> >>> I downloaded built Erlang successfully (minus jinterface, odbc, and
> >>> wx) then downloaded riak-0.10.  I did a make all and everything built
> >>> fine but then doing a make rel I get the following:
> >>>
> >>> ==> rel (generate)
> >>> ERROR: Unable to generate spec: read file info
> >>> /home/mpflueger/riak/rel/../deps/ebloom/.hg/inotify.sock failed
> >>>
> >>> Has anybody else run into this?  Could this be related to my mercurial
> >>> install (I'm using 1.51 downloaded and installed normally using
> >>> python2.5).
> >>>
> >>> --Matthew
> >>>
> >>> ___
> >>> riak-users mailing list
> >>> riak-users@lists.basho.com
> >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
> >>
> >>
> >
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

How to model this data layout in Riak?

[Mark Jones]

If I wanted to build an e-mail system for millions of users, how would I go 
about doing it in  Riak?

Let's say each e-mail has the following characteristics, to, sender, header, 
body, when, attachments. Every user is identified by a userid, and to is not 
necessarily the same thing as userid.

In addition to the above characteristics, the user would be allowed to place 
tags and flags on various e-mails in a user interface.

In Cassandra could model this in two ways, one using super columns, which I've 
been advised against, and another using the order preserving partitioner where 
the key is made up something like:  userid:convoid:when.  Then I can get  a 
range to bring all of those messages up at one time.

The idea of a convoid is similar to gmails conversation grouping of emails.

With distributed key structure of riak, I'm not sure how to pull this off. 
Since the keys are all consistently hashed, the users information never be 
adjacent to each other and pulling up a group of messages will result in lots 
of seeks.



-Original Message-
From: riak-users-boun...@lists.basho.com 
[mailto:riak-users-boun...@lists.basho.com] On Behalf Of Matthew Pflueger
Sent: Friday, April 23, 2010 11:19 AM
To: Ryan Tilder
Cc: riak-users@lists.basho.com
Subject: Re: Building rel on Debian 2.6.26

Cloning the riak repo and building worked fine.  However, not being
able to build from the tarball is a little disconcerting...
--Matthew



On Fri, Apr 23, 2010 at 12:13, Matthew Pflueger
 wrote:
> Thanks for the tip.  Unfortunately, disabling doesn't seem to work...
> I disabled it in my ~/.hgrc and in ebloom's .hg/hgrc to no avail.  I
> downloaded riak-0.10.tar.gz and installed so no .hg directory.  Any
> other suggestions?
>
> --Matthew
>
>
>
> On Fri, Apr 23, 2010 at 11:56, Ryan Tilder  wrote:
>> Sounds like you have Mercurial's inotify extension enabled.  hg showconfig
>> should show it.  Workaround for now would be to following the directions in
>> the below link for disabling the extension in the riak repo.  In
>> riak/.hg/hgrc:
>> [extensions]
>> inotify = !
>> http://mercurial.selenic.com/wiki/UsingExtensions#Enabling_an_extension
>>
>> --Ryan
>>
>> On Fri, Apr 23, 2010 at 8:48 AM, Matthew Pflueger
>>  wrote:
>>>
>>> I downloaded built Erlang successfully (minus jinterface, odbc, and
>>> wx) then downloaded riak-0.10.  I did a make all and everything built
>>> fine but then doing a make rel I get the following:
>>>
>>> ==> rel (generate)
>>> ERROR: Unable to generate spec: read file info
>>> /home/mpflueger/riak/rel/../deps/ebloom/.hg/inotify.sock failed
>>>
>>> Has anybody else run into this?  Could this be related to my mercurial
>>> install (I'm using 1.51 downloaded and installed normally using
>>> python2.5).
>>>
>>> --Matthew
>>>
>>> ___
>>> riak-users mailing list
>>> riak-users@lists.basho.com
>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>
>>
>

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Building rel on Debian 2.6.26

[Matthew Pflueger]

http://hg.basho.com/riak/get/riak-0.10.tar.gz

Yeah, I disabled it there also...

--Matthew



On Fri, Apr 23, 2010 at 12:46, Ryan Tilder  wrote:
> Where did you download an 0.10 tarball from?  We haven't actually published
> one yet.  Is it one of the release candidates?
> Also, I am assuming that you are attempting to build on a Linux
> distribution.  Do you have an /etc/mercurial or /usr/local/etc/mercurial
> directory where inotify might be getting enabled?
>
> --Ryan
>
> On Fri, Apr 23, 2010 at 9:19 AM, Matthew Pflueger
>  wrote:
>>
>> Cloning the riak repo and building worked fine.  However, not being
>> able to build from the tarball is a little disconcerting...
>> --Matthew
>>
>>
>>
>> On Fri, Apr 23, 2010 at 12:13, Matthew Pflueger
>>  wrote:
>> > Thanks for the tip.  Unfortunately, disabling doesn't seem to work...
>> > I disabled it in my ~/.hgrc and in ebloom's .hg/hgrc to no avail.  I
>> > downloaded riak-0.10.tar.gz and installed so no .hg directory.  Any
>> > other suggestions?
>> >
>> > --Matthew
>> >
>> >
>> >
>> > On Fri, Apr 23, 2010 at 11:56, Ryan Tilder  wrote:
>> >> Sounds like you have Mercurial's inotify extension enabled.  hg
>> >> showconfig
>> >> should show it.  Workaround for now would be to following the
>> >> directions in
>> >> the below link for disabling the extension in the riak repo.  In
>> >> riak/.hg/hgrc:
>> >> [extensions]
>> >> inotify = !
>> >> http://mercurial.selenic.com/wiki/UsingExtensions#Enabling_an_extension
>> >>
>> >> --Ryan
>> >>
>> >> On Fri, Apr 23, 2010 at 8:48 AM, Matthew Pflueger
>> >>  wrote:
>> >>>
>> >>> I downloaded built Erlang successfully (minus jinterface, odbc, and
>> >>> wx) then downloaded riak-0.10.  I did a make all and everything built
>> >>> fine but then doing a make rel I get the following:
>> >>>
>> >>> ==> rel (generate)
>> >>> ERROR: Unable to generate spec: read file info
>> >>> /home/mpflueger/riak/rel/../deps/ebloom/.hg/inotify.sock failed
>> >>>
>> >>> Has anybody else run into this?  Could this be related to my mercurial
>> >>> install (I'm using 1.51 downloaded and installed normally using
>> >>> python2.5).
>> >>>
>> >>> --Matthew
>> >>>
>> >>> ___
>> >>> riak-users mailing list
>> >>> riak-users@lists.basho.com
>> >>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>> >>
>> >>
>> >
>
>

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

[ANN] Riak Release 0.10

[Bryan Fink]

Hello, Riak users.  We are excited to announce the release of Riak
version 0.10.  There's a great writeup about the new features on the
Basho Blog:
http://blog.basho.com/2010/04/23/riak-0.10-is-full-of-great-stuff/

Pre-built installations and source tarballs are available at:
http://downloads.basho.com/

Release notes are at (also copied below):
http://downloads.basho.com/riak/riak-0.10/riak-0.10.txt

IMPORTANT: If you are upgrading an existing Riak cluster, please read
the transition document at
http://bitbucket.org/basho/riak/src/45f284c5e5c0/TRANSITION

Cheers,
The Basho Riak Team


---
Riak 0.10 Release Notes
---

IMPORTANT: If you are upgrading an earlier version of Riak, please read
   the TRANSITION file in the directory above this
   (http://bitbucket.org/basho/riak/src/55a7f83c2ae2/TRANSITION)

Riak 0.10 brings many new features and improvements.

In addition to the existing HTTP interface, Riak 0.10 exposes a
protocol buffers interface.  This interface allows for basic put/get
operations, and has client libraries in Python and Erlang.  Support
for map/reduce operations, and additional language libraries will be
added soon.  Read more about the interface on the wiki:
https://wiki.basho.com/display/RIAK/PBC+API

Riak 0.10 exposes the ability to tie into an object's update
lifecycle, via pre-commit and post-commit hooks.  Hook functions can
be implemented in Erlang or Javascript.  More detail on the wiki:
https://wiki.basho.com/display/RIAK/Pre-+and+Post-Commit+Hooks

Listing the keys stored in a bucket is faster an more reliable in 0.10.

The "eventer" subsystem has been removed from Riak.  It was found to
be a bottleneck, as well as the main source of non-modularity in the
code.  This should not affect client code, unless it was explicitly
calling 'riak_eventer:add_handler' function.

Chunks of Riak have been rearranged for cleanliness and modularity.
If you are upgrading an existing cluster to 0.10, please carefully
read and follow the instructions in the TRANSITION file, referenced at
the top of these release notes.  Some filenames and app.config
settings have changed, which you will want to account for in your
installation.

Erlang applications that Riak depends on (webmachine, erlang_js, etc.)
have been moved out of the Riak repository, and into their own
repositories.  If you install a prebuilt Riak, this change will not
affect you.  If you build Riak from the source tarball, this change
will not affect you.  If you build Riak by cloning from the Bitbucket
repository, your first "make" will download the additional source
needed from Bitbucket.

Client libraries have been moved into their own repositories.  Instead
of finding them under the client_lib subdirectory, please visit the
appropriate repo:
 - http://bitbucket.org/basho/riak-javascript-client
 - http://bitbucket.org/basho/riak-python-client
 - http://bitbucket.org/basho/riak-ruby-client
   (same as) http://github.com/seancribbs/ripple/
 - http://bitbucket.org/basho/riak-java-client
 - http://bitbucket.org/basho/riak-php-client
 - http://bitbucket.org/basho/riak-erlang-client
   (using protocol buffers instead of distributed Erlang)

Riak 0.10 also includes a number of minor improvements and bug fixes:
 - multipart/mixed responses from the HTTP interface now use proper
   line termination (\r\n, instead of just \n)
 - fixed the "fold" functionality (used during handoff) for the
   multi-backend.
 - improvements to gossip corner cases
 - improvements to shell scripts for cross-platform compatibility
 - improvements for running map/reduce jobs on a degraded cluster

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: [ANN] Riak Release 0.10

[Doug Tangren]

yipee!
-Doug Tangren
http://lessis.me


On Fri, Apr 23, 2010 at 1:49 PM, Bryan Fink  wrote:

> Hello, Riak users.  We are excited to announce the release of Riak
> version 0.10.  There's a great writeup about the new features on the
> Basho Blog:
> http://blog.basho.com/2010/04/23/riak-0.10-is-full-of-great-stuff/
>
> Pre-built installations and source tarballs are available at:
> http://downloads.basho.com/
>
> Release notes are at (also copied below):
> http://downloads.basho.com/riak/riak-0.10/riak-0.10.txt
>
> IMPORTANT: If you are upgrading an existing Riak cluster, please read
> the transition document at
> http://bitbucket.org/basho/riak/src/45f284c5e5c0/TRANSITION
>
> Cheers,
> The Basho Riak Team
>
>
> ---
> Riak 0.10 Release Notes
> ---
>
> IMPORTANT: If you are upgrading an earlier version of Riak, please read
>   the TRANSITION file in the directory above this
>   (http://bitbucket.org/basho/riak/src/55a7f83c2ae2/TRANSITION)
>
> Riak 0.10 brings many new features and improvements.
>
> In addition to the existing HTTP interface, Riak 0.10 exposes a
> protocol buffers interface.  This interface allows for basic put/get
> operations, and has client libraries in Python and Erlang.  Support
> for map/reduce operations, and additional language libraries will be
> added soon.  Read more about the interface on the wiki:
> https://wiki.basho.com/display/RIAK/PBC+API
>
> Riak 0.10 exposes the ability to tie into an object's update
> lifecycle, via pre-commit and post-commit hooks.  Hook functions can
> be implemented in Erlang or Javascript.  More detail on the wiki:
> https://wiki.basho.com/display/RIAK/Pre-+and+Post-Commit+Hooks
>
> Listing the keys stored in a bucket is faster an more reliable in 0.10.
>
> The "eventer" subsystem has been removed from Riak.  It was found to
> be a bottleneck, as well as the main source of non-modularity in the
> code.  This should not affect client code, unless it was explicitly
> calling 'riak_eventer:add_handler' function.
>
> Chunks of Riak have been rearranged for cleanliness and modularity.
> If you are upgrading an existing cluster to 0.10, please carefully
> read and follow the instructions in the TRANSITION file, referenced at
> the top of these release notes.  Some filenames and app.config
> settings have changed, which you will want to account for in your
> installation.
>
> Erlang applications that Riak depends on (webmachine, erlang_js, etc.)
> have been moved out of the Riak repository, and into their own
> repositories.  If you install a prebuilt Riak, this change will not
> affect you.  If you build Riak from the source tarball, this change
> will not affect you.  If you build Riak by cloning from the Bitbucket
> repository, your first "make" will download the additional source
> needed from Bitbucket.
>
> Client libraries have been moved into their own repositories.  Instead
> of finding them under the client_lib subdirectory, please visit the
> appropriate repo:
>  - http://bitbucket.org/basho/riak-javascript-client
>  - http://bitbucket.org/basho/riak-python-client
>  - http://bitbucket.org/basho/riak-ruby-client
>   (same as) http://github.com/seancribbs/ripple/
>  - http://bitbucket.org/basho/riak-java-client
>  - http://bitbucket.org/basho/riak-php-client
>  - http://bitbucket.org/basho/riak-erlang-client
>   (using protocol buffers instead of distributed Erlang)
>
> Riak 0.10 also includes a number of minor improvements and bug fixes:
>  - multipart/mixed responses from the HTTP interface now use proper
>   line termination (\r\n, instead of just \n)
>  - fixed the "fold" functionality (used during handoff) for the
>   multi-backend.
>  - improvements to gossip corner cases
>  - improvements to shell scripts for cross-platform compatibility
>  - improvements for running map/reduce jobs on a degraded cluster
>
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Re: Building rel on Debian 2.6.26

[Ryan Tilder]

I can't manage to duplicate the problem you're having with the inotify.sock.
 Will the tarball build after a "make distclean rel" ?

--Ryan

On Fri, Apr 23, 2010 at 10:40 AM, Matthew Pflueger <
matthew.pflue...@gmail.com> wrote:

> http://hg.basho.com/riak/get/riak-0.10.tar.gz
>
> Yeah, I disabled it there also...
>
> --Matthew
>
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Riak ubuntu initscript

[Matthew Heitzenroder]

I should have mentioned this, but I also put together an initscript for ubuntu, 
based on Vladimir Osintsev's debian script.

http://gist.github.com/raw/374888/08b52132863b772da565c3630265c8298c2b74e6/Ubuntu%20initscript%20riak

Ciao,
Matt



___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com