Problem adding compound indexes when run in separate Node contexts

[kevindente]

If the Schema's declared in JS that's running in a secondary context (via vm.runInNewContext), creating compound indexes via Schema.index({field: 1, ...}) fails. The ensureIndex fails when that part runs in a different context from the Schema definition.

The problem appears to be with DbCommand.createCreateIndexCommand(). In that function it compares the constructor of fieldOrSpec to Object to determine if it's an object literal. But because the fieldOrSpec was declared in a different context, the comparison fails (see joyent/node#1518 for more info).

[aheckmann]

can you provide something i can use to reproduce?

[aheckmann]

can you provide something i can use to reproduce?

[kevindente]

I'll work something up.

[kevindente]

I'll work something up.

[kevindente]

OK, here's a gist that repro's the problem:
https://gist.github.com/3836058

It looks like this is only a problem when the schema is constructed before the connection is open, causing the commands to get queued. In that case, the ensureIndex command gets executed in the original context, not the child context. OTOH, if the connection is open, then the indexes are created in the same context as the schema definition, and there's no problem.

[kevindente]

OK, here's a gist that repro's the problem:
https://gist.github.com/3836058

It looks like this is only a problem when the schema is constructed before the connection is open, causing the commands to get queued. In that case, the ensureIndex command gets executed in the original context, not the child context. OTOH, if the connection is open, then the indexes are created in the same context as the schema definition, and there's no problem.

[aheckmann]

ok just ran this, thanks for putting the test case together. this is a bug in the driver. I'll close this and open a ticket there instead and refer to this. https://github.com/mongodb/node-mongodb-native/issues/754

[aheckmann]

ok just ran this, thanks for putting the test case together. this is a bug in the driver. I'll close this and open a ticket there instead and refer to this. https://github.com/mongodb/node-mongodb-native/issues/754

[aheckmann]

i submitted the fix to the driver so whenever it gets merged and published I update.

[aheckmann]

i submitted the fix to the driver so whenever it gets merged and published I update.