[
https://issues.apache.org/jira/browse/CASSANDRA-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582251#comment-13582251
]
Jonathan Ellis commented on CASSANDRA-5267:
-------------------------------------------
I don't understand.
bq. Benefit is that we don't need to read original CF for other data when we
query by index
This sounds like a covered index query, but
bq. In the background we could have a CF having only (key, indexed_value), in
this case (posted_at, blog_id) so that we can maintain our index when we delete
a row or change blog_id, and we would store other values within the index
sounds like you want to change how the actual table data is stored.
> Index organized table
> ---------------------
>
> Key: CASSANDRA-5267
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5267
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Srdjan Mitrovic
> Priority: Minor
>
> The purpose is to enable very fast scans for queries which use WHERE
> indexed_column_value='foo';
> We could borrow syntax from Oracle (with a small difference).
> {noformat}CREATE TABLE blog_entries (
> posted_at timestamp,
> blog_id int
> author text,
> content text,
> PRIMARY KEY (posted_at)
> )
> ORGANIZATION INDEX ON (blog_id);
> {noformat}
> In the background we could have a CF having only (key, indexed_value), in
> this case (posted_at, blog_id) so that we can maintain our index when we
> delete a row or change blog_id, and we would store other values within the
> index.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
