[COMPASS-6436] Investigate changes in NODE-4961: commitTransaction and abortTransaction return command result Created: 17/Jan/23  Updated: 01/Feb/23  Resolved: 01/Feb/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: PM Bot Assignee: Unassigned
Resolution: Done Votes: 0
Labels: node-driver
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on NODE-4961 commitTransaction and abortTransactio... Closed
Documentation Changes: Not Needed

 Description   

Use Case

As a node driver engineer
I want to align with the driver spec

The transaction spec has function prototypes for abortTransaction and commitTransaction which indicate they should return void. Currently the driver returns the raw command result for each respective operation

User Impact

*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

Unknowns

  • questions that need to be answered to determine implementation

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

Generated at Wed Feb 07 22:43:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.