[MONGOCRYPT-35] libmongocrypt: schema cache Created: 07/Feb/19 Updated: 04/Sep/19 Resolved: 10/May/19 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | Kevin Albertson |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | Build libmongocrypt library | ||||||||
| Description |
|
Implement a cache for schemas within libmongocrypt. Stored schemas should be invalidated after one minute and removed from the cache. |
| Comments |
| Comment by Kevin Albertson [ 10/May/19 ] |
|
I'm closing this since the work for the JSONSchema (really collection info) cache and key cache are so similar they're being done together as part of |
| Comment by Kevin Albertson [ 09/Apr/19 ] |
|
Oh wait, maybe we still can cache. Collection info includes a UUID. That should be unique across clusters! |
| Comment by Kevin Albertson [ 09/Apr/19 ] |
|
Note, given the current API proposal we may need to close this as "Gone Away". |