On Tue, Apr 20, 2010 at 11:49 PM, Jon Meredith wrote:
> Hi Eric,
>
> For the HTTP interface to work correctly you need to supply a content type
> when you do your updated - if you add something like
>
> request.content.content_type = 'application/json'
>
> Then you should be in business. Th
Hi Eric,
For the HTTP interface to work correctly you need to supply a content
type when you do your updated - if you add something like
request.content.content_type = 'application/json'
Then you should be in business. The python client at
http://bitbucket.org/basho/riak-python-client i
If I add some data using the protobufs interface, can I retrieve that data
over HTTP? I'm getting an error when I try to GET the id but the return_body
looks proper.
=
import socket
from struct import *
import riakclient_pb2
s = socket.socket(socket.AF_
Hi Dan,
You're right - the documentation is woefully lacking. We'll try and
improve it soon, the protocol itself has an entry on the wiki, but each
of the clients need some too.
For now your best best is to look at the unit tests at the end of
riakc_pb_socket - that'll show you how you can
Is there any documentation for the new protobufs based Erlang client? The
README mentions a docs directory but I don't see a docs directory in the
riak-erlang-client repo.
Also, can the riak-erlang-client be built with Erlang R13B03?
Thanks,
Dan
___
ria
On Tue, Apr 20, 2010 at 6:28 PM, richard bucker wrote:
> I cloned riak from HG this evening and started to build. That's when I got
> the following errors. It seems to me that the URL of the dependencies are
> wrong.
>
> /r
>
>
> rbuc...@ubudev:riak$(default)$ make rel
> ./rebar compile generate
I cloned riak from HG this evening and started to build. That's when I got
the following errors. It seems to me that the URL of the dependencies are
wrong.
/r
rbuc...@ubudev:riak$(default)$ make rel
./rebar compile generate
==> luke (compile)
Compiled src/luke_flow_sup.erl
Compiled src/luke_fl
On Tue, Apr 20, 2010 at 3:01 PM, Kevin Smith wrote:
> Hipe shouldn't make a difference. The linker errors:
>
> ld: warning: in
> /usr/local/lib/erlang/lib/erl_interface-3.6.5/lib/liberl_interface.a, file
> is not of required architecture
> ld: warning: in /usr/local/lib/erlang/lib/erl_interface-3
Hi,
For the first part - we used protocol buffers because we had requests
for a PB interface from customers and as developers we have more
experience using it on other projects.
For the second part - I would recommend using the PB interface. It has
about the same performance as riak_client
BERT is used by GIthub as RPC for Ruby/Erlang integration and the purpose is
documented here github.com/blog/531-introducing-bert-and-bert-rpc and
bert-rpc.org/
It is mainly created to avoid some of the shortcomings in Protocol Buffer
and Thrift. BERT has good support for multipe languages like PB/
Hipe shouldn't make a difference. The linker errors:
ld: warning: in
/usr/local/lib/erlang/lib/erl_interface-3.6.5/lib/liberl_interface.a, file is
not of required architecture
ld: warning: in /usr/local/lib/erlang/lib/erl_interface-3.6.5/lib/libei.a, file
is not of required architecture
ld: war
On Tue, Apr 20, 2010 at 2:23 PM, Kevin Smith wrote:
> Do you have 64 or 32 bit Erlang installed? My guess is erlang_js is
> compiling the Spidermonkey VM for 64 bit but you have 32 bit Erlang
> installed.
>
I'm running a 64 bit version of Erlang. Could it have something to do with
hipe being ena
Do you have 64 or 32 bit Erlang installed? My guess is erlang_js is compiling
the Spidermonkey VM for 64 bit but you have 32 bit Erlang installed.
--Kevin
On Apr 20, 2010, at 2:14 PM, Eric Gaumer wrote:
> Build seems to have went fine but I get a core dump when I start riak.
>
> Slogan: Kernel
Build seems to have went fine but I get a core dump when I start riak.
Slogan: Kernel pid terminated (application_controller)
({application_start_failure,erlang_js,{{bad_return_value,{error,{load_error,[70,97,105,108,101,100,32,116,111,32,1
System version: Erlang R13B04 (erts-5.7.5) [source] [64-b
There still might be some benefit to segregating your data into multiple
buckets, but that will largely depend upon what your most common query is.
Also consider carefully your choice of key; choosing a suitable one will let
you bypass map/reduce on certain queries.
That said, Alexander is rig
Unfortunately, there is no offset, limit, sorted set or pagination
built in to riak. You kinda need to maintain your own index for any of
that and/or rely on m/r in a less than real-time sort of way. I would
take your day keys and make them smaller... Like hours or even
minutes. The number
16 matches
Mail list logo
