[GODRIVER-2622] Stabilize CSOT Created: 27/Oct/22  Updated: 18/Jan/24  Resolved: 18/Jan/24

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Epic Priority: Unknown
Reporter: Benji Rewis (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates GODRIVER-2602 Stabilize CSOT Closed
Related
related to GODRIVER-1885 Client Side Operations Timeout Closed
is related to GODRIVER-2944 Support CSOT spec timeoutMode for non... Scheduled
Documentation Changes Summary: 1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?
Scope Cost Estimate: 0
Cost to Date: 0
Final Cost Estimate: 0
Cost Threshold %: 100

 Description   

Summary

The CSOT spec now significantly diverges in its description of the feature from both the Python and Go implementations. We should wait for the spec to be updated (allowing language-specific syntax, bumping timeouts in tests, removing requirements for timeoutMode on cursors and timeoutMS options on non-client types) and the resolution of DRIVERS-2347. Once the spec is more stabilized and representative of what we've implemented in Go, we should make sure our implementation aligns with the new spec and continue the epic.

Motivation

Who is the affected end user?

Users of CSOT in the Go driver.

How does this affect the end user?

CSOT is not fully designed and remains provisional API. Users should have access to a more stable timeout API.

How likely is it that this problem or use case will occur?

Likely that users may encounter inconsistencies in CSOT features.

If the problem does occur, what are the consequences and how severe are they?

May push users away.

Is this issue urgent?

No. And we probably can't do this until CSOT spec work is re-prioritized.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

No.



 Comments   
Comment by Steve Silvester [ 18/Jan/24 ]

After reviewing this epic, it is out of date.
GODRIVER-2348, GODRIVER-2762, DRIVERS-2347, and DRIVERS-2722 cover the current state of CSOT in the driver.

If we find anywhere that the Go driver meaningfully deviates from the current CSOT spec, we should create new tickets to address those.

Generated at Thu Feb 08 08:39:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.