Restoring database with 2.X Mongo Driver version fails

[talbronfer]

I've tried dumping & restoring a database to/from a file using the 2.X Mongo Driver. The result is the following error:

error parsing element 0 of field documents :: caused by :: wrong type for '0' field, expected object, found 0: BinData(0, 5D000000075F696400559148BBC695410D36B301C1106C617465737452656C656173650001000000026E616D6500190000004D6F766552656C65617365436F6E666967757261...)

When forcefully downgrading to version 1.4.32 of the Mongo Driver, the restore process completes successfully. I found this link in Mongo's JIRA.

I don't know if this can be easily fixed, but perhaps you can change the package version for the Mongo driver so that it's explicitly 1.X, since now npm install automatically installs 2.X.

[boutell]

Grr...

Mongo 3.2 has utilities that will likely make this module obsolete, but
this transitional phase is a bear.

We could fall back on non-raw reads and writes but they are slow as
molasses.

On Wed, Aug 5, 2015 at 11:19 AM, talbronfer notifications@github.com
wrote:

I've tried dumping & restoring a database to/from a file using the 2.X
Mongo Driver. The result is the following error:

error parsing element 0 of field documents :: caused by :: wrong type for
'0' field, expected object, found 0: BinData(0,
5D000000075F696400559148BBC695410D36B301C1106C617465737452656C656173650001000000026E616D6500190000004D6F766552656C65617365436F6E666967757261...)

When forcefully downgrading to version 1.4.32 of the Mongo Driver, the
restore process completes successfully. I found this link
https://jira.mongodb.org/browse/NODE-443 in Mongo's JIRA.

I don't know if this can be easily fixed, but perhaps you can change the
package version for the Mongo driver so that it's explicitly 1.X, since now npm
install automatically installs 2.X.

—
Reply to this email directly or view it on GitHub
#8.

*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE | (215) 755-1330 | punkave.com

[aaani]

Ran into the same problem today with mongoDB 3.0. @boutell do you have any suggestions?

[boutell]

Not really, other than restoring to the same version of mongo you dumped
from and then migrating from there. We've stopped using these utilities
internally because of inconsistencies between the versions and the arrival
of similar standard utilities in 3.2.

On Tue, Aug 16, 2016 at 12:21 PM, Anirvana Mishra notifications@github.com
wrote:

Ran into the same problem today with mongoDB 3.0. @boutell
https://github.com/boutell do you have any suggestions?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#8 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fUDF8QL4N8w-jN-KBVX4waODaC9Fks5qgeN4gaJpZM4FmJxa
.

*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE | (215) 755-1330 | punkave.com

[boutell]

I've added a deprecation notice to the README.

On Tue, Aug 16, 2016 at 12:25 PM, Tom Boutell tom@punkave.com wrote:

Not really, other than restoring to the same version of mongo you dumped
from and then migrating from there. We've stopped using these utilities
internally because of inconsistencies between the versions and the arrival
of similar standard utilities in 3.2.

On Tue, Aug 16, 2016 at 12:21 PM, Anirvana Mishra <
notifications@github.com> wrote:

Ran into the same problem today with mongoDB 3.0. @boutell
https://github.com/boutell do you have any suggestions?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#8 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fUDF8QL4N8w-jN-KBVX4waODaC9Fks5qgeN4gaJpZM4FmJxa
.

*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE | (215) 755-1330 | punkave.com

*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE | (215) 755-1330 | punkave.com

[aaani]

Thank you!