[SERVER-2876] system.js + Sharding Created: 31/Mar/11 Updated: 31/Mar/11 Resolved: 31/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript, MapReduce, Sharding |
| Affects Version/s: | 1.8.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Gaetan Voyer-Perrault | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
When depending on JS stored on the server side the functionality fails if a collection is a sharded. Server-side JS: Looking at the Sharding Limits, this is not clearly stated: There's a mention that db.eval() fails, but no clarification that this includes server-side JS. Additionally, the docs state that $where works, but if the $where is dependent on the server-side JS, then it too will fail. In theory, this can be worked around by adding the same function to each shard individually, but this is bad practice. ====== 1. Disallow server-side JS in sharded scenarios ====== In case #1, we get an instance where mongoS behaves differently than mongoD |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 31/Mar/11 ] |