cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Fisk (JIRA)" <j...@apache.org>
Subject [jira] Created: (CASSANDRA-638) Check SlicePredicate/ColumnParent Column versus SuperColumn consistency
Date Thu, 17 Dec 2009 02:17:18 GMT
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.9


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