Remove FindCommandRequest from CanonicalQuery

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      CanonicalQuery is (roughly) our current logical plan for find() queries. It should be possible to create one without going through FindCommandRequest. (It seems like a layering violation: commands are messages that clients and servers use to communicate; CanonicalQuery is a lower-level, more internal, more normalized representation for a query.)

      It looks like CanonicalQuery only depends on FindCommandRequest out of convenience: many options happen to be shared between them, so CanonicalQuery exposes one large getter instead of smaller separate getters. While convenient, this makes it harder to see which information a CanonicalQuery contains or does not contain.

              Assignee:
              Unassigned
              Reporter:
              David Percy (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: