Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 285A818887 for ; Wed, 16 Sep 2015 20:33:46 +0000 (UTC) Received: (qmail 65442 invoked by uid 500); 16 Sep 2015 20:33:45 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 65398 invoked by uid 500); 16 Sep 2015 20:33:45 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 65382 invoked by uid 99); 16 Sep 2015 20:33:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2015 20:33:45 +0000 Date: Wed, 16 Sep 2015 20:33:45 +0000 (UTC) From: "Ariel Weisberg (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-10359) Saved caches use ambigous keyspace and CF name to identify tables MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ariel Weisberg updated CASSANDRA-10359: --------------------------------------- Reviewer: Robert Stupp > Saved caches use ambigous keyspace and CF name to identify tables > ----------------------------------------------------------------- > > Key: CASSANDRA-10359 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10359 > Project: Cassandra > Issue Type: Bug > Reporter: Ariel Weisberg > Assignee: Ariel Weisberg > Fix For: 3.x, 2.1.x, 2.2.x > > > 2i don't have a unique handle. Robert suggested writing the schema digests into the file and checking that they match before loading caches. > Schema changes would temporarily invalidate saved caches, but the next time they are saved they would be usable again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)