[ 
https://issues.apache.org/jira/browse/LUCENE-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559808#comment-14559808
 ] 

Michael McCandless commented on LUCENE-6481:
--------------------------------------------

I made test a bit more evil (use threads, sometimes randomly do poly query), 
but I hit this:

{noformat}
   [junit4] Started J0 PID(12760@localhost).
   [junit4] Suite: org.apache.lucene.search.TestGeoPointQuery
   [junit4] OK      0.04s | TestGeoPointQuery.testBBoxQuery
   [junit4]   2> de maig 26, 2015 3:30:16 PM 
com.carrotsearch.randomizedtesting.RandomizedRunner$QueueUncaughtExceptionsHandler
 uncaughtException
   [junit4]   2> WARNING: Uncaught exception in thread: 
Thread[T0,5,TGRP-TestGeoPointQuery]
   [junit4]   2> java.lang.OutOfMemoryError: Java heap space
   [junit4]   2>        at 
__randomizedtesting.SeedInfo.seed([E57ABD1CCC7F4388]:0)
   [junit4]   2>        at java.util.LinkedList.toArray(LinkedList.java:1050)
   [junit4]   2>        at java.util.List.sort(List.java:477)
   [junit4]   2>        at java.util.Collections.sort(Collections.java:141)
   [junit4]   2>        at 
org.apache.lucene.search.GeoPointInBBoxQuery$GeoBBoxTermsEnum.<init>(GeoPointInBBoxQuery.java:157)
   [junit4]   2>        at 
org.apache.lucene.search.GeoPointInBBoxQuery.getTermsEnum(GeoPointInBBoxQuery.java:86)
   [junit4]   2>        at 
org.apache.lucene.search.MultiTermQuery.getTermsEnum(MultiTermQuery.java:345)
   [junit4]   2>        at 
org.apache.lucene.search.MultiTermQueryConstantScoreWrapper$1.rewrite(MultiTermQueryConstantScoreWrapper.java:146)
   [junit4]   2>        at 
org.apache.lucene.search.MultiTermQueryConstantScoreWrapper$1.scorer(MultiTermQueryConstantScoreWrapper.java:212)
   [junit4]   2>        at 
org.apache.lucene.search.LRUQueryCache$CachingWrapperWeight.scorer(LRUQueryCache.java:585)
   [junit4]   2>        at 
org.apache.lucene.search.Weight.bulkScorer(Weight.java:137)
   [junit4]   2>        at 
org.apache.lucene.search.AssertingWeight.bulkScorer(AssertingWeight.java:72)
   [junit4]   2>        at 
org.apache.lucene.search.AssertingWeight.bulkScorer(AssertingWeight.java:72)
   [junit4]   2>        at 
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:560)
   [junit4]   2>        at 
org.apache.lucene.search.AssertingIndexSearcher.search(AssertingIndexSearcher.java:93)
   [junit4]   2>        at 
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:367)
   [junit4]   2>        at 
org.apache.lucene.search.TestGeoPointQuery$1._run(TestGeoPointQuery.java:337)
   [junit4]   2>        at 
org.apache.lucene.search.TestGeoPointQuery$1.run(TestGeoPointQuery.java:265)
   [junit4]   2> 
   [junit4]   2> NOTE: reproduce with: ant test  -Dtestcase=TestGeoPointQuery 
-Dtests.method=testRandomTiny -Dtests.seed=E57ABD1CCC7F4388 
-Dtests.locale=ca_ES -Dtests.timezone=America/Rankin_Inlet -Dtests.asserts=true 
-Dtests.file.encoding=UTF-8
   [junit4] ERROR   49.3s | TestGeoPointQuery.testRandomTiny <<<
{noformat}

It's curious because the {{testRandomTiny}} only indexes a few 10s of points...

> Improve GeoPointField type to only visit high precision boundary terms 
> -----------------------------------------------------------------------
>
>                 Key: LUCENE-6481
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6481
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/index
>            Reporter: Nicholas Knize
>         Attachments: LUCENE-6481.patch, LUCENE-6481.patch, LUCENE-6481.patch, 
> LUCENE-6481.patch, LUCENE-6481.patch, LUCENE-6481.patch, LUCENE-6481_WIP.patch
>
>
> Current GeoPointField [LUCENE-6450 | 
> https://issues.apache.org/jira/browse/LUCENE-6450] computes a set of ranges 
> along the space-filling curve that represent a provided bounding box.  This 
> determines which terms to visit in the terms dictionary and which to skip. 
> This is suboptimal for large bounding boxes as we may end up visiting all 
> terms (which could be quite large). 
> This incremental improvement is to improve GeoPointField to only visit high 
> precision terms in boundary ranges and use the postings list for ranges that 
> are completely within the target bounding box.
> A separate improvement is to switch over to auto-prefix and build an 
> Automaton representing the bounding box.  That can be tracked in a separate 
> issue.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to