incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Dennis <mden...@riptano.com>
Subject Re: Does the secondary index in 0.7 cost extra space like an extra ColumnFamily?
Date Thu, 07 Oct 2010 01:57:19 GMT
Creating indexes takes extra space (does in MySQL, PGSQL, etc too).

https://issues.apache.org/jira/browse/CASSANDRA-749 has quite a bit of
detail about how the secondary indexes currently work.

On Wed, Oct 6, 2010 at 7:17 PM, Alvin UW <alvinuw@gmail.com> wrote:

> Hello,
>
> Before 0.7, actually we can create an extra ColumnFamily as an secondary
> index, if we need.
>
> I was wondering whether the secondary index mechanism in 0.7 just likes
> creating an extra ColumnFamily as an index.
> The difference is only that users don't take care of the maintainence of
> the secondary index, instead the system will maintain it.
> Hence, the secondary index is also a redundant copy, which costs extra
> space as the same as creating an extra ColumnFamily as an index.
>
> Am I right?
> Thanks.
>
>
> Alvin
>



-- 
Riptano
Software and Support for Apache Cassandra
http://www.riptano.com/
mdennis@riptano.com
m: 512.587.0900 f: 866.583.2068

Mime
View raw message