This is a longer-term effort and would be a step towards alignment with the other clients.
Timeout specification should become a set of six different timeouts for as many different classes of operations (db-admin; keyspace-admin; collection ddl; table ddl; single-request methods; multiple-request-methods), with well-defined semantics defining how they interact per method.
It is a nontrivial effort and can surely wait well after GA :)
Example: see astrapy (docstring is pretty informative)
(As a side thing, since a timeout error may be due to a violation of any of the various values, ideally such an error should report what was the value that got exceeded (and its name)).
Relevant links/info:
This is a longer-term effort and would be a step towards alignment with the other clients.
Timeout specification should become a set of six different timeouts for as many different classes of operations (db-admin; keyspace-admin; collection ddl; table ddl; single-request methods; multiple-request-methods), with well-defined semantics defining how they interact per method.
It is a nontrivial effort and can surely wait well after GA :)
Example: see astrapy (docstring is pretty informative)
(As a side thing, since a timeout error may be due to a violation of any of the various values, ideally such an error should report what was the value that got exceeded (and its name)).
Relevant links/info: