You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simple question if parse-server works well with the new storage engine WiredTiger which provides a newer storage engine that compresses your database data over the standard MMAPv1.
My guess would be parse-server wouldn't care what default storage engine your using ..
The text was updated successfully, but these errors were encountered:
I ran into issues with it, although in retrospect I'm not entirely sure since I attempted the migration really really early, where I hit schema bugs and what have you.
However they explicitly have a requirement on mongo 2.6 up to 3.0. If I had to guess, that's because >= 3.0 made wiredTiger the default, so that might be one of the reasons.
Hopefully we'll get a better answer ;)
The reason we only supported 2.6 and 3.0 is because they are the ones we use on hosted Parse. My intuition is the same as yours, that WT and/or 3.2 would just work, but we don't want to officially support it until we've tested it thoroughly, and we just haven't had the time for that yet.
Simple question if parse-server works well with the new storage engine WiredTiger which provides a newer storage engine that compresses your database data over the standard MMAPv1.
My guess would be parse-server wouldn't care what default storage engine your using ..
The text was updated successfully, but these errors were encountered: