Invalid parameter for query: pipeline

[mtrezza]

After upgrading from Parse Server 3.0.0 to a version >3.0.0 and <=3.1.3 (latest) the aggregate query in cloud code does not work anymore.

The query:

const query = new Parse.Query("MyClass");
const pipeline = {
    "sort":{"_created_at":-1}
};

const results = await query.aggregate(pipeline);

fails with error:

ParseError: 102 Invalid parameter for query: pipeline

I also tried the pipeline object as array which also fails:

const pipeline = [
    {"sort":{"_created_at":-1}}
];

Such an error can be thrown at:

• ClassesRouter.js
• AggregateRouter.js

Seems to be a bug because I did not find any breaking changes documented regarding aggregate.
Parse Server 3.1.0 made the jump from Parse JS SDK 2.0.2 to 2.1.0, so maybe it is a bug in the JS SDK.

Note: I am not using the Parse JS SDK as a client, it is only used through cloud code.

Any ideas?

---

I posted this on SO before, but it looks like a bug, so posting here.

[mtrezza]

To rule out possibly conflicting parse-server / parse JS SDK versions, I deleted parse dependency from parse-server-example and deployed on heroku with node_module_cache=false.

npm list shows [email protected] installed under [email protected].
Still getting the error.

It would be great if anyone could try to reproduce this with a simple aggregate query in cloud code.

[mtrezza]

So it's not a bug, it was a Parse Server vs. Parse JS SDJ mismatch.
I had two parse servers running on the same DB for testing during migration. Turns out that some URLs in the v3.x server still pointed to the other v2.8.4 server. After correcting the URLs all works fine.

Thanks @dplewis (on SO).