[
https://issues.apache.org/jira/browse/CASSANDRA-12571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512357#comment-15512357
]
Stefania edited comment on CASSANDRA-12571 at 9/22/16 6:46 AM:
---------------------------------------------------------------
This behavior was changed by CASSANDRA-10686 in all versions since 2.1.13.
[~pauloricardomg] was there a reason to remove this functionality and should
the doc be updated or should we re-instate this behavior?
IMO it's better to use a large timeout rather than None and I would be inclined
to update the documentation.
was (Author: stefania):
This behavior was changed by CASSANDRA-10686 in all versions since 2.1.13.
[~pauloricardomg] was there a reason to remove this functionality and should
the doc be updated or or can we re-instate this behavior?
IMO it's better to use a large timeout rather than None and I would be inclined
to update the documentation.
> 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
>
> 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)
