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

Support BSON MinKey and MaxKey in BSONColumn

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0, 7.0.6, 6.0.14
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Storage Execution
    • Fully Compatible
    • v7.0, v6.0
    • Execution Team 2024-01-22, Execution Team 2024-02-05

      BSON MinKey and MaxKey are the only unencodable types/values in the BSONColumn format.

      If a user uses these special types when inserting data into a time-series collection we cannot use the compressed bucket format. This will prevent us from a future where we can rely on the compressed bucket format being used and the advantages that gives (guarantee for query that the data is sorted on time for example).

      It also makes the insertion logic more complicated. If the BSONColumn compressor throws when inserting data, we'd need to differentiate between unsupported user input and corrupt BSONColumn binary.

            henrik.edin@mongodb.com Henrik Edin
            henrik.edin@mongodb.com Henrik Edin
            0 Vote for this issue
            4 Start watching this issue