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-1566) indexType required for secondary indices and fails silently with out it
Date Fri, 01 Oct 2010 14:09:34 GMT

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

Jonathan Ellis resolved CASSANDRA-1566.
---------------------------------------

    Resolution: Not A Problem

it's optional for a reason: it's valid to want Cassandra to validate values as a specific
type, without also indexing them.

> indexType required for secondary indices and fails silently with out it
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-1566
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1566
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 0.7 beta 2
>            Reporter: Jesse McConnell
>            Priority: Minor
>
> When defining an secondary index on a column family the indexType is required to be set
to KEYS and if you don't set that cassandra will silently fail to add the index
>         for (ColumnDefinition info : metadata.column_metadata.values())
>         {
>             if (info.index_type != null)
>                 addIndex(info);
>         }
> You are able to make it to this code in the ColumnFamilyStore with no warnings (that
I noticed at least) and there ought to at least be an info message here where it indicates
the index is being tossed during creation. 
> Better yet there ought to be protection on the thrift call that requires this option
for the request to be valid or default it to the only option right now of KEYS 
> cheers

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