[
https://issues.apache.org/jira/browse/LUCENE-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521840#comment-16521840
]
Robert Muir commented on LUCENE-8368:
-------------------------------------
eeked out a bit more from the grid by not throwing way "outside query"
knowledge: ~ 5.25M hits/sec on that benchmark. I think removing the binary
search/numeric range stuff is the next step.
> facet by polygon
> ----------------
>
> Key: LUCENE-8368
> URL: https://issues.apache.org/jira/browse/LUCENE-8368
> Project: Lucene - Core
> Issue Type: New Feature
> Components: modules/facet
> Reporter: Robert Muir
> Priority: Major
> Attachments: LUCENE-8368.patch, LUCENE-8368_hacky_grid.patch,
> LUCENE-8368_hacky_grid.patch
>
>
> This can give some nice flexibility if you are working with search results on
> a map. Of course if everything about your use-case is static, its better to
> compute this up-front and index string values, but its not always the case.
> Also it can be helpful if your polygons are changing often, since you don't
> have to reindex.
> Polygon2D already supports multipolygons, but today it only returns a boolean
> value. This patch adds a {{find}} method that returns the polygon that
> actually matched, or -1 if it doesn't match. {{contains}} is then just
> written as {{find >= 0}}.
> Then we can solve the problem with just some sugar over the existing range
> faceting, as each multipolygon is just a range of ids coming back from
> {{find}} that correspond with it. e.g. if you were faceting by country, you
> might have ~200 countries with 100,000 total polygons, and polygons
> 22,000-32,000 correspond to Canada or whatever.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
