UpdateLifecycleImpl can return empty collectionMetadata even if ns is sharded

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.6.8, 3.0.0-rc7
    • Affects Version/s: 2.8.0-rc5
    • Component/s: Sharding
    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Original description:
      sharding/array_shard_key.js fails with a mixed version cluster

      If you run the set with a config as follows:

      var config = {                                              
              mongos: 2,                                          
              shards: 2,                                          
              other: {                                            
                  rs: true,                                      
                  mongosOptions: { binVersion: "2.8"},       
                  configOptions: { binVersion: oldVersion},       
                  rsOptions: {binVersion: ["2.6"], nodes:3}
              }                                                                       
          };                                                      
      

      The test will fail on the line that reads:

      assert.writeError(coll.update( value, Object.merge( value, { i : [ 3 ] } ) ));
      

              Assignee:
              Randolph Tan
              Reporter:
              Matt Dannenberg (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: