On Wed, Mar 13, 2013 at 4:23 AM, Mohan L wrote:
>
>
> On Fri, Mar 8, 2013 at 9:42 PM, aaron morton
> wrote:
>>
>> > 1). create a column family 'cfrawlog' which stores raw log as received.
>> > row key could be 'ddmmhh'(new row is added for each hour or less), each
>> > 'column name' is uuid w
On Fri, Mar 8, 2013 at 9:42 PM, aaron morton wrote:
> > 1). create a column family 'cfrawlog' which stores raw log as received.
> row key could be 'ddmmhh'(new row is added for each hour or less), each
> 'column name' is uuid with 'value' is raw log data. Since we are also going
> to use this
ites will be going to the same node, i.e., the node where the row
> resides. You need to come up with a row key that distributes writes evenly
> across all your C* nodes, e.g., time concatenated with a sequence counter.
>
> From: Mohan L [mailto:l.mohan...@gmail.com]
> Sent: Thurs
counter.
From: Mohan L [mailto:l.mohan...@gmail.com]
Sent: Thursday, March 07, 2013 2:10 PM
To: user@cassandra.apache.org
Subject: data model to store large volume syslog
Dear All,
I am looking Cassandra to store time series data(mostly syslog). The volume of
data is very huge and more entries
