Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Minor - P4
Fix Version/s: 2.13.0.rc1
Affects Version/s: None
Component/s: None
Labels:
- intern-project-candidate

Epic Link:
Driver Query Cache
Confidence Status:
None

Backwards Compatibility:
Fully Compatible

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

Currently the query cache, as implemented by Mongoid, duplicates a portion of driver's cursor code plus adds the query caching on top. This has two issues:

1. The code that was copied is by now outdated. It uses legacy read retries, performs server selection in an outdated way, etc.
2. Changes to the driver can break the query cache, due to the query cache's reliance on driver internals.

Since the query cache operates on collection/operation/cursor level, it can be implemented in the driver, with Mongoid only exposing the implementation using a (more) convenient API.

depends on

RUBY-2302 Write scope for moving Query Cache to Driver

Closed

RUBY-2308 Query Cache Project Design Document

Closed

duplicates

RUBY-2131 Implement query cache in driver

Closed

is depended on by

RUBY-2131 Implement query cache in driver

Closed

RUBY-2211 Use namespace returned from find command in getMore

Closed

is related to

MONGOID-4785 Mongoid forces legacy read retries regardless of driver configuration

Closed

RUBY-1851 Restore cursor's ability to be iterated more than once

Closed

links to

mongo-ruby-driver #1603: RUBY-1849 compl

mongo-ruby-driver #1606: RUBY-1849 refactor cursor logic for clarity

(2 is related to, 2 links to)

Assignee:: Grace Chong (Inactive)
Reporter:: Oleg Pudeyev (Inactive)
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Jun 21 2019 07:21:37 PM UTC
Updated:: Oct 28 2023 11:13:02 AM UTC
Resolved:: Jul 27 2020 09:25:10 PM UTC
Confidence Status Last Update:: 13/Jul/20 7:18 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates