[jira] [Commented] (CASSANDRA-7362) Be able to selectively mount a snapshot of a table as a read-only version of that table
[ https://issues.apache.org/jira/browse/CASSANDRA-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (CASSANDRA-7362) Be able to selectively mount a snapshot of a table as a read-only version of that table
[ https://issues.apache.org/jira/browse/CASSANDRA-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020535#comment-14020535 ] Brian Hess commented on CASSANDRA-7362: This could be exposed by a new construct in the catalog. Something like: CREATE OR REPLACE SNAPSHOT TABLE myks.mysnapshot ON myks.mytable; SELECT * FROM myks.mysnapshot WHERE pk=123; DROP SNAPSHOT TABLE myks.mysnapshot; 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)
[jira] [Commented] (CASSANDRA-7362) Be able to selectively mount a snapshot of a table as a read-only version of that table
[ https://issues.apache.org/jira/browse/CASSANDRA-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020583#comment-14020583 ] Jeremiah Jordan commented on CASSANDRA-7362: Is this a dup of CASSANDRA-2527? 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)
