// Create and shard collection.
db.apple.insert({a: 1})
sh.shardCollection('test.apple', {_id: 1})

// Disable the balancer so we can get the chunks to stay where we want them
sh.disableBalancing('test.apple')

// Let's have two chunks, and I'm going to move both to non-primary shard 'shard-rs1'.
sh.splitAt('test.apple', {_id: 0})
sh.moveChunk('test.apple', {_id: 1}, 'shard-rs1')
sh.moveChunk('test.apple', {_id: -1}, 'shard-rs1')

// Turn on schema validation - we see that "collMod" only runs on non-primary 'shard-rs1', because it owns all the
// chunks.
db.runCommand({collMod: "apple", validator: {$jsonSchema: {properties: {a: {bsonType: "int"}}}}})

// This doesn't reflect the collMod. My guess is this is because mongos talks to the primary shard
// which never ran collMod.
db.getCollectionInfos()

// Schema validation complains, as it should (query runs on non-primary shard):
db.apple.insert({_id: 0, a: "hello"})

// Move a chunk back to primary shard.
sh.moveChunk('test.apple', {_id: 1}, 'shard-rs0')

// Validation complains, because it is routed to 'shard-rs1':
db.apple.insert({_id: -2, a: "hello"})
// Doesn't complain and insert works, because it is routed to 'shard-rs0':
db.apple.insert({_id: 2, a: "hello"})