[JAVA-3395] Fix MongoCollection API mismatch between sync and async Created: 21/Aug/19 Updated: 28/Oct/23 Resolved: 20/Sep/19 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | API |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | John Stewart (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Minor Change |
| Description |
|
There are a couple of MongoCollection methods that have different signatures between sync and async. In the sync API the helper methods for aggregate and mapReduce that don't take a resultClass return elements of type <TDocument>. In the async API (reactive and callback), they return elements of type Document. Consider making a breaking change in 4.0 to resolve the discrepancy. |
| Comments |
| Comment by Githook User [ 15/Jan/20 ] |
|
Author: {'name': 'John Stewart', 'username': 'jstewart-mongo', 'email': 'john.stewart@mongodb.com'}Message: Fix MongoCollection API mismatch between sync and reactive streams
|