Rob,
I reproduced this at the command line. Here I'm storing two documents, with
> IDs 'doc8' and 'doc9', into a search-enabled bucket named 'test-search'.
>
> # This command works, even though 'lsh' is empty. I believe this is
> because I've never put a field named 'lsh' in this bucket, 'test-sea
So, actually, it turns out that's not exactly the command I typed. I
actually typed:
curl -v -XPUT -H "Content-Type: application/json" -d '{"terms": "",
segments: "d do doc docs"}' '
http://riak.lumi:8098/riak/test-search/doc9?returnbody=true'
That is, I left out a pair of quotation marks, so my
Oh right, and here's the error I get over HTTP when I run the second
command:
> PUT /riak/test-search/doc9?returnbody=true HTTP/1.1
> User-Agent: curl/7.27.0
> Host: riak.lumi:8098
> Accept: */*
> Content-Type: application/json
> Content-Length: 39
>
< HTTP/1.1 500 Internal Server Error
< Vary: Ac
I reproduced this at the command line. Here I'm storing two documents, with
IDs 'doc8' and 'doc9', into a search-enabled bucket named 'test-search'.
# This command works, even though 'lsh' is empty. I believe this is because
I've never put a field named 'lsh' in this bucket, 'test-search'.
curl -v
Rob,
I don't know what the exact data is. The thing is that it doesn't seem to
> cause an error on the client side; it just shows up in the server logs to
> be noticed later.
>
A non-2XX response will be returned. Verify that the response is 200. If
it isn't log an error in your app with the ex
I don't know what the exact data is. The thing is that it doesn't seem to
cause an error on the client side; it just shows up in the server logs to
be noticed later.
I'm confused why the search object would be getting a list. My
understanding from the documentation is that the only thing Riak Sear
Rob,
That cryptic error is saying that it expected a binary value type for the
field 'ish' ("binary" is a data structure in Erlang) but instead got an
empty list. Do you by any chance have the exact data which is causing the
issue? If you can isolate the data causing the problems then attach to