cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6477) Materialized Views (was: Global Indexes)
Date Wed, 29 Jul 2015 17:58:09 GMT


Aleksey Yeschenko commented on CASSANDRA-6477:

Didn't mean to actually add it as a new {{Flag}} enum field - only a boolean in {{CFMetaData}}
(and we want want for {{isIndex}} too, instead of the hack with the name, but it's unrelated
to the ticket). It being an actual extra thing in the enum is meaningless, since tables in
{{system_schema.tables}} will never have it, and views in the future {{system_schema.materialized_views}},
always will (no need to store it).

But it's good enough for now (will have to go before CASSANDRA-9921, though).

Thrift validation is still lacking. In particular {{system_update_column_family}} and {{system_drop_column_family}}.
Some tests by someone would be nice (not alpha-blocking).

{{SelectStatement}} is still not asking for {{SELECT}} on the base table for MVs.

> Materialized Views (was: Global Indexes)
> ----------------------------------------
>                 Key: CASSANDRA-6477
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>            Assignee: Carl Yeksigian
>              Labels: cql
>             Fix For: 3.0 alpha 1
>         Attachments:, users.yaml
> Local indexes are suitable for low-cardinality data, where spreading the index across
the cluster is a Good Thing.  However, for high-cardinality data, local indexes require querying
most nodes in the cluster even if only a handful of rows is returned.

This message was sent by Atlassian JIRA

View raw message