[SERVER-49189] Make the ReadThroughCache lookup send the old entry state to the lookup function Created: 30/Jun/20 Updated: 29/Oct/23 Resolved: 23/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Catalog, Sharding |
| Affects Version/s: | Backlog |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Kevin Pulo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The ReadThroughCache lookup function can return a LookupResult with a value of boost::none to inicate the lookup didn't found any result. As written in this comment, in those cases the time field of the LookupResult need to reflect the time for which the lookup request was issued. The problem is that in the scope of the LookupFn we don't have such a value, we only knows the key for which the lookup have been issued but not the time at which it was issued. Moreover this will be required in order to use the ReadThroughCache to store collection routing information. In fact the future lookup function of such instantiation will need access to the old routing information previously cached in order to perform an incremental refresh. |
| Comments |
| Comment by Githook User [ 27/Jul/20 ] |
|
Author: {'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}Message: |
| Comment by Githook User [ 23/Jul/20 ] |
|
Author: {'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}Message: |