-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Compressors, zstd
-
Not Needed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Use Case
As a... Node.js driver user
I want... zstd compression support to use the Node.js 22+ built-in feature
So that... I don't have to install additional npm packages in order to make zstd compression work.
User Experience
- The Node.js driver detects whether the addon is available and/or whether the Node.js-built-in zstd API is available, and uses it if either is (precedence TBD).
Dependencies
- This will likely be how we implement MONGOSH-825.
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- Is there an opportunity for better cross-driver alignment or testing in this area?
- Is there an opportunity to improve existing documentation on this subject?
Acceptance Criteria
Implementation Requirements
- functional reqs, potential snafus to avoid, performance targets, etc
Testing Requirements
- unit test, spec test sync, etc
Documentation Requirements
- DOCSP ticket, API docs, etc
Follow Up Requirements
- additional tickets to file, required releases, etc
- if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward
- is depended on by
-
MONGOSH-825 MongoParseError: zstd is not a valid compression mechanism
-
- Backlog
-