[
https://issues.apache.org/jira/browse/CASSANDRA-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-2035.
---------------------------------------
Resolution: Invalid
I think these need to be broken up into separate feature requests.
IMO, the last of these was adequately addressed by CASSANDRA-2498.
> Thread local client options
> ---------------------------
>
> Key: CASSANDRA-2035
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2035
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Edward Capriolo
> Priority: Minor
>
> In Cassandra 0.7.X keyspace moved from the method signature of the get
> request to a thread local variable. I think there are several other thread
> local variables that could be added that would could give special performance
> characteristics. These would be set on the client and change how the server
> processes requests.
> * nocache
> Currently we have two applications, one of them is a range scan and cleanup
> application, the other is some of of our data is fed into the system through
> a batch process that is hours behind current. Especially in the case of the
> second program we get cache pollution all day long. this option would allow
> us to batch/back load without ruining caches.
> * norepair
> This option would supersede the current read repair chance or work with it.
> Helpful if you know you may re-edit this column soon anyway
> * memtable read prefer
> I know this idea is ify. For most use cases the column being read is inside
> your memtable newer versions will not exist on disk. This option means -if
> you find data in the memtable use that, otherwise look on disk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
