[JAVA-608] Deprecate MongoURI collection stuff Created: 24/Jul/12 Updated: 12/Jul/13 Resolved: 12/Jul/13 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | API, Configuration |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
This is not in the spec. wrt using a collection name. We should also clarify in the javadocs that the DB is for authentication. We should check if the hadoop stuff uses the db/collection in any way; if so we should move that code into the hadoop plugin code since it doesn't make sense in the driver. |
| Comments |
| Comment by Jeffrey Yemin [ 12/Jul/13 ] | |||
|
MongoURI is deprecated now, so this is really a duplicate | |||
| Comment by Jeffrey Yemin [ 24/Jul/12 ] | |||
|
Yes, | |||
| Comment by Scott Hernandez (Inactive) [ 24/Jul/12 ] | |||
|
Okay, but the longer this stays in, the more confusing it is to users. We can deprecate immediately and cleanup the hadoop stuff at the same time. Seems like just inheriting in the hadoop code will give us a MongoHadoopURI or something specific to those use cases. Is there another issue for the authentication part? | |||
| Comment by Jeffrey Yemin [ 24/Jul/12 ] | |||
|
Let's not deprecate this until the mongo-hadoop issue is resolved. | |||
| Comment by Jeffrey Yemin [ 24/Jul/12 ] | |||
|
Also, it does not yet authenticate the database with the credentials. User has to do it manually:
| |||
| Comment by Jeffrey Yemin [ 24/Jul/12 ] | |||
|
The mongo-hadoop project does use several of the collection methods in MongoURI:
|