[
https://issues.apache.org/jira/browse/CASSANDRA-12571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516130#comment-15516130
]
Nate Sanders commented on CASSANDRA-12571:
------------------------------------------
I'd vote for not allowing None, as I agree that just using a high number for
the timeout is basically the same thing and that way there's no new code to
write. However, I think it might be worth calling out in newer documentation
that previously `connect_timeout` allowed for None and the new
`request_timeout` does not.
> cqlsh lost the ability to have a request wait indefinitely
> ----------------------------------------------------------
>
> Key: CASSANDRA-12571
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12571
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: Cassandra 3.7
> Reporter: Nate Sanders
> Assignee: Stefania
> Priority: Minor
> Labels: cqlsh, lhf
>
> In commit c7f0032912798b5e53b64d8391e3e3d7e4121165, when client_timeout
> became request_timeout, the logic was changed so that you can no longer use a
> timeout of None, despite the docs saying that you can:
> https://docs.datastax.com/en/cql/3.3/cql/cql_reference/cqlshUsingCqlshrc.html#cqlshUsingCqlshrc__request-timeout
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
