[
https://issues.apache.org/jira/browse/CASSGO-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Reis updated CASSGO-135:
-----------------------------
Change Category: Operability
Complexity: Normal
Fix Version/s: 2.x
Status: Open (was: Triage Needed)
> Rework timeout configuration
> ----------------------------
>
> Key: CASSGO-135
> URL: https://issues.apache.org/jira/browse/CASSGO-135
> Project: Apache Cassandra Go driver
> Issue Type: New Feature
> Components: Core
> Reporter: João Reis
> Priority: Normal
> Fix For: 2.x
>
>
> In CASSGO-125 we fixed a regression that caused ClusterConfig.Timeout to be
> used on all socket read operations. At that time we planned to introduce a
> ReadTimeout configuration property later. This ticket should address not only
> that but also potentially other things that we've identified since then:
>
> * Not possible to configure Metadata Query timeout (system table queries
> except ones used in the connection init phase, those should still fall under
> "ConnectTimeout" which already exists)
> * Not possible to override query/batch timeout on a per request basis. If
> you provide a context it will not disable the session level timeout that you
> defined on the ClusterConfig
> [This community
> PR|https://github.com/apache/cassandra-gocql-driver/pull/1953/] has a nice
> proposal from which we can draw some inspiration (the documentation on the
> README is also nice)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
