cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias Broecheler (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-9337) Advanced table options
Date Fri, 08 May 2015 23:46:00 GMT
Matthias Broecheler created CASSANDRA-9337:

             Summary: Advanced table options
                 Key: CASSANDRA-9337
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Matthias Broecheler

For applications that build on top of Cassandra, two common use cases emerge:

1) Secondary indexes are used to maintain some form of a custom materialized view locally
in a separate table. This is essentially what C* column indexes do. In that case, the table
should be local (i.e. not replicated) as it is maintained against another table.
2) A table is used to store configuration information to pertains to the application running
atop of Cassandra which needs to be replicated to all nodes.

In both cases, the replication strategy differs from standard tables and the tables should
not be visible to the user when doing a DESCRIBE KEYSPACE. In both cases, it would furthermore
be nice if writing could be restricted so that the tables can only be updated from within
the process but not by clients through CQL. No read restrictions need to be imposed.

This message was sent by Atlassian JIRA

View raw message