[JAVA-738] GridFS should support WriteConcern option on writes Created: 21/Jan/13 Updated: 03/Sep/15 Resolved: 02/Sep/15 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | GridFS |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 2 |
| Labels: | gridfs, writeconcern | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
Namely for GridFSFile.save(). Arguably, might be useful for GridFS ctor as well (along with a ReadPref). For now one can get the collections and set the WriteConcern/ReadPreference as a default before they use GridFS. The collections will be called <bucket> + ".files"/".chunks" (where the default bucket name is "fs") and one should set the options on both. |
| Comments |
| Comment by Ross Lawley [ 02/Sep/15 ] |
|
Fixed in the new GridFS implementation |
| Comment by Jeffrey Yemin [ 26/Aug/13 ] |
|
None yet. Does the suggested workaround not work for your use case? |
| Comment by Hans-Joachim Kliemeck [ 26/Aug/13 ] |
|
any progress on this? |
| Comment by Jeffrey Yemin [ 21/Jan/13 ] |
|
You can also set both read preference and write concern on the DB that is passed to the GridFS constructor but that will affect more than just the GridFS operations. |