This is an automated email from the ASF dual-hosted git repository.
absurdfarce pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cassandra-python-driver.git
The following commit(s) were added to refs/heads/master by this push:
new d0407ea0 PYTHON-1354 do not set timeout to None when calling
execute_async in execute_concurrent
d0407ea0 is described below
commit d0407ea0a9d51be1498a93d9d62ac3a9a0bacfa2
Author: Hannes Järrendal <[email protected]>
AuthorDate: Tue Nov 11 12:03:12 2025 +0100
PYTHON-1354 do not set timeout to None when calling execute_async in
execute_concurrent
The default timeout=_NOT_SET will use the request_timeout specified in
the execution_profile. This is not the same as setting the timeout to
None. This will instead result in having no timeout which is not ideal.
If this behaviour really is wanted, the request_timeout can be set to
None in the execution_profile instead.
patch by osttra-h-jarrendal; reviewed by Bret McGuire and Brad Schoening
---
cassandra/concurrent.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cassandra/concurrent.py b/cassandra/concurrent.py
index 394f462f..012f52f9 100644
--- a/cassandra/concurrent.py
+++ b/cassandra/concurrent.py
@@ -83,7 +83,7 @@ class _ConcurrentExecutor(object):
def _execute(self, idx, statement, params):
self._exec_depth += 1
try:
- future = self.session.execute_async(statement, params,
timeout=None, execution_profile=self._execution_profile)
+ future = self.session.execute_async(statement, params,
execution_profile=self._execution_profile)
args = (future, idx)
future.add_callbacks(
callback=self._on_success, callback_args=args,
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
