Inserts still rely on clients to validate nested fields - the shell must maintain this validation even in the bulk api case. The server itself will not validate nested fields for correctness.

Ideally these errors would be reported as write errors to maintain api consistency, but this isn't totally critical since it is safe to fail when building a batch.

Recommended solution is to have per-DBCollection validate function for each write type, which can be overridden for tests.