[
https://issues.apache.org/jira/browse/SOLR-10038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839852#comment-15839852
]
David Smiley commented on SOLR-10038:
-------------------------------------
After the other things I mentioned, I suggest an experiment in which you use
your largest POLYGON there instead of a MULTIPOLYGON, and see if that improves
anything dramatically.
BTW I linked this issue to SOLR-10039 that will probably help this
dramatically. Although I think I'm going to punt on Polygon/Multipolygon
support for a follow-up issue.
Some people who do polygonal search have use-cases that benefit from doing a
reverse-geocoding lookup at index time such that your points will be indexed
with information on what reference polygons matched. I'm doing this on another
project. The down side is some inflexibility and longer indexing time... but
up side is no complex/slow spatial queries at search time -- it's basically a
lookup.
> Spatial Intersect Very Slow For Large Polygon and Large Index
> -------------------------------------------------------------
>
> Key: SOLR-10038
> URL: https://issues.apache.org/jira/browse/SOLR-10038
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: spatial
> Affects Versions: 6.4.0
> Environment: Linux Ubuntu + Solr 6.4.0
> Reporter: samur araujo
> Assignee: David Smiley
> Labels: spatialsearch
>
> Hi all, I have indexed the entire geonames points (lat/long) with JTS
> enabled, and I am trying return all points (geonameids) within a certain
> polygon (e.g. Netherlands country polygon). This query takes 3 minutes to
> return only 10.000 points. I am using only solr intersect. no facets. no
> extra fitering.
> Is there any configuration that could slow down such a query to less than 300
> ms?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
