[
https://issues.apache.org/jira/browse/CASSANDRA-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580981#comment-13580981
]
Srdjan Mitrovic commented on CASSANDRA-5267:
--------------------------------------------
I was probably misunderstood, this is just a secondary index with some extra
info stored (beside keys) so partitions are still ordered by partitioner and
data by comparator.
Benefit is that we don't need to read original CF for other data when we query
by index. If this is not possible can you tell me if there is a wiki explaining
internal architecture so that I can read that before creating issues.
Thanks.
> 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
