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 DF8FD1171D for ; Thu, 12 Jun 2014 01:06:04 +0000 (UTC) Received: (qmail 56515 invoked by uid 500); 12 Jun 2014 01:06:04 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 56175 invoked by uid 500); 12 Jun 2014 01:06:03 -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 56164 invoked by uid 99); 12 Jun 2014 01:06:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2014 01:06:03 +0000 Date: Thu, 12 Jun 2014 01:06:03 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7362) Be able to selectively "mount" a snapshot of a table as a read-only version of that table 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-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028674#comment-14028674 ] Jonathan Ellis commented on CASSANDRA-7362: ------------------------------------------- Note that this requires 7190 or it will be very easy to mount snapshots that no longer match the current schema. > Be able to selectively "mount" a snapshot of a table as a read-only version of that table > ----------------------------------------------------------------------------------------- > > Key: CASSANDRA-7362 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7362 > Project: Cassandra > Issue Type: New Feature > Components: Core, Tools > Reporter: Tupshin Harper > Priority: Minor > Fix For: 3.0 > > > When doing batch jobs (thinking hive and shark as prominent examples) or repeated analysis of the same data, it can be challenging to get a consistent result if the data is changing under your feet. Rather than the low level CASSANDRA-2527, I propose that we add the capability to take a named snapshot (exact uuid in 2.1 and later), and be able to activate and deactivate it as a regular sstable (e.g. myks.mytable snapshot could be activated as myks.mytable-longuuid). That table would be queryable just like any other, but would not be writable. Any attempt to insert or update would throw an exception. -- This message was sent by Atlassian JIRA (v6.2#6252)