Don't encode object dot for JS map-reduce

[rzezeski]

There is no need to encode the dot for JavaScript map-reduce. It is an
internal thing and doesn't need to be exposed.

This fixes #779.

I see 6 eunit failures both on this branch and develop.

[russelldb]

WFM +1. Nice catch. Thanks.

[russelldb]

Actually, second thoughts, I think I might have to be smarter and binary encode the dot. What about downgrades? If data is written with a dot, then the node downgraded, this fix won't be there, but the dot still will be.

[rzezeski]

Yea, I didn't think of downgrade case. We should revisit this after holidays. Merging for now so tests will work in 2.0.

[jonmeredith]

@rzezeski can you open an issue to track?

On Tue, Dec 24, 2013 at 8:17 AM, Ryan Zezeski notifications@github.comwrote:

Yea, I didn't think of downgrade case. We should revisit this after
holidays. Merging for now so tests will work in 2.0.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/782#issuecomment-31174740
.

Jon Meredith
VP, Engineering
Basho Technologies, Inc.
jmeredith@basho.com

[seancribbs]

@jonmeredith We've put a known issue in release notes for the downgrade problem.

[jonmeredith]

Ok, great. It's good to have in both places - issues get reviewed more
often than release notes.

On Tue, Dec 24, 2013 at 8:41 AM, Sean Cribbs notifications@github.comwrote:

@jonmeredith https://github.com/jonmeredith We've put a known issue in
release notes for the downgrade problem.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/782#issuecomment-31175550
.

Jon Meredith
VP, Engineering
Basho Technologies, Inc.
jmeredith@basho.com

[jrwest]

its also been added to the kill bill for true N = 3 safety!