I think, at least currently, we should leave the logic of current SuperColumn and addational indexing features to application layer of cassandra core.
On Wed, Apr 28, 2010 at 6:44 PM, Schubert Zhang <zson...@gmail.com> wrote: > I don't think secondary index is necessary for cassandra core, at least it > is not urgent. > I think currently, the first urgent improvements of cassandra are: > 1. re-clarify the data-model. > 2. re-implement the storage and index, especially the current SSTable > implement is not good. > > In fact, the current storage/index implement is the most poor point. > > > > On Tue, Apr 27, 2010 at 12:11 AM, Jonathan Ellis <jbel...@gmail.com>wrote: > >> I think that once we have built-in indexing (CASSANDRA-749) you can >> make a good case for dropping supercolumns (at least, dropping them >> from the public API and reserving them for internal use). >> >> On Mon, Apr 26, 2010 at 11:05 AM, Schubert Zhang <zson...@gmail.com> >> wrote: >> > I don't think the SuperColumn is so necessary. >> > I think this level of logic can be leaved to application. >> > >> > Do you think so? >> > >> > If SuperColumn is needed, as >> > https://issues.apache.org/jira/browse/CASSANDRA-598, we should build >> index >> > in SuperColumns level and SubColumns level. >> > Thus, the levels of index is too many. >> > >> > >> > >
