On Sun, Apr 10, 2011 at 5:24 PM, Lance Norskog wrote:
> Wait! How can you do distance calculations across different shards
> efficiently?
Basic spatial search (bounding box filter, radius filter, sort by
distance) has no cross-document component, so "it just works" with
distributed search.
-Yon
Wait! How can you do distance calculations across different shards efficiently?
On Thu, Apr 7, 2011 at 7:19 AM, Smiley, David W. wrote:
> I haven't used PostGIS so I can't offer a real comparison. I think if you
> were to try out both, you'd be impressed with Solr's performance/scalability
> th
I haven't used PostGIS so I can't offer a real comparison. I think if you were
to try out both, you'd be impressed with Solr's performance/scalability thanks
in large part to its sharding. But for "functionality richness" in so far as
geospatial is concerned, that's where Solr currently comes s
Have you looked at solr sharding?
Best
Erick
On Thu, Apr 7, 2011 at 2:24 AM, Sean Bigdatafun
wrote:
> Thanks, David.
>
> I am thinking of a scenario that billions of objects, whose indices are too
> big for a single machine to serve the indexing, to serve the querying. Is
> there any sharding me
Thanks, David.
I am thinking of a scenario that billions of objects, whose indices are too
big for a single machine to serve the indexing, to serve the querying. Is
there any sharding mechanism?
Can you give a comparison between solr-based geospatial search and PostGIS
based geospatial search?
Sean,
Geospatial search in Lucene/Solr is of course implemented based on
Lucene's underlying index technology. That technology was originally just
for text but it's been adapted very successfully for numerics and querying
ranges too. The only mature geospatial field type in Solr 3.1 is LatLonTy
