ReadPreference not working for aggregate query

[mtrezza]

Issue Description

Setting the mongodb read preference is ignored for aggregate queries.

Steps to reproduce

const query = new Parse.Query("MyClass");
query.readPreference("SECONDARY");
const results = await query.aggregate([]); //Reads from primary

Expected Results

Should read from secondary.

Actual Outcome

Reads from primary.

Environment Setup

• Server

  • parse-server version (Be specific! Don't say 'latest'.) : 4.2.0
  • Operating System: [FILL THIS OUT]
  • Hardware: [FILL THIS OUT]
  • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): local

• Database

  • MongoDB version: 4.2.5
  • Storage engine: [FILL THIS OUT]
  • Hardware: [FILL THIS OUT]
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): local

Logs/Trace

mongodb nodejs driver log:

"executing command [{"ns":"development.$cmd","cmd":{"aggregate":"MyClass","pipeline":[],"cursor":{}},"options":{}}] against mySecondary.locahost:27010"

[mtrezza]

The read pref is already missing in the request, I assume it's actually a JS SDK issue.

parse-server/src/Routers/AggregateRouter.js

Line 156 in 9842c6e

return this.handleFind(req);

[mtrezza]

Added failing test cases in PR #6585

[mtrezza]

Added JS SDK PR parse-community/Parse-SDK-JS#1143

[mtrezza]

Status:

• waiting for release of JS SDK with merge fix read preference for aggregate query Parse-SDK-JS#1143
• then tests should pass in Fix read preference for aggregate #6585