Uploaded image for project: 'Python Driver'
  1. Python Driver
  2. PYTHON-4655

Decide whether to make Async Methods that Use Aggregate Sync Instead

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Python Drivers
    • 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?

      Show
      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?

      Context

      The following Collection methods are synchronous in Motor and return a "Latent cursor". We should decide whether to do the same in PyMongo Async to better align the APIs, or else call these out in the migration guide. The reason to make them async is that an aggregate command with an $out stage performs I/O.

      • aggregate
      • aggregate_raw_batches
      • watch
      • list_indexes
      • list_search_indexes

      Definition of done

      Decide on a path and either implement or add to migration guide.

      Pitfalls

      We want to balance migration effort and a correct API.

            Assignee:
            Unassigned Unassigned
            Reporter:
            steve.silvester@mongodb.com Steve Silvester
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: