Optimize client-side projections to perform as much as possible of the projection on the server

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: LINQ
    • None
    • None
    • Fully Compatible
    • Dotnet Drivers
    • Needed
    • Hide
      1. What would you like to communicate to the user about this feature?
        2. Would you like the user to see examples of the syntax and/or executable code and its output?
        3. Which versions of the driver/connector does this apply to?

      There should be existing documentation on client-side projections.

      Maybe it could be changed to include information that we now try to do as much of the work server-side as possible.

      Show
      What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to? There should be existing documentation on client-side projections. Maybe it could be changed to include information that we now try to do as much of the work server-side as possible.
    • None
    • None
    • None
    • None
    • None
    • None

      The initial implementation of client-side projections fetches the entire document from the server to pass it to the projection lambda.

      If we analyze the projection we can determine which parts of the document the projection actually needs and fetch only those parts.

            Assignee:
            Robert Stam
            Reporter:
            Robert Stam
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: