[JAVA-1906] Allow to specify a default maxTime Created: 28/Jul/15 Updated: 17/Dec/19 Resolved: 25/Jan/18 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | API |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jochen Kemnade | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Case: | (copied to CRM) |
| Description |
|
It should be possible to define a default maxTime for queries. That could be collection level, db level or even client level. |
| Comments |
| Comment by Ross Lawley [ 27/Aug/15 ] |
|
Hi jkemnade, Apologies for the delay in responding. Currently, the 3.0 API follows the new CRUD specification with regards to maxTime which makes it optional on a per operation basis as this is the anticipated normal use case. The alternative would be to make it immutable similar to how ReadPreference is in the MongoCollection. This while certainly feasible, it would be a breaking change to the current API's. It would also require a change the CRUD specification so that all drivers behave in a similar way going forward. Ross |