[ https://issues.apache.org/jira/browse/CASSANDRA-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001732#comment-13001732 ]
Jonathan Ellis commented on CASSANDRA-2231: ------------------------------------------- bq. if for every index type we want to add, we need to add a new CF, this will quickly become as infeasible (this is inherently why we cannot use 2ndary indexes to begin with) Why? How many indexes are you creating? > Add CompositeType comparer to the comparers provided in > org.apache.cassandra.db.marshal > --------------------------------------------------------------------------------------- > > Key: CASSANDRA-2231 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2231 > Project: Cassandra > Issue Type: Improvement > Components: Contrib > Affects Versions: 0.7.3 > Reporter: Ed Anuff > Priority: Minor > Attachments: 0001-Add-compositeType.patch, > edanuff-CassandraCompositeType-1e253c4.zip > > > CompositeType is a custom comparer that makes it possible to create > comparable composite values out of the basic types that Cassandra currently > supports, such as Long, UUID, etc. This is very useful in both the creation > of custom inverted indexes using columns in a skinny row, where each column > name is a composite value, and also when using Cassandra's built-in secondary > index support, where it can be used to encode the values in the columns that > Cassandra indexes. One scenario for the usage of these is documented here: > http://www.anuff.com/2010/07/secondary-indexes-in-cassandra.html. Source for > contribution is attached and has been previously maintained on github here: > https://github.com/edanuff/CassandraCompositeType -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira