[JAVA-5290] CSOT: Deprecation of timeout configuration options Created: 10/Jan/24  Updated: 19/Jan/24

Status: Backlog
Project: Java Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Slav Babanin Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to JAVA-5264 Deprecate CRUD method options Closed
Epic Link: Client Side Operations Timeout
Quarter: FY24Q3

 Description   

Description:

This ticket addresses the deprecation of various configuration timeout options in favor of a unified timeoutMS parameter. The aim is to simplify and standardize timeout configurations across the drivers.

Deprecation Details:

  • Configuration Timeout Options:
    • socketTimeoutMS
    • waitQueueTimeoutMS
    • wTimeoutMS

These options are to be deprecated in favor of the more unified timeoutMS setting.

  • Deprecation of maxTime() in Iterable/Observable/Publisher/Flow:
    • ListDatabases
    • ListIndexes
    • ListCollections
    • ListCollectionNames
    • ListSearchIndexes
    • MapReduce
    • GridFS

The maxTime setting in all these methods will be deprecated in favor of timeoutMS.

  • Additional Deprecations:
    • ConnectionString#getSocketTimeout()
    • ConnectionString#getMaxAwaitTime()
    • SocketSettings#readTimeout
    • SocketSettings#getReadTimeout
    • ConnectionPoolSettings#maxWaitTime
    • ConnectionPoolSettings#getMaxWaitTime
    • CreateIndexOptions#maxTime

These additional settings will also be deprecated and aligned with the timeoutMS configuration.


Generated at Thu Feb 08 09:04:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.