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] Resolved: (CASSANDRA-638) Check SlicePredicate/ColumnParent Column versus SuperColumn consistency
Date Mon, 18 Jan 2010 19:26:54 GMT

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

Jonathan Ellis resolved CASSANDRA-638.
--------------------------------------

    Resolution: Incomplete

> Check SlicePredicate/ColumnParent Column versus SuperColumn consistency 
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-638
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-638
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Adam Fisk
>            Priority: Minor
>             Fix For: 0.6
>
>
> This crops up in any call taking both a ColumnParent and a SlicePredicate, as some settings
apply only to Columns while others apply only to SuperColumns.
> For example, it doesn't make sense to call setColumn_names on the SlicePredicate when
the ColumnParent is a ColumnFamily that contains SuperColumns, as the return values will be
SuperColumns, not Columns. The resulting error is currently difficult to decipher (16 byte
UUID required).
> Similarly, I'm not sure what happens if you don't call setColumn_names on the SlicePredicate
in the case where you are querying a ColumnFamily with Columns, although I'm guessing it returns
all column names.
> Just a quick check to make sure the SlicePredicate doesn't have column names set when
the ColumnParent is a SuperColumnFamily, returning a more informative error if so, should
do the trick.

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