forced index creation?

[Sasha Dolgy]

hi, just deployed a new keyspace on 0.7.4 and added the following column family:

create column family applications with comparator=UTF8Type and column_metadata=[
    {column_name: app_name, validation_class: UTF8Type},
    {column_name: app_uri, validation_class: UTF8Type,index_type: KEYS},
    {column_name: app_id, validation_class: UTF8Type}
];

I then proceeded to add two new rows of data to it.  When i try and
query the secondary index on app_uri, my query with phpcassa fails.
on the same CF in a different cluster, it works fine.  when comparing
the CF between clusters, see there's a difference: ---  Built indexes:
--- shows up when i run --> describe keyspace foobar;



      Column Metadata:
        Column Name: app_name (app_name)
          Validation Class: org.apache.cassandra.db.marshal.UTF8Type
        Column Name: app_id (app_id)
          Validation Class: org.apache.cassandra.db.marshal.UTF8Type
        Column Name: app_uri (app_uri)
          Validation Class: org.apache.cassandra.db.marshal.UTF8Type
          Index Type: KEYS

Checking out a bit further:

get applications where 'app_uri' = 'get-test';
-------------------
RowKey: 9d699733-9afe-4a41-83ca-c60d040dacc0


get applications where 'app_id' = '9d699733-9afe-4a41-83ca-c60d040dacc0';
No indexed columns present in index clause with operator EQ

So .. I can see that the secondary indexes are working.

Question 1:  Has "Built indexes" been removed from the "describe
keyspace" output?  Or have i done something ....
Question 2:  Is there a way to force secondary index creation?





-- 
Sasha Dolgy
sasha.do...@gmail.com