Make the variable type for 'limit' consistent across sort code

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • QE 2025-09-15, QE 2025-09-29
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      DocumentSourceSort holds its 'limit' as a boost::optional<long long> and its SortStageOptions hold a uint64_t. Furthermore, the SortExecutor asks for a uint64_t while its SortOptions inside sorter.h ask for an unsigned long long . Inside DocumentSourceSort::createFromBson() we get the limit from the spec by way of elem.parseIntegerElementToNonNegativeLong(). This inconsistency adds complexity to passing the same value around.

            Assignee:
            Logan Karbiner
            Reporter:
            Mariano Shaar
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: