-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Unable to make a count on a query with a GeoConstraint #5285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
type:bug
Impaired feature or lacking behavior that is likely assumed
Comments
If it can help: I used some dichotomy and ran my minimal Parse server on top of different Parse Server versions. The issue seems to be introduced by the 3.1.0 version. Indeed, with |
jlnquere
added a commit
to jlnquere/parse-server
that referenced
this issue
Jan 9, 2019
I also sent a PR with a test that cover this issue: #5286 |
jlnquere
added a commit
to jlnquere/parse-server
that referenced
this issue
Jan 16, 2019
… $geoWithin) All credit goes to @dplewis !
UnderratedDev
pushed a commit
to UnderratedDev/parse-server
that referenced
this issue
Mar 21, 2020
…ity#5285) (parse-community#5286) * Add a tests that fails due to issue parse-community#5285 * Make test code much simpler * Fix parse-community#5285 by rewriting query (replacing $nearSphere by $geoWithin) All credit goes to @dplewis ! * move logic to transform
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
When I try to make a count on a query with a GeoConstraint, I have an
internal server error
. It seems to be tied to an issue with Mongo:MongoError: $nearSphere is not allowed inside of a $match aggregation expression
.Steps to reproduce
I built a minimal parse instance (just a copy paste of documentation):
On client side:
Expected Results
I'm expecting
query.count()
to return a count.Actual Outcome
Instead, the client got an
internal server error
. On server, I got this trance:The request (so far, so good):
The error:
Environment Setup
Server
Database
The text was updated successfully, but these errors were encountered: