I think this one is better… https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjF6eD9hdzLAhWCCj4KHfNwDHoQFggdMAA&url=https%3A%2F%2Fmail-archives.apache.org%2Fmod_mbox%2Fcassandra-user%2F201603.mbox%2F%253CCANeMN%3D-KEiXXgyWLnSYKnhQMWfWmmy3b68PkLsw55CGSm_UmmQ%40mail.gmail.com%253E&usg=AFQjCNGGod8eDERVUbwHe6SVBoOq1y8N7Q&sig2=zzAKcoVlUb2M6YuuNy8AHw
Sean Durity From: K. Lawson [mailto:klawso...@gmail.com] Sent: Friday, March 25, 2016 10:17 AM To: user@cassandra.apache.org Subject: Re: What is the best way to model my time series? Sean, the link you have supplied does not seem to work. On Fri, Mar 25, 2016 at 9:43 AM, <sean_r_dur...@homedepot.com<mailto:sean_r_dur...@homedepot.com>> wrote: You might take a look at this previous conversation on queue-type applications and Cassandra. Generally this is an anti-pattern for a distributed system like Cassandra. https://mail-archives.apache.org/mod_mbox/cassandra-user/201603.mbox/<CANeMN=-keixxgywlnsyknhqmwfwmmy3b68pklsw55cgsm_u...@mail.gmail.com<https://mail-archives.apache.org/mod_mbox/cassandra-user/201603.mbox/%3cCANeMN=-keixxgywlnsyknhqmwfwmmy3b68pklsw55cgsm_u...@mail.gmail.com>> Sean Durity ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
