I've seen this too (your second case) - it seems like the entire row
contents (or some big subset of the row) are loaded to memory on the
server before any column value is returned. The partitioner selection
did not make any difference to performance in my case. I did not find a
way around this e
We looking into migrating from a replicated solr infrastructure to some
form of clustered approach. Lucandra looks fantastic -- but this
statement is troubling:
"No normalizations are stored (no scoring)" from
http://github.com/tjake/Lucandra
When I use the demo/samples get do get a relevance s
It's sort of an interesting problem - in RDBMS one relatively simple
approach would be calculate a rectangle that is X km by Y km with User
1's location at the center. So the rectangle is UserX - 10KmX ,
UserY-10KmY to UserX+10KmX , UserY+10KmY
Then you could query the database for all other us
