Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-5290

CSOT: Deprecation of timeout configuration options

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 5.1.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed
    • Hide

      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?

      Show
      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?

      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.

            Assignee:
            slav.babanin@mongodb.com Slav Babanin
            Reporter:
            slav.babanin@mongodb.com Slav Babanin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: