No. But, it is not recommended to mix default_validation_class and column definitions. If you have a relatively static set of columns, column definitions are recommended.
On Mon, Apr 18, 2011 at 2:23 AM, Sasha Dolgy <sdo...@gmail.com> wrote: > Hi all, > > When defining a new column family, there is the possiblity to define > columns. I see the benefit in defining the columns when I want to > explicitly define that a secondary index will be created on that > column. I also see the benefit of predefining the type of that column > if it will differ from the default for the column family (byte versus > utf8 for example). > > If none of these scenarios are needed, is there any benefit gained by > pre-defining the columns in a CF when creating the column family > initially? > > -sd > > -- > Sasha Dolgy > sasha.do...@gmail.com > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
