Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <7879688.58311283881598528.JavaMail.jira@thor>
Date: Tue, 7 Sep 2010 13:46:38 -0400 (EDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Updated: (CASSANDRA-1417) add cache save/load
In-Reply-To: <810356.488111282394119688.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-1417:
--------------------------------------

    Attachment: 1417-v2.txt

started cleaning it up (v2 attached): spaces after //, justification after newline according to style guide, operator spacing, etc.

major fix still needed is converting the timer to an executor (creating a new thread and joining it is a clever workaround but clearly worse than just using an executor -- DTPE has a constructor that does what you want).

> add cache save/load
> -------------------
>
>                 Key: CASSANDRA-1417
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1417
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Matthew F. Dennis
>             Fix For: 0.6.6
>
>         Attachments: 1417-cassandra-0.6.txt, 1417-v2.txt
>
>
> Since mixing 0.7 nodes with 0.6 is looking increasingly unlikely to be supported because of the deep changes to the Thrift API, we should allow saving out the 0.6 cache and loading it on startup so that we don't inflict the pain of an entire cluster of cold cache on upgraders.
> The cache format should just be a list of row keys.  Loading it is as simple as calling getColumnFamily (with a zero-column predicate) on each row, for row cache.
> Key cache is more complicated, but only a little.  First is that you have to de-duplicate the row keys from multiple sstables.  (Saving which sstable version it's associated with is less useful, since that will be obsoleted by compaction.)  Second is that we don't need to actually read any row data, we just need to go through the index locator part of the read path (getPosition).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.