tx was looking at http://code.google.com/p/javageomodel/ too
2012/5/14 aaron morton
> So it seems it's not a good idea, to use Cassandra like that?
>
> Right. It's basically a table scan.
>
> Here is some background on the approach simple geo took to using
> Cassandra...
> http://www.readwritewe
> So it seems it's not a good idea, to use Cassandra like that?
Right. It's basically a table scan.
Here is some background on the approach simple geo took to using Cassandra...
http://www.readwriteweb.com/cloud/2011/02/video-simplegeo-cassandra.php
Also PostGis for Postgress seems popular http:
I was thinking of a CF with many many rows with id, type, latitude and
longitude (indexed), and do geolocation queries: type=all and lat < 43 and
lat >42.9 and lon < 7.3 and lon > 7.2
where all rows have type=all
(at least try how Cassandra deals with that)
So it seems it's not a good idea, to use
Inequalities on secondary indices are always done in memory, so without
at least one EQ on another secondary index you will be loading every row
in the database, which with a massive database isn't a good idea. So by
requiring at least one EQ on an index, you hopefully limit the set of
rows tha
Sorry for askign that
but Why is it necessary to always have at least one EQ comparison
[default@Keyspace1] get test where birth_year>1985;
No indexed columns present in index clause with operator EQ
It oblige to have one dummy indexed column, to do this query
[default@Keyspace1] get test wh
