lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7152) Refactor lucene-spatial GeoUtils to core
Date Fri, 01 Apr 2016 15:12:25 GMT


Robert Muir commented on LUCENE-7152:

I don't think the current situation is "madness" but you do... okay... yet isn't it self-imposed?
I was always a fan of keeping all our spatial code in one spatial module. Clearly that's simple
for users to grok too.

Because putting all stuff (both 99% case and more esoteric stuff) in a module does not solve
the problem. It means as i just mentioned above, things like expressions have to rely on spatial/
just to do very basic things like make a bounding box.

This is why i think the 99% basic use case should be in core. It keeps things from being a
rat's nest.

> Refactor lucene-spatial GeoUtils to core
> ----------------------------------------
>                 Key: LUCENE-7152
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Nicholas Knize
>         Attachments: LUCENE-7152.patch, LUCENE-7152.patch
> {{GeoUtils}} contains a lot of common spatial mathematics that can be reused across multiple
packages. As discussed in LUCENE-7150 this issue will refactor GeoUtils to a new {{o.a.l.util.geo}}
package in core that can be the home for other reusable spatial utility classes required by
field and query implementations. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message