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

XMLWordPrintableJSON

    • Not Needed
    • 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
              Nabil Hachicha
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: