-
Type: Sub-task
-
Resolution: Fixed
-
Priority: Unknown
-
Affects Version/s: None
-
Component/s: None
Use Case
As a Node.js engineer
I want to use async/await inside the bulkWrite implmeentation
So that I can get full stack traces
User Experience
- What is the desired/expected outcome for the user once this ticket is implemented?
- If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
Dependencies
- upstream and/or downstream requirements and timelines to bear in mind
- None, but would be nice for CSOT. (debugging)
Risks/Unknowns
- What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
- We could break the entire driver. But not likely if we run our existing tests
- Is there an opportunity for better cross-driver alignment or testing in this area?
- No
- Is there an opportunity to improve existing documentation on this subject?
- No
Acceptance Criteria
Implementation Requirements
- Refactor handleWriteError, handleMongoWriteConcernError to throw instead of call a callback
- Refactor executeCommands to be async and loop over the batches awaiting each operation
Testing Requirements
- Existing tests pass
Documentation Requirements
- No internal only change
Follow Up Requirements
- None