*WHy not use UTF8Type or BytesType as default * The CompareWith attribute tells Cassandra how to sort the columns + for slicing operations. For backwards compatibility, the default + is to use AsciiType, which is probably NOT what you want. + Other options are UTF8Type, UUIDType, and LongType. + You can also specify the fully-qualified class name to a class + of your choice implementing org.apache.cassandra.db.marshal.IType. + + if FlushPeriodInMinutes is configured and positive, it will be flushed to disk with that period whether it is dirty or not. This is intended for lightly-used columnfamilies so that they do not prevent commitlog segments from being purged. On Tue, Jul 21, 2009 at 2:27 PM, <[email protected]> wrote:
> thanks jonathantrying this > <ColumnFamily ColumnType="Super" *CompareWith="UTF8Type" *Name="Super1"/> > > > On Tue, Jul 21, 2009 at 2:24 PM, Jonathan Ellis <[email protected]> wrote: > >> On Tue, Jul 21, 2009 at 4:21 PM, Jonathan Ellis<[email protected]> wrote: >> >> does this work in python thrift >> > >> > probably not, given the thrift utf8 bugs. >> >> to correct myself: now that we are using binary data in the thrift api >> it can't screw us over. so yes, UTF8Type should be fine. >> > > > > -- > Bidegg worlds best auction site > http://bidegg.com > -- Bidegg worlds best auction site http://bidegg.com
