[
https://issues.apache.org/jira/browse/CASSGO-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Reis updated CASSGO-61:
----------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: API /
Semantic Implementation(12988)
Complexity: Normal
Component/s: Core
Discovered By: User Report
Fix Version/s: 2.x
Severity: Low
Status: Open (was: Triage Needed)
> Connection timeout does not overrided with query context timeout
> ----------------------------------------------------------------
>
> Key: CASSGO-61
> URL: https://issues.apache.org/jira/browse/CASSGO-61
> Project: Apache Cassandra Go driver
> Issue Type: Bug
> Components: Core
> Reporter: Oleksandr Luzhniy
> Priority: Normal
> Fix For: 2.x
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{exec()}} method for connection considers both ({{{}Conn{}}} and
> {{{}ctx{}}}) timeouts.
> And handles the first one that expires
> ([here|https://github.com/apache/cassandra-gocql-driver/blob/trunk/conn.go#L1150]).
> That affects query custom timeout, you can set it to less than Connection
> timeout and that will work, but if it's bigger than {{connection}} timeout -
> it won't be taken into account. That is half of the functional.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
