[
https://issues.apache.org/jira/browse/CASSANDRA-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783714#action_12783714
]
Jonathan Ellis edited comment on CASSANDRA-569 at 11/30/09 3:59 PM:
--------------------------------------------------------------------
Thanks for the patch! A question:
Why do we need resetLocalSettings in getProcessor? Since we are using threaded
server, shouldn't the threadlocalness handle that for us when a new client
connects?
Also, since we are moving towards using DatabaseDescriptor for fat clients as
well as servers (see CASSANDRA-535), StorageProxy is a better place for the
threadlocal.
was (Author: jbellis):
Why do we need resetLocalSettings in getProcessor? Since we are using
threaded server, shouldn't the threadlocalness handle that for us when a new
client connects?
Since we are moving towards using DatabaseDescriptor for fat clients as well as
servers (see CASSANDRA-535), StorageProxy is a better place for the threadlocal.
> 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.
