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

Clearly separate concerns of BucketSpec and BucketUnpacker

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It's unclear what should be in BucketSpec and what should be in BucketUnpacker. Recently there was a bug that occurred as a result of this confusion. We should come up with a clear rationale for what should live where (or if they should be combined), and in what situations one should use one or the other.

      My general sense was that BucketSpec contains parameters that are specific to the bucket, and that BucketUnpacker would then contain query-specific attributes determined through analysis. But BucketSpec contains computedMetaProjFields which is query-specific, so that doesn't hold.

            Assignee:
            Unassigned Unassigned
            Reporter:
            chris.wolff@mongodb.com Chris Wolff
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None