odd error on mapreduce

Giancarlo Frison gfrison at chelab.com
Wed Aug 31 09:20:19 EDT 2011

Thanks Bryan,

I skirt the problem using base64.

Giancarlo Frison

On Fri, Aug 26, 2011 at 1:11 PM, Bryan Fink <bryan at basho.com> wrote:

> On Fri, Aug 26, 2011 at 6:32 AM, Giancarlo Frison <gfrison at chelab.com>
> wrote:
> > If i serialize the body as Json I catch errors any more instead of
> protobuf
> > object representation (application/octet-stream).
> > Would be an mapreduce bug?
> > Is it possibile to skirt any body parsing during the mapreduce? Just for
> > evaluating headers values?
> All objects passed through Javascript map or reduce phases must be
> valid UTF-8-encoded JSON.  There is no way to change that at this
> time.  Erlang map/reduce phases do not have such requirements.
> The fact that your earlier ProtocolBuffer-encoded object made it
> through a Javascript phase was probably a fluke, based on the encoding
> containing nothing that was completely invalid UTF-8.  It probably
> came through as a string, maybe with one or two odd characters
> prepended.
> Hope that helps,
> Bryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20110831/63b5d86f/attachment.html>

More information about the riak-users mailing list