You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2016/07/05 14:23:10 UTC
[jira] [Updated] (CASSANDRA-12062) Prevent key invalidation if
there's no key to invalidate
[ https://issues.apache.org/jira/browse/CASSANDRA-12062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Stupp updated CASSANDRA-12062:
-------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.x)
3.10
Status: Resolved (was: Ready to Commit)
Thanks!
Committed as [c57d0d4fabb8b1c8b9b312010a706245a203be57|https://github.com/apache/cassandra/commit/c57d0d4fabb8b1c8b9b312010a706245a203be57] to [trunk|https://github.com/apache/cassandra/tree/trunk]
> Prevent key invalidation if there's no key to invalidate
> --------------------------------------------------------
>
> Key: CASSANDRA-12062
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12062
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
> Fix For: 3.10
>
>
> In {{SSTableRewriter}} we currently assume that there are keys to be invalidated in the key cache. That's not always true - especially if a bunch of tiny sstables have been generated.
> Patch saves one {{synchronized}} and a few objects if that's the case.
> Just a small optimisation, but maybe worth to include.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)