We are using loc2d indexes on a 'loc' property of our documents. When adding these documents to a collection, we run:

collection.update({
    'set': {
        'loc.long': -100,
        'loc.lat': 45
    }
},
{ 'upsert': true }
);

Which results in:

{
    '_id': [Id],
    'loc': {
        'lat': 45,
        'long': -100
    }
}

Which on the environment described seems to work incorrectly and set the lat before the long. Since loc2d indexes are order specific, that is posing a problem for us. In testing on a dev box with Mongo 2.6 the problem seems to be fixed. Behavior seems inconsistent either way. Did I miss the fix in a change log, or am I doing something wrong?

Thanks.