Invalid index in source DB causes unrecovered panic (mongodb)

[johnnason]

Directions

mongoexport a small mongo db, edit the meta data to have an index with a boolean true value, mongoimport into a back-level DB (verified in 2.6.10).

Use transporter to copy the DB inot another.

Bug report

I've seen this with some old mongo databases where an index is present that has a val that is not a int nor a string. For instance, a boolean value for sort order.

While this is clearly incorrect, a Panic is not the correct response.

The Panic actually originates in all version of the mgo driver.

Relevant pipeline.js:

System info:

• Transporter version: 5.2
• OS: OSX
• DB version(s): Mongo 2.6.10

Reproducible Steps:

See Directions.

What did you expect to happened?

Import successfully.

What actually happened?

Panic.

Proposal:

It seems like we don't need to iterate indexes in the code that causes the panic.