cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Tata (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-277) combine _range slice methods into main ones
Date Tue, 07 Jul 2009 17:42:15 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sandeep Tata updated CASSANDRA-277:
-----------------------------------

    Attachment: 277-systest.patch

Shouldn't isAscending determine the order in which results are returned?

I've added a system test in the attached patch. Is this an incorrent understanding of isAscending?

> combine _range slice methods into main ones
> -------------------------------------------
>
>                 Key: CASSANDRA-277
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-277
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>         Attachments: 277-systest.patch, 277.patch
>
>
> Instead of
>   list<column_t> get_slice_by_name_range(1:string tablename, 2:string key, 3:string
columnParent, 4:string start, 5:string finish, 6:i32 count=100)
>   throws (1: InvalidRequestException ire, 2: NotFoundException nfe),
>   
>   list<column_t> get_slice(1:string tablename, 2:string key, 3:string columnParent,
4:bool isAscending, 5:i32 count=100)
>   throws (1: InvalidRequestException ire, 2: NotFoundException nfe),
> we would just have
>   list<column_t> get_slice(tablename, key, columnParent, start, finish, isAscending,
count=100)
> (note that get_slice currently has "start" arg folded into columnParent which is the
wrong way to go for CASSANDRA-139 and also caused the CASSANDRA-260 regression, so breaking
that back out seems like the Right Thing To Do.)

-- 
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