cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2717) duplicate rows returned from SELECT where KEY term is duplicated
Date Mon, 18 Jul 2011 19:59:57 GMT

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

Jonathan Ellis updated CASSANDRA-2717:
--------------------------------------

         Reviewer: xedin
    Fix Version/s: 0.8.2

> duplicate rows returned from SELECT where KEY term is duplicated
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-2717
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2717
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.0 beta 2
>            Reporter: Aaron Morton
>            Assignee: Jim Ancona
>            Priority: Minor
>              Labels: cql, lhf
>             Fix For: 0.8.2
>
>         Attachments: v1-0001-CASSANDRA-2717-Prevent-multiple-KEY-terms-properly-han.txt
>
>
> Noticed while working on CASSANDRA-2268 when random keys generated during a mutli_get
test contain duplicate keys. 
> The thrift multiget_slice() returns only the unique rows because of the map generated
for the result. 
> CQL will return a row for each KEY term in the SELECT. 
> I could make QueryProcessor.getSlice() only create commands for the unique keys if we
wanted to. 
> Not sure it's a bug and it's definitely not something that should come up to often, reporting
it because it's different to the thrift mutli_get operation. 
> Happy to close if it's by design. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message