cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-749) Secondary indices for column families
Date Tue, 30 Mar 2010 16:56:27 GMT


Jonathan Ellis commented on CASSANDRA-749:

I suppose that's an option, but

 - that tombstoned keys give empty result sets is correct, if unexpected, and even so it's
possibly the #1 FAQ we get.  adding Yet Another Special Case, this time with null sets to
indicate that "maybe it had the columns requested, maybe not, but it didn't match your where
clause" isn't even remotely intuitive.
 - In 10 years of using relational databases I can count on zero fingers the number of times
that an indexed query was killing the system because of extra where clauses that made it scan
extra data.  Sure, it's theoretically possible, but in practice it just doesn't seem to matter.
 - "my system lets me do queries that are slow" is NOT a complaint most people have about
sql.  you're addressing a pain point that people just aren't feeling.

So I'd be more inclined to say, let's do it the intuitive way.

> Secondary indices for column families
> -------------------------------------
>                 Key: CASSANDRA-749
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Gary Dusbabek
>            Assignee: Gary Dusbabek
>            Priority: Minor
>             Fix For: 0.8
>         Attachments: 0001-simple-secondary-indices.patch, views-discussion-2.txt, views-discussion.txt

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message