Big Changes in Riak Tip

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Big Changes in Riak Tip

bryan-basho
Administrator
Hello, Riak users.  We wanted to give you all a heads up that we have
just pulled a large changelog into the tip of the Riak repository.  We
have been working on this list of changes privately, in order to cause
less confusion, as it covers a fairly major change, that was
experimental at first.

The big change is that we have split the 'riak' Erlang application
into two cooperating applications: 'riak_core' and 'riak_kv'.  This
has both forced us to untangle some code, making interfaces cleaner,
as well as provided us with the ability to implement new functionality
on top of the clustering tools that Riak provides, without hacking
around the needs of the key/value store.

If you are interested in testing before the 0.10 release, please read
through the TRANSITION document included with the source.  The most
important notes in there are the ones about changing your
configuration and ring file names.

If you're looking for the last updates just before this large change,
please pull the revision tagged "pre-0.10".

More details to come in the 0.10 release notes!

-The Basho Riak Team

_______________________________________________
riak-users mailing list
[hidden email]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Reply | Threaded
Open this post in threaded view
|

Re: Big Changes in Riak Tip

Ali Sabil-2
On Tue, Apr 13, 2010 at 8:58 PM, Bryan Fink <[hidden email]> wrote:

> Hello, Riak users.  We wanted to give you all a heads up that we have
> just pulled a large changelog into the tip of the Riak repository.  We
> have been working on this list of changes privately, in order to cause
> less confusion, as it covers a fairly major change, that was
> experimental at first.
>
> The big change is that we have split the 'riak' Erlang application
> into two cooperating applications: 'riak_core' and 'riak_kv'.  This
> has both forced us to untangle some code, making interfaces cleaner,
> as well as provided us with the ability to implement new functionality
> on top of the clustering tools that Riak provides, without hacking
> around the needs of the key/value store.
>
> If you are interested in testing before the 0.10 release, please read
> through the TRANSITION document included with the source.  The most
> important notes in there are the ones about changing your
> configuration and ring file names.
>
> If you're looking for the last updates just before this large change,
> please pull the revision tagged "pre-0.10".
>
> More details to come in the 0.10 release notes!
>
> -The Basho Riak Team
>

Are there any plans to split this further and have riak_core, riak_kv
and riak_http ?

Ali

_______________________________________________
riak-users mailing list
[hidden email]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Reply | Threaded
Open this post in threaded view
|

Re: Big Changes in Riak Tip

bryan-basho
Administrator
On Tue, Apr 13, 2010 at 4:37 PM, Ali Sabil <[hidden email]> wrote:
>
> Are there any plans to split this further and have riak_core, riak_kv
> and riak_http ?
>
> Ali
>

Hi, Ali.  I have a couple of answers, depending on the intent of your question.

The first answer, is that the code actually handling HTTP connections
has already been broken out: that's what Riak uses webmachine and
mochiweb for.

The second answer is that we don't intend to break out any more of the
HTTP interface code.  The things that the riak_kv_wm_* resources do
are so closely related to how riak_kv functions, that we don't think
it really makes sense to separate them.

-Bryan

_______________________________________________
riak-users mailing list
[hidden email]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Reply | Threaded
Open this post in threaded view
|

Re: Big Changes in Riak Tip

Jonathan Lee-2
In reply to this post by bryan-basho
Hello,

I'm having trouble building with the latest tip on OS X 10.6.  Does 0.10 require Erlang R13B04?

$ make
./rebar get-deps
...
==> riak_kv (get-deps)
Pulling ebloom from {hg,"http://bitbucket.org/basho/ebloom","RELEASE_2"}
destination directory: ebloom
...
==> ebloom (compile)
Compiling c_src/ebloom_nifs.cpp
c_src/ebloom_nifs.cpp:24: error: expected initializer before ‘*’ token


Thanks,
Jonathan

On Tue, Apr 13, 2010 at 2:58 PM, Bryan Fink <[hidden email]> wrote:
Hello, Riak users.  We wanted to give you all a heads up that we have
just pulled a large changelog into the tip of the Riak repository.  We
have been working on this list of changes privately, in order to cause
less confusion, as it covers a fairly major change, that was
experimental at first.

The big change is that we have split the 'riak' Erlang application
into two cooperating applications: 'riak_core' and 'riak_kv'.  This
has both forced us to untangle some code, making interfaces cleaner,
as well as provided us with the ability to implement new functionality
on top of the clustering tools that Riak provides, without hacking
around the needs of the key/value store.

If you are interested in testing before the 0.10 release, please read
through the TRANSITION document included with the source.  The most
important notes in there are the ones about changing your
configuration and ring file names.

If you're looking for the last updates just before this large change,
please pull the revision tagged "pre-0.10".

More details to come in the 0.10 release notes!

-The Basho Riak Team

_______________________________________________
riak-users mailing list
[hidden email]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


_______________________________________________
riak-users mailing list
[hidden email]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
Reply | Threaded
Open this post in threaded view
|

Re: Big Changes in Riak Tip

Justin Sheehy
On Wed, Apr 14, 2010 at 1:47 PM, Jonathan Lee <[hidden email]> wrote:

> I'm having trouble building with the latest tip on OS X 10.6.  Does 0.10
> require Erlang R13B04?

Yes, it does.  That (and the reason for it) will be in the 0.10 release notes.

Our apologies for not making that clearer earlier.

-Justin

_______________________________________________
riak-users mailing list
[hidden email]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com