[
https://issues.apache.org/jira/browse/SOLR-10038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848760#comment-15848760
]
David Smiley commented on SOLR-10038:
-------------------------------------
I'm glad to be of help Samur.
Spatial4j is what parses the WKT string. Assuming JTS is used as well, it
constructs a JTS MultiPolygon. However Spatial4j can natively handle
collections of shapes; it's probably much faster. Set {{useJtsMulti}} to false
and I bet this will improve in performance a lot (defined here
https://locationtech.github.io/spatial4j/apidocs/org/locationtech/spatial4j/context/jts/JtsSpatialContextFactory.html
).
> 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
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
