[jira] [Resolved] (CASSANDRA-5437) multiget specific key filtering

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

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

Aleksey Yeschenko resolved CASSANDRA-5437.
------------------------------------------
    Resolution: Won't Fix

With Thrift deprecated now, closing the ticket.

> multiget specific key filtering
> -------------------------------
>
>                 Key: CASSANDRA-5437
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5437
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Brooke Bryan
>            Priority: Minor
>
> Currently, you are able to specify a list of columns, or a slice when pulling back keys from a multiget, however, we find ourselves pulling back a lot more data than we actually need when columns overlap.  We currently have 2 options (as far as im aware).
> 1. perform multiple get calls, and get the required data back, but connect to thrift more
> 2. perform a multiget, and get more data due to column crossovers, but in a single request.
> Similar to a batch mutation, a batch read would solve this problem perfectly.
> e.g.
> read = [
>   'columnFamily' => [
>     'key' => ColumnPath,
>     'key2' => SlicePredicate,
>     'key3' => ColumnPath
>   ]
> ];
> result = batch_read(read);
> //result
> 'columnFamily' => [
>     'key' => [1 => 'a',2 => 'b',3 => 'c'],
>     'key2' => [4 => 'd',5 => 'e'],
>     'key3' => [1 => 'a',3 => 'c']
>   ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)