Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-25275

Investigate performance implications of refactoring Pipeline authorization checks to happen after parsing

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Aggregation Framework
    • None
    • Query Optimization

    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.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: