Use Case

As a... node user
I want... server selection to only be executed as many times as needed
So that...  server selection timeoutMS is respected correctly.

User Impact

• Execute operation and server selection will not be performed multiple time
  • users will be able to witness this through shorter execution times and server selection logging events 

Certain AbstractOperation subclasses are just wrappers to other commands and are not their own operations. They should not be subclasses of AbstractOperation, but rather be implemented in helper functions to Db and Collection classes. 

An example of a wrapper class is IsCappedOperation, which only performs a listCollectionsOperation under the hood. This results in a duplicate executeOperation call. The class's functionality can just be moved collection.isCapped() function, and have the function execute listCollections.

https://github.com/mongodb/node-mongodb-native/pull/4034 removed the redundant index management operations.

AC

• remove wrapper classes:
  • EnsureIndexOperation,
  • IndexInformationOperation,
  • CollectionsOperation,
  • IsCappedOperation,
  • OptionsOperation
  • IndexOperation
• move their functionality to the corresponding functions that call them:
  • db.ensureIndex()
  • db.indexInformation()
  • db.collections()
  • collections.isCapped()
  • collection.options()
  • collections.indexOperation()
• Audit this functionality to determine if any of them can be deprecated for the next major release