cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1745) index scan should treat not-present columns as not matching index expressions
Date Thu, 18 Nov 2010 00:17:15 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933250#action_12933250
] 

Hudson commented on CASSANDRA-1745:
-----------------------------------

Integrated in Cassandra-0.7 #13 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/13/])
    

> index scan should treat not-present columns as not matching index expressions
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1745
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1745
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.7.0
>
>         Attachments: 1745.txt
>
>
> As reported on the mailing list,
> {code}
> I created a column family and added index on column A,B,C. 
> Now I insert three rows. 
> row1 : A=123, B=456, C=789 
> row2 : A=123, C=789 
> row3 : A=123, B=789, C=789 
> Now if I perform an indexed query for A=123 and B=456, both row1 and row2 are returned.

> {code}

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


Mime
View raw message