You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Adam Fisk (JIRA)" <ji...@apache.org> on 2010/01/22 02:52:54 UTC
[jira] Commented: (CASSANDRA-638) Check SlicePredicate/ColumnParent
Column versus SuperColumn consistency
[ https://issues.apache.org/jira/browse/CASSANDRA-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803571#action_12803571 ]
Adam Fisk commented on CASSANDRA-638:
-------------------------------------
Sorry Jonathan -- got outrageously busy. I can still take a look at this, but I'm really not sure when I'll realistically get to it.
> 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.