[SERVER-9655] mongodump doesn't work for a out collection of M/R Created: 13/May/13 Updated: 10/Dec/14 Resolved: 13/Aug/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.0.4, 2.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kihyun Kim | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
I'm making some collections by map/reduce that contains unique value for auto-complete. |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 13/Aug/13 ] |
|
Hi Kihyun, Given that the problem does not appear to be reproducible on 2.4.2 or the current production branch of MongoDB, I'm going to resolve this issue. MongoDB 2.0.4 was released in March 2012 and since then there have been numerous stability and feature improvements. The MongoDB 2.0.x series has reached end-of-life and is no longer being updated. We would encourage you to update to the latest production release of MongoDB 2.4.x, which is our recommended stable release. Thanks, |
| Comment by Kihyun Kim [ 05/Aug/13 ] |
|
I found that a problem is only appearing when mongoD v2.0.4 is running. MongoD v2.4.2 works well and not depend on mongodump. |
| Comment by Daniel Pasette (Inactive) [ 29/Jul/13 ] |
|
I'm unable to reproduce this behavior on 2.4.2 given the steps you've provided. Can you give any more details? |
| Comment by Kihyun Kim [ 26/Jul/13 ] |
|
It looks like collection name problem having dot notation. |