Support the "operation" key when doing standardized server selection logging

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Logging, Server Selection
    • 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

      From the implementation standpoint, we need to pass operation name (see LogMessage.OPERATION and operation) to Cluster.selectServer/selectServerAsync via OperationContext. It seems that if each ReadOperation/WriteOperation/AsyncReadOperation/AsyncWriteOperation exposes the name of the operation, we can then take it and put in the OperationContext. Or, maybe each operation may expose its OperationContext, in which case, we will need to create an OperationContext when/before we are creating the corresponding operation.

      If we do this, we need to update LogMatcher.assertLogMessageEquality such that it start comparing operation again.

            Assignee:
            Ross Lawley
            Reporter:
            Valentin Kavalenka
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: