[ https://issues.apache.org/jira/browse/LUCENE-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560985#comment-14560985 ]
ASF subversion and git services commented on LUCENE-6481: --------------------------------------------------------- Commit 1682029 from [~mikemccand] in branch 'dev/branches/LUCENE-6481' [ https://svn.apache.org/r1682029 ] LUCENE-6481: validate lat/lon passed to the queries > 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