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.
- is depended on by
-
SERVER-85323 BSONColumnBuilder support for BSON MinKey and MaxKey
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-84170 Time-series bucket compression fails with certain input
-
- Closed
-
-
-
- Closed
-