[
https://issues.apache.org/jira/browse/CASSANDRA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-755.
--------------------------------------
Resolution: Invalid
This is not a good fit for Cassandra. See
http://wiki.apache.org/cassandra/ArchitectureInternals (and read the Dynamo
paper).
erasure codes are a good fit when you are storing (a) relatively large pieces
of data that (b) don't care too much about latency. neither of those applies
to cassandra.
also note that jira is not a good place for "is X a good fit for cassandra?"
discussions; use the -dev mailing list for that.
> Use a systematic online code for efficient redundancy
> -----------------------------------------------------
>
> Key: CASSANDRA-755
> URL: https://issues.apache.org/jira/browse/CASSANDRA-755
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Anthony Di Franco
> Priority: Minor
>
> Use a systematic online code for efficient redundancy (or specify why this is
> not appropriate for Cassandra in the documentation). Systematic online codes
> permit an arbitrarily large or small number of repair symbols to be added to
> the original data to more smoothly increase the amount of redundant storage;
> in particular, they would permit redundancy ratios between 1 and 2 to be used.
> See here:
> http://en.wikipedia.org/wiki/Online_codes
> and here:
> http://archipelago.rubyforge.org/svn/trunk/oneliner/
> and here:
> http://tools.ietf.org/html/rfc5053
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
