Consolidate command execution logic

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      We have accumulated several ways of running commands in the codebase. PYTHON-1357 identifies one area where we could reduce duplication, and probably should be done before this one. This keeps coming up when we have to change any logic around command execution, such as the client backpressure work.
      We should have a single code path for command execution, and use it for all operations.
      This will require some refactoring and making the centralized command runner more flexible.

      Definition of done

      All database operations are done from a central location.

      Pitfalls

      Ensure that we do not sacrifice performance or introduce any other regressions.

            Assignee:
            Unassigned
            Reporter:
            Steve Silvester
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: