[
https://issues.apache.org/jira/browse/CASSANDRA-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851668#action_12851668
]
Stu Hood commented on CASSANDRA-749:
------------------------------------
> "maybe it had the columns requested, maybe not, but it didn't match your
> where clause"
I'm not talking about looking at values here: just keys/names. So the only
question that query is answering is "did this column key/name exist with these
parents".
The _only_ way to query values with the API I proposed is to create a view by
the value.
> "my system lets me do queries that are slow" is NOT a complaint most people
> have about sql
I disagree, but perhaps we misunderstood eachother on that first point.
----
Are there any alternatives to 'null rows', that aren't as awkward? Essentially,
what a user is supposed to understand is: "the database had to scan 100 null
rows for every 1 that it returned"
> Secondary indices for column families
> -------------------------------------
>
> Key: CASSANDRA-749
> URL: https://issues.apache.org/jira/browse/CASSANDRA-749
> 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.
