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

Sandeep Tata updated CASSANDRA-81:
----------------------------------

    Attachment: CASSANDRA-81-v7.patch

1. fixed test.
2. inlined filter :-)

> get_slice ignores the "start" parameter
> ---------------------------------------
>
>                 Key: CASSANDRA-81
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-81
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: trunk
>         Environment: all
>            Reporter: Sandeep Tata
>            Assignee: Sandeep Tata
>             Fix For: 0.3
>
>         Attachments: 81-v5.patch, CASSANDRA-81-v6.patch, 
> CASSANDRA-81-v7.patch, fix_for_get_slice.patch, 
> get_slice_fix_and_unit_tests_v2.patch, get_slice_fix_and_unit_tests_v3.patch, 
> get_slice_fix_and_unit_tests_v4.patch, unit_tests_for_get_slice.patch
>
>
> get_slice(string tablename, string key, string columnFamily_column, i32 
> start, i32 count) is expected is return all columns starting at offset 
> "start" subject to a maximum of "count" columns. The current code does not do 
> this.
> Example interaction:
> ./Cassandra-remote insert 'Table1' 'key' 'DATA:c1' 'val1' 1
> None
> ./Cassandra-remote insert 'Table1' 'key' 'DATA:c2' 'val2' 1
> None
> ./Cassandra-remote insert 'Table1' 'key' 'DATA:c3' 'val3' 1
> None
> ./Cassandra-remote get_slice 'Table1' 'key' 'DATA'  0 2
> [ {'columnName': 'c1', 'value': 'val1', 'timestamp': 1},
>   {'columnName': 'c2', 'value': 'val2', 'timestamp': 1}]
> ./Cassandra-remote get_slice 'Table1' 'key' 'DATA'  1 2
> [ {'columnName': 'c1', 'value': 'val1', 'timestamp': 1},
>   {'columnName': 'c2', 'value': 'val2', 'timestamp': 1}]]  <<---- Same as 
> prev! "start" ignored
> ./Cassandra-remote  get_slice 'Table1' 'key' 'DATA'  0 1
> [{'columnName': 'c1', 'value': 'val1', 'timestamp': 1}]
> ./Cassandra-remote get_slice 'Table1' 'key' 'DATA'  2 1
> [{'columnName': 'c1', 'value': 'val1', 'timestamp': 1}]    <<---- Same as 
> prev! "start" ignored

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

Reply via email to