MongoDB error on geoPoint query

36 views
Skip to first unread message

Yaakov Gesher

unread,
Aug 3, 2016, 12:58:23 AM8/3/16
to back{4}app
I have a project that was working perfectly, but recently I noticed that when I make a GeoPoint query (using the HTTP API), I get a server error from Parse Server.  The error logs read like this:

  1. 2016-08-03T04:57:28.290Z - Uncaught internal server error. { [MongoError: use geoNear command rather than $near query] name: 'MongoError', message: 'use geoNear command rather than $near query', '$err': 'use geoNear command rather than $near query', code: 13501 } MongoError: use geoNear command rather than $near query at Function.MongoError.create (/usr/src/app/node_modules/mongodb/node_modules/mongodb-core/lib/error.js:31:11) at queryCallback (/usr/src/app/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:182:34) at Callbacks.emit (/usr/src/app/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:119:3) at null.messageHandler (/usr/src/app/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:358:23) at Socket.<anonymous> (/usr/src/app/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:292:22) at emitOne (events.js:77:13) at Socket.emit (events.js:169:7) at readableAddChunk (_stream_readable.js:146:16) at Socket.Readable.push (_stream_readable.js:110:10) at TCP.onread (net.js:523:20)
Looks to me like the parse server code needs to be updated to be compatible with a new version of MongoDB

Davi Macêdo

unread,
Aug 22, 2016, 3:43:46 AM8/22/16
to back{4}app
Hi, Yaakov. Sorry about the delay. Could you please choose a time slot in the link below? I'd like to solve it together with you in a conference call. Best!
Reply all
Reply to author
Forward
0 new messages