Re: Help on Designing Cassandra table for my usecase

It does sound like that could work for you. From the sample data it doesn't look like tag will be high cardinality (relative to number of rows) so as long as you won't have rows with too many tags (collections are best kept small, but they claim can be in the hundreds but not to exceed 64k) I do

Re: Help on Designing Cassandra table for my usecase

indexes on columns with high cardinality is a general database issue, so it's not unique to cassandra or nosql. On Fri, Jan 10, 2014 at 7:35 AM, Vivek Mishra wrote: > @Naresh > Too many indices or indices with high cardinality should be discouraged > and are always performance issues. A set wil

Re: Help on Designing Cassandra table for my usecase

@vivek thanks for pointing that out..Other than primary key defining only one secondary index tags and in my case same tags will be repeating itself across period for sure for a metric=Sales AND also across metric Sales, Cost also can be same set of tags to some extent not always.. Thanks Naresh

Re: Help on Designing Cassandra table for my usecase

@Naresh Too many indices or indices with high cardinality should be discouraged and are always performance issues. A set will not contain duplicate values. -Vivek On Fri, Jan 10, 2014 at 5:48 PM, Naresh Yadav wrote: > @Thunder > I just came to know about > (CASSANDRA-4511

Re: Help on Designing Cassandra table for my usecase

@Thunder I just came to know about (CASSANDRA-4511) which allows Index on Collections and that will be part of release 2.1. I hope in that case my problem will be solved by changing your designed table with tag column as set and defining seconda

Re: Help on Designing Cassandra table for my usecase

@Thunder thanks for suggesting design but my main problem is indexing/quering dynamic Tag on each row that is main context of each row and most of queries will include that.. As an alternative to cassandra, i tried Apache Blur, in blur table i am able to store exact same data and all queries also

Re: Help on Designing Cassandra table for my usecase

Well I think you have essentially time-series data, which C* should handle well, however I think your "Tag" column is going to cause troubles. C* does have collection columns, but they are not indexable nor usable in WHERE clause. Your example has both the uniqueness of the data (primary key) and q

Re: Help on Designing Cassandra table for my usecase

To my eye that looks something what the traditional analytics systems do. You can check out e.g. Acunu Analytics which uses Cassandra as a backend. Cheers, Hannu 2014/1/9 Naresh Yadav > Hi all, > > I have a use case with huge data which i am not able to design in > cassandra. > > Table name :

Re: Help on Designing Cassandra table for my usecase

@thunder It will be write once 80% of time but there can be cases client makes correction in data and then we need to overwrite that.. Thanks Naresh On Thu, Jan 9, 2014 at 11:49 PM, Naresh Yadav wrote: > @thunder thanks for guidance queries will be fired by application on this > table when

Re: Help on Designing Cassandra table for my usecase

@thunder thanks for guidance queries will be fired by application on this table when users login and browse the application and also through mobile apps through webservice. Response needs to be quick as user will be doing analysis over this data on the fly. Writes also needs to be fast as there is

Re: Help on Designing Cassandra table for my usecase

This sort of work sounds much more like a Hadoop/Hive/Pig type of analysis. What are your latency requirements on queries? Are they ad-hoc or part of an application? What is the case where you would need to change an existing value? If it is write once, then Hadoop/Hive is great, if it changes

Help on Designing Cassandra table for my usecase

Hi all, I have a use case with huge data which i am not able to design in cassandra. Table name : MetricResult Sample Data : Metric=Sales, Time=Month, Period=Jan-10, Tag=U.S.A, Tag=Pen, Value=10 Metric=Sales, Time=Month, Period=Jan-10, Tag=U.S.A, Tag=Pencil, Value=20 Metric=Sales, Time=Mo