Please give more detailed info about what exactly you are worried about or trying to solve.
Please take a step back and look at cassandra's architecture again and what it's trying to solve. It's a distributed database so if you do what you are describing there is a potential of getting hotspots. Which will probably lead in other problems. You might solve one problem but then intriduce another like slow reads or one node getting overloaded. IF you really want to do what you described you can solve it simply by designing your data model in that way. For eg: For User A you can store information for all it's friends. This will lead to duplicate data but will solve your problem. I also suggest run some stress test and worry about the load, performance only if it is a real problem for your kind of data. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Direct-control-over-where-data-is-stored-tp6441048p6442802.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
