Re: Help on modeling a table

2015-02-02 Thread Asit KAUSHIK
I'll try your recommendations and would update on the same Thanks so much Cheers Asit On Mon, Feb 2, 2015, 9:56 PM Eric Stevens wrote: > Just a minor observation: those field names are extremely long. You store > a copy of every field name with every value with only a couple of > exceptions: >

Re: Help on modeling a table

2015-02-02 Thread Eric Stevens
Just a minor observation: those field names are extremely long. You store a copy of every field name with every value with only a couple of exceptions: http://www.datastax.com/documentation/cassandra/1.2/cassandra/architecture/architecturePlanningUserData_t.html Your partition key column name (lo

Re: Help on modeling a table

2015-02-02 Thread Jan
HI Asit;  The Partition key is only a part of the performance. Recommend reading this article:  Advanced Time Series with Cassandra   |   | |   | |   |   |   |   |   | | Advanced Time Series with CassandraDataStax - Software, support, and training for Apache Cassandra | | | | View on www.datast

Re: Help on modeling a table

2015-02-02 Thread Jack Krupansky
A leading wildcard is one of the slowest things you can do with Lucene, and not a recommended practice, so either accept that it is slow or don't do it. That said, there is a trick you can do with a reverse wildcard filter, but that's an expert-level feature and not recommended for average develop

Help on modeling a table

2015-02-02 Thread Asit KAUSHIK
HI All We are working on a application logging project and this is one of the search tables as below : CREATE TABLE logentries ( logentrytimestamputcguid timeuuid PRIMARY KEY, context text, date_to_hour bigint, durationinseconds float, eventtimestamputc timestamp, ipaddr