[
https://issues.apache.org/jira/browse/CASSANDRA-20385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-20385:
----------------------------------------
Resolution: Duplicate
Status: Resolved (was: Triage Needed)
> CEP-45: Consistent sstable import process
> -----------------------------------------
>
> Key: CASSANDRA-20385
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20385
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Consistency/Coordination
> Reporter: Blake Eggleston
> Priority: Normal
>
> Existing methods of importing sstables won’t work with mutation tracking
> because the sstables / their data don’t have mutation ids associated with
> them and we’re not comparing digests of data for reads/repairs.
> We should be able to implement this with the bulk transfer mechanism. The
> special case here is figuring out if/how we’ll support import processes where
> an external process adds sstables to each replica instead of relying on a
> single C* replica to stream data. It seems like we could just use the second
> half of the bulk transfer process to make this imported data visible, but
> we’d want to verify that the sstables being imported are identical before
> doing that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
