[SERVER-29757] Investigate whether $_internalSchema* MatchExpressions can be banned for use by applications Created: 20/Jun/17 Updated: 12/Sep/17 Resolved: 12/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Query 2017-10-02 |
| Participants: |
| Comments |
| Comment by Tess Avitabile (Inactive) [ 12/Sep/17 ] |
|
I suggest we do not ban $_internalSchema* MatchExpressions for use by applications. mongos can send $_internalSchema* expressions to mongod when there is a $jsonSchema in a $match stage that participates in match splitting. So we have to allow $_internalSchema* in aggregation commands with fromMongos=true. We could restrict $_internalSchema* to only be allowed when fromMongos=true, but nothing prevents a user from specifying fromMongos true in order to work around this. |