Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-23224

Remove obsolete ShardRegistry::QueryResponse::opTime field from ShardRegistry::QueryResponse

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding 16 (06/24/16)

    Description

      It's the return value of ShardRegistry::_exhaustiveFindOnConfig, which is called down the chain by CatalogManagerReplicaSet::_exhaustiveFindOnConfig, which extracts the ShardRegistry::QueryResponse::opTime and returns it as StatusWith<OpTimePair<vector<BSONObj>>>.

      CatalogManagerReplicaSet::_exhaustiveFindOnConfig has a lot of callers, some of which have invariants on the returned opTime.

      Attachments

        Activity

          People

            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: