[
https://issues.apache.org/jira/browse/CASSANDRA-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Broecheler updated CASSANDRA-9337:
-------------------------------------------
Summary: Expose LocalStrategy to Applications (was: Advanced table options)
> Expose LocalStrategy to Applications
> ------------------------------------
>
> Key: CASSANDRA-9337
> URL: https://issues.apache.org/jira/browse/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
(v6.3.4#6332)
