Ah ok .. I had an older Riak installed. Then didn't purge the config before
installing the new Riak deb. Do'h
On Thu, Feb 6, 2014 at 11:11 AM, Eric Redmond wrote:
> Ahhh there's your problem. You don't have the new search activated. You
> have old search. Are you configuring with riak.conf, or
On Tue, Feb 4, 2014 at 4:38 PM, Jeremy Pierre wrote:
> Hi Eric,
>
> Thanks very much - getting a 405 response for that curl command though.
> POST to same endpoint yields the following:
>
>
The schema resources does not accept POST requests. Only PUT and GET.
-Z
Hi Srdjan,
On Mon, Feb 3, 2014 at 12:06 PM, Srdjan Pejic wrote:
>
>
> [{"viewer_id_s"=>"004615eb-5c0e-4c4a-890c-c6fc29e3fc56",
>> "video_time_i"=>475, "type_s"=>"joined"},
>> {"viewer_id_s"=>"635dcd2d-fdeb-46c1-9920-803ccdd6176b",
>> "video_time_i"=>522, "type_s"=>"joined"},
>> {"viewer_id_s"=>"
Hey Ryan,
Yeah, I figured that out once I got the indexing to work properly. It was a
case of code outpacing the docs, because I was setting the prop yz_index
rather than search_index.
Thanks for the help. I do have a possible issue who yokozuna and map
reduce, but that's a separate thread.
On Fe
I'm wondering if someone tried or is working on a Riak wrapper that is
a drop-in replacement for AWS DynamoDB? It seems that it could work
with the combination of the next-gen search. Any thoughts?
Istvan
___
riak-users mailing list
riak-users@lists.bas
Our test environment Riak cluster is looking pretty unhealthy at the
moment, with quite a lot of crashes being reported. Is anyone able to
advise what the cause is?
>From error.log:
[error] <0.13413.31> CRASH REPORT Process <0.13413.31> with 0
neighbours exited with reason: no match of right hand
Hi Toby, this is a recently identified regression in 1.4.7.
Go into your bitcask data directories, and you'll likely see a number
of 0 byte data files and 18 byte hintfiles with the same file ID
number. Stop the node, move those aside and you should be back in
business. find can be used to auto
Hi Evan,
Thanks for the fast response on this.
I'll look out for the forthcoming new release.
Toby
On 7 February 2014 12:05, Evan Vigil-McClanahan wrote:
> Hi Toby, this is a recently identified regression in 1.4.7.
>
> Go into your bitcask data directories, and you'll likely see a number
> of 0
