[SERVER-25275] Investigate performance implications of refactoring Pipeline authorization checks to happen after parsing Created: 25/Jul/16  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Optimization
Participants:

 Description   

As part of SERVER-24654, we considered adding a virtual method on the DocumentSource interface to ensure all new stages added any required privileges, but decided against it because it would involve parsing before we checked for privileges, and thus double parsing, or dramatically increasing the scope of the project.

This ticket is meant to represent some investigatory work to see how much of a performance hit it would be to parse the aggregation pipeline during PipelineCommand::checkAuthForCommand.


Generated at Thu Feb 08 04:08:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.