[
https://issues.apache.org/jira/browse/CASSANDRA-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tupshin Harper updated CASSANDRA-7362:
--------------------------------------
Description: 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 CASSSANDRA-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. (was: 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 CASSSANDRA-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. Because it would )
> 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
> CASSSANDRA-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)
