[SERVER-36186] Ignore value of oplogReplay find command option Created: 18/Jul/18 Updated: 29/Oct/23 Resolved: 24/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Xin Hao Zhang (Inactive) |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||||||
| Sprint: | Query 2019-07-01, Query 2019-07-15, Query 2019-07-29 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Linked BF Score: | 50 | ||||||||||||||||||||||||||||
| Description |
|
The oplogReplay option to the find command (and oplogReplay bit in the legacy OP_QUERY find protocol) currently must be set by the client in order to enable an optimized code path for queries looking for a particular range of ts values in the oplog. See getOplogStartHack() in get_executor.cpp. Instead of requiring clients to explicitly enable this optimization, the query system should automatically optimize such queries, whether or not oplogReplay is set. This should allow us to mark the oplogReplay option as deprecated. The implementation can change to accept oplogReplay but entirely ignore its true/false value. |
| Comments |
| Comment by Githook User [ 26/Jul/19 ] |
|
Author: {'name': 'Xin Hao Zhang', 'email': 'xinhao.zhang@mongodb.com', 'username': 'xinhaoz'}Message: |
| Comment by Githook User [ 24/Jul/19 ] |
|
Author: {'name': 'Xin Hao Zhang', 'username': 'xinhaoz', 'email': 'xinhao.zhang@mongodb.com'}Message: |