Failed JS MR includes Erlang terms

[basho]

Failed JS MR includes Erlang terms

[russelldb]

I'm pretty sure this is deliberate as of Bryan's work to have more meaningful errors come out of MapReduce.

[rzezeski]

So I'm hearing that this change was intentional. I.e. returning the input field as a string of an Erlang term. That seems to make sense to me. I just have 2 concerns:

1. I'm not sure it makes sense to return the error field as a string of Erlang terms. Client writers have to parse a very awkward string to get at the various fields such as lineno, message and source.
2. This beaks any clients that are using JS and relied on the lineno, message, and source fields being top-leve in the object.

I just want to make sure we are aware of these two points.

@seancribbs Given you are the guy in charge of the client team I think it's best if you make the call here. What do you say?

[seancribbs]

@rzezeski I don't know any part of the clients that explicitly expects specific fields in a MapReduce error response. I think the error message should be plain text as much as possible, but the offending input could go either way.

[rzezeski]

I'm closing this since it is intended behavior.