[
https://issues.apache.org/jira/browse/CASSANDRA-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795348#action_12795348
]
Jonathan Ellis commented on CASSANDRA-569:
------------------------------------------
Revisiting this, I find I don't understand the motivation for the change. What
use case is this fixing? If most operations complete within time X, but a few
need time X + Y, then why not just make the global timeout X + Y?
> Add Thrift API to set per-connection settings
> ---------------------------------------------
>
> Key: CASSANDRA-569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-569
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Paul Querna
> Attachments: CASSANDRA-569.patch
>
>
> For thrift API, let you set configuration options per-connection. These
> would be stored thread-local on the server, and when a thrift connection
> dies, they would be reset.
> An example use case is setting the timeout for requests on a per-connection
> basis.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
