>From what I understand, wide rows have quite a bit of overhead, especially
if you are picking columns that are far apart from each other for a given
row.
This post by Aaron Morton was quite good at explaining this issue
http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
-Phil
On Thu, Ju
what version of cassandra are you using. I found a big performance hit
when querying on the secondary index.
I came across this bug in versions prior to 1.1
https://issues.apache.org/jira/browse/CASSANDRA-3545
Hope that helps.
2012/4/25 Jason Tang
> And I found, if I only have the search con
I am currently working on a data model where the purpose is to look up
multiple products for given days of the year. Right now, that model
involves the usage of a super column family. e.g.
"2012-04-12": {
"product_id_1": {
price: 12.44,
tax: 1.00,
fees: 3.00,
},
"product_id_2":
Thanks a bunch.
On Wed, Feb 29, 2012 at 12:51 PM, juri wrote:
> This is a good example.
>
> https://gist.github.com/1847261
>
> I couldn't make it work with DynamicComposite though.
>
>
>
ust fine. Was there
> something in particular you were trying to do?
>
> - Chris
>
> Chris Gerken
>
> chrisger...@mindspring.com
> 512.587.5261
> http://www.linkedin.com/in/chgerken
>
>
>
> On Feb 28, 2012, at 10:25 AM, Philip Shon wrote:
>
> I have not found an
I have not found any examples of utilizing a CompositeType of
DynamicCompositeType as a row key. Is doing this frowned upon? All the
examples I've seen have been using a CompositeType only for Column names
(or values).
My particular use case involves having the two components in the key being
a D
Are there any good resources for best practices when running Cassandra
within EC2? I'm particularly interested in the security issues, when the
servers communicating w/ Cassandra are outside of EC2.
Thanks,
-Phil